iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
In a first-pass 8D review, a customer quality engineer needs to see a measurable problem and its scope, evidence that interim containment protects the customer, and a verified link from causes to corrective actions. Treat the first five minutes as a triage heuristic—not a universal checklist or a substitute for reviewing the full investigation. Customer forms, portals, deadlines, and acceptance rules differ.
1. Can you identify the defect and its scope?
Start with the problem description, commonly D2. It should state what failed, which part or process is involved, where and when the issue occurred, and how much product may be affected. Quantified evidence—such as affected quantities or a defined time window—lets the reviewer assess exposure; a label such as “quality issue” does not.
Siemens describes D2 as building an information base around who, what, where, when, and how much. Its 8D report guidance is a useful reference for the questions a clear problem statement should answer.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems2. Is the customer protected while the investigation continues?
Review interim containment, commonly D3, as immediate protection—not proof that the permanent cause has been corrected. The report should identify the affected population covered, the actions taken, and evidence that those actions are effective. A containment claim without a defined scope or effectiveness evidence leaves the customer unable to judge whether suspect product may still escape.
Siemens describes D3 as protecting internal and external stakeholders and validating containment effectiveness. Graco also includes containment in its supplier corrective-action process. Those sources support the value of containment evidence; they do not establish one universal containment method or acceptance threshold.
3. Does the investigation explain both how the defect happened and how it escaped?
Check that the report distinguishes two questions:
- Occurrence: Why was the defect created?
- Escape: Why did the supplier’s controls fail to detect it before it reached the customer?
These are separate cause paths, and an explanation for one does not answer the other. Siemens recommends verifying a proposed cause by checking whether the problem is present when the cause is present and absent when the cause is absent. A plausible narrative without a test or supporting process evidence is not a demonstrated cause.
Rank #2
4. Can you trace each verified cause to an action and validation?
For every cause, look for a corresponding corrective action with an owner, timing, implementation evidence, and a measurable validation method. The chain should be traceable: verified cause, selected action, evidence the action was implemented, and results showing whether it worked.
Siemens says actions should eliminate the root cause, be checked for unintended effects, and be validated using the original measurable indicator. If the report does not connect an action to a cause or show how effectiveness will be judged, the reviewer cannot tell whether the proposed fix addresses the demonstrated failure.
5. Does the report show how recurrence will be prevented?
Look for changes to the relevant system, procedure, control, or standard, and evidence that similar products or processes were considered. In Siemens’ 8D framing, D7 addresses the systems and standards that allowed recurrence and standardizes process changes. A fix confined to the individual defective batch may not show that the conditions enabling recurrence have been addressed.
6. Does the submission follow this customer’s instructions?
Use the actual SCAR, required form, portal, due date, and requested evidence as the authority for submission and acceptance. There is no universal customer deadline or approval workflow established by these references.
For example, Graco’s supplier corrective-action instructions say a supplier SCAR response must be complete by its specified due date, include a complete 8D, and be submitted to the Divisional Supplier Quality Engineer for validation and approval. That is Graco’s process, not a rule for every customer. The VDA QMC’s 2021 English-language reference, Quality Management in the Automotive Industry, describes the 8D report as an information document from supplier to customer.
Recommended Free Tools
What a first-pass review can—and cannot—tell you
A quick review helps identify whether the report makes exposure, protection, causes, actions, and recurrence prevention assessable. It is triage, not a technical audit of the full investigation. Whether a particular report is acceptable depends on the requesting customer’s current instructions and the evidence the case requires.
Quick Recap
Best Value
- The Certified Quality Engineer Handbook, 4th Edition
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
