First pass yield (FPY) is the percentage of units that complete a process step correctly the first time, with no rework, repair, or scrap. FPY = units good on the first attempt ÷ units entering the step. Unlike final yield, it counts rework as a failure, which is why it doesn't lie.

Plenty of plants report 99% yield while running a full-time rework crew. The trick is in the definition: if a unit fails, gets reworked, and eventually ships, most yield numbers count it as good. First pass yield refuses the laundering. It asks one blunt question, did the process do it right the first time?, and its answer is usually the most honest quality number in the building. This post covers FPY versus its softer cousins, the rolled throughput yield calculation with a worked example, and how to put FPY to work.

What is the difference between FPY, final yield, and scrap rate?

They differ in what they forgive. Final yield forgives rework; scrap rate forgives everything that isn't thrown away; FPY forgives nothing:

The gap between final yield and FPY is the hidden factory the inspection, rework, retest loop that consumes labor, floor space, and schedule while producing nothing new. That gap is a major component of cost of quality which the American Society for Quality notes commonly runs 15–20% of sales revenue, up to 40% at poor performers. A plant reporting 99% final yield and 84% FPY is paying for the difference every day; the yield report just declines to mention it.

FPY vs final yield: the rework loop is the difference (hypothetical numbers)One step, two yields (hypothetical: 100 units in)100 inPROCESS +FIRST INSPECTION88 goodfirst time9 reworked → re-enter → eventually pass3 scrappedFinal yield = 97/100 = 97% · First pass yield = 88/100 = 88%
The rework loop, hypothetical numbers. Final yield counts the 9 reworked units as good; FPY does not. The 9-point gap is the hidden factory.

What is rolled throughput yield?

Rolled throughput yield (RTY) is the probability that a unit passes every step of a multi-step process right the first time: multiply the FPY of each step. RTY = FPY₁ × FPY₂ × … × FPYₙ. Like OEE's three factors the yields compound, and the compounding is brutal at scale.

A worked example with hypothetical numbers. A line has four stations, each with a respectable FPY:

StationFPYRunning RTY
1 · Forming97%97.0%
2 · Assembly95%92.2%
3 · Finishing98%90.3%
4 · Pack-out inspection96%86.7%

Every station clears 95%, yet only 86.7% of units sail through untouched, about one unit in eight needs intervention somewhere. Stretch the same math to a 10-station process at 97% each and RTY drops to about 74%. This is why multi-step operations with "great" station-level yields still drown in rework, and why RTY, not any single station's FPY, is the number that describes what the customer's order actually experiences.

RTY across four stations: good stations, compounding loss (hypothetical)Rolled throughput yield across 4 stations (hypothetical)1 · FormingFPY 97%2 · AssemblyFPY 95%3 · FinishingFPY 98%4 · Pack-outFPY 96%100%80%97.0%92.2%90.3%RTY 86.7%Every station ≥95%, yet ~1 in 8 units needs intervention somewhere on the line.
RTY compounds station FPYs: 0.97 × 0.95 × 0.98 × 0.96 = 86.7%. Hypothetical numbers, honest arithmetic.

How do you start measuring first pass yield?

Define "first pass" at each step, count entries and first-time passes, and resist every temptation to soften the definition. The sequence:

  1. Map the steps that can fail. Every station with an inspection, test, or the possibility of rework gets its own FPY. Lumping steps together hides which one bleeds.
  2. Define "good, first time" per step, in writing. Any rework, repair, retest, re-run, or adjustment-after-failure counts as a first-pass failure, even a ten-second touch-up. Fuzzy definitions are how FPY drifts back into final yield.
  3. Count units in and first-pass units out. From test records, inspection logs, or operator tallies at the station. Rework must be logged where it happens, not reconstructed at month-end.
  4. Attach defect codes to every failure. An FPY number without reasons is a scoreboard without a game plan; a short code list feeding defect tracking turns it into a Pareto.
  5. Compute FPY per step and RTY for the line, weekly at minimum. Post both where the crew can see them.
  6. Work the worst step's top defect code with root-cause tools, SPC on the variable that drives it, and poka-yoke where the failure mode is human error. Then re-measure.

Where should you measure FPY first?

Start where the failures are expensive, not where the counting is easy. Three placements pay fastest:

One caution: do not launch FPY as a people metric. The first honest measurement usually looks worse than anyone expected, and if the number is used to grade operators, the logging will quietly improve instead of the process. FPY measures the process, design, materials, settings, standards, and the fastest way to kill it is to make it a scoreboard for blame.

How does FPY connect to OEE and downtime?

FPY is the Quality factor of OEE wearing its own uniform. OEE's Quality term counts first-pass good units over total units for exactly the reason FPY does: rework is a loss even when the unit is saved. The two metrics should be built from the same records, if OEE Quality and station FPY disagree, one of the counting rules is wrong, and finding which one is a useful afternoon. (The OEE calculator makes the Quality factor's arithmetic explicit.)

The rework loop also feeds back into the time ledger. Reworked units consume capacity twice, rework stations starve or block their neighbors, and defect investigations stop lines, losses that land in the six big losses as quality losses and in the downtime log as quality stops. A falling FPY is frequently the earliest warning that downtime and schedule misses are coming, which is why it belongs on the daily board, not just the monthly quality review.

One practical note on data: FPY is only as honest as rework logging, and paper rework logs are where honesty goes to die, a touch-up at the station takes ten seconds, and writing it down takes thirty. Plants that digitize capture at the station, the way Harmony turns paper checks and quality logs into live, searchable records feeding root-cause analysis (see the platform), find their real FPY within weeks. It is usually lower than the reported one, and knowing that is the beginning of fixing it.