NEEDО · SUPPLIER QUALITY

Supplier Corrective Action Request (SCAR): Template and Closure Checklist

A supplier corrective action request (SCAR) is useful when a supplier-related defect or nonconformance needs a documented response, not just a replacement shipment or an informal apology. The request should make the problem reproducible, protect any affected stock or customers, ask for evidence of the cause and corrective action, and define how the buyer will verify that the fix worked. A form alone does not solve the problem: unclear evidence, unverified root causes and closure based only on a promise can allow the same defect to return.

Needo editorial illustration of a defective component, measurement gauge and quality record representing supplier containment, correction and verification

Decide whether the issue needs a formal SCAR

Use your quality procedure, contract and risk assessment to decide when a formal supplier corrective action is required. A one-off administrative correction may need only a documented follow-up. A repeated defect, a product that escaped agreed controls, a significant customer complaint, a traceability failure or a safety- or function-related issue may require a more formal investigation. Your trigger should reflect the product and consequence of failure rather than a universal rule copied from a template.

A SCAR is the request issued by the buyer; an 8D report or another root-cause method may be the supplier's response format if your agreement or quality process accepts it. Confirm the expected format, escalation route and required response timing before issuing the request. If product safety, regulatory reporting or customer notification may be involved, follow the relevant internal procedure and obtain the appropriate specialist review immediately.

Before opening the record

  • Identify the requirement or contract clause that was not met
  • Assess affected stock, open orders, work in progress and prior shipments
  • Check whether containment or customer notification is needed now
  • Confirm the approved SCAR or 8D process and response owner
  • Set priority and deadlines according to risk, contract and internal procedure

Describe the nonconformance so the supplier can reproduce it

Write the observed condition, not a theory about why it happened. Identify the supplier site, part or service, drawing or specification revision, purchase order, receipt or shipment, lot/batch/date code, affected and inspected quantities, date found, detection point and the actual requirement. Attach measurements, photographs, inspection records or customer evidence when available, and label the units and test method. If a value is unknown, mark it unknown rather than estimating it.

A useful problem statement lets the supplier locate the same material, understand the acceptance criterion and check the scope of the issue. For example, state the required dimension and tolerance, the measured range, how many pieces were checked and how many failed. Avoid vague descriptions such as bad quality or careless work. Avoid blaming an operator or naming a root cause before the evidence supports it.

Problem statement fields

  • SCAR number, issue date, issuer and response owner
  • Supplier legal name, site and contact role
  • Part/service, revision, PO, lot, shipment or date code
  • Requirement and source document, including revision
  • Observed condition, measurement or test method
  • Quantity received, quantity checked, quantity affected and current location
  • Photos, reports, samples and evidence references

Contain the risk before investigating the permanent cause

Containment is the immediate action that limits exposure while the cause is investigated. Depending on the situation, it may include identifying suspect stock, stopping dispatch, segregating inventory, checking work in progress, reviewing stock at other sites, adding temporary inspection or notifying the relevant internal team. State who owns each action, the affected scope, the evidence required and the deadline agreed for the issue's severity.

Do not assume that a supplier's promise to inspect is proof that all affected material has been found. Ask for counts, lot identification, disposition, inspection results and the location of suspect stock. If material has already shipped, follow the organization's customer and regulatory escalation process. The exact response time should come from the risk, contract and applicable procedure; no single deadline is right for every defect.

Containment record

  • Affected and potentially affected lots, dates and locations
  • Immediate stop, segregation, screening or other controls
  • Stock and shipment quantities reconciled
  • Owner and response deadline for each containment action
  • Disposition of suspect product: hold, rework, return, scrap or other approved route
  • Evidence that containment is in place and communicated

Ask for a verified cause, including why the defect escaped

A strong supplier response distinguishes the cause of the defect from the reason the existing process did not prevent or detect it. The first explains how the nonconforming condition occurred; the second explains how it passed the control that should have caught it. Depending on the problem, a team may use 5 Whys, a fishbone diagram, process analysis, measurement-system review or an 8D method. Choose a method that fits the issue and require evidence that supports the proposed cause.

Do not accept a phrase such as operator error as the complete explanation without asking what process condition allowed the error and why the control system failed to catch it. A plausible narrative is a hypothesis until the evidence supports it. ASQ's cause-analysis resources describe tools such as fishbone diagrams and Pareto charts; the tool is less important than a problem statement, data and a cause that explains the observed failure.

Root-cause review questions

  • What evidence supports the occurrence cause?
  • Why did the normal process or inspection not detect the issue?
  • Have other lots, parts, shifts, machines or sites been checked for the same condition?
  • Which possible causes were ruled out, and on what evidence?
  • Does the proposed cause explain the timing, pattern and measured defect?
  • What additional test or record would confirm or disprove the hypothesis?

Copy-ready supplier corrective action request template

Adapt this template to your supplier agreement and quality process. Replace every bracket with verified information, remove fields that do not apply and attach the relevant requirement and evidence. Do not include sensitive customer information unless it is necessary and authorized to share.

SCAR request

  • Subject: Supplier Corrective Action Request [SCAR number] — [part/service and concise defect]
  • Supplier/site/contact: [legal name, production site, response owner]
  • Reference: [PO, part number, revision, lot/batch, shipment and date]
  • Requirement: [document, revision, acceptance criterion or agreed service level]
  • Observed nonconformance: [measured or directly observed condition, sample size and affected quantity]
  • Evidence attached: [photos, measurement records, inspection report, customer report or other authorized records]
  • Immediate containment requested: [specific scope, action, owner and due date agreed for the risk]
  • Investigation requested: [occurrence cause, escape/detection cause, evidence and other affected product check]
  • Permanent corrective action: [action linked to each verified cause, responsible owner and target date]
  • Effectiveness verification: [test, inspection, next lots or defined observation period, acceptance criteria and reviewer]
  • Supplier response due: [date agreed under the applicable procedure or contract]
  • Buyer review and closure: [reviewer, required records, open conditions and approval route]

Review the action plan against the cause

A correction fixes the immediate nonconforming item; a corrective action changes the process or control that allowed the cause. Sorting, replacing the affected parts or reminding staff may be necessary, but those actions alone may not prevent recurrence. Ask the supplier to connect each proposed action to a verified cause, name an owner, state when it will be implemented and identify the record or test that will show completion. If several causes were confirmed, check that each one has an action.

Review whether the action creates new risks or changes a controlled process, specification, work instruction, inspection plan, tooling or training requirement. For a material change, involve the appropriate engineering, quality or regulatory owner. Do not dictate a technical fix without understanding the process, but do require the supplier to explain why the proposed action addresses the evidence and how it will be controlled.

Corrective-action plan fields

  • Verified cause and evidence reference
  • Action that directly addresses the cause
  • Owner, planned date and implementation evidence
  • Interim controls while the action is not yet effective
  • Related parts, processes or locations checked for the same risk
  • Required updates to drawings, work instructions, inspection plans or other controlled records

Define effectiveness and closure before accepting the response

A submitted plan is not proof that the problem is resolved. Agree how effectiveness will be checked: for example, specified inspections on defined subsequent lots, a repeat test, a process audit or another measurable check that fits the defect. State the acceptance criterion, sample or observation scope where appropriate, who will review the result and what happens if the issue recurs. The required number of lots or duration should be chosen for the actual risk and process—not copied as a universal rule.

Keep the SCAR open while required evidence is missing or a critical containment action remains unresolved. At closure, record which actions were implemented, the evidence reviewed, the effectiveness result, any residual risk, the approver and the date. If the result is inconclusive, extend the check or escalate according to procedure. Cost recovery, chargebacks and other remedies depend on the actual contract or quality agreement; a SCAR form does not create rights that were never agreed.

Closure checklist

  • Containment scope reconciled and remaining suspect stock dispositioned
  • Occurrence and escape causes supported by evidence
  • Corrective actions implemented and records updated
  • Effectiveness check passed against agreed criteria
  • Read-across to related parts, processes or lots completed where relevant
  • Commercial or customer actions handled under the applicable agreement
  • Quality owner approved closure and recorded the evidence

Worked example: make the request measurable

Illustrative example only: incoming inspection finds that 18 of 240 brackets from one identified lot have hole diameters outside the drawing tolerance. The request should cite the drawing revision, required tolerance, measurement method, actual results, lot number and location of the remaining pieces. The immediate containment plan should account for the supplier's stock, in-transit units, the buyer's stock and any affected work in progress where relevant.

The supplier response should then show how the defect occurred, why the existing inspection did not detect it, which process change addresses the verified cause and what later evidence will demonstrate effectiveness. The example figures are fictional and do not set a universal defect threshold or sampling plan. If the defect affects safety or regulated use, follow the applicable escalation and reporting procedure rather than treating the generic template as sufficient.

The decision trail

  • What failed and against which requirement
  • Which material may be affected and where it is now
  • What protects the next shipment while the cause is investigated
  • What evidence supports the cause and permanent action
  • How the buyer will verify that the issue no longer recurs

Use Needo to prepare a reviewable SCAR

Needo can organize your inspection notes, photos, purchase order and specification into a draft SCAR, identify missing traceability fields, separate observation from hypothesis, prepare questions for the supplier and create an effectiveness checklist. Give it the actual measurements, quantity, lot, requirement and relevant deadlines. Ask it to preserve evidence references, mark unknowns, and adapt the request to your existing procedure and supplier agreement.

Have the quality or procurement owner review the request before issuing it. Needo should not invent a defect measurement, assign blame without evidence, send the request without approval, claim a corrective action worked before the effectiveness check or mark a record closed automatically. The useful output is a clear, evidence-backed request and a closure decision that can be reproduced by another reviewer.

Sources and further reading

  • Graco — Supplier Corrective Action Request

    A manufacturer-published supplier-quality example covering problem description, cause analysis, corrective action, validation and approval. Its specific deadlines and requirements apply to Graco's supplier process, not universally.

  • ASQ — Cause Analysis Tools

    Overview of root-cause tools including fishbone diagrams and Pareto charts that can help structure an evidence-based investigation.

  • ASQ — Supplier Quality

    Supplier-quality resources discussing supplier selection, performance data, process controls and evaluation of corrective-action responses.

  • NIST Manufacturing Extension Partnership — Supply Chain Management

    Official resource on supply-chain risk assessment and supplier development; relevant when a defect review requires dependency or alternative-source assessment.

Sources support the specific points noted above. Confirm current requirements for your product, destination and contract before committing.

Need the actual problem solved?

This guide explains the method. Needo can work from your specific requirement, compare relevant options, verify important details and help move the next step forward.

Start with your exact problem →

Selling or exporting? See live buyer requirements by product · see a sample verified shortlist