Skip to content
CorrectiveActionReport.comSupplier CAR Response Desk — home

8D Reports

What Is an 8D Report? The Eight Disciplines from the Supplier's Desk

An 8D report is the record of eight disciplines, from forming the team to closing the request. Here is what each one asks of a supplier team answering a customer.

Rovaryn Digital · · 11 min read

When the rejection notice lands and the 8D is due

What is each section of a customer's 8D form really asking for? The question usually comes up under pressure. A rejection arrives with a photo of a bracket with a burr along one edge, a lot number, and a request to respond in the customer's 8D format. The supplier manual sets the response window, and its first step is measured in hours while the later steps run to days or weeks.

The team answering does not need a lecture on quality theory. It needs to know what each section wants, who should fill it in, and what the reader on the customer's side will look for when the form comes back. The form looks like paperwork, but it is a sequence of questions that only make sense in order.

This article walks through the 8D method from the supplier's side of the desk: what the record is, what each discipline from D1 to D8 asks of your team, and how the pieces connect so a response can be signed off and closed.

What an 8D report is, and what it is not

An 8D report is the written record of a team-based problem-solving method with eight disciplines. A customer sends a corrective action request (CAR) or a supplier corrective action request (SCAR); the label depends on the customer, not the industry. You answer by working through the disciplines and documenting each one. The record shows who worked on the problem, what went wrong, and how the customer was protected. It also shows why it happened, what fixes it permanently, how you know the fix holds, and what else you changed. Finally, it shows how the request closed.

The method has a traceable history. Ford developed the 8D process and published it in its 1987 manual "Team Oriented Problem Solving (TOPS)", then added a D0 planning step in the mid-1990s, according to Mind Tools (2025). Some customer formats still include a D0 step and others begin at D1. "8D" is the generic name for the method, and each customer adapts the layout to its own needs.

An 8D record is not three things:

  • Not just a form. The form is the container. The thinking happens on the shop floor, at the whiteboard and in the lab, and the form records it.
  • Not a hunt for someone to blame. The aim is to find how the process allowed the failure and how detection missed it, which means looking at systems more than at the person on the line.
  • Not the same across customers. Field order, labels, required attachments and response windows differ by customer, and they change when a customer revises its manual.

Four terms get mixed up in responses, and mixing them makes a response harder to follow. The burr example shows how they separate:

Term The question it answers Example (burr on a bracket)
Containment How do we protect the customer right now? Sort stock at the plant, in transit and at the customer
Correction How do we deal with the affected parts? Rework or scrap the parts the sort finds
Corrective action How do we remove the cause? Change how die wear is tracked
Prevention Where else could the same cause appear? Apply the change to other dies and part numbers

The eight disciplines, one at a time

Each discipline answers one question. What follows is what each question means for a supplier team and what to write down.

D0: Prepare, where the format includes it

Some formats add a step before D1. Use it to confirm you received the whole request, that the part and lot are yours, and whether the situation needs an emergency response right away. Log the date and time of receipt, because each customer's manual defines when its clocks start.

D1: Form the team

Choose D1 team members to cover both the process that made the part and the process that should have caught the problem. That usually means a team leader (often the Quality Engineer), someone from production who runs the process, someone from engineering or tooling, and someone from inspection or the lab. Add a person who can commit time and money, since D5 and D6 often need both.

Record names, roles and the date the team formed. In a small shop the team may be only three people, so note who else you consulted. Check whether your customer's format asks for a champion or sponsor field.

D2: Describe the problem

Write the problem so that someone who was not there can picture it. The 5W2H questions (who, what, where, when, why, how, how many) are a handy frame. Capture the part number and revision, lot or date codes, quantity affected, where the issue was found, and how it differs from the specification.

Use measurements rather than adjectives. Add an is/is-not comparison: which lots, cavities or shifts show the problem and which do not. Keep D2 to the symptom, and leave the cause for D4.

D3: Interim containment

Containment protects the customer while you work on the cause. Look in every place suspect parts can be: finished goods, work in process, in transit, at the customer's dock, at a sorting service, and at your own sub-suppliers.

Record who sorted, which method they used, how many parts were checked, how many were nonconforming, and the date and time. Containment is not a fix. It buys time. Its window is set in each customer's supplier manual or customer-specific requirements (CSRs), so read the current revision. Keep the containment log, because you will need it again when you decide when containment can stop.

D4: Root cause analysis

Root cause analysis asks two questions. Why did the defect occur? And why was it not detected before shipment, which is the escape? Name both causes in the record.

Two tools do most of the work. Taiichi Ohno, architect of the Toyota Production System, called the five whys the basis of Toyota's scientific approach, as Tulip (2026) notes. The fishbone diagram, also called a cause-and-effect or Ishikawa diagram, sorts possible causes into categories and is one of ASQ's seven basic quality tools. Use the fishbone to widen the search and the 5 Whys to drill down. A cause is credible when you can switch it on and off and the symptom follows.

Here is an illustrative chain for the burr, with an occurrence branch and an escape branch:

Occurrence

  1. Why was there a burr on the edge? The die clearance had opened beyond what the part tolerates.
  2. Why had it opened? The die ran past its planned sharpening point.
  3. Why did it run past it? The hit count is kept on a paper sheet, and the sheet was not updated at shift change.
  4. Why was it not updated? The shift handoff checklist has no line for tool life.
  5. Why is there no line? The checklist predates this die, and nobody owns updating it when tooling changes.

Escape

  1. Why did the burr reach the customer? The final inspection sample did not include that edge.
  2. Why not? The inspection plan checks that edge only at setup.
  3. Why only at setup? Burrs were not a recurring problem on this part, so the plan was not revisited.
  4. Why not revisited? Control plan reviews follow a calendar, and tooling changes do not trigger one.

Five is a guide, not a rule. Stop when the answer points to a system you can change.

D5: Choose and verify the permanent corrective action

Permanent corrective action should address both branches of D4. Compare options on effect, cost and the risk of creating a new problem. Verify the chosen action before full rollout, with a trial run, a pilot lot or measurement, so you hold evidence that it works.

Keep it separate from containment. If the action depends on someone remembering to inspect, it is probably still containment. Write each action as an item with an owner and a due date.

D6: Implement and validate

Put the chosen actions into the process, then collect data on how they perform. Watch output for a period long enough to show the fix holds, given your volume and your customer's expectations. Relax or end containment only against the exit criteria in your customer's manual.

Attach evidence to the discipline it supports: the revised work instruction, the tool-life log, and before-and-after measurements.

D7: Prevent recurrence

Prevention widens the view. Update the process FMEA, control plan, work instructions and training that the cause touched. Then look sideways: the same process on other part numbers, other lines, other plants, and parts you make for other customers.

IATF 16949 audit data points the same way. In IAOB data shown at the 2025 AIAG Quality Summit, sub-clause 10.2.3 f), reviewing and updating documented information, accounted for 40.83% of clause 10.2.3 nonconformances, as reported by simpleQuE (2025). The practical point is that when a fix changes how work is done, the documents describing the work must change too, and someone should own that.

D8: Close the request and recognize the team

D8 closure has two sides, the customer's and your own. The customer accepts the response and closes the request in its own system. Internally, you confirm that every action item is done, evidence is attached, the effectiveness check is dated, and a reviewer other than the author has signed off the final version.

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 customer's CSRs for the exact requirement.

Recognition belongs here too. Thank the team and add a short lessons-learned note. It is how the next response starts faster.

How your customer's requirements shape the 8D format

Clause 10.2.3 of IATF 16949:2016 requires a documented problem-solving process covering containment and interim actions, root cause analysis, and systemic corrective actions. Where a customer has prescribed processes, tools or systems for problem solving, the same clause says you use them unless the customer approves otherwise. Both points are paraphrased from the IATF 16949 Sanctioned Interpretations (Nov 2025). That is why the 8D report format you fill in changes with the customer: field order, labels, required attachments and windows are theirs to set.

Aerospace has its own reference point. 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. Check whether your aerospace customers reference it.

Problem solving is an industry-wide concern. In AIAG's 2015 Quality 2020 study, about 95% of respondents said closing the gap in problem solving would have a moderate to extremely high impact on quality, according to AIAG. AIAG went on to publish its CQI-20 Effective Problem Solving Guide.

Customer portals are part of the picture. They are channels the customer runs and the supplier must use, and the response often has to be entered there. Keep your own copy of the full record, so the portal entry is a transfer of work you have already done.

Two lists for the day a request arrives

Customer manuals are revised over time, so read the response section of the current revision each time. This checklist keeps the reading consistent:

  1. Find the current revision of the manual and its date.
  2. Find when each clock starts, and whether days are calendar or working days.
  3. List each deliverable and its window, such as containment, root cause, corrective action plan, implementation and closure. Names and counts vary.
  4. Note the required format or portal, and whether your own format is accepted.
  5. Note any administrative charge, late-response fee or escalation step, and what triggers it.
  6. Note who to contact (the customer's supplier quality engineer or buyer) and how to ask for an extension.
  7. Note the evidence and record-retention expectations.

Then capture these fields when the request arrives. Doing so turns an email into a record:

  • Customer, request number, and date and time received
  • Part number, revision and description
  • Lot or date codes and quantity affected
  • Where the problem was found
  • Severity or class, as the customer labeled it
  • The customer contact and the channel or portal
  • Each deliverable and its due date, taken from the manual
  • Fee terms stated in the manual, if any
  • Your owner and team
  • A link to the evidence folder

Keeping the 8D record in one place

An 8D is a chain. Each discipline's output is the next one's input, so the record is only as useful as the links between the disciplines.

A clear 8D report is the visible end of that chain, and a supplier-side record is where the chain lives while the work is in progress. Supplier CAR Response Desk is designed for this. Each request becomes its own record with editable per-customer response rules, guided D1–D8 entry with 5 Whys and fishbone fields, and PDF or Excel export in the customer's field order. It is built to work alongside the customer's portal, not instead of it. It records and calculates; it is not advice or certification, and it does not write the analysis for you. The Response Desk is not yet open.

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.