What Is First Pass Yield?
First pass yield measures the percentage of output produced correctly the first time, without rework or correction. It is one of the most direct indicators of process quality and efficiency.
Key Takeaways
- First pass yield is the percentage of units or tasks completed correctly first time.
- Low FPY means rework is consuming capacity that could be used for new output.
- Even a small FPY improvement can significantly increase effective throughput.
- Root cause analysis of defects is essential for sustainably improving FPY.
What first pass yield measures
First Pass Yield (FPY) is the percentage of units, tasks, or outputs that are completed correctly the first time — without requiring rework, correction, or rejection. Formula: FPY = (Units Produced Correctly on First Attempt ÷ Total Units Started) × 100%. If your team processes 200 invoices per day and 18 have errors that require correction, FPY is 91%. In manufacturing, FPY measures items that pass quality inspection without rework. In service businesses, it might track reports submitted without revisions, customer orders fulfilled without errors, or applications processed without rejection. High FPY is a direct indicator of process quality.
The cost of low FPY
Rework is expensive in ways that are often invisible in the accounts. Direct costs include the labour time spent correcting errors that could have been used for productive output. Indirect costs include the capacity consumed at the bottleneck stage (rework items typically flow back through the bottleneck), delays in delivering to the customer, and the management time spent investigating and resolving quality issues. A team with 85% FPY is spending roughly 15% of its capacity on rework — the equivalent of losing one person-day per week in a five-person team. Improving FPY from 85% to 95% effectively adds capacity without adding headcount.
Finding the root causes
To improve FPY sustainably, you must understand why defects occur. Common root causes in SMEs include: unclear or inconsistent process documentation; inadequate training, especially for new starters; complex handover points where context is lost between team members; time pressure leading to shortcuts; and poor-quality inputs (bad data, incorrect specifications from clients). A simple defect log — recording what went wrong, where in the process, and why — is the most practical starting tool. Even two weeks of logging typically reveals a small number of causes responsible for the majority of defects, allowing targeted fixes.
Setting FPY targets and tracking progress
For most business processes, an FPY of 95% or above is a reasonable target, though highly complex processes may have lower benchmarks. Start by establishing your current baseline, then set incremental improvement targets. Track FPY weekly or monthly, broken down by process step or work type — the aggregate figure hides which specific steps are generating most of the rework. Celebrate and document improvements so the team understands what changed and why. Over time, FPY data also informs decisions about automation: if a manual step has chronically low FPY despite training and process improvements, it may be a strong candidate for automation.