# Supplier 8D Discipline D0 to D8 Review Reference > Source: https://netray.co/tools/supplier-8d-discipline-d0-d8-review-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A reviewer's guide to each 8D discipline, with the evidence to expect from a supplier and the weak answers that should be sent back. ## Category quality ## Audience - Supplier quality engineer - Buyer - Quality manager ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Discipline **Key:** disc **Type:** text #### Name **Key:** name **Type:** text #### What the supplier should provide **Key:** expect **Type:** text #### Reviewer question **Key:** ask **Type:** text #### Weak answer to send back **Key:** weak **Type:** text **Rows:** #### Plan and emergency response **Disc:** D0 **Expect:** Confirmation the complaint was received and an owner assigned, with emergency actions to protect the customer **Ask:** Who owns this and when was the first response sent? **Weak:** No named owner or response beyond the acknowledgement date #### Form the team **Disc:** D1 **Expect:** Named team leader and members with the right functions **Ask:** Is the process owner on the team? **Weak:** Quality department only, no one from production or engineering #### Describe the problem **Disc:** D2 **Expect:** Who, what, where, when, how many, with part number, lot and defect description measured against the requirement **Ask:** Is the defect described against the drawing requirement, with quantities? **Weak:** Part was bad or a copy of the complaint text #### Interim containment action **Disc:** D3 **Expect:** Sorting of stock at the supplier, in transit and at the customer, with results and a way to identify certified parts **Ask:** Where was stock checked and how are good parts marked? **Weak:** Only the customer stock was sorted, or no results recorded #### Containment verification **Disc:** D3 **Expect:** Evidence that containment is effective, for example inspection records and sort counts **Ask:** How many parts were sorted and how many rejected? **Weak:** Statement that parts were checked with no counts #### Occurrence root cause **Disc:** D4 **Expect:** Verified cause of why the defect was made, found with a method such as 5 Whys, fishbone or is/is not analysis **Ask:** How was the cause verified by turning it on and off? **Weak:** Operator error or training with no process cause #### Escape root cause **Disc:** D4 **Expect:** Verified reason the defect was not detected at the supplier **Ask:** Why did final inspection and the control plan not catch it? **Weak:** Not addressed at all, only the making of the defect is analysed #### Systemic root cause **Disc:** D4 **Expect:** Management system gap behind the occurrence and escape, such as FMEA or change control **Ask:** Which procedure or system allowed this? **Weak:** Absent, so the same gap will reproduce the defect on other parts #### Choose permanent corrective actions **Disc:** D5 **Expect:** Actions that remove the root causes, with owners and dates **Ask:** Does each action link to a verified cause? **Weak:** Retrain operators, or increase inspection as the only action #### Verify before launch **Disc:** D5 **Expect:** Evidence the chosen action works before full implementation, such as a trial run **Ask:** Was the action tested on a trial lot? **Weak:** No evidence the action fixes the cause #### Implement and validate **Disc:** D6 **Expect:** Date of implementation, records of changed documents and new data showing the defect is gone **Ask:** What data shows the fix is working? **Weak:** Statement that the action is implemented with no data #### Remove interim containment **Disc:** D6 **Expect:** Defined criteria for ending containment and a decision record **Ask:** On what evidence was containment stopped? **Weak:** Containment dropped on a date with no criteria #### Prevent recurrence **Disc:** D7 **Expect:** Updated PFMEA, control plan, work instructions and checks across similar parts and lines **Ask:** Which documents changed and which similar parts were checked? **Weak:** Only the affected part number is covered #### Lessons learned **Disc:** D7 **Expect:** A record of what was learned and shared with other sites or products **Ask:** Where is it recorded for reuse? **Weak:** Blank or generic text #### Recognise the team and close **Disc:** D8 **Expect:** Customer agreement to close, with effectiveness monitoring plan **Ask:** How long will you monitor and what is the trigger to reopen? **Weak:** Closed by the supplier with no customer confirmation #### Effectiveness check **Disc:** D8 **Expect:** Follow-up data after a defined period, such as three months of ppm or no repeat lots **Ask:** What was the defect rate in the months after closure? **Weak:** No follow-up date set **Notes:** The eight disciplines D1 to D8 are common practice and D0 was added in later versions of the method. Customers may use their own form. Use this as a review aid and follow your customer's supplier quality manual where it differs. ## Content **Intro:** A supplier 8D is only as good as its root cause and its escape analysis. This reference lists each discipline, what a supplier should provide, and the weak answers that should be sent back before you close a corrective action. **Sections:** #### How to use this guide **Body:** Open the supplier's 8D report next to the table and search for the discipline you are reviewing, for example D4. Compare the report to the expected content, then use the reviewer question as your reply when the answer is thin. Export the table to Excel and add a column for accept or reject if you want a record of each review round. Many teams reject D4 and D7 most often, so spend your time there. **Bullets:** - Search by discipline, such as D3 or D4 - Use the reviewer question as written feedback - Look for escape and systemic causes, not only occurrence - Export the list for your review record #### Why root cause is where reports fail **Body:** A strong D4 separates three questions: why the defect was made, why it was not detected, and why the system allowed it. Reports that stop at the first question tend to produce corrective actions that only retrain people. Ask the supplier to show how the cause was verified, for example by reproducing the defect when the cause is present and removing it when the cause is fixed. If a cause cannot be verified, it is still only a hypothesis. #### Containment and closure **Body:** Containment in D3 should cover stock at the supplier, in transit, at your plant and at your customer if parts have shipped. Ask for sort counts and how certified parts are marked. At D8, do not close on the supplier's word. Agree an effectiveness window, commonly a few months or several lots, and reopen the case if the defect returns. Record the closure date and the evidence in your supplier file. #### Common mistakes by the buyer **Body:** Buyers sometimes accept 8Ds that arrive on time but have no data, set response deadlines the supplier cannot meet with a real root cause, or close the case before containment is removed with criteria. Another mistake is not scoring the response quality. Track timeliness and quality of 8D responses on the supplier scorecard so poor reports show up in the next review. **Bullets:** - Do not trade quality of analysis for speed alone - Ask for data at D3, D4 and D6 - Track 8D quality on the scorecard - Reopen cases on repeat defects **Cta:** If you receive many 8D reports by email, we can build an assistant that checks each one against these questions and links it to the receiving inspection history in your ERP. **Faq:** #### What is the difference between 8D and CAPA? **Answer:** 8D is a structured team problem-solving format, often used for customer and supplier complaints. CAPA is a broader quality system process that may use 8D, fishbone or other tools. An 8D can serve as the investigation record inside a CAPA. #### Why is there a D0? **Answer:** D0 was added to cover the planning step and emergency response before the team is formed. It records the trigger, who is responsible and the immediate actions to protect the customer. Some forms leave it out, which is acceptable if the content appears elsewhere. #### How long should a supplier have to respond? **Answer:** Many customers ask for containment within 24 hours, an initial root cause in a few days and the full report in around 30 days. Your supplier quality manual or agreement should state the actual times. Allow longer for complex failures. #### Should every defect need an 8D? **Answer:** No. Reserve 8D for significant, repeat or safety related failures. Minor one-off defects can be handled with a short corrective action request. Setting a threshold avoids filling the supplier's engineers with paperwork and protects the quality of the major reports. ## Search terms 8D report review checklist, 8D D0 to D8 explained, supplier 8D report template review, 8D root cause review, supplier corrective action 8D, 8D disciplines list, how to review a supplier 8D, 8D containment root cause --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json