Table of Contents
A process can eventually produce the right result and still be expensive, slow, and frustrating to run. Work gets returned for missing information, documents need correcting, approvals happen twice, and teams spend their time repairing problems that should have been prevented earlier.
Final output quality does not always show this hidden effort. A case may be approved after three rounds of corrections. A product may pass inspection after rework. A client may receive the right deliverable after several avoidable revisions.
First pass yield reveals what happened before the final result. It measures how much work was completed correctly the first time, without rework, repair, correction, or resubmission. This guide explains how to calculate FPY, how it differs from overall yield and rolled throughput yield, and how to improve quality at the source.
Key takeaways
First pass yield measures right-first-time performance: FPY shows the percentage of work that meets requirements the first time it passes through a process.
FPY exposes hidden rework: A process may have an acceptable final yield while teams quietly spend significant time fixing errors and resubmitting work.
Quality at the source prevents downstream cost: The earlier a defect is identified, the less labor, time, and capacity it consumes.
FPY is different from overall yield: Overall yield may include work that eventually passes after correction. FPY counts only work that passes without rework.
Improvement requires context: Compare FPY by product, case type, process stage, team, and defect category rather than relying on one universal benchmark.
What is first pass yield?
First pass yield is the percentage of units, cases, or transactions that meet requirements the first time they pass through a process.
The formula is:
FPY = work completed correctly without rework ÷ total work entering the process × 100
For example, if 950 submissions enter a process and 900 pass without correction:
FPY = 900 ÷ 950 × 100 = 94.7%
The 50 submissions that required correction do not count as first-pass successes, even if they eventually pass.
FPY can be measured at a single process step or across a defined workflow. The important part is to establish clear start and end points, define what counts as a pass, and record rework consistently.
What does quality at the source mean?
Quality at the source means building checks into the point where work is created or handled instead of waiting until the end of the process to find defects.
In manufacturing, this may mean inspecting components during assembly. In customer onboarding, it may mean validating required documents before the request reaches compliance. In professional services, it may mean checking that a statement of work contains the required scope, pricing, and approvals before it reaches the client.
Quality at the source depends on three things:
- Clear requirements: People know what a complete and acceptable submission looks like.
- Early checks: Missing or incorrect information is identified before it moves downstream.
- Ownership: The person or team creating the work remains responsible for its quality.
The objective is not to add inspection everywhere. It is to prevent predictable defects from travelling through the process.
First pass yield versus overall yield and rolled throughput yield
These metrics answer different questions.
Overall yield measures the percentage of output that eventually passes, including work that needed rework.
Rolled throughput yield measures the probability that work passes every step in a multi-step process without rework.
Suppose a three-step process has the following FPY:
- Step 1: 97%
- Step 2: 94%
- Step 3: 91%
The rolled throughput yield is:
0.97 × 0.94 × 0.91 = 0.83, or 83%
Each step may appear reasonably healthy in isolation, but only 83% of work passes through the complete process without a rework event.
That gap is often called the hidden factory. It includes the informal work required to correct, chase, recheck, and reapprove items that should have moved through correctly the first time.
Why first pass yield matters
First pass yield connects quality with time, cost, capacity, and customer experience. A process that produces acceptable output only after repeated corrections is carrying hidden operational waste.
- Less rework: Teams spend fewer hours correcting forms, products, files, or transactions.
- Shorter cycle time: Work moves forward instead of returning to earlier stages.
- Higher throughput: Capacity is used for new work rather than repeated fixes.
- Lower cost of quality: Early defect prevention costs less than downstream correction.
- Better customer experience: Customers receive complete, accurate work sooner.
- Stronger process visibility: FPY shows where standards, inputs, or handoffs are failing.
Quality at the source supports these benefits by placing checks where work is created or handled. The earlier an issue is found, the less disruption it causes later.
Why first pass yield matters
FPY connects quality with capacity, cost, and customer experience.
- Lower rework: Fewer corrections consume less labor and process capacity.
- Shorter cycle time: Work spends less time moving backward through the process.
- Higher throughput: Teams can complete more new work instead of repairing previous work.
- Lower cost of quality: Defects are addressed before they create downstream expense.
- Better customer experience: Customers receive complete and accurate work sooner.
- Clearer improvement priorities: Defect categories show where the process needs attention.
A low FPY may indicate unclear requirements, poor inputs, weak quality gates, incorrect data, approval confusion, or a recurring process defect. The metric becomes useful when it is connected to the reason behind the failure.
Read related: Operational efficiency: principles, metrics, and practical examples.
How to calculate first pass yield and set a useful baseline
First pass yield measures the percentage of work that meets all requirements on its first attempt.
FPY = work completed correctly without rework ÷ total work entering the process × 100
For example, if 950 customer onboarding cases enter a workflow and 900 are completed without correction:
FPY = 900 ÷ 950 × 100 = 94.7%
Before calculating FPY, define:
- What counts as one unit, case, or transaction
- Where the process starts and ends
- What qualifies as a successful pass
- Which corrections, repairs, or resubmissions count as rework
- Which process stages should be measured separately
Do not rely on one universal “good FPY” percentage. Targets vary by process complexity, risk, industry, and customer expectations. Establish an internal baseline first, then compare FPY by product, case type, team, stage, or defect category.
As a directional reference, APQC reports a median finished-product first-pass quality yield of 95% across 5,453 companies. This is a benchmark for a specific measure, not a target for every process. See APQC’s first-pass quality measure.
Follow the steps to find calculate FYP:
1. Define the process and the unit
Decide what is being measured. It could be a manufactured unit, a completed form, a customer onboarding case, an invoice, a claim, or an approved deliverable.
Set a clear start and end point. For example, the process may start when a request is submitted and end when it is approved and ready for execution.
2. Define what counts as a pass
Write down the acceptance criteria before measuring performance.
A pass might require:
- All required fields completed
- Correct and current documents attached
- No data validation errors
- Required approvals captured
- Compliance checks completed
- No correction or resubmission required
3. Count total work entering the process
Record the total number of units, cases, or transactions that entered the defined process during the measurement period.
4. Count first-time successes
Count only the work that met all requirements on its first attempt.
Work that was corrected, repaired, returned, or resubmitted should not be included in first-pass successes.
5. Apply the formula
Divide first-time successes by total work entering the process, then multiply by 100.
6. Segment the result
Review FPY by:
- Product or service
- Process stage
- Team or role
- Customer segment
- Defect category
- Shift, location, or supplier
A single average can hide the area creating the most rework.
What is a good first pass yield percentage?
There is no universal FPY percentage that applies to every business.
A reasonable target depends on process risk, complexity, regulatory requirements, customer expectations, and the cost of failure. A simple internal request may have a different target from a regulated financial review or a safety-critical manufacturing process.
Establish an internal baseline first. Then set a realistic improvement target based on the process’s historical performance and the severity of its defects.
As a directional reference, APQC reports a median finished-product first-pass quality yield of 95% across a dataset of 5,453 companies. This should be treated as a benchmark for a specific measure and population, not as a universal target for every process. See APQC’s first-pass quality measure.
Common causes of low first pass yield
The most useful question is not only “How many items failed?” It is also “What made them fail?” Defect categories turn FPY from a reporting metric into an improvement tool.
How to improve first pass yield
The best first pass yield improvement programs make the right action easier and the wrong action harder.
Standardize inputs
Use structured forms, required fields, approved templates, and clear submission instructions. The goal is to prevent incomplete work from entering the process.
Validate information early
Check data, documents, dates, identifiers, and required evidence at intake. An error found at the beginning is easier and cheaper to correct than one discovered after several approvals.
Add quality gates at high-risk stages
A quality gate should stop work when a defined requirement is missing or incorrect. It should also explain what needs to be corrected and who owns the next action.
Clarify approval ownership
Define who reviews, who approves, and who handles exceptions. Approval work should not sit in a shared inbox without a named owner or deadline.
Route exceptions separately
Not every case should follow the same path. Low-risk work can move through a standard route, while high-risk or incomplete work receives additional review.
Capture defect causes
Record whether a failure came from missing information, unclear policy, incorrect data, system limitations, training gaps, or external delays.
Close corrective actions
A defect is not fully resolved when the immediate item is fixed. Track the corrective action until the underlying cause has been addressed and verified.
Review FPY by stage
End-to-end FPY tells you that a problem exists. Stage-level FPY helps identify where it enters the process.
Read related: Value stream mapping: how to see quality and delays across the full process.
A quality-at-source checklist
Before allowing work to move to the next stage, ask:
- Are all required fields complete?
- Are the documents current, readable, and correctly named?
- Has the correct policy or template been used?
- Has the right reviewer been assigned?
- Are exceptions clearly identified?
- Is approval evidence captured?
- Can the next team act without requesting more information?
- Has the defect category been recorded if the item was returned?
This checklist should be adapted to the process. It should be short enough to use consistently and specific enough to prevent avoidable errors.
Common FPY failure modes and rework loops
Low FPY usually points to a recurring process weakness, not one isolated mistake. Use the failure pattern to decide what needs to change.
- Incomplete inputs: Required information is missing, so the request is returned. Use required fields and clear instructions at intake.
- Incorrect documents: An outdated or invalid file reaches review. Add document-type, date, and completeness checks before acceptance.
- Unclear standards: Different people interpret “complete” or “approved” differently. Define acceptance criteria and examples.
- Approval delays: Work waits because no one knows who should decide. Assign roles, deadlines, and escalation paths.
- Manual data entry: Information is copied incorrectly between systems. Reduce duplicate entry and validate key fields.
- External participant delays: Clients, vendors, or partners cannot easily provide the required evidence. Give them a simple, structured submission path.
- Unclosed corrective actions: The immediate error is fixed, but the cause remains. Track corrective actions to completion and review whether the defect recurs.
A rework loop should be counted even when the item eventually passes. Otherwise, the final yield may look healthy while the process continues to consume avoidable capacity.
How to monitor FPY and turn trends into action
A single FPY percentage does not explain what is happening. Review the trend alongside the reasons for failure and the operational impact.
Track:
- FPY over time: Identify whether quality is improving, declining, or fluctuating.
- FPY by process stage: Find where defects first enter the workflow.
- Rework reason: Separate missing information, policy errors, system issues, and training gaps.
- Cycle time impact: See whether rework is creating longer queues or delayed completion.
- SLA impact: Identify whether corrections are causing missed commitments.
- Corrective-action closure: Confirm that known causes are being addressed.
- Customer impact: Connect FPY changes to complaints, satisfaction, or repeat requests.
Use short-interval reviews to address active problems and longer-term reviews to identify patterns. If FPY drops suddenly, check for a policy change, system release, supplier issue, demand spike, or new type of work.
Read related: Operational excellence KPIs and visual management and daily huddles.
How to build quality checks into the workflow
Quality checks work best when they are part of the process itself, rather than a final inspection after problems have already travelled downstream.
- Standardize intake: Use structured forms, required fields, approved templates, and clear submission instructions.
- Validate early: Check information, documents, dates, and identifiers before work reaches the next team.
- Add quality gates: Pause work when a required condition is missing or incorrect.
- Clarify ownership: Assign a named reviewer and define the expected response time.
- Route exceptions: Send high-risk or incomplete cases through an additional review path.
- Capture evidence: Record approvals, corrections, and decisions in the workflow.
- Close the loop: Track corrective actions until the underlying cause has been addressed.
For example, a vendor onboarding process can require a current insurance certificate before the request moves to approval. This prevents the compliance team from discovering the missing document at the end of the process.
How Moxo supports first pass yield improvement
First pass yield improves when quality checks happen inside the workflow rather than after the work has already moved downstream.
Moxo provides a business orchestration layer for coordinating people, documents, approvals, AI agents, and connected systems. The Moxo product platform can structure a process so participants know what to submit, reviewers know what to check, and exceptions have a defined path.
Moxo’s HAI Flow model combines human judgment with AI-supported execution. AI agents can prepare submissions, validate information, identify missing evidence, and route work to the right person. Humans remain accountable for exceptions, approvals, and decisions that require context.
For a customer onboarding process, the Moxo customer onboarding workflow can bring forms, file requests, approvals, reminders, and progress visibility into one structured flow. This helps reduce the incomplete submissions and approval gaps that often lower FPY.
The same approach works for vendor processes. The Moxo vendor onboarding workflow gives vendors a clear way to submit documents and confirmations while internal teams maintain ownership, compliance visibility, and an audit trail.
Professional services teams can use the Moxo professional services solution to manage deliverables, client feedback, approvals, and milestones. That is especially useful when first-time quality depends on several internal and external participants.
Moxo can also report on FPY, rework, cycle time, defect categories, and bottlenecks by process stage, team, role, or case type. Leaders can see whether an improvement is raising first-pass success or simply moving the rework somewhere else.
Build quality at the source with governed Moxo workflows.
How to monitor FPY over time
A monthly FPY number is not enough. Review the metric with the operating conditions around it.
Track:
- FPY trend over time
- FPY by process stage
- Rework rate
- Defect category
- Cost per rework event
- Cycle time impact
- SLA impact
- Customer or stakeholder impact
- Corrective-action closure
Use a daily or weekly review for active issues and a monthly review for trends. A sudden FPY decline may point to a new policy, system change, supplier issue, demand spike, or training gap.
Read related: Operational excellence KPIs: the metrics that connect quality to execution.
Build quality into the process from the start
First pass yield is valuable because it shows how much work succeeds without correction. It connects quality with cycle time, throughput, capacity, cost, and customer experience.
The strongest improvement programs do not wait for final inspection to reveal a problem. They define quality clearly, check it early, route exceptions intelligently, and learn from the reasons work fails.
Moxo supports this by giving teams a structured place to run quality checks, manage exceptions, and measure first-time performance across complex workflows.
Frequently asked questions
What is first pass yield?
First pass yield is the percentage of work that meets all requirements the first time it passes through a process, without rework, correction, repair, or resubmission.
How is FPY calculated?
Divide the number of items that pass correctly on the first attempt by the total number entering the process, then multiply by 100.
What is first pass yield in manufacturing?
In manufacturing, FPY measures the percentage of units that meet specifications at a process step without repair, rework, or adjustment.
What is a good FPY percentage?
There is no universal target. The right benchmark depends on the process, risk level, complexity, customer expectations, and historical internal performance.
How can first pass yield be improved?
Improve inputs, validate information early, standardize requirements, add quality gates, clarify ownership, route exceptions, and track defect causes.
What is the difference between FPY and rolled throughput yield?
FPY measures first-time success at one process step. Rolled throughput yield measures the probability that work passes every step in a multi-step process without rework.
