This page is a practical writing guide for D4: what the section must answer, how to separate occurrence from escape, how to show verification in the text, and how to link causes to D5. It reflects common automotive and industrial 8D practice. Always follow your customer’s required form and customer-specific requirements.
What D4 must answer
A usable D4 answers two questions when the defect reached the customer or the next process:
- Occurrence: Why was the defect made (or why did the condition occur)?
- Escape (non-detection): Why didn’t existing controls detect it before it left?
Both answers need to be verified, not only brainstormed. ASQ’s 8D summary puts it plainly: causes should be proved, not left as fuzzy brainstorming. Tools such as 5-Why and cause-and-effect diagrams organize thinking; they do not replace evidence.
If you only answer occurrence, reviewers often treat the analysis as unfinished. If you answer escape with “inspection didn’t notice,” you have usually restated the symptom of detection failure, not the cause. See also: Escape point in 8D: what it is and how to write it.
Separate occurrence and escape
Write them as two labeled blocks.
Occurrence (example pattern, fictional)
“Opening width on clip TC-BH-4412 exceeded USL because the progressive-die setup sheet did not require a first-piece verification of opening width after a die change. Setup record SR-260302 shows the change without a recorded first-piece check.”
Escape (example pattern, fictional)
“Final inspection IP-CLIP-12 Rev B required a go/no-go feel check only. The gauge could not discriminate opening width within the ±0.15 mm tolerance. The characteristic was not on the control plan as a measured check.”
Pattern: named document or control, specific gap, and evidence that belongs in the report.
Verify causes — don’t close on a team vote
A common weak pattern is: fishbone workshop → team agrees → D4 closed. Workshops are fine for candidates. Closing D4 means you tested those candidates.
Practical verification methods (pick what fits):
- Reproduce the defect by introducing the suspected condition, then remove it and see the defect stop.
- Compare is/is-not (lot, machine, shift, fixture, material lot).
- Check process records, setup sheets, tool life, and scrap data against the D2 problem window.
- Review the control plan / inspection instruction against the failed characteristic.
- Rule out alternatives briefly (“material lot X ruled out: cert and incoming check within spec”).
If you cannot verify yet, label the cause as a hypothesis with the next test and date. A labeled hypothesis is clearer than a firm root cause with no data.
What “operator error” is missing
“Operator carelessness,” “lack of attention,” and “operator error” usually read as unfinished analysis. People make mistakes when the process allows the mistake and when detection does not catch it.
Push past the person to a controllable system cause, for example:
- No verified setup standard or first-piece approval after changeover
- Ambiguous work instruction or missing step after cleaning/handling
- Fixture or tool wear without a defined check frequency
- Characteristic not on the control plan, or sampling too coarse for the risk
- Inspection method that cannot discriminate the tolerance
Training may appear later as a supporting action. It is rarely a complete permanent corrective action when the enabling process gap remains.
Drafting D4 now? Run a free pre-send readiness check on your pack — you get an Accept / Conditional / Reject advisory with the gaps named, before the customer reads it.
8D Gate is a free pre-send readiness advisory. It doesn't replace the customer's decision. We don't store your 8D body in our database; you can delete anytime. Anthropic processes the text for the review.
Evidence that belongs in the text
Reviewers read the document in front of them. “See attachment” and “available on request” are weak if key figures are not summarized in D4. Include method used, confirming data, alternatives ruled out, and separate occurrence and escape statements. Even with required attachments, put a short verified statement in the body.
Link D4 to D5
Every verified root cause should map to at least one D5 action that changes process, tooling, method, or detection — not only attention. Occurrence and escape each need actions. Specific D4 wording also makes D6 effectiveness criteria easier to write.
Pre-send check with 8D Gate
When D4 is drafted, a second skeptical read helps catch person-blame, missing escape analysis, and causes stated without evidence in the text.
Paste text or upload PDF, DOCX, or Excel. You get an Accept / Conditional / Reject advisory, section ratings, missing evidence, and questions to close gaps. It is a pre-send readiness check for your team, not a customer decision.
8D Gate is a free pre-send readiness advisory. It doesn't replace the customer's decision. We don't store your 8D body in our database; you can delete anytime. Anthropic processes the text for the review.
FAQ
- Does every 8D need an escape cause?
- When the customer or a downstream process found the defect, yes. For a defect caught at your own final inspection before shipment, escape analysis may be shorter — still explain why earlier controls missed it if relevant.
- Is a 5-Why enough?
- Yes, if each step is factual and the last step is controllable and verified. Many teams brainstorm with a fishbone, then 5-Why only verified branches (often occurrence, detection, and systemic legs).
- What if we cannot reproduce the failure?
- Document tests run, alternatives ruled out, the most probable cause with the evidence you have, and monitoring or containment that stays while confirmation continues.