8D Report Generator
Work through the eight disciplines in order and get a finished report you can share or export as a PDF. No signup, your data stays in the browser.
0 / 8 disciplines completed
- D1
Build the team
Who is working on this problem? Give names and roles. An 8D team is small, cross-functional, and has one person accountable for it.
- D2
Describe the problem
What happened, where, since when, and how much of it? Describe it in measurable terms rather than judgements. Whoever reads the report later was not there.
- D3
Contain the problem
What protects the customer today, before the cause is known? Containment is deliberately temporary and gets replaced later.
- D4
Find the root cause
Why did the problem occur, and why did it escape detection? Both questions belong in an 8D. Evidence the cause instead of assuming it.
Not sure of the cause yet? Use the 5 Whys tool or the fishbone tool.
- D5
Choose corrective actions
Which permanent actions remove the cause? Every action needs an owner and a date, otherwise nothing happens.
- D6
Implement and verify effectiveness
What was actually implemented, and how do you know it worked? Name the measure and the period you watched it over.
- D7
Prevent recurrence
What changes in the system so the same failure cannot appear elsewhere? Control plan, FMEA, work instruction, training, standard for sister lines.
- D8
Recognise the team and close the report
Record what the team learned and close the report deliberately. An 8D without a closure stays an open task.
What is an 8D report?
The 8D report is the standard answer to a customer complaint in automotive and its supply base. Eight disciplines run from the complaint to closure: team, problem description, containment, root cause, corrective actions, effectiveness verification, prevention, and closure. The structure is fixed because customer and supplier have to read the same record.
Two disciplines decide how good the report is. D4 asks for an evidenced cause rather than a plausible guess, and it asks it twice: why it occurred and why it escaped. D7 asks for a system change so the same failure cannot appear on another line. Reports that stay thin there come back from the customer.
How to use the generator
Identify the report
Enter report number, product, customer, and date so the report can be filed and found later.
Fill in the disciplines in order
Work through D1 to D8 from top to bottom. The progress bar shows what is still open.
Evidence the cause
For D4, use the 5 Whys tool for depth or the fishbone tool for breadth, then bring the result back here.
Give every action an owner
For each action in D3 and D5, record who owns it and when it is due.
Share or export
Copy the report as text, share the link with your team, or save it as a PDF.
For the eight disciplines in detail, common mistakes, and a worked example, read the guide to the 8D report and see our other free tools.
A report is a document, not a closed loop
Mobile2b tracks actions from 8D reports, audits, and complaints through to verified effectiveness, across the plant and on premise if you need it.
See how it works