First-Pass Yield for Small Manufacturers: How to Measure It by Work Order and Use It to Cut Hidden Rework Costs

First-pass yield sounds like a metric for large plants with quality engineers, dashboards, and a full-time analyst. In a small shop, it can feel like one more number you do not have time to track. But if you already run work orders, record quantities, and note when parts go back for touch-up, remake, or inspection holds, you already have most of what you need. For a complete overview, see our manufacturing execution system software guide.

That matters because rework is rarely just a quality problem. It steals machine time, absorbs labor, creates schedule disruption, hides true job profitability, and makes on-time delivery harder than it should be. When you measure first-pass yield by work order instead of only looking at monthly scrap totals, you can see exactly which jobs, parts, machines, or process steps are creating the most hidden cost. Then you can fix the real causes without adding complicated reporting.

What first-pass yield actually means

First-pass yield, often shortened to FPY, measures how many units make it through a process correctly the first time, without rework or repair. In other words, it answers a simple question: Of the parts we made on this work order, how many passed through production as expected on the first try?

A simple work-order-level formula is:

First-Pass Yield = Good units completed without rework ÷ Total units processed

Example:

• Work order quantity processed: 100
• Units accepted the first time: 92
• Units sent to rework: 6
• Units scrapped: 2

FPY = 92 ÷ 100 = 92%

This is different from final yield. If those 6 reworked parts are eventually saved and shipped, final yield may look much better. But FPY shows the hidden cost of not making the part right the first time. That is why it is so useful. It exposes friction that final shipment numbers can hide.

If your shop already tracks scrap but not rework, you are only seeing part of the problem. Scrap is visible because material is lost. Rework is often less visible because the order still closes. But the labor, machine occupancy, queue delays, and inspection burden are real.

For broader context on yield terminology, Wikipedia has a decent overview of first-pass yield, but for small manufacturers the practical value comes from tying it directly to work orders and day-to-day decisions.

Why small manufacturers should measure FPY by work order

Monthly quality summaries have their place, but they are usually too broad to drive action in a small operation. A shop owner needs to know where problems start, not just that quality was worse this month than last month.

Work-order-level FPY helps you answer questions like:

• Which customers, part numbers, or revisions create the most rework?
• Are problems concentrated on one machine, shift, operator, or outside process?
• Which jobs look profitable until rework hours are included?
• Are rushed jobs more likely to fail first pass?
• Do setup errors, unclear travelers, or missing specs lead to repeat defects?

That last point is important. Many small shops do not have a quality data problem so much as a workflow problem. If operators are working from paper packets, outdated prints, or inconsistent instructions, first-pass yield will suffer. If that sounds familiar, see how digital traveler packets can reduce setup and first-article mistakes.

FPY also complements other operational metrics. OEE tells you how effectively equipment is running. Downtime tracking shows where availability is being lost. But FPY shows whether the output is right the first time. Together, those measures provide a much more honest picture of capacity. If useful, you can pair FPY with FactoryOS resources like the free OEE calculator and this guide on using downtime codes to uncover hidden capacity.

The simplest way to calculate first-pass yield from work-order data

You do not need a complex quality system to start. For most small shops, FPY can be calculated from a short list of fields already tied to the work order.

The minimum data you need

• Work order number
• Part number and revision
• Total quantity processed
• Quantity accepted on first pass
• Quantity sent to rework
• Quantity scrapped
• Optional: machine, operator, shift, operation, customer, and defect code

If you do not currently record “accepted on first pass” explicitly, you can derive it:

First-pass good quantity = Total processed − Rework quantity − Scrap quantity

Then calculate:

FPY = First-pass good quantity ÷ Total processed

A practical table example

Even this basic view is useful. WO-1844 may not create the highest scrap cost, but it clearly creates a lot of disruption. Five reworked parts on a 25-piece order is a warning sign, especially in a high-mix, low-volume environment where every hour of machine time matters.

How to handle multi-operation work orders

Many shops do not make a part in one step. A work order may go through cutting, machining, deburring, welding, coating, assembly, and final inspection. In that case, there are two practical ways to use FPY.

1. Work-order FPY

This is the easiest place to start. Measure whether the finished units on the work order were completed without rework anywhere in the routing. It gives you a simple, management-level signal.

2. Operation-level FPY

Once you want better root-cause visibility, calculate FPY at key operations. That helps you find where defects are introduced.

Example:

• Operation 10: Saw cut, FPY 99%
• Operation 20: CNC mill, FPY 88%
• Operation 30: Deburr, FPY 98%
• Operation 40: Final inspection, FPY reflects escapes caught late

In this example, the milling step deserves attention. Without operation-level FPY, the whole work order just looks “messy.” With it, the likely source becomes obvious.

If you want to support this kind of tracking consistently, digital work-order systems make it much easier than paper. FactoryOS has written about replacing paper work orders and tracking production without spreadsheets for exactly this reason.

What counts as rework, and what should not

Small shops often get inconsistent numbers because people define rework differently. Before rolling out FPY, set a simple rule everyone understands.

A practical definition is:

Rework is any additional labor or processing required because the part did not meet requirements on the first pass through that operation or work order.

This can include:

• Extra machining to correct dimensions
• Deburring repeated because finish was not acceptable
• Assembly disassembled and rebuilt
• Additional inspection caused by a suspected defect
• Remake of paperwork or labels when traceability errors block release

This usually should not include:

• Standard multi-step routing that was planned from the start
• Normal first-article approval before production begins
• Customer-approved engineering changes that altered the original scope

Consistency matters more than perfection. You want comparable data from one work order to the next.

How FPY reveals hidden rework cost

The biggest mistake shops make is treating rework only as a quality annoyance. In reality, low FPY affects labor, machine time, scheduling, and customer service all at once.

Labor and machine time

Every reworked part consumes time that was not in the estimate. That time could have been spent on the next order. If your shop is busy, poor FPY is often a hidden capacity problem.

Schedule disruption

Rework bumps planned work off the machine. It also creates priority confusion: should the team finish the next scheduled order or recover the previous one? This is one reason low-FPY shops often feel overloaded even when booked capacity looks reasonable on paper.

Underestimated job profitability

A work order may close and invoice normally, but if the team spent three extra hours correcting parts, margin just disappeared. Measuring FPY by work order helps you identify jobs that consistently consume more effort than the quote assumed.

Delivery risk

A job with heavy rework may still ship complete, but only by creating overtime, expediting outside services, or delaying another customer order. That is why FPY should be reviewed alongside due-date performance.

If you want to put a dollar figure on quality losses, the scrap cost calculator can help with material loss, but be aware that rework often costs more in labor and schedule impact than scrap alone.

How to find the jobs and processes causing the most rework

Once you start capturing FPY by work order, do not stop at the average. Averages can hide the problem jobs. Instead, sort and group your data in ways that make action easier.

Look at the worst work orders first

Start with the 10 work orders with the lowest FPY over the last 30 to 90 days. For each one, ask:

• What defect occurred?
• At which operation?
• Was the issue setup-related, material-related, tooling-related, or instruction-related?
• Did the same part number or revision fail before?

Group by part number and revision

If the same part repeatedly shows weak FPY, the issue may be in process design, fixturing, tolerance stack-up, or documentation. Revision-level grouping is important because a drawing change can quietly introduce a new problem.

Group by machine, operation, or cell

If one machine or process step consistently has lower FPY, investigate calibration, tooling condition, preventive maintenance, or setup standardization. The NIST Manufacturing resources are a good reference point for process improvement and quality practices relevant to U.S. manufacturers.

Group by operator or shift carefully

This can be useful, but it should be handled constructively. The goal is not to blame people. Often a lower FPY by operator points to training gaps, unclear work instructions, or inconsistent setup handoffs.

A simple weekly review process for small shops

You do not need a formal quality meeting with slides and charts. A 20-minute weekly review is enough to make FPY useful.

1. Pull all closed work orders from the last week.
2. Calculate FPY for each order.
3. Highlight exceptions, such as any order below your threshold. For many shops, that might be 95% or 98%, depending on process and product.
4. Identify the top recurring defect reasons.
5. Assign one corrective action per major issue, with an owner and due date.
6. Check whether last week’s actions worked.

Keep it simple. The point is to create a closed loop between data and action. If the review does not result in one or two concrete changes, the metric will become background noise.

Common causes of low first-pass yield in small shops

• Unclear work instructions: Operators interpret the same job differently.
• Outdated prints or revisions: Good parts become bad parts because the packet is wrong.
• Weak setup control: First-piece approval is inconsistent or undocumented.
• Tool wear: Dimensions drift before anyone notices.
• Material mix-ups: Wrong lot, thickness, or hardness creates downstream defects.
• Rushed scheduling: Expedited jobs bypass normal checks and create avoidable mistakes.
• Poor traceability: Holds and paperwork corrections create hidden rework.

Traceability is especially important when quality problems are hard to isolate after the fact. If that is a challenge in your shop, this article on practical lot tracking and sign-offs is worth a read.

How to improve FPY without adding complex reporting

The goal is not to build a giant reporting system. The goal is to capture a few fields consistently and use them to fix repeatable problems.

Start with one defect code list

Use 8 to 12 defect or rework reasons, not 50. Examples: dimension out, wrong setup, burr/finish, material issue, paperwork/revision, tooling wear, weld defect, assembly error. Simple coding is far better than no coding.

Record rework at the time it happens

End-of-week memory is unreliable. The closer the record is to the event, the more useful the data will be.

Tie quality to the work order, not a separate spreadsheet

Quality notes are most useful when linked directly to the job, part, and operation. Separate logs are harder to maintain and rarely get reviewed in context.

Focus on repeat offenders

Do not launch ten improvement projects. Fix the two or three part numbers, operations, or defects that create the most rework hours.

Use visual thresholds

Flag any work order below your target FPY so supervisors can act quickly. This does not require advanced analytics. A simple exception list is often enough.

Conclusion: make FPY practical, then make it useful

For a small manufacturer, first-pass yield is not about chasing a textbook quality metric. It is a practical way to see where hidden rework is stealing time, margin, and delivery performance. When you calculate FPY by work order, then review it by part, process, and defect reason, you get a much clearer picture of where to improve.

You do not need complex reporting to start. You need consistent work-order data, a clear definition of rework, and a short weekly review that turns low-FPY jobs into specific corrective actions. If you want a simpler way to track work orders, production, and quality in one place, start a free FactoryOS trial.