20. Supplier corrective action and response governance
Connect one contained supplier NCR to an independently issued SCAR, immutable supplier-response revisions, sustained effectiveness and attributable closure without granting Quality custody or supplier-master authority.
Purpose
Connect one contained supplier NCR to an independently issued SCAR, immutable supplier-response revisions, sustained effectiveness and attributable closure without granting Quality custody or supplier-master authority.
Quality Inspector, Supplier Quality Engineer, different QA Head, Buyer and Procurement Manager read-only, Auditor
NCR-E2E-SUP-001 → SCAR-E2E-001 → supplier 8D response R0 rejected → R1 accepted → three-delivery effectiveness evidence → supplier closure ACK-E2E-001.
Before you begin
- The NCR affected object is SUPPLIER, references one registered vendor and has completed containment
- Supplier Quality Engineer and QA Head are separate named users with the NCR site scope and clearance
- At least one ACTIVE, CLEAN controlled evidence version exists at the same site
- Buyer, Procurement Manager and Auditor have read-only Supplier Quality access
SCAR authority boundaries
Only a contained and still-open supplier-linked NCR can start one SCAR. An open, closed or non-supplier NCR is not eligible.
Problem, requested containment, root-cause response, corrective action, due date, supplier routing reference, classification and exact CLEAN evidence are fixed in the draft.
The author/submitter cannot issue. QA records issue date, delivery method and a manual delivery reference. Moduvio does not claim external portal or automated message delivery in this slice.
Every capture is a new version with representative, reference, received/implementation dates, containment, structured root cause, correction, corrective/preventive action and CLEAN evidence.
The SCAR author, submitter and response capturer cannot accept their work. Rejection preserves the version and returns the SCAR to ISSUED for a revised response.
QA verifies the current accepted response with a sustained method, observed result, residual risk and evidence. INEFFECTIVE returns to ISSUED; EFFECTIVE retains a separate closure gate.
Closure requires an EFFECTIVE latest review for the current response plus supplier closure/acknowledgement reference and CLEAN evidence. It does not close the parent NCR; an open SCAR blocks premature parent-NCR closure.
No SCAR route updates vendor AVL/registration/approval, creates an ASN or receipt, or changes current_stock or stock_ledger. Those remain separately governed.
Buyer, Procurement Manager and Auditor can inspect the complete chain but cannot submit, issue, respond, decide, verify or close.
Flow 23 provides a one-scorecard, one-response public evidence boundary but no supplier tenant login or automated delivery/acknowledgement. Commercial recovery and debit/credit remain outside this workflow.
Procedure
- 1
Raise and contain one supplier NCR as Quality Inspector.
- 2
Create the evidence-backed SCAR draft and submit it as Supplier Quality Engineer.
- 3
Independently issue it as QA Head with a manual delivery reference.
- 4
Capture supplier response v1, reject it independently and capture corrected immutable response v2.
- 5
Accept v2 as QA Head, then independently verify sustained effectiveness against CLEAN evidence.
- 6
Close the SCAR with a supplier acknowledgement reference and closure evidence.
- 7
As Buyer, Procurement Manager and Auditor, verify read-only access, two response versions, actor separation, unchanged supplier approval and unchanged inventory.
Expected result
- Lifecycle follows DRAFT → PENDING_ISSUE → ISSUED → RESPONSE_PENDING_APPROVAL → EFFECTIVENESS_VERIFICATION → CLOSED
- Supplier Quality cannot issue, accept, verify or close their own work
- QA cannot author or capture supplier responses by default
- Rejected responses remain immutable and the next capture advances the version
- Effectiveness is tied to the current accepted response
- Open SCAR prevents premature parent-NCR closure; SCAR closure never closes the parent automatically
- Supplier AVL, registration and approval version remain unchanged
- Buyer, Procurement Manager and Auditor mutations are rejected
- Every transition is attributable in audit and outbox history
- SCAR routes never create or mutate current stock or stock-ledger rows