CAR & SCAR Response
Corrective Action Report Template: Fields Every Supplier Response Needs
Every customer lays out its corrective action report differently, but the underlying fields are similar. This guide lists them and shows how to map one record to each customer's field order.
Rovaryn Digital · · 8 min read

When the same complaint arrives in three different layouts
Three customers can describe much the same complaint and still ask for three different forms. The complaint itself, a burr on a formed part, looks familiar each time. The response forms do not. One puts the containment description in the first block, one puts the part number and revision at the bottom, and a third asks for a "problem statement" where the others say "nonconformance description."
Meanwhile, the facts sit in three places. A supervisor has them in a notebook, the engineer on the first request keeps them in a spreadsheet, and the latest version of the template lives in someone's email. Nobody is sure which file is current.
The facts in these forms overlap a great deal. What changes is the order, the labels and the deadlines. This article lists the fields a corrective action report template should carry, shows how to map one master record to each customer's field order, and explains where a plain document template runs out.
The fields a corrective action report template needs
A usable corrective action report template is a master record first and a customer form second. Capture the fields below once, then reshape them for each customer. The groups follow the eight disciplines of the 8D method, with the request details added at the front.
| Group | Fields to capture |
|---|---|
| Request details | Customer, customer's request number, request type (CAR, SCAR or 8D request), part number and revision, quantity affected, severity or classification, date received, customer contact |
| Response dates | Containment due, plan due, final response due, each taken from that customer's current manual or CSRs (customer-specific requirements) |
| Team and problem (D1–D2) | Team members and roles, problem description, where and when it was found, how it was detected, what the customer measured |
| Containment (D3) | Actions taken, where suspect stock sits (your plant, in transit, at the customer), quantity checked, sort or inspection results, owner, date implemented, how certified stock is identified |
| Root cause (D4) | Occurrence cause, escape cause (why it was not detected), method used, supporting evidence |
| Corrective action (D5–D6) | Permanent action chosen, owner, due date, status, implementation date, verification that it worked, evidence |
| Prevention (D7) | Similar parts, lines and customers checked, documents updated, lessons recorded |
| Closure (D8) | Reviewer, sign-off date, version (interim or final), revision history |
Some customer formats add a D0 step for preparation or emergency response. If yours does, treat it as one more block on the master record rather than a separate template.
Why the response dates belong on the record
Response windows are not part of the form layout. They live in the customer's supplier manual or CSRs, and they differ from customer to customer. Revisions of the same customer's manual can differ too. Your template should have a place for each date and a note of which manual revision you read to get it. Check the current revision of each customer's manual for the exact windows, and do not assume that one customer's rule carries over to the next.
Occurrence and escape belong in separate fields
Many suppliers write one root cause and stop. A cause for why the defect occurred is only half the answer. The other half is why it reached the customer. Give each its own field, and give each its own 5 Whys chain or fishbone sketch. That makes the record easier to read for a customer's supplier quality engineer, and it keeps the corrective action tied to the right cause.
Why customers' layouts differ while the fields stay similar
IATF 16949:2016 clause 10.2.3 asks for a documented problem-solving process. In the IATF's published text with Sanctioned Interpretations (November 2025), that covers containment and interim actions, root cause analysis with its methodology and results, and systemic corrective actions. It also says that where a customer has prescribed processes, tools or systems for problem solving, the organization uses them unless the customer approves otherwise. You can read the IATF 16949 text with Sanctioned Interpretations at IATF Global Oversight.
In practice, that is why you answer in each customer's layout: the customer's tool or form is the one you are expected to use. In aerospace, SAE AS13000A, "Problem Solving Requirements for Suppliers," defines the process a supplier follows when responding to a customer's request for corrective and preventive action. It was issued by the G-22 Aerospace Engine Supplier Quality (AESQ) Committee, and its SAE listing is the place to check its scope. Which customers apply it is for each customer's own documents to say.
So the method is shared, but the layout is the customer's. A good template should make that gap cheap to cross.
How to map one record to each customer's field order
Mapping means changing field order and field labels. It does not mean copying a customer's form design. The steps below work in a spreadsheet, a Word file or any other tool.
- Get the current revision. Download the latest supplier manual or CSR for the customer and find its response section. Note the revision or date.
- List the customer's fields in order. Write down each field label exactly as it appears, in the order it appears.
- Match each one to a master field. Most will map one to one. Some will combine two of your fields, and a few will have no match.
- Flag the gaps. A customer field with no master equivalent needs a new field on your master record. A master field the customer never asks for stays in your record and out of their form.
- Record the dates and any fee terms separately. Windows and administrative or late-response fee terms come from the manual text, not from the form. Store them against the customer, with the revision you read.
- Keep the mapping. Save the match list per customer, so the next request from that customer starts from it rather than from a blank page.
Here is an illustration of what a mapping can look like. The labels are invented for this example and do not represent any real customer's form.
| Master field | Customer A label | Customer B label |
|---|---|---|
| Problem description | Nonconformance description | Problem statement |
| Interim containment | Immediate action | Containment |
| Occurrence cause | Root cause | Why it happened |
| Escape cause | Why not detected | Detection failure |
| Permanent corrective action | Corrective action | Systemic fix |
| Verification of effectiveness | Effectiveness check | Verification |
Keep one master record per request and treat each customer's form as a view of it, not as the place where the work happens.
Treating the form as a view prevents a common failure: edits made in a customer's file that never reach your own history.
Where a Word or Excel template runs out
Free corrective action report templates are easy to find, and a Word or Excel file is a reasonable place to start. They are flexible and cost nothing. Our guide to 8D report templates in Excel covers how to set one up, and the 8D report template hub compares the options.
A general-purpose template, though, is not written for a customer-issued automotive or aerospace request. It will not know that one customer wants the containment description first and another wants it third. A spreadsheet or document also does not start a clock, flag an overdue response, or connect a request to a similar one from another customer unless someone builds and maintains that by hand. That is the gap a record organized per request, per customer clock and per customer format is meant to fill.
If you are still sorting out how a customer corrective action request differs from a supplier one, see SCAR vs CAR. For the response itself from start to finish, the SCAR response guide walks through it.
What a supplier-side record should do
A supplier-side record keeps your own history of every request across all your customers, alongside whatever portal each customer requires. Supplier CAR Response Desk is designed to be that record. It is built to:
- store each request with its customer, part, severity and received date;
- run editable per-customer response rules that start a containment clock and a plan clock, with an overdue state;
- guide the response through D1–D8 with 5 Whys and fishbone entry;
- hold action items with an owner, due date and status, and evidence attached to a discipline;
- keep interim and final versions with revision history and a reviewer sign-off before export;
- map fields to each customer's format, by field order and labels only, and export to PDF or Excel, with a generic 8D layout as a fallback;
- offer a copy-friendly field view, so you can re-key into a customer's portal yourself.
The Response Desk records and calculates; it is not advice or certification. It does not write the analysis, submit to any portal, or reproduce a customer's own form. The root cause stays yours, and the clock windows are editable starting values that you set from each customer's manual.
Start with the fields, then choose the tool
Whatever you use, begin with the master field list above and a mapping for each customer. If you would like to hear when the Response Desk opens, you can join the waitlist.
Put it to work
Compare plans on the pricing page.
Get the next guide
Practical guides for supplier quality teams, delivered straight to your inbox.
Related guides

Answering a Customer Corrective Action Request: The Supplier's Guide
A request arrives, the clock starts, containment goes out, and the 8D is built, signed off and returned. This guide walks the whole job from the supplier's side of the desk, across every customer you answer.
Rovaryn Digital · · 17 min read

SCAR Response: How to Answer a Supplier Corrective Action Request Step by Step
A SCAR response has a rhythm: log, contain, analyze, sign off, return. This guide covers each step and how your own record works alongside the customer's portal.
Rovaryn Digital · · 14 min read

SCAR vs CAR: What the Letters Mean When a Request Lands
Customers use CAR, SCAR and 8D request in overlapping ways. This piece sorts out the general meanings and explains why one consistent log serves all three.
Rovaryn Digital · · 7 min read