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

The request lands, and the clock is already running
A supplier corrective action request (SCAR) is short. It follows a rejected lot at the customer's incoming inspection, and it names a part number, describes the defect, attaches a few photos of tagged rejects and gives a response due date. Each item is simple to read. Together they start a job that several people must finish in a fixed order, often while the person who handled the last similar request is away and the earlier file is hard to find.
What makes the next few days hard is that the work comes in layers: sort the suspect parts, tell the customer what you have done, find the cause, agree a fix, and return all of it in the layout that customer's system expects. Each layer has its own deadline, and each customer sets those deadlines differently.
This guide walks through a SCAR response from receipt to closure, from the supplier's side of the desk. It covers what to log on day zero, how to read the customer's rules, how to build the analysis, how to get it reviewed internally, and how to keep your own record alongside whatever portal the customer requires.
What a SCAR asks you to deliver
A SCAR is a formal request from a customer asking a supplier to contain a nonconformance, find out why it happened and show what has changed so it does not return. Customers use different names for it: CAR (corrective action request), SCAR, 8D request, problem report. The layout also varies. If you are unsure how a SCAR differs from a CAR, SCAR vs CAR covers the vocabulary. The underlying ask is consistent, though: contain, explain, correct, verify.
Standards give this a shape, though not a form. For automotive suppliers, IATF 16949 clause 10.2.3 calls for a documented problem-solving process. In paraphrase, that process covers containment and interim actions, root cause analysis with the method and results recorded, and systemic corrective actions (IATF 16949:2016 with Sanctioned Interpretations, Nov 2025). The same clause says that where a customer has prescribed problem-solving processes, tools or systems, the organization uses them unless the customer approves otherwise. That is why you answer in each customer's format rather than your own.
In aerospace, SAE AS13000A, "Problem Solving Requirements for Suppliers," defines the process a supplier uses to respond to a customer request for corrective and preventive action. It was issued by the G-22 Aerospace Engine Supplier Quality (AESQ) Committee (SAE International, 2024). Whether a given prime or tier-1 asks you to follow it is written in that customer's own documents. For the aerospace side of root cause work, see aerospace root cause and corrective action.
Two practical points follow. First, the standard tells you what a sound response contains. Your customer's supplier manual and customer-specific requirements (CSRs) tell you when and how to deliver it. Second, those documents are revised over time, so always work from the current revision.
SCAR response step by step
The steps below run in roughly the order they happen, though in practice containment and logging overlap.
Step 1: Log the request on the day it arrives
Before anyone starts sorting parts, create a record. A request that lives only in an inbox depends on whoever happens to be reading it. Capture these fields at minimum:
- Customer name and the customer's request or reference number
- Part number, description and revision
- Defect description in the customer's words, plus any photos or measurements they sent
- Date and time received, and who received it
- Severity or priority level, if the customer assigns one
- Quantity affected, lot or date codes, and where the suspect material is
- Response due dates the notice states, and the portal or email channel the response goes through
- Internal owner and the people on the response team
Writing the due dates from the notice into the record is not the same as knowing the customer's rules. That is the next step.
Step 2: Read the customer's response rules
Open the current revision of that customer's supplier manual or CSRs and find the section on nonconformance or corrective action response. Then check it against the notice itself, since a notice sometimes states its own dates. Use this checklist:
- Which windows exist? Look for separate expectations for containment, for the root cause or plan, and for final closure. Some customers set one date; others set several.
- How is time counted? Hours or days, calendar or working, counted from notice, from receipt or from a portal timestamp.
- What counts as a response? An interim report, a full 8D or a portal form may each satisfy a different deadline.
- Who approves? Some customers close the request after reviewing your response. Others expect you to verify effectiveness first and then report.
- What happens when a response is late? Look for administrative charges, late-response fees, debit memos or scorecard effects, and write down the exact terms in the manual.
- Which format and channel? A customer-specific form, a layout you must follow, or a portal with its own fields.
Counting method alone can shift a deadline. As a worked example with invented round inputs: suppose a manual said a response was due five days after receipt, and the request arrived on a Thursday. The table shows how the count differs.
| Counting method | Day 1 | Day 5 lands on |
|---|---|---|
| Calendar days | Friday | Tuesday |
| Working days (Monday–Friday) | Friday | Thursday of the following week |
The five-day figure is made up to demonstrate the counting only. It is not any customer's rule. Windows vary by customer and change between manual revisions, so check the wording in yours. For more on how requirements differ, see 8D response time customer requirements.
Step 3: Contain the problem
Containment protects the customer and your own shipments while you work out the cause. Start with the suspect parts you can see, then widen the net:
- Quarantine and tag nonconforming material in your plant, in transit and in any outside processing.
- Ask the customer where their affected stock sits, so sorting and replacement can be coordinated.
- Check upstream and downstream: other lots, other part numbers from the same tool or process, and finished goods already shipped.
- Decide what interim check will protect shipments until the permanent fix is verified, such as added inspection or a dedicated gauge.
- Record who did each action, when, and how many pieces were checked and found good or bad.
A simple containment log has one row per action: location, quantity checked, quantity rejected, method, person, date and time. That log becomes evidence for the response and for any later question about what was sorted and when.
Containment is not correction. It stops the problem from reaching the customer again; it does not explain why the problem occurred. Customers generally treat the two as separate deliverables, so keep them separate in your record.
Step 4: Find the cause, occurrence and escape
A SCAR response is judged mostly on its root cause analysis. Customers tend to look for two causes: why the defect was made (occurrence) and why it was not caught (escape, or non-detection). A response that explains only one leaves the question half answered.
Common methods include 5 Whys, fishbone diagrams and is/is-not comparisons. The fishbone, also called a cause-and-effect or Ishikawa diagram, sorts possible causes into categories, and ASQ lists it among its seven basic quality tools. Taiichi Ohno, architect of the Toyota Production System, called the five whys the basis of Toyota's scientific approach (Tulip, 2026).
Here is a generic 5 Whys layout with an occurrence branch and an escape branch, using a burr on a stamped bracket as the example:
Occurrence branch
- Why was the part shipped with a burr? The burr was produced during stamping.
- Why was it produced? The die edge was worn past its useful condition.
- Why was the wear not addressed? Maintenance was scheduled by calendar, not by hits on the die.
- Why was it scheduled that way? The die's maintenance plan was set when volumes were lower and never revisited.
- Why was it never revisited? There is no trigger that reviews tool maintenance when volumes change.
Escape branch
- Why was the burr not caught before shipping? The final check did not include that edge.
- Why not? The inspection instruction listed critical dimensions but not edge condition.
- Why not? Edge condition was not flagged as a characteristic when the control plan was written.
Each answer should be something you can support with evidence, not an assumption. The chain above is a layout example, not a finding about any real process. The cause that matters is the one your own data and your own people can verify.
Industry data shows why this section gets attention. In simpleQuE's analysis of IATF nonconformance data, clause 10.2.3 (problem solving) was the most frequent major nonconformance in IATF 16949 audits, at 10.06% of major nonconformances as of November 25, 2024 (simpleQuE, 2024). That describes what auditors found across the industry. It says nothing about any one supplier's results.
Step 5: Plan and implement the corrective action
Corrective actions should address the causes you identified, not the symptoms. For each cause, write one or more actions, and for each action capture an owner, a due date and a status. Where possible, distinguish:
- Correction: fixing the affected parts.
- Corrective action: changing the process, tool, instruction or control that allowed the occurrence or the escape.
- Prevention: looking for the same weakness in similar parts, lines or other customers' products.
Then decide how you will verify that the fix worked: a defined period of production data, added audits of the changed step, or a confirmed capability check. Say in the response what evidence will show effectiveness and when it will be collected. The 8D report guide walks through each discipline if you want the longer version.
Step 6: Review and sign off internally
Before anything goes to the customer, someone other than the author should read it. A short review checklist helps:
- Does the problem description match the customer's notice?
- Does containment cover all suspect material, with numbers that add up?
- Is there an occurrence cause and an escape cause, each backed by evidence?
- Does every action have an owner and a date?
- Are attachments labeled and legible?
- Does the response use the customer's required format and terms?
Record who reviewed it and when. If the response goes out in interim and final versions, keep both, with a note on what changed. A revision history is useful the first time a customer asks what you reported on a given date.
Step 7: Return the response in the customer's channel and format
Now you deliver. Use the format and channel the customer requires, which might be an emailed form, a spreadsheet layout, a PDF or entry in a portal. If the customer uses a portal, the response goes into the portal, and your own record holds the working copy. The next section covers how the two fit together.
Keep proof of what you sent and when: the confirmation, the exported file or a screenshot of the submission. If the customer replies with questions or asks for a rework, log the question, the date and the revised answer the same way.
Step 8: Verify effectiveness and close
Closure is where many responses stall. The containment is over and the plan was accepted, but the verification data still needs to be collected and reported. Put the verification date in your record when you write the plan, then check it. When the data is in, send the evidence the customer expects and note the closure date and who confirmed it.
After closure, keep the record. IATF 16949 clause 7.5.3.2.1 sets minimum retention for certain quality records, and customers may specify their own periods. Check the clause and your customers' CSRs for the exact requirement.
Keeping your own record alongside the customer's portal
Many customers run their own complaint or problem-solving channel and require suppliers to answer inside it. SupplyOn Problem Solver is one example: an issuer-side tool that follows the 8D method, where the customer runs the process and suppliers respond within it (SupplyOn Support Center). For suppliers that customer's portal is a required channel, and using it is simply part of the job.
A portal usually holds that one customer's requests. If you serve several customers, each has its own portal, its own layout and its own history, and none of them can show you the whole picture. This is where your own record matters. It is the working copy where you:
- log every request in one place, whichever customer sent it;
- track your own response clocks against each customer's rules;
- draft the analysis once, in a consistent structure, before re-entering it field by field in the customer's system;
- keep the evidence, sign-offs and versions together;
- find an earlier request when the same cause shows up for a second customer.
Your record does not replace the portal, and it does not talk to it. You still enter the response in the customer's system. What your record gives you is a first draft and a history that do not depend on any one customer's tool, or on one engineer's inbox.
What a supplier-side record should hold
The usual starting point is a spreadsheet or Word file, sometimes from a free template, and that works for a lot of suppliers. SafetyCulture and mobile2b both publish free 8D and corrective action templates. A general template is not written around a customer-issued automotive or aerospace request, though. A spreadsheet or document also does not start a clock, flag an overdue response or connect history across customers unless someone builds and maintains that by hand. If you want to start with a template, the corrective action report template page is a good place to begin.
Whichever tool you use, a supplier-side record for SCAR work should do these things:
- hold one entry per request, with customer, part, severity and received date;
- apply each customer's own response rules, as editable settings rather than fixed assumptions;
- show what is open, due soon and overdue;
- walk through the eight disciplines with room for 5 Whys and fishbone entries;
- track actions with owner, due date and status, and attach evidence to the discipline it supports;
- keep interim and final versions with revision history and a reviewer sign-off step before export;
- produce an export in the customer's field order, or a generic 8D if none exists.
The Supplier CAR Response Desk is designed around that list. It is built as a web workspace where a supplier logs each CAR, SCAR or 8D request as its own record. Each record runs a containment clock and a plan clock using per-customer rules that you set, and the 24-hour and 10-day defaults the product ships with are editable starting values, not a statement of any customer's rule. Once live, the Response Desk will export PDF or Excel in a customer's field order and offer a copy-friendly field view for re-keying into a customer portal. It records and calculates; it is not advice or certification, and it does not write the analysis or submit anything to a portal. Pricing is one flat price per plant rather than per seat.
Some features are tier-gated. Cross-customer search and repeat-failure flags will be available on Professional and above, as will a fee-exposure view that calculates from the fee terms you enter from your own customer's manual.
Common ways a SCAR response slips
A few patterns show up often enough to watch for:
- The window is read from memory. Someone remembers a customer's deadline from a previous request, but the manual was revised since. Check the current revision each time.
- Containment and corrective action are blended. The response says "100% sort completed" under root cause, and the customer sends it back asking for the cause.
- Only the occurrence is explained. The escape, meaning why inspection did not catch it, is left out.
- Actions have no owner or date. "Review the process" is not an action a customer can verify.
- The record lives in one person's inbox. When that person is out or leaves, the history goes with them.
- The draft is rewritten for each customer. The same cause for two customers gets worded two ways, and nobody notices they are connected.
A calm way to handle all of these is the same: log early, read the rules, keep containment and correction separate, name an owner for every action, and review before you return. For the full picture of how different customers handle the process, see the supplier corrective action request guide.
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 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

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