Guide
SCAR Response Best Practices
How to write supplier corrective action responses that pass first-submission review. Avoid common rejection triggers and demonstrate a systematic approach to problem resolution.
What Is a SCAR?
A Supplier Corrective Action Request (SCAR) is a formal document issued by a customer to a supplier when a quality nonconformance is identified. It requires the supplier to investigate the root cause, implement corrective actions, and provide evidence that the problem has been resolved and will not recur.
SCARs are triggered by incoming inspection failures, in-process defects traced to supplier material, field returns, audit findings, or customer complaints. The expected response format is typically an 8D report, though some customers use their own templates (CAPA, CAR, NCR response forms). The underlying methodology is the same.
Response Timelines
Missing deadlines is one of the most common reasons for supplier scorecard downgrades. Most customers expect responses within specific windows:
| Milestone | Typical Deadline | What's Expected |
|---|---|---|
| Acknowledgment | 24–48 hours | Confirm receipt, assign team leader |
| Containment | 48–72 hours | Interim actions to protect the customer |
| D1–D4 (Investigation) | 5–10 business days | Team, problem description, root cause |
| D5–D7 (Corrective action) | 15–30 business days | Permanent fixes implemented and verified |
| D8 (Closure) | 30–45 business days | Full report with effectiveness data |
Timelines vary by customer and severity. Check the SCAR for specific deadlines.
Top 10 Rejection Triggers
Quality engineers reviewing SCAR responses look for evidence of systematic problem-solving. These are the most common reasons responses are rejected on first submission:
- “Operator error” as root cause. This tells the customer nothing about why the system allowed it. Always ask: why did the process allow the error to occur? What was missing from training, work instructions, error-proofing, or inspection?
- “Retrain operator” as sole corrective action. Training alone rarely prevents recurrence. Pair it with process changes, error-proofing, or inspection improvements.
- No containment evidence. Stating you “will sort” is not containment. Provide evidence: how many units sorted, where (supplier, in-transit, customer), results of the sort, disposition of nonconforming units.
- Vague problem description. “Parts were out of spec” doesn't tell the reviewer what was wrong. Specify the defect, the spec, the measurement, and the deviation.
- Root cause doesn't explain the defect. If the root cause is “tool wear,” explain why tool wear was not detected before it produced nonconforming parts. What monitoring or change interval failed?
- Corrective actions with no owner or due date. Every action must have a named owner (not a department) and a specific completion date.
- No verification data. Post-implementation inspection results, capability data, or test reports must demonstrate the corrective actions are effective.
- No systemic prevention (D7). Fixing one part number is not enough. Show that FMEA, control plans, or work instructions were updated to prevent similar issues on other products.
- Copy-paste from previous 8D. Reviewers notice generic language. Every response must be specific to the problem at hand.
- Missing dates and timelines. When were containment actions taken? When were corrective actions implemented? Customers need to see a timeline of response.
Evidence Requirements
A strong SCAR response is backed by objective evidence. Assertions without evidence are the primary reason for rejection. Include:
Containment
Sort records, quarantine tags, inspection results, rework documentation, replacement shipment tracking
Root Cause
5-Why worksheets, fishbone diagrams, process data, measurement records, photos of the defect and the process
Corrective Action
Updated work instructions (redlined), tooling change orders, photos of error-proofing devices, training records with sign-off
Verification
Post-implementation inspection data, Cpk studies, first article inspection reports, customer quality feedback
Prevention
Updated FMEA (before/after RPN), revised control plan, lessons-learned distribution list
Closure
Effectiveness check results (30/60/90 day), customer acceptance or close-out confirmation
Writing Effective Narratives
Be specific. Replace “the operator did not follow the procedure” with “on 2024-03-15, Operator B on 2nd shift skipped step 4.2 (torque verification) of WI-2847 Rev C because the torque wrench was unavailable due to calibration.”
Use data. Replace “we improved our process” with “defect rate decreased from 2.3% (n=500, pre-action) to 0.0% (n=1200, post-action, 30-day window).”
Show cause-and-effect. Explicitly link each corrective action to the root cause it addresses. Reviewers should be able to trace: defect → root cause → corrective action → verification result.
Use professional tone. Avoid blame language. Focus on what the system allowed and what systemic changes prevent it. The 8D is about process improvement, not personnel action.
Customer-Specific Requirements
Different customers and industries have specific requirements beyond the standard 8D format:
Automotive (IATF 16949): Expect PFMEA and Control Plan updates in D7. May require Cpk data as verification evidence. Some OEMs (GM, Ford, Toyota) have proprietary SCAR portals and formats.
Aerospace (AS9100): Require full traceability to lot/serial numbers. Root cause must address the Quality Management System, not just the product. Expect references to AS13000 (problem-solving requirements).
Medical Device (ISO 13485): Regulatory implications must be assessed. May trigger CAPA, field safety corrective action, or regulatory notification. Document risk assessment per ISO 14971.
General Manufacturing: Focus on the basics — clear root cause, actionable corrective actions, and evidence. Most rejections are for vagueness, not format violations.
Stop getting SCAR responses rejected
8D Pack includes 30+ built-in lint rules that catch weak root cause language, missing evidence, and other rejection triggers before you submit.
Start Free Trial14 days free / no credit card