Supplier corrective action
Draft a supplier corrective-action request (SCAR) from a contained supplier NCR, capture a versioned response, and independently decide, verify and close the supplier action.
Screen orientation
Reading requires supplier_quality:read within site scope and clearance. Drafting/submission uses :write; issue, response capture, response approval, verification and closure use :issue, :respond, :approve, :verify and :close respectively. These suffixes belong to supplier_quality. Buttons depend on permission and current state; the server also enforces named-user independence. Procurement and Audit are readers, not SCAR decision-makers.
Six summary cards show open, pending issue, supplier response, overdue, response decision and verification work. Draft SCAR opens an inline creation form. Each supplier-action register card shows the parent NCR, supplier, author, issue and current response; its available action opens a form below the register.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Contained supplier NCR | Select | Required to draft; no existing SCAR may be linked. | Select an open supplier-linked NCR already at containment or a later pre-closure stage. The supplier and affected reference come from that NCR, not a separately editable vendor choice. | Links the request to the exact supplier problem; it creates no containment hold. |
| SCAR title | Text | Required; at least 10 characters. | Review the title populated from the NCR and name the requested supplier action clearly. | Labels the immutable draft and register card. |
| Supplier contact / routing reference | Text | Required. | Record the intended contact or controlled routing reference, not an assumption that an invitation has been sent. | Retains routing context only. |
| Response due date | Date | Required; not in the past when drafting. | Set the requested response deadline. At issue, this deadline cannot precede Issued on. | Drives due/overdue visibility, not automatic escalation or delivery. |
| Classification | Select | Required; subject to source classification and your clearance. | Use the appropriate handling classification. The server will not lower the linked sources' classification merely because a lower value was selected. | Scopes the SCAR and its evidence. |
| Problem statement | Multiline text | Required; at least 20 characters. | Describe the objective supplier problem and its affected scope, separately from the requested remedy. | Freezes the issue being sent for supplier action. |
| Requested containment / Requested root-cause response / Requested corrective action | Three multiline text controls | Each required; at least 20 characters each. | Specify immediate containment expectations, the investigation needed and the required corrective response separately. Describing containment here does not execute it. | Defines the supplier's response obligations. |
| SCAR issue-package evidence | Controlled evidence select | Required when creating the draft. | Select one CLEAN immutable version from an active document at the NCR site; use Manage evidence if it is missing. The server checks classification as well. | Pins the exact issue-package evidence; a typed delivery reference cannot replace it. |
| Submission note | Multiline text | Required to submit; at least 20 characters. | Explain why the draft is ready for independent issue. The author submits; the server also permits a tenant-admin submission exception. | Moves DRAFT to PENDING_ISSUE. |
| Issued on / Delivery method / Delivery reference | Date, select and text | All required for independent issue; date cannot be future or later than the response deadline. | Capture the actual issue date and EMAIL, PORTAL, LETTER or OTHER delivery reference. These are records of delivery, not send controls. | Records how the independently issued SCAR was routed; no message is sent by this action. |
| Independent issue note | Multiline text | Required; at least 20 characters. | Record the QA issue rationale. The SCAR author or submitter cannot independently issue the same request. | Makes the issue decision attributable. |
| Supplier response reference / Supplier representative | Two text controls | Both required when capturing a response. | Identify the exact response received and its supplier representative; the signed-in capturer remains a separate internal actor. | Identifies the next immutable response version. |
| Received on / Implementation date | Two dates | Required; received date cannot be future and implementation cannot be later than receipt. | Use completed dates supported by the response, not a forecast implementation date. | Records receipt and implemented-action timing. |
| Root-cause method / Root cause / Contributing factors | Select and multiline text | Method required; root cause at least 20 characters; contributing factors at least 10. | Select FIVE_WHY, FISHBONE, FAULT_TREE, EIGHT_D or OTHER and retain the supplier's causal findings and contributing conditions separately. | Stores the supplier analysis for independent acceptance. |
| Supplier containment / Correction / Corrective action | Three multiline text controls | Each required; at least 20 characters each. | Capture what contained the issue, corrected the immediate defect and addressed recurrence. Do not substitute a generic completion statement for all three. | Records supplier assertions, not a stock transaction or verified effectiveness. |
| Preventive action (optional) | Multiline text | Optional; if supplied, at least 20 characters. | Use only a genuine documented preventive action when applicable. Leaving the field blank omits it cleanly from the controlled response. | Retains a preventive-action statement when supplied; it is not evidence of acceptance. |
| Supplier response evidence | Controlled evidence select | Required for response capture. | Select the exact CLEAN same-site response document version, within the SCAR classification. The independent issuer cannot capture this response. | Binds evidence to the new response version and sends it for approval. |
| Decision / Independent QA decision note | Select and multiline text | ACCEPT or REJECT and a note of at least 20 characters are required. | Decide the current pending response. The author, submitter and response capturer cannot make this decision. | ACCEPT starts effectiveness verification; REJECT returns the SCAR to ISSUED for a new response version. |
| Outcome / Residual risk | Two selects | Required at verification; EFFECTIVE cannot retain UNACCEPTABLE risk. | Choose EFFECTIVE or INEFFECTIVE and ACCEPTABLE, MONITOR or UNACCEPTABLE risk on the basis of sustained results. | An ineffective review returns the request to ISSUED; effective verification enables closure review. |
| Independent verification method / Observed sustained result | Two multiline text controls | Each required; at least 20 characters each. | Describe how effectiveness was independently tested and what was actually observed, not merely whether a response was received. | Records the verification basis against the current accepted response. |
| Effectiveness evidence | Controlled evidence select | Required for verification. | Select a CLEAN same-site version that supports the observed result within the SCAR classification. | Pins effectiveness evidence without replacing the supplier response. |
| Closure summary / Supplier closure / acknowledgement reference | Multiline text and text | Both required; summary at least 20 characters. | Summarise the effective action and record the supplier acknowledgement reference. Closure requires the latest review for the current accepted response to be effective with ACCEPTABLE or MONITOR risk. | Closes this supplier action only. |
| SCAR closure evidence | Controlled evidence select | Required for closure. | Select the CLEAN same-site closure package. The SCAR author, submitter and response capturer cannot verify or close their own supplier action. | Retains exact closure evidence and the independent closing actor. |
Actions and effects
When to use: After the supplier NCR is contained and the issue package is complete.
What it does: Creates DRAFT, then submits to PENDING_ISSUE. This page provides no in-place editor for a saved draft.
When to use: By permitted QA independent of the author and submitter, at PENDING_ISSUE.
What it does: Records delivery references and sets ISSUED; it does not send email or open a supplier portal.
When to use: Capture at ISSUED, then independently decide the current pending response.
What it does: Adds an immutable response version. Rejection retains that version and permits another; acceptance proceeds to effectiveness, not immediate closure.
When to use: After acceptance, then after a qualifying latest effective review.
What it does: Records independent verification and closure with evidence. The same independent QA actor may decide, verify and close; the author, submitter and response capturer remain excluded.
Lists and states
- Supplier-action register: SCAR number, classification, status, response deadline, site, supplier and parent NCR identify the exact request; a closed SCAR does not imply a closed NCR.
- Current response and expandable details show the latest response version, status, capturer, representative, root cause, corrective action and latest effectiveness. Older immutable versions are retained by the system, but this screen is not a full response-history editor.
- The lifecycle strip marks the current stage; rejection or ineffective verification can return the request to an earlier stage without erasing prior evidence.
Authority boundary
SCAR closure does not close the parent NCR, approve or suspend the supplier, create or release a hold, or post inventory. Delivery and acknowledgement fields capture references only; they are not external-message authority.