Your 8D template forgets one question
A free 8D report template with one extra field: has this been solved before? With a real case that shows why, ready to copy into Word or Excel.

An 8D report template is a form that walks a team through the eight disciplines of an 8D, from the first response to a complaint to the closure of the case. A useful one adds a field for one more question: has this problem, or one like it, been solved before?
In our pilot of 10 real 8D cases at 8 Slovenian manufacturers, engineers spent on average 47 minutes per case only finding old reports, data and notes, before the analysis could start.
In my view, that search deserves its own field.
What an 8D report template should hold
The disciplines are the same in every 8D. Many teams add D0 for the first response, before the team is formed.
A template tells the team what to do next. It also leaves a record that the customer and the auditor can follow, from the complaint to the proof that the fix works.
Two European 8D forms we checked in October 2026, a free template and a supplier manual, have no field for the look back in D2 or D4. In both, D7 covers only the same problem coming back.
The look back belongs at the start. Before the team analyses anything, someone should search what the plant already knows.
The template
Copy the table into Word or Excel, one row per field.
| Step | Field | What to write |
|---|---|---|
| D0 Emergency Response | First response | Customer, part, symptom, date found, what was done in the first hours |
| D1 Team Formation | Team | Names and roles: lead, process owner, quality, someone from the line |
| D2 Problem Description | Is / Is not | What, where, when, how many, and where the defect does not occur |
| D2 Problem Description | Solved before? | Where you searched and with which words, the case numbers found, what matched and what differed |
| D3 Containment | Protect the customer | Sorting, stock in transit and in the warehouse, results |
| D4 Root Cause | Why it occurred, why it escaped | The cause, proven by switching the defect on and off, and the point where it escaped |
| D5 Corrective Actions | Actions and trial | One action per cause, and the trial that shows it works |
| D6 Verification | Proof | Date and data that show the defect is gone |
| D7 Prevention | Where else? | Other lines, parts and products with the same cause, FMEA and control plan changes |
| D8 Closure & Recognition | Closure | Who closed it, and the words the next engineer will search for |
The field to add
The row “Solved before?” sits in D2, right after the problem description. It has four parts:
- Where you searched and with which words.
- Which past cases you found, by number.
- What matched and what differed.
- What you take from them into D3 and D4.
One of our pilot partners, a Tier-2 supplier in CNC machining, shows what the field is for. A team spent three months looking for the cause of a dimensional deviation.
The same problem had been documented in an 8D report two years earlier. Nobody on the team knew the report existed.
Write it down even when the search finds nothing. “Searched the 8D archive and the complaint log by symptom, part and line, nothing found” is a result. The next engineer does not have to repeat it.
The same question comes back in D7, pointed sideways. Where else could this cause occur? On which line, part or product? That answer goes into the FMEA and the control plan.
The standards ask for both looks
ISO 9001:2015 asks, in clause 10.2.1 b), to determine “if similar nonconformities exist, or could potentially occur”. The first half of that sentence is the look back in D2. The second half is the look sideways in D7.
IATF 16949:2016 asks, in clause 10.2.3 d), for systemic corrective actions “including consideration of the impact on similar processes and products”.
ISO 9001 got a new edition on 16 September 2026. It keeps clause 10.2, with editorial changes.
A template with one field for each look turns those two sentences into two lines the team fills in on every case.
What the 47 minutes were
In the pilot, engineers opened PDF files and old Excel sheets and called colleagues. The searching also went on during the root cause analysis.
A field in a template does not make that search faster. It makes the work visible, and the next engineer finds the result in the case itself.
Finding similar past cases in seconds is the work we built SolveR for.
More on galileon.si
- The 8D method, step by step
- 8D report software compared
- Pilot results: 10 real 8D cases at 8 manufacturers
References
- VDA QMC, 8D - Problem Solving in 8 Disciplines. Method, Process, Report, 1st edition, November 2018. VDA QMC webshop
- ISO 9001:2015, Quality management systems, Requirements, clause 10.2.1. ISO
- LRQA, ISO 9001 publication date confirmed: 16 September 2026. LRQA
- Advisera, ISO 9001:2015 vs. ISO 9001:2026, main differences, updated 8 October 2026. Advisera
- IATF 16949:2016, Quality management system requirements for automotive production and relevant service parts organizations, clause 10.2.3. DIN Media
- Matej Kalčič, Z umetno inteligenco podprt organizacijski spomin (AI-Powered Organizational Memory), proceedings of the 10th International Scientific Conference, Faculty of Industrial Engineering Novo mesto, 14 May 2026, pp. 77-82. PDF