Detection rate is the number quality engineers report. Escape rate is the number that actually costs money. The two are not the same, and conflating them is one of the most persistent measurement problems on inspection lines.
Detection rate tells you how many defective parts your inspection system flagged. Escape rate tells you how many defective parts left your facility without being flagged — and reached a downstream customer, an assembly operation, or a field deployment. You can have a detection rate of 97% and still be shipping a volume of bad parts that triggers warranty claims, line stops, or worse.
We've spent time with quality engineers at stamping, machined parts, and PCBA lines who are under pressure to prove their inspection investments are working. Almost universally, they have strong visibility into what their systems detect. Almost none of them have a reliable measure of what their systems miss.
Why detection rate isn't the right numerator
The classic detection rate formula is: (defects detected) / (total defects present). The problem is that "total defects present" is never directly observable. You're estimating it, usually from a combination of incoming quality data, statistical sampling, and field feedback. Every one of those sources has a lag. Field returns might surface 60 to 90 days after the part shipped. Incoming quality audits from your customer happen on their schedule, not yours.
Escape rate flips the measurement: instead of asking what fraction of defects you caught, you ask what fraction of defective parts left your building uninspected. The numerator is the uncomfortable number — defective parts that passed your inspection gate.
To measure escape rate directly, you need a secondary measurement point downstream of your inspection station. That can be:
- An end-of-line functional test with logged failure data
- A sampling audit table at shipping — pulling N parts per lot and re-inspecting against a tighter standard
- Customer receiving inspection data, if your customer shares it back to you
- Field return data tagged to manufacturing lot numbers
Each method has resolution limits. Functional tests catch only defects that affect function; cosmetic or dimensional escapes often pass. Sampling audits have inherent confidence intervals — a 5% sample from a lot of 2,000 means you're estimating escape rate with a 95% CI of roughly ±2% at best. Customer receiving data is the most accurate but the slowest and most politically charged to obtain.
Constructing an escape rate measurement baseline
Before you introduce any new inspection system, you need a baseline. Without it, you can't quantify improvement and you can't size the business case.
The most practical baseline approach we've seen work at growing manufacturers is a dual-source audit run for 4 to 6 weeks before a pilot inspection system goes live. During that window, you run your existing inspection process as-is, but you add a 100% re-inspection audit on a random daily sample — typically 3 to 5% of daily output, re-inspected at a controlled station by your best inspector under consistent lighting conditions.
The key discipline: the auditor must not know whether a part was originally passed or failed by the line inspector. Blind auditing eliminates confirmation bias. If the auditor knows a part "passed," they'll be less likely to flag marginal defects on it.
Log the following per part in the audit sample: part serial or lot, original line disposition (pass/fail), audit disposition (pass/fail), defect type if found, shift, and operator ID for the original inspection. Four weeks of this data gives you a statistically useful picture of what's actually escaping.
The ratio you want: (parts audited as defective that were originally passed) / (total parts audited). That's your escape rate. It's not a detection rate. It's the answer to "what fraction of parts that left the inspection gate defective?"
The field return connection
Audit-based escape rates measure escapes from your inspection gate. Field return data measures escapes from your entire quality system — including any downstream assembly test or outgoing audit. These are different numbers, and both matter.
The discipline required to connect field returns back to escape rate is lot traceability. Each defective return needs a lot or serial number that maps back to a production date, shift, machine, and inspection result. Without that linkage, field data is anecdote. With it, you can identify whether escapes cluster by shift, by cavity in a die or mold, by day of the week, or by inspector.
Lot traceability is often missing or partial at smaller manufacturers. When we run pilots, this comes up frequently: the quality team has strong per-part inspection data but no reliable way to link a field return back to a specific production run. That makes it impossible to calculate a meaningful field escape rate. If this describes your operation, fixing lot traceability is actually a prerequisite to measuring escape rate honestly — and it's work that pays off regardless of what inspection technology you run.
Using escape rate to size an inspection investment
Once you have an escape rate baseline, the cost calculation is straightforward. Let's walk through a realistic example.
Suppose you run a machined aluminum housing at 160 parts per minute, two 8-hour shifts, 5 days per week. That's roughly 768,000 parts per month. Your audit-based escape rate is 0.6% — about 4,600 defective parts per month that pass through your inspection gate.
Now you need to assign a cost to each escape. This number varies enormously by part and industry: an escaped cosmetic defect on a consumer electronics housing might cost $2 to $8 per occurrence in rework or return processing; an escaped dimensional defect in an automotive subassembly can run $50 to $300 per occurrence once you account for assembly rework, customer claim handling, and debit notes. The range is wide. Use your own data.
At $25 per escaped defect (a conservative middle ground for a machined component going into a mid-tier assembly), your monthly escape cost is roughly $115,000 at 0.6% escape rate. If inline AI inspection brings that to 0.08%, your monthly savings from escaped defects alone is about $100,000. That sizing exercise is how you justify a pilot.
We're not saying every line will show those numbers. The math only works if you start with honest baseline data. Lines with very low existing escape rates, cheap consequence-per-defect costs, or low volumes will show a much smaller case for automation. The point isn't to prove a predetermined conclusion — it's to have a number that can be tested against reality after the pilot runs.
What changes when you add inline AI inspection
When Procunit goes live on a line, the escape rate measurement problem gets easier and harder at the same time. Easier because you now have granular, timestamped, logged inspection data on every part — not a sampling estimate. Harder because the baseline you set with manual or legacy AOI inspection is no longer comparable apples-to-apples.
What we do in pilots: run a parallel audit period for the first two weeks where every part rejected by Procunit is physically pulled and auditor-confirmed, and every part passed by Procunit is subject to a 5% sampling audit. That gives you a real-time view of the model's false negative rate (escapes through the new system) during the learning period.
The most important metric we track in early deployments isn't detection rate. It's the audit confirmation rate on passed parts. If Procunit passes 1,000 parts and the auditor re-inspects 50 and finds 0 defects, that's strong signal. If the auditor finds 2 defects in 50 re-inspected parts, that's a 4% escape rate through the model, which tells you what to retrain on.
Instrumenting your line for ongoing measurement
Escape rate measurement shouldn't be a one-time baseline exercise. It should be a continuous quality metric with control limits, the same way you'd track Cpk or first-pass yield.
The practical instrument for ongoing escape rate monitoring is a lightweight audit station at the point of shipment or at the delivery to the next process step. It doesn't need to be 100% — a statistically designed sampling plan (ANSI/ASQ Z1.4 attribute sampling is the standard reference for this) will tell you how many parts to pull per lot at what AQL level to detect a given escape rate with specified confidence.
The control metric: track defective-per-lot-audited over time. When it trends up, something changed — either the production process drifted, or the inspection system degraded, or the part mix shifted. Any of those hypotheses requires a different response. The audit data doesn't tell you which one; it tells you there's a signal worth investigating.
If you're running Procunit, model confidence drift — the gradual shift in per-prediction confidence scores as the production environment changes — is an early indicator that escape rate may be about to trend upward. We surface that in the quality dashboard so you see it before the audit data confirms it. The audit data is the ground truth. The confidence trend is the leading indicator.
Escape rate is a harder metric to track than detection rate. It requires a second measurement point, real lot traceability, and consistent audit discipline. But it's the only number that directly connects your inspection investment to the cost it's supposed to prevent. Everything else is a proxy.