Quality & InspectionFree referencePDF, Excel, Word exportAutomotive and Aerospace Manufacturing

8D Steps D0 to D8 Reference Table

The 8D method breaks a quality problem into disciplines from D0 to D8. Use this table when you are writing a report, reviewing a supplier's response, or training a team on what each step must contain.

Download:

Step	Discipline	Purpose	Typical outputs	Usual owner	Common mistake
D0	Prepare and emergency response	Decide whether an 8D is warranted and protect the customer immediately	Symptom statement, emergency response action, 8D trigger decision	Quality manager	Starting an 8D for a one-off issue that needs only a simple correction
D1	Establish the team	Assemble people with process knowledge and authority to act	Team roster, champion, team leader, roles	Quality manager	Team made only of quality staff with nobody from the process owner area
D2	Describe the problem	State the problem in measurable terms using facts, not opinions	Is/Is Not analysis, 5W2H, part and lot identification, photos, quantity	Team leader	Writing the suspected cause instead of the observed symptom
D3	Interim containment action	Isolate the problem from the customer until a permanent fix exists	Sort and inspection results, quarantine locations, certified stock, verification of containment effectiveness	Operations and quality	Containment not verified, or not extended to in-transit and customer stock
D4	Root cause analysis and escape point	Find the technical cause and the point where the defect should have been caught	Occurrence root cause, escape (detection) root cause, systemic cause, verification of cause	Team leader	Stopping at the first plausible cause without testing it by turning the defect on and off
D5	Choose and verify permanent corrective actions	Select actions that remove the root cause and prove they work before release	Selected actions, trial or pilot results, risk check against FMEA	Engineering	Choosing retraining as the only action
D6	Implement and validate permanent corrective actions	Put the fix in the process and confirm results on live production	Updated work instructions, control plan, PFMEA, validation data, containment removal date	Operations	Removing containment before enough production data proves the fix
D7	Prevent recurrence	Spread the learning to similar products, lines and sites and fix the system	Updated procedures, lessons learned, horizontal deployment list, FMEA updates	Quality manager	Treating D7 as a copy of D6 with no look at similar parts or processes
D8	Congratulate the team and close	Recognise the team, record learning and close with evidence	Closure approval, final report, lessons learned entry, customer sign-off if required	Champion	Closing on the date actions are done, not on proven effectiveness

The 8D method is widely used in automotive and aerospace supply chains. Your customer may require a specific form or step wording, so always follow their supplier requirements where they differ from this table.

Get an 8D review checklist for your suppliers

Optional: we can send an Excel review sheet built from this table with accept and reject criteria.

Optional. The tool and every export work without this. No spam.

How to use the table

Search for a step number or a word such as containment or escape point. Each row gives the purpose of the discipline, the evidence a reviewer expects, who normally owns it, and the mistake that most often gets a response bounced back. Export the table to Excel to turn it into a review checklist for supplier 8D submissions, or to PDF to hand to a new team leader before the first team meeting.

Why D4 is where reports fail

Most rejected 8D reports fail at D4 and D5. Reviewers want two causes: the occurrence cause that created the defect and the escape cause that explains why detection missed it. A report that names only operator error, or only a missed inspection, usually leaves the system exposed. Prove the cause by showing that you can switch the defect on and off, and tie the permanent action back to the specific cause and to the PFMEA and control plan.

Separate occurrence cause from escape cause
Verify the cause with data before choosing actions
Link actions to the PFMEA and control plan
Show containment removal criteria in D6

ERP and quality system notes

In most ERP systems the 8D lives as an attachment or a linked quality notification, while the facts it depends on sit in lot, serial and shipment records. For D3 you need to trace every lot made with the suspect material or process, so check that your lot traceability reports return supplier, work order, shipment and customer in one query. Gaps found here are often the real finding of the investigation.

Frequently Asked Questions

What does D0 mean in 8D?

D0 is the preparation step added to the original eight disciplines. It covers planning, the symptom statement and any emergency response needed to protect the customer, and it is where you decide whether the problem is serious enough to justify a full 8D.

What is the difference between D3 and D5?

D3 is a temporary barrier that protects the customer while you investigate, such as sorting stock. D5 selects permanent actions that remove the cause. Containment is removed only after D6 data shows the permanent fix works.

Do I need all eight steps for every problem?

No. Use 8D for significant, recurring or customer-mandated problems. A simple one-off defect with an obvious cause is better handled with a corrective action record. Your customer or quality system procedure may set thresholds.

Who should approve the closure of an 8D?

The champion or quality manager normally approves, after checking effectiveness data and that documents such as the PFMEA and control plan were updated. Customer-mandated 8Ds may also need the customer to accept the response.

If your 8D evidence is scattered across ERP lots, inspection records and email, we can help pull it into one traceable record that stays read-only against your ERP.

Talk to an Expert Explore More Free Tools

Related Tools

Quality & Inspection

More Quality & Inspection tools

See all

Back to All Tools