Supplier corrective action request template

TL;DR

• Use a SCAR to connect one supplier nonconformity to containment, verified causes, corrective actions, implementation, effectiveness, and an authorized buyer closure decision under the vocabulary in ISO 9000:2026.
• Reconcile suspect quantities by location and keep containment, correction, corrective action, occurrence cause, escape cause, implementation evidence, and effectiveness evidence separate.
• Hold closure when traceability, clean point, verified cause, cause-to-action link, controlled-change evidence, monitoring window, criterion, concession, customer response, or justified applicability is incomplete.
• Use the six-tab workbook to reach READY FOR BUYER CLOSURE DECISION, then let the authorized buyer record Close, Return, or Keep open manually.

Use a SCAR for one detected supplier nonconformity

A SCAR is a controlled evidence trail for a detected issue, not a substitute for the agreement, qualification, shipment, or change gate around it. Start with one requirement, actual condition, supplier site, item revision, order, shipment, lot or batch, and detection record. Link the NCR or complaint instead of rewriting it.

Use the supplier change notification guide when a corrective action changes a controlled product, process, site, tool, sub-tier, software, or test method. The SCAR explains the detected failure and response. The SCN controls the proposed change before implementation when the buyer's procedure requires it.

Define the request and reconcile containment by location

The supplier cannot contain an undefined population. Record supplier entity and site, buyer site, part and revision, PO and shipment, supplier lot or batch, serial or heat or date code, requirement revision, measured actual, detection, received quantity, initial sample, nonconforming count, suspect quantity, unit, and every known destination.

Containment controls current exposure. It does not determine cause, correct every affected unit, approve a deviation, or close the SCAR. Normalize one row for Supplier stock, Supplier WIP, In transit, Buyer, and Customer. Mark a location Not applicable only with evidence-based rationale.

Repeat the parent supplier lot or batch, part number, revision, supplier site, and buyer site exactly on every containment row. The row gate rejects a mismatched parent key. A Not applicable row must keep every quantity blank and use Not applicable in the unit and control fields, so no quantity can disappear from the applicable total.

Reconcile two quantity equations

For each applicable location, suspect quantity must equal inspected plus pending quantity. Inspected quantity must equal conforming plus nonconforming quantity. Use one unit across the request and containment rows. A clean point needs both a definition and an evidence reference so later material is not mixed with the affected population.

Keep correction outside the containment total

Sorting can identify conforming and nonconforming pieces. Rework, replacement, scrap, return, or document correction then controls the identified output. Preserve the original result and quantity trail. Do not overwrite a failed unit, lot, or record with its corrected state.

Verify occurrence and escape causes before assigning permanent action

ASQ's 8D overview separates why the problem occurred from why it went unnoticed and says causes should be verified rather than selected from unsupported brainstorming. Use that distinction even when the supplier responds in another approved format.

A 5 Why, fishbone, fault tree, experiment, record reconstruction, or process challenge is a method. It is not evidence by itself. Record the hypothesis, test or evidence reference, observed result, reviewer, date, verification reference, and extent of condition. An operator-error label without a tested process cause remains on Hold.

Join each corrective action to a verified cause

Correction and containment can use a justified Not applicable cause link because they address output and exposure. Corrective and systemic actions cannot. Each must name one verified cause, implementation evidence, verification method, criterion, result, adverse-effect review, and an effectiveness record.

Cross-link controlled changes before implementation

A cause can be correct while the proposed action still creates new risk. If an action changes a controlled element, record the SCN ID and approval or validation evidence. The FDA-hosted MDSAP Audit Approach is a sector-specific example that checks adverse effects and controlled design changes. Use the principle only where the buyer's governing requirements apply.

Test effectiveness after implementation against a defined window

Implementation evidence shows that the action happened. Effectiveness evidence shows whether the planned result was achieved in a defined population and period. Keep those decisions separate. The MDSAP corrective-action procedure is a scoped example that requires documented effectiveness verification and assigns closeout review to a representative or designee rather than the action assignee.

1. Define the metric and preserve its baseline start, end, numerator, denominator, and unit.
2. State the buyer-approved criterion, operator, limit, unit, and evidence basis before judging the result.
3. Define the monitoring start and end dates plus required lots, shipments, sites, shifts, tools, or other exposure.
4. Record the observed numerator, denominator, unit, actual scope, recurrence result, and evidence reference.
5. Use an independent reviewer where the buyer's procedure requires it, after the monitoring window ends.

Zero observed recurrence can meet a stated criterion for a stated window. It does not prove permanent elimination. Do not invent three clean lots, Cpk 1.33, a severity score, or a fixed number of days. Choose the window and metric from the failure mechanism, recurrence opportunity, process cadence, risk, contract, and customer requirements.

Copy the six-tab SCAR workbook

Create six tabs with the exact names below and paste each block into cell A1. Keep the sheet names unchanged because the formulas use cross-sheet references. The workbook contains a fictional completed example with one intentional Hold. Replace every fictional value before using it operationally.

Use exact values and preserve the formulas

• Applicability accepts Applicable or Not applicable. A Not applicable row needs a substantive basis.
• Cause type accepts Occurrence or Escape. Verified status must be Yes for a required cause.
• Action class accepts Correction, Containment, Corrective, or Systemic. Corrective and Systemic rows must link to verified cause and effectiveness IDs.
• Controlled change and recurrence fields accept Yes or No. Change-control Not applicable entries need a substantive basis.
• Use real spreadsheet dates. The starter DATE formulas create numeric dates; format those columns as yyyy-mm-dd after paste.
• The gates require cause verification on or before action implementation, followed by monitoring start, monitoring end, and independent review.
• Record required opportunity count, unit, and scope separately from observed scope and counts; the observed denominator must meet the required count in the same controlled denominator unit.
• Rate formulas and criteria use fraction as the controlled rate unit, while numerator and denominator units must match between baseline and observation.
• The effectiveness reviewer person ID must differ from the linked action-owner person ID, even if either display name changes.
• The final formula in Review_Close!L2 returns only HOLD or READY FOR BUYER CLOSURE DECISION.
• Review_Close!M2 is manual and accepts Pending, Close, Return, or Keep open. The workbook never changes it.

Do not use readiness as product release

ISO 9000:2026 treats release as permission to proceed to the next process stage. SCAR closure, product disposition, supplier status, production approval, shipment authorization, payment, and customer response can be separate decisions. Preserve each authority and reference.

Worked example: one missing independent review reference holds closure

The fixture is fictional and designed to reproduce the workbook logic. Its dates, quantities, rates, names, criteria, and consequences are examples, not benchmarks or recommendations.

Confirm the quantity and cause links

1. Confirm all five Containment location buckets exist and the Customer row has a substantive Not applicable basis.
2. Confirm the four applicable rows total 1,900 suspect, 1,900 inspected, 1,883 conforming, 17 nonconforming, and 0 pending pieces.
3. Confirm OCC-01 and ESC-01 are verified Yes and have separate evidence, reviewer, date, reference, and extent records.
4. Confirm CA-01 links OCC-01 to EFF-01 and SCN-2026-009, while CA-02 links ESC-01 to EFF-02 and SCN-2026-010.

Close the single intended Hold without auto-closing

1. Confirm Effectiveness!AI3 is blank, Effectiveness!AL3 is HOLD, and Review_Close!L2 is HOLD.
2. Enter EFF-REV-017 in Effectiveness!AI3 as the independent review evidence reference.
3. Confirm Effectiveness!AL3 and Review_Close!L2 change to READY FOR BUYER CLOSURE DECISION.
4. Leave Review_Close!M2 as Pending until the authorized buyer reviews the complete evidence and records Close, Return, or Keep open.

Ten supplier corrective action pitfalls

Each consequence is fictional and illustrates workbook control, not a typical result or forecast.

Opening a SCAR without exact product identity

The supplier sorts Rev G while the buyer holds Rev F, leaving a fictional 1,000-piece receipt blocked for four extra days.

Using received quantity as total suspect quantity

Nine hundred pieces at the supplier and in transit remain outside the containment record, and five more nonconforming pieces reach receiving.

Skipping a location because its quantity is zero

A blank Customer row is read as not checked, forcing two teams to spend a fictional six hours proving that no delivery occurred.

Calling a 100 percent sort corrective action

The next 600-piece run repeats the program-transfer failure because the sort controlled output but did not change the cause.

Accepting operator error without evidence

The supplier retrains one operator, but a program handoff fault remains and creates 14 more oversize bores on the next order.

Combining occurrence and escape cause

The machining control is corrected while the inspection export still omits one cavity, delaying buyer review by a fictional three days.

Assigning an action without a cause link

A software update closes on schedule but addresses no verified failure mechanism, so the buyer returns the response for another review cycle.

Implementing a controlled change without SCN evidence

The supplier changes the inspection method before approval, and 400 otherwise acceptable pieces require a new validation and release review.

Reporting zero defects without a denominator

Zero of an unknown population cannot be compared with the criterion, so the closure package remains on Hold for a fictional seven days.

Letting the spreadsheet close the SCAR

A green readiness cell is copied as approval, and a 200-piece shipment moves before the authorized buyer records the closure decision.

Glossary

Supplier corrective action request (SCAR)

A controlled buyer request for a supplier to contain, investigate, correct, and address a specified nonconformity with reviewable evidence.

Nonconformity

Failure to meet a stated requirement.

Containment

Temporary control of current exposure while scope, cause, correction, and permanent action are determined.

Correction

Action that addresses a detected nonconformity in identified output.

Corrective action

Action that addresses verified cause to prevent recurrence.

Occurrence cause

The verified reason the nonconformity happened.

Escape cause

The verified reason detection, inspection, release, or another control did not stop the nonconformity.

Extent of condition

The bounded products, processes, sites, lots, dates, tools, records, or other populations that may share the issue or cause.

Clean point

The defined and evidenced boundary after which product is represented as unaffected by the contained condition.

Implementation verification

Evidence that an agreed action was completed and works as implemented against its verification criterion.

Effectiveness review

A later comparison of defined observed results with a pre-stated criterion over a completed monitoring window.

Concession

Bounded permission to use or release output that does not conform to specified requirements.

Deviation permit

Bounded permission to depart from originally specified requirements before realization.

Release

Permission to proceed to a next process stage, which can remain separate from SCAR closure.

Traceability

The ability to follow an object's history, application, or location through identified records.

SCN

A supplier change notification used to control a proposed change and its approval, evidence, effectivity, and implementation boundary.

Frequently asked questions

These answers are operating guidance. The purchase order, supplier quality agreement, customer requirements, applicable sector rules, and buyer approval matrix govern the real SCAR.