Supplier Corrective Action Report (SCAR) — Complete Guide

How to write effective supplier corrective action reports. SCAR vs 8D explained, response deadlines, evidence requirements, and free SCAR template from 8D.wiki.

Browse our complete knowledge base for in-depth articles on this topic, or use the free AI 8D report generator to create professional IATF 16949 compliant reports.

Free AI 8D Report Generator: Generate professional IATF 16949 compliant 8D reports from your problem description. Includes AI-powered 5-Why and fishbone analysis. No registration required. Start generating →

8D.wiki

Supplier Corrective Action Report (SCAR) — Complete Guide for SQE Teams

What Is a SCAR?

A Supplier Corrective Action Report (SCAR) is a formal document sent by a customer to a supplier when a nonconformity is detected. It requires the supplier to:

  • Investigate root causes
  • Implement corrective actions
  • Provide evidence of effectiveness
  • Most OEMs require suppliers to respond using the 8D methodology format.

    SCAR vs 8D

    **SCAR** = The REQUEST document sent TO the supplier

    **8D** = The RESPONSE document sent BY the supplier

    They are complementary: you issue a SCAR, the supplier responds with an 8D.

    When to Issue a SCAR

    Issue a SCAR when:

  • Recurring defect (same part, same defect, 2+ occurrences)
  • Safety or regulatory nonconformity
  • Customer line stoppage caused by supplier defect
  • Supplier fails to meet PPAP requirements
  • Significant PPM spike (statistically out of control)
  • Do NOT issue a SCAR for:

  • One-time, isolated incident with clear cause and fix
  • Issues resolved during regular supplier communication
  • Cosmetic issues below specification threshold
  • SCAR Response Requirements

    A complete SCAR response should include:

    1. **D1 — Team**: Cross-functional team members with names and roles

    2. **D2 — Problem Description**: 5W2H with objective evidence (photos, data, dates, lot numbers)

    3. **D3 — Containment**: Actions taken, quantities, dates, clean point

    4. **D4 — Root Cause**: 5-Why and fishbone with TRC, MRC, and escape point

    5. **D5-D6 — Corrective Actions**: Permanent fixes with implementation dates and verification data

    6. **D7 — Prevention**: System changes, FMEA updates, horizontal deployment

    7. **D8 — Verification**: Evidence package (photos, data, capability studies)

    Timeline Expectations

    Common SCAR Mistakes

    1. **Vague problem descriptions** — "Quality issue with Part X" is unacceptable. Be specific: "0.5mm burr on Part X P3 edge, Lot#A938, detected at customer incoming inspection"

    2. **Accepting "operator retrained" as D6** — retraining is not a permanent corrective action

    3. **No verification data** — "Implemented" without capability study data is not verified

    4. **Supplier ghosting** — no response after initial acknowledgment

    Key Takeaways

    1. SCAR is the request, 8D is the response

    2. Be specific in problem descriptions — data beats adjectives

    3. Set clear deadlines and escalate promptly when missed

    4. Retraining alone is never a valid permanent corrective action

    5. When a supplier's 8D blames "operator error", push back — ask what system failed