D4 is not finished when you only explain why the defect was made. When the part reached the customer, you also owe an explanation of why your detection system let it through.
This page defines the escape point, shows how to find it from the process flow, and gives weak vs usable wording for supplier 8Ds. Follow your customer’s template and CSRs; some forms label this “non-detection cause” or “escape cause.”
Definition
- Root cause (occurrence): why the undesirable condition was created.
- Escape point: the nearest process control after that cause where detection should have worked — inspection, test, audit, poka-yoke, or system check — and did not.
Standard 8D training treats identifying and verifying the escape point as part of D4, then improving that control through permanent actions and prevention work.
Occurrence vs escape
| Occurrence | Escape | |
|---|---|---|
| Question | Why was it made? | Why wasn’t it caught? |
| Looks at | Process, material, design, setup, tooling | Control plan, inspection method, sampling, MSA, error-proofing |
| Weak answer | “Operator error” | “Inspector didn’t notice” |
| Stronger direction | Enabling process/system gap | Why that control could not detect the characteristic |
You can do solid occurrence analysis and still get the pack sent back if escape is missing or is only person-blame.
How to find the escape point
- Start from the occurrence location on the process flow.
- Walk forward through each detection opportunity: in-process check, final inspection, pack or dock audit, and so on.
- Ask at each step: Could this control have detected this failure mode with the method and frequency we actually use?
- The escape point is typically the closest control that should have worked but could not — wrong method, characteristic not listed, sampling too sparse, gauge incapable, optional check skipped, or a missing/bypassed poka-yoke.
- Verify with evidence: inspection instruction revision in force, control plan line, MSA or gauge type, sample size, and records from the affected window.
Example pattern (fictional): occurrence = seal orientation not confirmed after cleaning; escape point = final pressure-test instruction required a pressure hold but no seal-face visual check before pack, so a damaged seal that still held pressure briefly could ship.
Weak vs usable wording
Weak
- “Final inspection did not notice the problem.”
- “Human error at QC.”
- “Escape root cause: lack of attention.”
Usable
- “IP-HSG-88 Rev B required final pressure testing but did not require a seal-face visual check before packing. Review of IP-HSG-88 Rev B and pack records for lot HSG88-LOT-0726A confirmed the visual check was absent from the instruction.”
- “Control plan line for opening width specified attribute feel-check only; digital measurement was not required. Attribute check cannot resolve ±0.15 mm.”
Usable versions name the control, the gap, and the evidence. They give D5 something concrete to change.
Customer found the defect? Check that your D4 has a clear escape analysis before you send — free Accept / Conditional / Reject advisory with the gaps named.
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.
What D5 and D7 should change
Once the escape point is verified:
- D5 should include a permanent detection improvement for that point (method change, added check, poka-yoke, or moving detection earlier) — not only “remind inspectors.”
- D6 should define how you will know the new detection works (challenge parts, MSA, trial results, audit of live orders).
- D7 should update system documents: control plan, PFMEA detection where appropriate, work / inspection instructions, and a read-across to similar parts or lines.
Containment (extra 100% sort) can protect the customer while that work finishes. Sorting is not the escape-point corrective action.
Pre-send check with 8D Gate
If your customer found the defect and D4 has no clear escape analysis — or escape is only person-blame — fix that before you send.
Upload or paste your pack (PDF, DOCX, or Excel) and get an Accept / Conditional / Reject advisory with section ratings, missing evidence, and follow-up questions. Advisory only; it does not replace the customer’s 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.
Related writing guide: How to write D4 root cause in an 8D.
FAQ
- Is “escape point” the same as “escape cause”?
- Teams use both. “Escape point” emphasizes the location/control; “escape cause” or “non-detection cause” emphasizes why that control failed. D4 should cover both the where and the why.
- What if detection never existed for that characteristic?
- That can still be the escape story: the characteristic was not on the control plan or inspection instruction. Say that explicitly and fix detection in D5/D7.
- Do internal NCRs need an escape point?
- If the defect was caught inside your process, document which control caught it and whether earlier controls should have. Full customer-style escape analysis matters most when the defect left your facility.