8D report: the 8 disciplines with example
An 8D report is a structured document that helps you solve a complaint or quality problem in eight steps (disciplines). These run from forming a team and taking immediate action, to finding the cause, solving it permanently and preventing it from coming back. The report shows your customer what you did and why the problem will not return.
The method comes from the American car industry (Ford). The German VDA (Verband der Automobilindustrie) set it down in Europe in the handbook 8D - Problem Solving in 8 Disciplines . In the car industry, IATF 16949 requires a documented problem-solving process, and many customers explicitly ask for an 8D. Outside automotive, an 8D is a strong way to carry out the corrective actions required by ISO 9001.
When do you write an 8D report?
An 8D is more demanding than a normal nonconformity record. You use it when a problem is serious, recurring or critical for a customer. For a small internal nonconformity, a root cause analysis with 5 whys is enough.
| Situation | Suitable approach |
|---|---|
| Customer asks for an 8D after a complaint | 8D report |
| Recurring problem, earlier measures did not work | 8D report |
| Safety risk or large financial impact | 8D report |
| One-off, small internal nonconformity | Nonconformity record with 5 whys |
The 8 disciplines of an 8D report
The eight steps below follow the VDA’s naming. Ford later added a step D0: planning and deciding on emergency measures before the team starts. Many templates therefore begin at D0.
| Discipline | Name | What you do |
|---|---|---|
| D0 | Preparation | Decide whether an 8D is needed, first emergency measure |
| D1 | Team | Small group with knowledge of the product and process, with a team leader |
| D2 | Problem description | What, where, when, how many, with facts and photos |
| D3 | Immediate actions | Protect the customer: block stock, sort, extra inspection |
| D4 | Causes | Root cause of the occurrence and of the failure to detect it |
| D5 | Planned corrective actions | Choose actions and show that they work |
| D6 | Implemented corrective actions | Implement, remove temporary measures, measure the effect |
| D7 | Prevent recurrence | Adjust procedures, FMEA and similar products |
| D8 | Recognise the team | Close the case, share the result, thank the team |
D4 is the core. A good 8D looks for two causes: why the error happened, and why your inspection did not stop it. For this investigation you often use an Ishikawa diagram and 5 whys.
An 8D is in effect an extended PDCA cycle for one problem. D1 to D5 are the plan, D6 is the do, measuring in D6 is the check and D7 is the act.
Example of a completed 8D report
A supplier of plastic housings receives a complaint: 340 of the 5,000 housings delivered have scratches on the visible side. The customer asks for a first response within a few days and a full 8D afterwards. This is what the report looks like, in shortened form.
| Discipline | Completed |
|---|---|
| D1 Team | Team leader: quality engineer. Members: injection moulding shift supervisor, packing operator, logistics, customer representative (on call). |
| D2 Problem | 340 of 5,000 housings (6.8%) with scratches of 5-20 mm on the visible side. Batch 24-118, produced in week 11 on machine 4. Reported by the customer at incoming inspection on 18 March. |
| D3 Immediate actions | Stock at the customer and in our own warehouse sorted (1,920 pieces, 41 rejected). Extra visual inspection at packing on all open orders. |
| D4 Cause of occurrence | Housings fall from the conveyor belt into a bin without an interlayer. Since week 10, new bins without a foam rubber base. Test confirms scratches on drop. |
| D4 Cause of non-detection | Final inspection only checks dimensions, not the visible side. The inspection instruction does not mention scratches. |
| D5 Chosen actions | Slide chute with soft lining from the belt to the bin. Interlayers in all bins. Inspection instruction extended with a visual requirement and a boundary sample. |
| D6 Implementation and effect | Implemented on 26 March. Three following batches: 0 scratches on 15,000 pieces. Extra sorting inspection stopped after three batches without defects. |
| D7 Prevent recurrence | Process FMEA extended with the failure mode “damage during removal”. Same chute on machines 2 and 6. Requirement “no packaging change without a quality check” added to the purchasing procedure. |
| D8 Closure | Report discussed with the customer on 15 April, customer agreed. Result shared in the shift meeting. |
Note D7. The team does not only adjust machine 4, but also similar machines and the FMEA. That is the difference between solving a problem and preventing it from coming back.
Template for an 8D report
Copy these fields into your own form. They follow the VDA structure and cover what ISO 9001 asks for in corrective actions.
| Field | To complete |
|---|---|
| Header | Customer, complaint number, product, date reported, team leader |
| D1 | Names and roles of team members |
| D2 | What, where, when, how many, how it was discovered, photos |
| D3 | Measure, number checked, number rejected, date |
| D4 | Cause of occurrence and cause of non-detection, with evidence |
| D5 | Chosen actions and how you tested that they work |
| D6 | Date of implementation, results after implementation |
| D7 | Adjusted documents, FMEA, other products or locations |
| D8 | Date of closure, customer agreement |
How quickly must an 8D report be ready?
The standard does not set fixed deadlines. Customers set them in their supplier requirements. They often ask for a quick first response with D1 to D3, and the full report later. The VDA handbook warns that such deadlines must not come at the expense of a good solution. Agree a realistic date for D4 to D6 rather than submit a report with a cause you have not proven.
What does an auditor check in an 8D report?
An auditor for IATF 16949 or ISO 9001 reviews a few 8Ds from the past year. They look at:
- Is the cause supported by evidence, or is it an assumption?
- Has the cause of non-detection also been investigated?
- Has effectiveness been measured with figures after implementation?
- Have the FMEA, control plan and instructions been updated?
- Have similar products and processes been taken into account?
If the effectiveness check is missing, this can lead to a minor or major nonconformity, depending on how often it occurs.
What is the difference between an 8D report and a corrective action?
A corrective action is what ISO 9001 requires in clause 10.2: determine the cause, take action, and assess effectiveness. An 8D report is one way to do this, with fixed steps and a fixed format. Every 8D is therefore a corrective action, but not every corrective action has to be an 8D.
In the medical sector the same process is called CAPA (corrective and preventive action). The steps are very similar. If you work across several sectors, you can use one register with the 8D steps as fields.
Common mistakes in an 8D report
- Confusing D3 and D5. Sorting is an emergency measure, not a solution.
- D4 with one cause. The question of why your inspection missed the error remains open.
- No figures in D6. “Problem solved” without measurement does not convince a customer or an auditor.
- Skipping D7. The problem comes back on another machine or with another product.
Further reading
- Root cause analysis and 5 whys
- Ishikawa diagram with example
- CAPA under ISO 13485 - the similar approach in the medical sector