Build a customer-ready 8D report step by step. D4 asks for both root causes — why the defect happened and why your controls let it escape — because a missing escape analysis is the single most common reason customers send an 8D back.
Stays in your browser. Autosaved locally, never uploaded. No signup, no email, no limit.
D0 — Preparation and emergency response
Capture the complaint as the customer worded it. Your job in D2 is to turn it into facts; D0 preserves the original claim so nobody can later argue you solved a different problem.
D1 — Team
An 8D signed by one person reads as one person's opinion. Reviewers look for cross-functional membership: whoever owns the process, whoever owns the control that failed, and whoever can authorise the change.
Team members — aim for at least three functions.
D2 — Problem description
Quantified facts, not a paragraph. The 5W2H fields below are what a supplier quality engineer checks first: if how many and since when are missing, the report goes back before anyone reads D4.
The gap between IS and IS NOT is where the cause lives. If both columns look the same, the description is still too broad — see the Is / Is Not method and 5W2H.
D3 — Interim containment
Containment protects the customer today without removing the cause. Sorting, 100% inspection, quarantine, a temporary supplier switch. If your D3 and D5 end up reading the same, D5 is wrong.
D4 — Root cause: occurrence and escape
Every defect has two root causes. Why it happened, and why your controls did not catch it. A missing escape analysis is the number one reason 8D reports are rejected — so this step asks for both chains separately.
Why did the defect happen? Keep asking until you reach something in the process, not in a person. "Operator error" is a symptom of a process that allowed the error.
Why did it reach the customer? If the answer is "the inspector missed it", keep going: what about the inspection method made the miss possible?
Need to work the chains out loud first? Use the 5 Whys tool for depth or the fishbone maker for breadth, then paste the result here.
D5 — Permanent corrective actions chosen
One action per root cause, minimum. An action without an owner and a date is a wish — and reviewers count how many of your rows have both.
Action plan — owners and dates.
D6 — Implement and validate
"Implemented" and "worked" are different claims. D6 needs the second one, with numbers before and after.
D7 — Prevent recurrence
This is where repeat complaints die. Fixing one line is D5; changing the system so the same weakness cannot appear elsewhere is D7 — and it is the discipline most often left as a single empty sentence.
D8 — Close and recognise the team
Closure is a claim that the metric moved and stayed moved. Recognition is not decoration — it is why anyone volunteers for the next 8D.
Review and export
Before you send it: the check below looks for the patterns that get 8D reports returned. It is built from the rejection reasons our own 8D material documents, not from a generic completeness rule.
An 8D is not a form you fill in to close a ticket. It is an argument you make to somebody who was not there, usually a supplier quality engineer with forty other reports on their desk. That argument has to survive four questions, and the generator above is ordered around them.
Every defect that reaches a customer represents two failures. Something made the defect, and something let it through. In 8D language those are the cause of occurrence and the cause of escape, and a report that answers only the first is incomplete by construction — because even a perfectly corrected process will eventually produce another defect, and the same blind control will pass it again.
The pattern to watch for in your own draft: if the escape answer is "the operator missed it" or "inspection did not detect it", the chain has stopped one step early. Keep asking. What about the sampling plan, the lighting, the gauge resolution, the cycle time, or the absence of that check in the control plan made the miss possible? That answer is the one that leads to a corrective action you can actually implement.
| Discipline | What reviewers check first | Most common rejection |
|---|---|---|
| D2 | Quantified: how many, since when, measured vs spec | A prose paragraph instead of numbers |
| D3 | Date implemented, effectiveness verified, scope beyond the complained lot | Containment covering only the lot that was complained about |
| D4 | Two chains, each with evidence | Escape analysis missing entirely |
| D5 | One action per root cause, with owner and date | Containment repeated as if it were correction |
| D6 | Metric before and after, over a stated period | "Implemented" with no evidence it worked |
| D7 | FMEA and control plan revised, sister parts named | One sentence saying "operators retrained" |
8D exists for problems where a customer or an auditor will retrace your reasoning. A specific failure, an external complaint, weeks of work, a formal document at the end. If the problem is internal and the causal chain is short, a 5 Whys worksheet gets you there in half an hour, and forcing it into eight disciplines produces form-filling fatigue and copy-pasted "retraining" actions. The comparison is laid out in 8D vs 5 Whys; for a one-page internal canvas see A3.
If you need the blank document rather than the guided flow — because a customer demanded their own layout, or you want to fill it in offline — the free 8D report template covers D0 to D8 in Excel, Word and PDF. The full method walkthrough, discipline by discipline with a worked automotive example, is in the 8D guide.
D0 to D3 belong in the first 24 to 72 hours, because containment is what buys you the time to think. D4 to D6 take two to six weeks, most of it validation rather than analysis. D7 and D8 close inside the 30 to 60 day window most customers expect. Writing the whole thing retrospectively on the last day is visible in the document: dates cluster, evidence is thin, and D3 looks identical to D5. Practical guidance on running the sessions is in how to facilitate an 8D.
No. Everything you type stays in your browser. The report autosaves to your own device so you can close the tab and come back, and the "Save file" button writes a JSON file you keep. Nothing reaches our server, and there is no account to create.
Because a defect that reached a customer represents two failures: one that created it and one that let it pass. Correcting only the first guarantees the next defect of the same family will also escape. A missing escape analysis is the most frequent reason customer quality engineers return an 8D.
Use "Export PDF" and you get a clean, paginated document in the layout customers expect, without the tool interface around it. If your customer mandates their own template, generate the PDF anyway as your working record and transcribe the fields — the structure matches the standard AIAG discipline order, so it maps across one to one.
Say so in the field rather than leaving it blank, and give the reason. "Not applicable: no FMEA exists for this legacy part; one was created as part of D7" is an answer. An empty field reads as an oversight, and reviewers treat it as one.
It tells you whether your report contains the things reviewers look for, and flags the specific patterns that get reports returned — a missing escape cause, containment repeated as correction, a root cause that stops at human error, actions with no owner. It cannot judge whether your analysis is right. That still needs the people who know the process.
Related: 8D template (Excel, Word, PDF) · 8D guide D0-D8 · Is / Is Not analysis · 5W2H for D2 · Control plan for D7 · 5 Whys tool · Fishbone maker
Using this in a real workshop? The Workshop Kit adds the agendas, slides and crisis cards around the tools. Launching soon · waitlist gets 50% off.