An 8D report is a structured problem-solving record used mostly for customer and supplier quality problems. It moves through eight disciplines, D1 to D8, with a D0 preparation step added later: form a team, describe the problem, contain it, find and verify the root cause and the escape point, choose and verify the fix, implement it, prevent recurrence, and close. Below is a filled-in example for a supplier part that reached a customer, the template as a CSV, and the reasons customers reject weak 8Ds.
- D3 containment protects the customer now; D4 to D7 remove the cause. Do not skip D3 to get to the fix.
- D4 has two answers: why the defect happened and why it was not caught.
- Every root cause and every fix needs evidence: data, a test, or a reproduction.
- Keep the 8D with the NCRs and test results it refers to, under one ID.
What is an 8D report?
8D, short for eight disciplines, is a team-based method for solving a recurring or serious quality problem and documenting it. According to the Wikipedia summary, it "is a method or model developed at Ford Motor Company used to approach and to resolve problems", described in Ford's manual "Team Oriented Problem Solving (TOPS), first published in 1987", and "8Ds has become a standard in the automotive" industry and others. The same summary notes that "it was later augmented by an initial planning stage", which is why most forms now start at D0 (Wikipedia).
Customers usually ask for an 8D when a defect reaches them. Regulated manufacturers need an equivalent anyway: FAA production approval holders must have procedures for "identifying, analyzing, and initiating appropriate corrective action for products or articles that have been released from the quality system" (14 CFR 21.137). An 8D is one common way to meet that. Many customers supply their own 8D form; the content is the same.
What are the 8D problem solving steps? D0 to D8
Discipline names follow the Wikipedia summary (Wikipedia); the "must show" column is what a customer reviewer looks for.
| Discipline | Name | What the report must show |
|---|---|---|
| D0 | Preparation and emergency response | Why an 8D is needed and any immediate action taken |
| D1 | Use a team | Names and roles, with product and process knowledge represented |
| D2 | Describe the problem | What, where, when, how many, in measurable terms; what is not affected |
| D3 | Interim containment | Where suspect stock was, how much was sorted, results, and the date containment started |
| D4 | Root causes and escape points | Why it happened and why it was not detected, each verified with evidence |
| D5 | Verify permanent corrections | Evidence that the chosen fix removes the cause before it is rolled out |
| D6 | Implement corrective actions | What changed, when, and data showing the problem is gone |
| D7 | Prevent recurrence | Changes to procedures, FMEAs, control plans and similar products |
| D8 | Recognize the team | Closure date, sign-off, and thanks to the team |
D3 is about the customer first: in the summary's words, "Define and implement containment actions to isolate the problem from any customer." D4 has a second question that weak reports forget: "Also identify why the problem was not noticed at the time it occurred." (Wikipedia).
8D report example and sample: a supplier escape reaches the customer (illustrative)
An illustrative example, not a real company record. A plastics moulder ships housings to an electronics assembler; the assembler finds cracked screw bosses.
| Discipline | Entry |
|---|---|
| D0 | Customer complaint CC-3381 on 3 March: 27 cracked bosses on housing HSG-40 rev B, found at the customer's assembly. Customer line stopped for 2 hours. 8D-0094 opened. |
| D1 | Quality engineer (lead), moulding process engineer, tooling technician, shift supervisor, customer quality contact. |
| D2 | Cracks at the root of boss 3 on housings from lots 2240 to 2243 (moulded 20 to 24 February, press 7). 27 of 1,800 delivered parts (1.5 percent). Other bosses, other presses and earlier lots not affected. |
| D3 | All stock of lots 2240 to 2243 at the plant, in transit and at the customer quarantined and 100 percent inspected under magnification: 61 more cracked parts removed. Certified clean parts marked with a green dot from 4 March. |
| D4 | Occurrence: mould cooling line to boss 3 partly blocked after a tool repair on 19 February, causing high residual stress. Verified by cooling flow test and by reproducing cracks on 5 test shots. Escape: final inspection checks appearance only; boss cracks are inside the part and need a torque test that was not in the control plan. |
| D5 | Cooling line cleared; 200 test shots torque-tested to 1.5 times specification with no cracks. Torque test added to sampling and shown to detect cracked bosses on 5 known-bad parts. |
| D6 | Cooling-flow check added to the tool-repair release form on 10 March. Torque test at 5 parts per hour on press 7 from 10 March. 12 lots shipped since with zero rejects. |
| D7 | Tool-repair release procedure updated for all 14 moulds with cooling near bosses. PFMEA updated (cooling blockage added). Lesson shared at the monthly quality meeting. |
| D8 | Closed 14 April after customer acceptance. Team thanked at the plant meeting. |
Note how D4 has two verified causes, each with its own fix in D6, and how D2 states what is not affected. Those are the parts customers check first.
8D report template (CSV for Excel)
Download the 8D report template (CSV). It has one row per discipline with the fields a reviewer expects (owner, date, description, evidence, status) and opens in Excel or Google Sheets. If your customer requires its own form, copy the content across; keep your own copy linked to the NCR numbers.
Common weak 8Ds and why customers reject them
Customers send 8Ds back for a small number of reasons. Each one is avoidable.
- "Operator error" as the root cause. It explains nothing; ask why the process allowed the error.
- No escape point in D4, so inspection is left exactly as it was.
- Root cause stated but not verified: no reproduction, no data, no test.
- D3 containment that covers stock at the plant but not parts in transit or at the customer.
- Retraining as the only corrective action, with no change to the process, fixture or check.
- D6 closed on the day of implementation, before any data shows the problem has stopped.
- D7 left blank: the same weakness on similar parts and processes is never checked.
8D vs CAPA vs 5 Whys
CAPA (corrective and preventive action) is the general process every quality system needs for removing the causes of problems. An 8D is one structured format for doing a corrective action, with containment and team steps built in; it suits customer complaints and supplier escapes. 5 Whys and fishbone (Ishikawa) diagrams are tools used inside D4 to reach a root cause; they are not reports on their own. A one-page A3 report is a shorter format some companies use for internal problems.
Whichever format you use, the obligation is the same for FAA production approval holders: procedures "to eliminate the causes of an actual or potential nonconformity" (14 CFR 21.137). Medical device makers work under a quality management system that "complies with the applicable requirements of ISO 13485" (21 CFR 820.10). On government contracts, a contractor is ordinarily given "an opportunity to correct or replace nonconforming supplies or services" (FAR 46.407), and a credible 8D is how that correction is usually shown.
Keeping 8Ds with the NCRs and test results
An 8D is only useful later if its evidence stays attached: the NCRs it covers (see the NCR template), the inspection and test data from D3 to D6, and any engineering change order it triggered. FAA production approval holders also need procedures for "receiving and processing feedback on in-service failures, malfunctions, and defects", and must keep quality records "for at least 5 years" for products made under the approval and 10 years for critical components (14 CFR 21.137).
Use one ID scheme across NCRs, 8Ds, CAPAs and ECOs, and record the IDs in both directions. A reviewer, an auditor or a new engineer should be able to start from any one record and find the rest.
Your 8D archive is also a data asset
A decade of 8Ds, each tied to its NCRs, test data and the change that fixed it, is a detailed record of real failure analysis: how a problem was described, which causes were ruled out, which fix worked. That reasoning is rarely written down anywhere public.
AI developers building tools for quality and engineering work ask for this kind of linked, outcome-bearing history; where a license is agreed, it is de-identified and under written terms. Customer-owned drawings, export-controlled technical data and personal details stay out (see the export-control checklist and how to de-identify records). The guide for engineered-product manufacturers covers what is in scope and who signs; licensing CAD and engineering data covers the design side.
If your company keeps years of quality and engineering change records, the guide for engineered-product manufacturers explains what AI developers ask for and who signs. To see what yours could be worth, describe them in six questions; no files or system access needed.
Common questions
What does 8D stand for?
Eight disciplines. It is a team-based problem-solving method, developed at Ford Motor Company according to the Wikipedia summary, that moves from team and problem description through containment, root cause, correction and prevention to closure. Most forms add a D0 preparation step.
When is an 8D report required by a customer?
Usually when a defect reaches the customer, when a problem repeats, or when a supplier escape stops their line. Many customers name the 8D format in their supplier quality terms. Check the supplier manual or purchase order for the trigger and the deadline.
Who owns D3 containment in an 8D?
The supplier who caused the problem owns containment of every suspect part, wherever it is: at the plant, in transit and at the customer. In practice the 8D lead assigns a named person and records quantities sorted, results and the date certified clean parts started shipping.
How long should an 8D take to complete?
Your customer's supplier manual or purchase order sets the deadlines, and they differ. Containment always comes first and fast, because suspect parts may still be at the customer. The 8D closes only after data shows the permanent fix works, so the last disciplines take longer than the first.
What is the difference between an 8D and 5 Whys?
5 Whys is a questioning technique for reaching a root cause. An 8D is a complete report and process that includes a team, containment, verification and prevention. 5 Whys is often used inside D4 of an 8D.
Do customers require suppliers to use their own 8D form?
Many large customers do and supply a form or portal. The disciplines are the same, so a supplier can keep its own 8D record and copy the content into the customer form. Keep your own copy linked to your NCR numbers.
Can 8D reports be anonymised and shared outside the company?
Yes, with care. Remove customer names, part numbers that identify a customer design, employee names and anything export-controlled, and check confidentiality terms in customer contracts first. Engineering details of your own processes usually remain yours to share.
What is 8D problem solving?
8D problem solving is a team method for fixing a serious or repeated quality problem in eight steps: build a team, describe the problem, contain it, find and verify the root cause and the escape point, choose and verify a fix, implement it, prevent recurrence and close. The 8D report is the written record of those steps.
How do you write the problem description in D2 of an 8D?
State the problem in measurable terms, using the who, what, where, when, why, how and how many questions known as 5W2H. ASQ describes D2 as specifying the problem "in quantifiable terms" with those seven questions. A good D2 names the part, the defect, the quantity affected and where it was found, without guessing at the cause.
Should we use an 8D report or an A3 report?
Use an 8D for a specific problem that needs a verified root cause, such as a scrapped part or a customer complaint. A 2023 Quality Progress article by Matthew Barsalou, listed on ASQ's 8D page, finds the 8D better suited to root cause analysis and the A3 to continuous improvement, such as removing the causes of scrap across a process. ASQ adds that 8D suits problems whose root cause is not apparent at once or that affect several departments.
Sources and further reading
Origin Data Partners is an independent data partner. We work with buyers, and a buyer may pay us when a deal closes.