First-Pass Inspection Escape Rate

A product passes its first inspection but fails a later check before shipment, so the defect escaped the first gate even though it did not reach a customer. First-pass inspection escape rate counts confirmed defects missed by an initial defined inspection and found later under a stated denominator.

Fabrico distinguishes first-pass yield from defect escape measures and ASQ classifies failures caught internally and externally within cost-of-quality concepts, so a first-gate escape measure needs its own checkpoint and denominator and is not identical to customer escape rate. Define the first gate by identifying the test, station, criteria and timestamp, since a vague "quality checked" label is not enough.

Define a confirmed escape, which requires later inspection or customer evidence linking a real defect that existed at the first gate and should have been caught there. Avoid hindsight assumptions, because a defect created after the first inspection was not an escape from that inspection, so trace timing and cause.

Choose the denominator, since all units passing first inspection, all confirmed defects, or all inspected units give different measures and the report should state which one. Track internal and external findings, because a second factory test and a customer return have different consequences though both may reveal first-gate misses.

Watch sampling, since a later audit that checks only a small sample will not find every escape, so report the inspection coverage and limitations. Reconcile defect identity, so that one physical defect reported by two later checks is not counted as two distinct escapes under a unit-based rule, and separate false positives, because an initial rejection that later proves good is a different quality-control problem measured as unnecessary holds.

Check test conditions, since a sensor can pass a bench test but fail under normal production speed or environmental conditions, so test realistic operation. Review calibration, because worn gauges or drifting thresholds can let defects through, and verify calibration and system versions.

Track defect types, as missing labels, wrong dimensions and cosmetic flaws may have different causes and a single aggregate hides the failing detection mode. Assess severity, because a rare safety-critical escape deserves urgent action even if its percentage is low, and map downstream detection, since a later station may prevent customer harm but the first-gate weakness should stay visible.

Avoid shifting blame, because an escape can reflect a poorly designed test, weak training or an upstream process defect, so investigate the mechanism. Use containment by holding potentially affected lots when needed, following sector-specific requirements and actual evidence, and review changes, since a new material or software rule can invalidate an old inspection test and the gate should be retested after meaningful changes.

Check repair outcomes, track trends by lot and compare first-pass yield, because reworked units should be retested under the applicable plan, one supplier batch can create many escapes, and a process can have high first-pass yield but still let dangerous rare defects through. Define the response, since escapes should trigger cause review, control validation and, where appropriate, customer or regulator handling under law and contract, validate the fix with seeded defects or controlled samples, keep linked records because missing records should not be counted as passes, and remember that for an owner the escape rate tells whether the first inspection is catching what it is supposed to catch, but only with a clear defect definition and later-detection coverage.