# 8D Steps D0 to D8 Reference Table > Source: https://netray.co/tools/eight-d-steps-d0-d8-reference-table > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A searchable table of every 8D discipline from D0 to D8 with its purpose, expected outputs and the mistakes that get reports rejected. ## Category quality ## Industry Automotive and Aerospace Manufacturing ## Audience - Quality manager - Quality engineer - Supplier quality engineer ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Step **Key:** step **Type:** text #### Discipline **Key:** name **Type:** text #### Purpose **Key:** purpose **Type:** text #### Typical outputs **Key:** outputs **Type:** text #### Usual owner **Key:** owner **Type:** text #### Common mistake **Key:** mistake **Type:** text **Rows:** #### Prepare and emergency response **Step:** D0 **Purpose:** Decide whether an 8D is warranted and protect the customer immediately **Outputs:** Symptom statement, emergency response action, 8D trigger decision **Owner:** Quality manager **Mistake:** Starting an 8D for a one-off issue that needs only a simple correction #### Establish the team **Step:** D1 **Purpose:** Assemble people with process knowledge and authority to act **Outputs:** Team roster, champion, team leader, roles **Owner:** Quality manager **Mistake:** Team made only of quality staff with nobody from the process owner area #### Describe the problem **Step:** D2 **Purpose:** State the problem in measurable terms using facts, not opinions **Outputs:** Is/Is Not analysis, 5W2H, part and lot identification, photos, quantity **Owner:** Team leader **Mistake:** Writing the suspected cause instead of the observed symptom #### Interim containment action **Step:** D3 **Purpose:** Isolate the problem from the customer until a permanent fix exists **Outputs:** Sort and inspection results, quarantine locations, certified stock, verification of containment effectiveness **Owner:** Operations and quality **Mistake:** Containment not verified, or not extended to in-transit and customer stock #### Root cause analysis and escape point **Step:** D4 **Purpose:** Find the technical cause and the point where the defect should have been caught **Outputs:** Occurrence root cause, escape (detection) root cause, systemic cause, verification of cause **Owner:** Team leader **Mistake:** Stopping at the first plausible cause without testing it by turning the defect on and off #### Choose and verify permanent corrective actions **Step:** D5 **Purpose:** Select actions that remove the root cause and prove they work before release **Outputs:** Selected actions, trial or pilot results, risk check against FMEA **Owner:** Engineering **Mistake:** Choosing retraining as the only action #### Implement and validate permanent corrective actions **Step:** D6 **Purpose:** Put the fix in the process and confirm results on live production **Outputs:** Updated work instructions, control plan, PFMEA, validation data, containment removal date **Owner:** Operations **Mistake:** Removing containment before enough production data proves the fix #### Prevent recurrence **Step:** D7 **Purpose:** Spread the learning to similar products, lines and sites and fix the system **Outputs:** Updated procedures, lessons learned, horizontal deployment list, FMEA updates **Owner:** Quality manager **Mistake:** Treating D7 as a copy of D6 with no look at similar parts or processes #### Congratulate the team and close **Step:** D8 **Purpose:** Recognise the team, record learning and close with evidence **Outputs:** Closure approval, final report, lessons learned entry, customer sign-off if required **Owner:** Champion **Mistake:** Closing on the date actions are done, not on proven effectiveness **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the table **Body:** 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 **Body:** 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. **Bullets:** - 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 **Body:** 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. **Cta:** 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. **Faq:** #### What does D0 mean in 8D? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms 8d steps explained, 8d report steps d0 to d8, 8 disciplines problem solving, d0 d1 d2 d3 meaning, 8d methodology steps, 8d interim containment action, 8d report checklist, 8d problem solving reference --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json