Skip to content
CorrectiveActionReport.comSupplier CAR Response Desk — home

CAR & SCAR Response

What Is a Corrective Action Request? A Guide for Shops Without a Quality Manager

In a small shop, the first corrective action request often lands on the operations manager's desk. This guide explains what it is and walks through the first steps in plain terms.

Rovaryn Digital · · 9 min read

The first corrective action request usually lands on whoever answers the email

A first corrective action request is rarely addressed to anyone in particular. It carries a subject line you have not seen before. A tier-1 customer has rejected a lot of parts at incoming inspection, and the message attaches a form with your company name at the top and several empty boxes beneath it. It asks for a response, and it names a date.

In a shop without a dedicated quality manager, nobody has a job title that matches this email. The operations manager reads it, the owner reads it, and the second-shift lead hears about it by evening. Everyone agrees it matters, yet no one is quite sure what a complete answer looks like or how much time there is.

That uncertainty is normal, and it is manageable. A corrective action request is a structured document with a predictable shape. Once you can recognize the parts, the work becomes a short list of decisions made in order.

This guide explains what the request is, what happens after it arrives, and what to do in the first hours. It also covers why the timeline varies so much from one customer to the next.

What is a corrective action request, in plain terms

A corrective action request (CAR) is a formal notice from a customer saying that something you supplied did not meet its requirements. It asks you to find out why and to show what you did about it. When the customer is the one asking its supplier for the response, many shops call it a supplier corrective action request (SCAR). Our guide on SCAR versus CAR covers the naming differences, which are mostly habit and vary by company.

Requests usually ask for the same four things:

  • Containment: what you did right away to keep more bad parts from reaching the customer, and what you did about the suspect parts already shipped or in stock.
  • Root cause: why the problem happened, and why it was not caught before shipment.
  • Corrective action: the permanent change that stops the cause from recurring.
  • Verification: proof that the change worked.

Many customers ask for this in an 8D format. The "8D" label stands for eight disciplines, a structured problem-solving method. The disciplines run from forming a team and describing the problem through containment, root cause, corrective action, verification, prevention and closure. Some formats add a preparation step at the start. Ford published an early version of the method in 1987, and today it is a generic name used across industries.

If your plant is certified to IATF 16949, the standard's clause 10.2.3 requires a documented problem-solving process. Where a customer has prescribed particular tools or formats for problem solving, the standard expects you to use them unless the customer approves otherwise. That is one reason you may answer three customers in three different layouts. Aerospace suppliers will meet a similar idea in SAE AS13000A, which describes the process a supplier follows when responding to a customer's request for corrective and preventive action. Both documents are paraphrased here, so read the originals before relying on them.

A corrective action request is not a lawsuit or an audit finding, and it is not a verdict. It is a request for evidence that you understand the problem and have dealt with it.

What happens when a supplier corrective action request is issued

The sequence is similar across many customers, even though the details differ.

  1. The customer finds a problem. It might be a rejected lot at incoming inspection, a line stoppage, a field return or an audit finding.
  2. The customer issues the request. It goes through email, a customer-run portal or both. The request carries a part number, a description of the problem, a received or issued date and a deadline for response.
  3. A clock starts. Many customers set one window for containment and a later one for the full root cause and corrective action plan. Some use a single date. The exact timing sits in the customer's supplier manual or customer-specific requirements (CSR), not in any general rule.
  4. You respond in stages. An initial or interim response usually covers containment. A fuller response covers root cause and permanent action.
  5. The customer reviews your answer. It may be accepted, returned with questions or sent back for more evidence. Some customers also track repeat issues on a supplier scorecard.
  6. The request closes. Closure typically depends on evidence that the fix held, and that can take weeks of production.

Alongside the technical response, other things can happen on the customer's side: administrative fees, debit memos, or tighter inspection of your shipments. If an invoice deduction has already appeared, why did I get a debit memo explains how those usually connect to the request.

The first hour: what to capture before you do anything else

Before debating root cause, write down the facts of the request while they are fresh. A small shop does not need software for this. A one-page sheet is enough, as long as it is filled in the same way every time.

Capture these fields:

  • Customer name and the name of the person who issued the request
  • The customer's reference number for the request
  • Part number, revision and description
  • Date and time you received the request, and how it arrived (email, portal, phone)
  • The problem as the customer describes it, copied word for word
  • Quantity affected, and where that material currently is: at the customer, in transit, in your stock, on your floor
  • The deadline or deadlines stated on the request
  • A pointer to the section of the customer's manual that governs the response
  • Who owns the response at your end, and who backs that person up

Then do the thing many small shops skip: put the stated deadline on a calendar that more than one person sees. Check whether the customer counts calendar days or working days, and from which date. A window that starts on the issue date can look very different from one that starts when you open the email.

A corrective action request is a sequence of dated commitments. Writing down the dates and the owner in the first hour matters more than a polished answer on day one.

Containment comes first, and it is its own step

The most common early mistake is treating containment as a small part of the final report. Containment is separate work with its own timing, and customers often look for it first. If you want the full picture, what is containment in quality goes through it in detail.

In short, containment answers: where is the suspect material, and what have you done to stop it from reaching the customer? Typical actions include:

  • Quarantining and tagging suspect parts in your own stock
  • Sorting or inspecting finished goods and work in process
  • Asking the customer what it is doing with parts already on its floor
  • Adding a temporary check at the operation where the problem likely started

Containment is not the fix. It buys time while you find the cause. A response that says "we re-inspected everything" and stops there has handled the symptom and has not yet addressed why it occurred.

How long an 8D report takes to complete

Shops often ask how long an 8D takes, and there is no honest single answer. Two things set the pace.

The customer's windows. Each customer states its own timing in its supplier manual or CSRs. Those documents are revised over time, so a window you remember from a previous request may have changed. Check the current revision each time, and ask the customer's supplier quality engineer (SQE) or buyer if the wording is unclear.

The problem itself. A mislabeled box can be contained and explained quickly. A dimensional drift that only appears after a tool has run for weeks can take much longer to understand, and the verification step needs enough production time to show the fix holds.

Because of this, think of an 8D in layers:

Layer What it covers What controls the timing
Initial response Acknowledgment, team, problem description, containment The customer's first window
Root cause and plan Why it happened, why it escaped, what will change The customer's second window and your investigation
Verification and closure Evidence the change worked Production time and the customer's review

If you cannot finish a layer by its date, tell the customer before the date passes. Customers tend to respond better to an early, specific note about what is done and when the rest will follow than to silence.

Reading your customer's manual when nobody has done it before

If this is your first request from a given customer, the manual is the most useful document you have. It may be long, so read only the response section first. Look for:

  • The definition of each type of notice the customer issues, and which ones require a formal response
  • The response windows, how days are counted and what date they start from
  • Any required format or portal for submitting the answer
  • Administrative or late-response fees, if the customer charges them
  • What the customer expects as evidence for closure
  • What happens after repeated or late responses, such as scorecard impact or a formal escalation

Print or save the pages, and note the revision date. If something is unclear, ask in writing. Our supplier corrective action request guide goes deeper on this reading exercise, and the SCAR response guide covers building the response itself.

Resist the urge to rely on what another customer told you, or on a template you found online. General templates are a useful starting point for the thinking, but they were not written for your customer's specific form or timing.

Keeping a record that survives staff changes

The real risk in a small shop is not the first request. It is the fifth, when the person who handled the first four has left or moved to another job, and the history sits in their inbox.

Whatever you use, keep one record per request containing the fields above, the dates, who did what, and the evidence attached. Keep the record in a place others can open, and keep it across customers rather than inside each customer's portal. Portals are channels the customer runs, and you will have to use them, but they show only that customer's requests.

A supplier-side record can hold all of this. Supplier CAR Response Desk is designed to be that workspace: a record per request, with response rules you set from each customer's manual and a guided D1–D8 for the response. The Response Desk is built to record and calculate; it does not give advice or certify anything, and you stay in charge of the analysis and of what you submit.

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.