Quality managementReading time 12 min

Write an 8D Report That Proves the Fix

An 8D report is not complete when every box is filled. It needs evidence for the root cause, a verified corrective action and a plan to prevent recurrence. Work through what reviewers actually need to see.

01The eight steps

Step	Name	Deliverable
D1	Form the team	Cross-functional list with responsibilities and an owner
D2	Describe the problem	5W2H, the symptom, quantity, lot numbers, occurrence rate
D3	Interim containment	Disposition and completion time for shipped, in-stock, WIP and in-transit material
D4	Root cause	Occurrence cause plus escape cause, each verified
D5	Permanent corrective action	The chosen action and verification of its effectiveness
D6	Implement and confirm	Implementation date, lot number, tracking data
D7	Prevent recurrence	Standardisation: SOP, FMEA, control plan, gauges
D8	Close and recognise	Horizontal deployment to similar processes and part numbers

Containment timing depends on the customer's requirement and the risk; record what was covered and when.

02Two root causes to verify

A useful 8D must answer two separate questions about the defect:

Occurrence. Why was the defect produced?
Escape. Why, having been produced, was it not caught?

Finding why the defect occurred is only half the investigation. The 8D must also explain why inspection or process controls failed to catch it. If that escape route stays open, a different defect can reach the customer next time.

Ask why until you reach something you can control

Level	Example	Assessment
Symptom	Dimension out by 0.05 mm	Not yet a cause
Direct cause	Tool wear past the limit	Getting closer
System cause	Tool changes judged by experience, with no defined limit	Now at a level you can change
Management cause	The work standard sets no tool change criterion	Root cause

“Operator error” is not a verified root cause. Ask which process control allowed the mistake to occur or escape.

03Proving the corrective action

Choose a permanent action that removes or controls the cause, then define how its effectiveness will be measured. Detection alone is not the same as prevention.

Level	Approach	Effectiveness
1. Eliminate	Change the design so the problem cannot occur	Highest
2. Mistake-proof	Get it wrong and it will not assemble, or the machine will not run	High
3. Detect	Automatic detection that stops the line	Medium
4. Control	SPC monitoring of the trend	Medium-low
5. Procedure	SOP, training, extra patrol inspection	Lowest

A permanent action should have an effectiveness check, not only a promise of more attention.

04What reviewers check

Are quantity and scope clear in D2? Affected lots, date range, quantity already shipped.
Does D3 cover everything in transit? The customer, the warehouse, WIP and the supplier all need a disposition.
Does D4 give both causes? Occurrence and escape.
Is D5 high enough in the hierarchy? Stopping at training gets it rejected.
Did D7 go back and change the documents? FMEA, control plan, SOP and gauge list must all be updated, with revision and date.

Close the report only after updating the controls that will govern future work. If the PFMEA, control plan or work instruction remains unchanged, the same failure mode can return in the next project.