A quality escape is a defect that gets past your normal quality controls and is found only later, at the next operation, the customer's dock, or out in the field. Escape analysis is the investigation into two questions at once: why was it made, and why did we not catch it? Answer only the first and the defect can escape again through the same blind spot.
Most investigations stop at "why was it made," fix the process, and call it closed. Then a different defect slips through the same undetected gap and the customer is unhappy again. Escape analysis exists to prevent exactly that, by treating detection failure as a root cause in its own right. This guide covers the two-track method, how to find the escape point, and how to close both gaps for good.
What is a quality escape?
A quality escape, sometimes called a quality spill or a defect escape, is a nonconformance that passes through the controls meant to stop it and is detected downstream instead. The defect existed inside your process; your controls did not catch it. Where it surfaces, at the next internal operation, at final inspection, at the customer, or in service, tells you how far it traveled, and the further it goes the more it costs to contain.
The key idea is that an escape is always two failures, not one. Something in the process created the defect, and something in the detection system let it through. A part machined to the wrong dimension is a process failure. That wrong part reaching the customer is a detection failure on top of it. Escape analysis refuses to treat the second failure as an afterthought, because the detection gap is usually the more general problem: fix the one dimension and you fixed one defect, but fix the reason inspection missed it and you protect against a whole family of defects. It starts, as most quality investigations do, from a clean non-conformance report that captures what escaped and where it was found.
What are the two tracks of an escape root cause?
The two tracks are the occurrence root cause and the escape root cause, and a complete analysis answers both. The occurrence root cause explains why the defect was created: a tool wore, a setting drifted, a material was wrong, an instruction was unclear. The escape root cause explains why the defect was not caught before it left: the inspection did not check that feature, the sample missed it, the test did not stress it, the gage could not resolve it, or the standard was too vague to fail against.
This split is not a nice-to-have; it is built into the standard problem-solving disciplines. The 8D method requires both an occurrence cause and an escape cause at its root-cause step, precisely because addressing one without the other leaves the door open. You can reach each cause with the usual tools, a 5 Whys on the occurrence side and another on the escape side, or a broader root cause analysis when the paths are tangled. The discipline is running the tool twice, once for each question, and not letting a satisfying answer on the occurrence side end the investigation.
The two-track approach is standard in structured problem solving:
- Root cause analysis identifies the underlying cause of a nonconformance so it can be corrected and prevented not just the symptom (ASQ, Root Cause Analysis).
- The 8D discipline and automotive core tools require both an occurrence root cause and an escape (detection) root cause before a problem is considered solved (AIAG Quality Core Tools).
- Correcting only the occurrence cause leaves the detection gap open so a related defect can escape through the same undetected path again.
How do you find the escape point?
The escape point is the place in your process where the defect should have been caught first and was not. Finding it is a matter of walking the process forward from where the defect was created to where it was finally found, and marking every control it passed through untouched. Each of those controls is an escape point, and the first one is where the containment should have happened.
Say a part is machined out of tolerance at operation 20, passes an in-process check at operation 40, clears final inspection, and ships. The customer finds it. Walk it back: the defect was born at 20, and the first control that should have caught it was the check at 40. That check is the primary escape point. The final inspection is a secondary one. The occurrence investigation lives at operation 20; the escape investigation lives at operation 40, asking why a control that exists on paper did not stop a real defect.
Why do defects escape detection?
Escapes cluster around a short list of detection weaknesses, and naming yours is most of the fix. The inspection method simply cannot see the failure mode, so it was never going to catch it. The sampling plan is too thin, so a real defect fell between sampled parts. The test does not reproduce the condition that triggers the failure, so a part that fails in the field passes on the bench. The measurement system is unstable, so a marginal part reads as good on one check and bad on another. The standard is ambiguous, so an inspector had no clear line to fail against. Or the drift got normalized, and everyone quietly accepted parts that should have been rejected.
Each of these points at a different corrective action. A method that cannot see the defect needs a new method, not more training. A thin sampling plan needs more coverage or a shift to inline checking. An ambiguous standard needs a clear limit and a boundary sample. Matching the escape cause to the right kind of fix is what keeps the corrective action from being the useless default of "re-inspect and remind operators to be careful," which changes nothing.
How do you run an escape analysis?
Run it as a disciplined sequence so both tracks get closed and the fix is verified, not assumed.
- Contain first. Before any analysis, stop the bleeding: sort suspect stock, protect the customer, and mark the boundary of what might be affected. Containment is not the fix, but it buys time to investigate.
- Confirm and describe the defect. Get the actual part or clear evidence, and write exactly what is wrong and where it was found. A vague problem statement produces a vague root cause.
- Find the occurrence root cause. Walk back to where the defect was created and use 5 Whys or a fuller root cause analysis to explain why the process made it.
- Find the escape point and escape root cause. Walk forward to the first control that should have caught it, and explain why that control let it through, matching the reason to one of the known detection weaknesses.
- Correct both, then verify. Put a corrective action on each track, then prove each works: confirm the process no longer makes the defect and the control now catches a seeded example. Close the loop in your CAPA only after both are verified.
Containment and correction are different things, and treating a sort as a fix is a classic mistake; the distinction between containment and corrective action is worth being strict about. An escape analysis is not closed when the customer stops complaining. It is closed when both the making and the missing are provably fixed.
Why does an escape cost so much more than an in-house catch?
The cost of a defect climbs sharply the further it escapes, which is why escape analysis focuses on detection, not just prevention. A widely used rule of thumb in quality, sometimes called the 1-10-100 rule or the rule of ten, holds that a defect caught at the source costs a fraction of one caught at final inspection, which in turn costs a fraction of one that reaches the customer. The numbers are illustrative rather than exact, but the shape is real: catching a bad part at the machine is a quick reject, catching it at the customer means containment, sorting, expedited replacement, a corrective action report, and a dent in your scorecard.
That escalating cost is the business case for fixing the escape point, not just the process. Preventing the defect is ideal, but detection is your safety net for the defects you did not prevent, and a net with a hole in it is the difference between a scrap ticket and a customer complaint. Every escape point you close raises the floor on what your worst day looks like.
How escape analysis compounds over time
One escape analysis fixes one detection gap. A hundred of them, tracked together, redraw your whole control plan around where defects actually slip through instead of where you assumed they would. That only works if escapes are recorded consistently, with the escape point and escape cause captured every time, so patterns emerge: the same operation showing up as the escape point again and again is a control that needs rebuilding, not another reminder.
Getting that pattern requires the data to live somewhere durable and searchable, not on incident forms in a drawer. When escapes and their defect tracking are logged live at the source and rolled up automatically, the escape points stack into a picture you can act on, and the same record feeds the quality metrics your customer watches, including DPPM. That is the kind of institutional quality record Harmony builds for manufacturers on top of the systems they already run, with no rip-and-replace (see how CLS replaced paper logging). Fix both tracks every time, record the escape point every time, and the customer complaints that trigger these investigations get rarer. More on connected quality data is on our features overview.