What is an 8D report?
8D (Eight Disciplines) is a team-oriented problem-solving method developed by Ford and now the standard response to customer complaints in automotive, aerospace and electronics manufacturing. Its strength is discipline: protect the customer first (containment), prove the root causes before fixing them, and close the gaps in both the process that made the defect and the controls that missed it.
The eight disciplines (plus D0)
| D | Discipline | Key output |
|---|---|---|
| D0 | Prepare | Symptom confirmed, emergency response actions, decision to open an 8D |
| D1 | Team | Cross-functional team with a champion and a leader |
| D2 | Problem description | Quantified problem statement (5W2H, Is/Is Not) |
| D3 | Containment | Interim actions that protect the customer, with proof they work |
| D4 | Root cause | Verified root causes of occurrence and of escape (5 Whys, fishbone) |
| D5 | Corrective actions | Permanent corrective actions chosen and verified before implementation |
| D6 | Implement & validate | Actions in production, results validated, containment removed |
| D7 | Prevent recurrence | FMEA, control plan, standards and similar products updated |
| D8 | Recognize & close | Customer acceptance, lessons learned, team recognized |
8D example
A customer reports connector housings cracking at the latch. The team stops shipments and starts sorting at the customer within hours (D0), then describes the problem precisely: 11,600 PPM, all from cavity 3 of one tool, moulded in a two-week window (D2). Sorting 42,300 parts contains the problem (D3). The investigation finds two root causes (D4): occurrence, over-dried material after a dryer setpoint change, combined with a thin latch in cavity 3; and escape, no latch flex test in the control plan. Both are reproduced on and off. The corrective actions (D5) restore and lock the dryer setting, repair the cavity and add a flex test, proven on a 3,000-part trial. D6 to D8 track implementation, a read-across to all 14 moulding cells and closure.
Common 8D mistakes
- Weak D2. A vague problem statement leads to a weak root cause. Quantify it and say where the problem is not.
- "Operator error" as the root cause. Ask why the process allowed the error, and consider poka-yoke.
- Forgetting the escape. Every defect that reached a customer also passed your controls.
- Unverified actions. D5 needs evidence that the actions work before they go into production.
- Closing without D7. Update the FMEA and control plan, and check similar products, or the problem will come back elsewhere.
Managing the corrective action itself in your quality system? Use the CAPA tool to add a risk rating and an effectiveness check.
How to use this 8D Report tool
- Open the 8D. Enter the problem title, 8D number, customer, part and opening date.
- D0 and D1. Describe the symptom and emergency response, then name the team with a champion and a leader.
- D2 and D3. Describe the problem with 5W2H and record the containment actions and their effectiveness.
- D4 and D5. Record and verify the root causes of occurrence and escape, then the chosen corrective actions for each.
- D6 to D8. Record implementation and validation, systemic preventive actions with the D7 checklist, and closure.
- Track and export. Track actions by type, watch the response-time targets on the roadmap, and export the 8D report to PDF or Excel for the customer.
Frequently asked questions
What is an 8D report?
An 8D (eight disciplines) report documents a team-based approach to solving a quality problem, usually a customer complaint. It covers the team, a precise problem description, containment, the root causes of occurrence and escape, verified permanent corrective actions, prevention of recurrence and closure.
What are the 8 disciplines?
D1 Form the team, D2 Describe the problem, D3 Contain the problem, D4 Find the root causes, D5 Choose and verify permanent corrective actions, D6 Implement and validate them, D7 Prevent recurrence, D8 Recognize the team and close. Most companies add D0 (prepare and emergency response) before D1.
What is the difference between occurrence and escape root causes?
The occurrence root cause explains why the defect was made. The escape (or non-detection) root cause explains why it was not caught before reaching the customer. A complete 8D finds and fixes both, because fixing only the occurrence leaves the detection gap open for the next problem.
How fast must an 8D be completed?
Customer requirements vary, but a common pattern in automotive is containment (D3) within 24 hours, root cause and corrective actions (D4–D5) within 10 days, and closure within 30 to 60 days. Set your customer's targets in D3, D5 and D8 and the tool flags anything late.
What is the difference between 8D and CAPA?
8D is a problem-solving method and report format, mainly used for customer complaints in automotive and manufacturing. CAPA is the quality system process (required by ISO 13485, FDA 21 CFR 820 and others) that manages corrective and preventive actions from any source. An 8D can serve as the investigation record of a CAPA.
Who created the 8D method?
The 8D method was developed by Ford Motor Company and published in 1987 as "Team Oriented Problem Solving" (TOPS). It is now standard practice across the automotive industry (IATF 16949) and widely used in aerospace, electronics and medical devices.