Skip to content
CorrectiveActionReport.comSupplier CAR Response Desk — home

8D Reports

8D vs CAPA: How the Two Fit Together in a Supplier Plant

8D and CAPA get used as synonyms, but they answer different questions. This piece explains the overlap and where a customer's 8D request fits in your own process.

Rovaryn Digital · · 7 min read

A customer 8D request arrives, and your own CAPA log already has a line for it

Which is the real record: the customer's 8D or your own corrective action log? A customer's rejection notice asks for an 8D, and the response window and the format come from its supplier manual. Meanwhile your plant's own corrective action procedure says every nonconformity gets a record, an owner, and an effectiveness check. Two documents now describe the same problem, and someone has to decide how they fit together.

This is where 8D and CAPA get used as synonyms. In casual conversation that is harmless. In a supplier plant it can lead to a customer's form being treated as the whole process. It can also lead to your internal record being sent out in a layout the customer cannot read. Neither is a crisis, but both cost time and leave gaps.

This article explains what each term covers, where they overlap, and how a customer's 8D request sits inside your own corrective action process. It also touches on 8D vs A3 and on what the standards ask, by clause number.

8D vs CAPA: what each one is

CAPA stands for corrective and preventive action. It is a process: how your organization decides that a problem needs action, assigns the work, confirms the action held, and keeps the record. It is an internal system, owned by you, and it applies to problems from many sources, including internal scrap, audit findings and customer complaints.

8D is a method: a structured sequence of eight disciplines for working one problem. Ford developed the approach and published it in its 1987 manual, "Team Oriented Problem Solving (TOPS)", and added a planning step in the mid-1990s, according to Mind Tools (2025). The disciplines run from forming a team and describing the problem, through interim containment and root cause, to permanent corrective action, verification, prevention and closure. Some customer formats add a D0 step for preparation or emergency response.

So the short version is that CAPA is the system and 8D is one way to work inside it. When a customer sends an 8D request, the customer is choosing the method and the format. Your CAPA process still decides how the problem is recorded, owned and verified on your side. For a fuller walk through the method, see the 8D report guide.

Where 8D and CAPA overlap, and where they don't

Both ask you to contain the problem, find the cause, fix it and check that the fix worked. The differences are mostly about who sets the rules and how far the record extends.

Question Customer 8D request Your CAPA process
Who defines the format? The customer, in its supplier manual or customer-specific requirements (CSRs) You, in your own procedure
Who sets the deadlines? The customer, and they vary by customer You, usually tied to severity or risk
What triggers it? A complaint, rejection or finding from that customer Any nonconformity, from any source
How long does it live? Until the customer accepts and closes it Until you verify effectiveness and close it
What does it cover? One problem for one customer Your whole plant, across customers

The last row matters most. A customer 8D sees only that customer's problem. If the same root cause shows up on a second customer's request, the 8D format has no reason to tell you. Your own record is the place where that connection gets made.

How a customer 8D sits inside your corrective action process

In practice the two run in parallel, and the work is done once. A workable sequence looks like this:

  1. Log the request in your own record first. Capture the customer, part, date received, severity and the response window from that customer's current manual.
  2. Start containment right away. Containment is a response to the customer's clock and to your own risk. Track it separately from the later analysis.
  3. Work the analysis in your own record. Root cause, corrective action and verification belong to your process, whatever the customer's form looks like.
  4. Map your record into the customer's format. Field order and labels change. The content should not.
  5. Return the response, then keep your record open. The customer's acceptance is not the same as your effectiveness check. Keep your record open until you have confirmed the action held.
  6. Look sideways before you close. Ask whether the same cause could affect other parts, lines or customers.

Two pieces go deeper on this: permanent corrective action at D5 and verifying that a corrective action worked. The second is where many closed 8Ds are weakest, because the customer's form often closes before your own verification does.

8D vs A3 in a supplier plant

The other comparison readers search for is 8D vs A3. An A3 is a one-page problem-solving format from lean practice, built around a structured story: background, current condition, goal, analysis, countermeasures and follow-up. Teams often use it for internal improvement work, where nobody outside the plant has prescribed a format.

8D is more common when a customer has asked for it, because the customer wants to see containment, root cause and corrective action laid out in a recognizable order. The two are not rivals. Many plants use A3 thinking internally and still deliver an 8D to a customer. What matters is that the analysis behind either one is sound. Root cause tools like 5 Whys and fishbone diagrams work inside both, and neither format fixes weak analysis on its own.

Whatever you use, check the customer's current supplier manual first. If the customer prescribes a method, you generally follow it. If it prescribes nothing, your own process decides.

What the standards ask, by clause number

You do not need the standards' wording here, only where to look.

  • IATF 16949, clause 10.2.3. This is the problem-solving clause. It calls for a documented process 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, you use them unless the customer approves otherwise. That is the reason suppliers answer in each customer's format. See the 10.2.3 problem-solving overview.
  • IATF 16949, clause 10.2.1 and AS9100, clause 10.2. Both cover nonconformity and corrective action, which is your CAPA process in standards language. Check the current standards for the exact requirements.
  • SAE AS13000A. For suppliers whose aerospace customers call it up, SAE AS13000A 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.

Problem solving draws audit attention. At the 2025 AIAG Quality Summit, the IAOB ranked clause 10.2.3 as the top IATF 16949 major nonconformance, according to a simpleQuE summary (2025). That is a description of what auditors found across the industry, not a prediction for any one plant. Confirm exact clause wording with the current standard and your certification body.

A short checklist for reading a customer's response section

Before you build the response, open your customer's current supplier manual and check these items:

  • The response windows for containment, root cause and closure, and whether they run in calendar or working days
  • Whether the manual prescribes a method, a form or a portal
  • Whether fees or chargebacks are tied to the request or to late responses
  • Who at the customer accepts or closes the response
  • What evidence the customer expects to see attached

Windows and fee terms vary by customer and change between manual revisions, so a note from last year's request may be out of date. The supplier corrective action request guide covers the intake step in more detail.

Keeping one record across all your customers

A supplier-side record can hold each request with its analysis, map the response to that customer's layout, and show when the same cause appears on another customer's request. Supplier CAR Response Desk is designed around that idea, as the supplier's own record across customers. It records and calculates; it is not advice or certification, and it is not a CAPA system or a quality management system.

If you want 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.