CAR & SCAR Response
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

One Request, Three Different Names
Is a SCAR the same kind of thing as the CAR you answered last month for a different customer, or something heavier? The question comes up in every plant sooner or later, often because one request carries every label at once. The email subject line says "SCAR". The attached form is titled "Corrective Action Request". The customer portal banner calls it an "8D request".
Most of the time, the label matters less than the document behind it. Customers use these terms in overlapping ways, and no single definition governs all of them. What does matter is which clock the request starts, which format the customer expects back, and whether the request ends up in your own records.
This article sorts out what the letters usually mean in the scar vs car question and where usage differs. It also shows how to keep one consistent log across every customer, so the label on the email never decides how carefully you record the request.
What CAR Usually Means
CAR most often stands for corrective action request. You will also see "corrective action report", and the two get swapped constantly. A useful way to separate them is that the request is the ask and the report is the response document. In daily practice, people use both words for either one.
In general use, a CAR asks someone to investigate a nonconformance, find out why it happened, and put a fix in place. The term is broad. It can describe an internal request raised from your own audit or a line problem. It can also describe a request that arrives from a customer.
That breadth is the source of most confusion. When someone says "we got a CAR", you cannot tell from the word alone who issued it or how formal it is. If you want the longer definition, the guide on what a corrective action request is covers it in detail.
SCAR vs CAR: What the S Adds
The S stands for supplier. A supplier corrective action request is a request a customer sends to a supplier, asking it to respond to a problem with the parts or service it provided. The difference between a SCAR and a CAR is mainly direction. A CAR can point anywhere, while a SCAR points at the supplier receiving it.
From your side of the desk, that makes the distinction less sharp than it looks. If a customer sends you a request about your product, you are the supplier answering it, whatever the customer calls it. Some customers say CAR for everything they issue and never use the word SCAR. Others reserve SCAR for a formal, higher-severity request and use CAR or another term for lesser ones.
Whether a customer draws that line is a fact about that customer. Do not assume it from general usage. The only reliable source is the definitions or glossary section of that customer's current supplier manual.
Where the 8D Request Fits
8D is a method, not a document type. It organizes a response into eight disciplines: team, problem description, interim containment, root cause, permanent corrective action, implementation and verification, prevention, and closure. Ford developed the process and published it in its 1987 manual on team-oriented problem solving, according to Mind Tools (2025). That is history, and the method has since spread well beyond one company.
So an "8D request" usually means the customer wants your response structured through those disciplines. It does not tell you how severe the problem is or how fast you must answer. A SCAR can ask for an 8D response. A CAR can too. The 8D report guide walks through each discipline.
Two standards explain why customers care about format. In automotive, clause 10.2.3 of IATF 16949:2016 says that where a customer has prescribed processes, tools or systems for problem solving, the organization uses them unless the customer approves otherwise, per the IATF Global Oversight publication of the standard with Sanctioned Interpretations (November 2025). In aerospace, SAE AS13000A (2024) defines the process a supplier uses to respond to a customer request for corrective and preventive action.
Here is a quick comparison of how the terms are commonly used.
| Term | What it usually refers to | What to check in the customer's manual |
|---|---|---|
| CAR | A request to investigate and correct a nonconformance; may be internal or customer-issued | Whether the customer uses it for external requests at all |
| SCAR | A customer-issued request directed at a supplier | Whether it signals a formal or severe level |
| 8D request | A request for a response structured through the eight disciplines | Which format, field order and sign-off the customer expects |
Why Your Customer's Manual Is the Authority
The meaning of a term, the severity levels behind it, the response windows and any fees all live in each customer's supplier manual and customer-specific requirements (CSRs). Those documents are revised over time, so the version you read last year may not be the version in force today. Check the current revision rather than relying on memory or on what another customer does.
When you open a manual, a short checklist keeps the reading consistent:
- Find the definitions or glossary section and note every term the customer uses for a request it sends you.
- Note whether the manual distinguishes levels or severities, and what triggers each.
- Find where the response windows are stated and whether they run in calendar or working days.
- Note what response format is required, and whether a portal is mandatory.
- Find any administrative or late-response terms, and how they are triggered.
- Record the manual's revision and date alongside your notes.
If anything is unclear, ask the customer's supplier quality engineer (SQE) or buyer, and keep the answer in writing.
A word about forms. Free corrective action request forms and supplier corrective action report templates are easy to find. A general template can help you think through what a response needs, but it was not written for your customer's request. When a customer has its own form or portal, that customer's format governs. The corrective action report template article goes into what a generic template can and cannot do. The same caution applies to any supplier corrective action request template: use it as a reference, not as the document you send back.
One Log for All Three
The practical answer to SCAR vs CAR is to stop letting the label sort your work. Whatever the customer calls it, the same few facts decide how you manage it. Capture these when any request arrives:
- Customer name and the request number exactly as the customer wrote it
- The label the customer used (CAR, SCAR, 8D request or something else)
- Part number, quantity and a one-line description of the problem
- Severity or level, if the customer assigns one
- Date and time received
- Containment due and response due, taken from that customer's current manual
- Owner, current status and where the customer's portal or form lives
- Required response format
Keep the customer's label as written, and add your own neutral category beside it, such as "customer-issued request". That way, a customer who changes terminology between manual revisions does not break your history. It also lets you search across customers later and notice when the same cause appears on a second request.
The guides on responding to a SCAR and on the broader supplier corrective action request cover what to do once the request is logged.
Where a Supplier-Side Record Can Help
A supplier-side record can hold all of this in one place. Supplier CAR Response Desk is designed to keep each request as its own record, with editable response rules set per customer and a guided D1–D8 workspace. It is built to record and calculate. It does not give advice or certify anything, and it is not yet open to the public.
If you would like to hear when it 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

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