QM Bench

8D Report Template Online with Photos and PDF Export

Fill in the eight disciplines step by step, attach photos of the defect and the fix, and download a clean PDF for your customer. Your work is saved automatically in this browser.How to use ↓
  1. 1Enter your data
  2. 2Read the verdict
  3. 3Download the PDF report
Loading…

Report header

D0

Emergency response

What was done immediately to protect the customer?

D1

Team

Cross-functional team with process knowledge and authority to act.

D2

Problem description

Describe the problem in measurable terms with 5W2H and is / is not.

Is / is not analysis
IsIs notDistinction / change
What
Where
When
How many

Comparing where the problem is and where it could be but is not points to what changed.

Photos
D3

Containment actions

Interim actions that stop defects reaching the customer.

#ActionOwnerDueStatusEffectiveness
1
Photos
D4

Root cause analysis

Why did it occur, and why was it not detected?

5 Why
Why 1
Why 2
Why 3
Why 4
Why 5

Build a fishbone diagram and send it here with “Add to 8D report”, it appears as a photo below.

Photos
D5

Permanent corrective actions

Actions that remove the root causes.

#ActionOwnerDueStatus
1
D6

Implementation and verification

Evidence that the corrective actions work.

Photos
D7

Prevent recurrence

Update systems so it cannot happen again, here or elsewhere.

D8

Team recognition and closure

Recognise the team and close the report.

How to write a good 8D report

  1. Contain first. D0 and D3 protect the customer while you investigate: sort stock, add inspection, ship replacements.
  2. Describe the problem with facts. D2 uses 5W2H: what, where, when, who, how, how many and why it matters. Numbers and photos beat adjectives.
  3. Find both root causes. In D4 explain why the defect occurred and why it escaped detection. Use 5 Why, a fishbone diagram and data such as a Pareto chart, and verify the cause by switching it on and off.
  4. Fix the cause, not the symptom. D5 actions should remove the root cause. Extra inspection is containment, not a permanent action.
  5. Prove it works. D6 shows evidence: defect-free quantities, a capability study or a control chart after the change.
  6. Prevent recurrence. D7 updates the FMEA, control plan and work instructions, and applies the fix to similar processes.

Common mistakes

  • Naming "operator error" as the root cause. Ask why the process allowed the error.
  • Closing D5 with "retrain the operator" or "100 % inspection" only.
  • No evidence in D6 that the actions are effective.
  • Forgetting the non-detection root cause.

Frequently asked questions

›What is an 8D report?

An 8D (eight disciplines) report is a structured problem solving method used in automotive, aerospace and general manufacturing to respond to customer complaints and internal quality problems. It moves from containment through root cause to permanent corrective and preventive actions.

›What are the 8 disciplines?

D0 emergency response, D1 team, D2 problem description, D3 containment, D4 root cause, D5 permanent corrective actions, D6 implementation and verification, D7 prevention of recurrence and D8 team recognition and closure. D0 was added later, so many forms show 9 steps.

›Can I add photos to the 8D report?

Yes. You can add photos to the problem description, containment, root cause and verification steps by clicking, dragging files, or taking a photo directly on your phone. Photos are compressed in your browser and included in the PDF with numbered captions.

›Is my report uploaded anywhere?

No. The report and its photos are stored only in your browser on this device, and the PDF is created locally. Use Save file to keep a backup or move the report to another computer.

›How long should an 8D take?

Customers commonly expect D3 containment within 24 to 48 hours, D4 root cause within 1 to 2 weeks and closure within 30 to 60 days. Check your customer requirements, they are often written in the supplier quality manual.

›Why does an 8D need two root causes?

Every escape has a cause of occurrence (why the defect was made) and a cause of non-detection (why it was not caught). Fixing only one leaves the door open. D4 asks for both and D5 needs actions for both.