SCAR Template: What a Good One Contains

A SCAR template is the format the supplier returns when responding to a Supplier Corrective Action Request. The template is also what the customer uses to issue the request. A good template forces the same evidence and the same structure on every response, which is what makes scorecard rollups, repeat analysis, and audit defense possible. See the broader supplier quality guide for the surrounding program.

Why a structured template matters

Free-form supplier responses look fine at low volume and break completely at scale. Without structure, two suppliers responding to identical failure modes will return wildly different documents, which makes it impossible to compare response quality across the supply base. A structured template eliminates that variance and turns SCAR responses into queryable records.

The 8D structure is the most common backbone because most automotive and aerospace OEMs require it. AS9100, IATF 16949, and ISO 13485 supplier programs all accept 8D-aligned SCARs even when not explicitly required.

The required sections

1. Header and traceability block
2. Problem statement (D2)
3. Team (D1)
4. Containment actions (D3)
5. Root cause analysis (D4) — occurrence and detection
6. Permanent corrective actions (D5)
7. Implementation evidence (D6)
8. Prevent recurrence and read-across (D7)
9. Close-out (D8)
10. Effectiveness check

Header and traceability block

The header carries the SCAR number, revision, severity (critical, major, minor), issue date, required response dates for each stage, customer contact, supplier contact, part number and revision, affected lot or serial numbers, source NCR reference, and the customer's required response format. This block is what makes the SCAR queryable in a tracker and what links it to the upstream nonconformance report.

Problem statement (D2)

Written by the customer, not the supplier. What is wrong, where it was found, when it occurred, how many units are affected, and how it was detected. Evidence — photos, measurements, returned samples — should be referenced here, not described.

Containment actions (D3)

Filled in by the supplier. Required content: specific actions, scope (lots, locations, quantities) at the supplier site, at the customer site, and at any sub-tier, plus dates and the evidence (sort reports, quarantine records, stop-ship confirmations). Containment that lists "100% inspection" with no quantity or location is not auditable.

Root cause analysis (D4) — occurrence and detection

The template should require the supplier to name the analysis method (5 Whys, Fishbone, 8D, FTA) and present root cause in two separate fields:

• Occurrence root cause — why the defect was produced.
• Detection root cause — why the supplier's quality controls did not catch it.

Combining the two into one field is the single most common SCAR response weakness. Treating only one means the next variation slips through the same hole. See root cause analysis methods for the techniques.

Corrective actions (D5) and implementation (D6)

One row per action. Each row needs an action description, the root cause it addresses, action type (process, equipment, control, documentation, training), a single named owner, a due date, and the evidence required for closure. At least one action should be an engineering control or poka-yoke; plans consisting only of retraining and procedure updates almost always recur.

D6 evidence — revised work instruction with rev level, updated PFMEA, training records — should be attached to the SCAR, not summarized. The customer's verification step is reading the attached evidence, not re-interviewing the supplier.

Prevent recurrence (D7)

Read-across to similar parts, similar processes, and sister plants. The supplier should explicitly list which other parts were reviewed for the same cause, and what additional actions (if any) were opened. Without read-across, the same defect resurfaces on the next part number with the same process — one of the most common supplier scorecard failure patterns.

Format options

Most customers accept Word, PDF, or their own supplier portal form. Word is the working format because the supplier needs to edit. PDF is the submission format. A portal entry is the same data plus tracking on top. Whatever the wrapper, the underlying section structure should match the 8D backbone so the supplier can reuse the same response across multiple customers.

For the SCAR process itself, see the SCAR process guide. For the surrounding corrective action structure, see the corrective action template guide.