Customers and auditors read hundreds of 8D reports. The good ones are easy to spot: they are specific, evidence-based and they close. The weak ones describe activity rather than learning. Here is what each discipline should contain, and what tends to get a report sent back.

The eight disciplines at a glance

  1. D1 – Team. Name the people, their roles and who leads. Include someone who knows the process first-hand, not only quality staff.
  2. D2 – Describe the problem. State what is wrong, where, when, how many, and how it was detected. Use measurable facts, not opinions. An is / is-not comparison helps.
  3. D3 – Containment. Interim actions that protect the customer immediately: sorting stock, 100% inspection, quarantine, a call to the customer. Record who did what and the results.
  4. D4 – Root cause. Find the cause of the problem and the cause of the escape (why it was not detected). Tools such as 5-Why, fishbone and Pareto help, but the proof matters more than the tool.
  5. D5 – Choose corrective actions. Select actions that remove the root cause and say why they will work.
  6. D6 – Implement and verify. Put the actions in place, then show evidence they worked: data, trial results, audit findings.
  7. D7 – Prevent recurrence. Update FMEAs, control plans, work instructions and training, and apply the lesson to similar products and processes.
  8. D8 – Recognise the team and close. Confirm the problem is resolved, share the learning and formally close the report.

What gets a report rejected

  • "Operator error" as the root cause. This points at a person, not a system. Ask why the process allowed the error, and why detection failed.
  • No escape-point analysis. If you cannot say why the defect reached the customer, the same escape can happen again.
  • Containment presented as the fix. Sorting parts is not corrective action.
  • No verification evidence. "Training completed" does not show the problem is gone. Show results over time.
  • Documents not updated. If the FMEA and control plan are unchanged after a real failure, D7 has not been done.

A quick self-check before you submit

  • Can a stranger understand the problem from D2 alone?
  • Is every action owned, dated and evidenced?
  • Does the root cause explain both the occurrence and the escape?
  • Have you checked other products, lines and sites for the same weakness?

For a deeper technical reference see our 8D problem solving and root cause analysis page, or our automotive core tools guidance for how FMEAs and control plans fit in.