What is first time right (FTR) in manufacturing?

First time right is the percentage of units that pass every operation and every inspection correctly on the first attempt, with no rework, no touch-up, and no re-inspection. It is stricter than a scrap rate because it counts the cost of catching and correcting a problem, not just the cost of the parts thrown away.

How is FTR different from first pass yield?

In most plants the two terms are used for the same idea, the share of units made correctly on the first pass. The practical distinction is intent: teams often reserve first time right to stress that quiet corrections at the station also count as a miss, even when the part eventually ships good.

Why is FTR usually overstated on paper-run lines?

Because the event you most want to measure, a part that needed a quick correction, is the one that happens fastest and gets written down least. Silent rework, re-inspection loops, and end-of-shift copy-forward paperwork all push the reported number higher than the true first-pass result.

How does paperless manufacturing software improve first time right?

When the traveler, the inspection record, and the machine signal live in one place, first time right is derived from actual reject kicks, re-measures, and re-scans rather than entered from memory. That makes the real number visible per operation, shift, part, and changeover, which is where improvement projects can be aimed correctly.

Where does first time right leak the most?

The largest recoverable loss is often in the first-article window right after a changeover, where early parts are adjusted by feel until the process settles. Handoff mismatches between shifts and silent rework at the station are the other common leaks that rarely reach a defect log.

First Time Right (FTR) in Manufacturing

First time right is the share of units that clear every step correctly on the first pass, and on most lines the real number is lower than the daily report claims.

What first time right actually measures on the floor

First time right, often shortened to FTR, is the share of units that move through every operation and every inspection correctly on the first attempt, with no rework, no quiet touch-up at the bench, and no second trip past the gauge. It is a simple idea that gets slippery in practice. A part that was out of spec, adjusted by the operator in ten seconds, and then passed is not first time right, even though it left the cell looking perfect. On most lines the gap between “shipped good” and “made good the first time” is exactly the number that tells you where money and hours are going.

The reason FTR matters more than a plain scrap rate is that it captures the cost of catching and correcting a problem, not just the cost of throwing a part away. A unit that gets reworked usually consumes a second setup, a second inspection, extra material handling, and a slice of a supervisor’s attention. None of that shows up as scrap. It shows up as a line that feels busy but ships less than the headcount and the runtime would predict.

Where FTR really leaks on a paper-run line

When a plant runs on travelers, clipboards, and tribal knowledge, first time right leaks in places that are hard to see from the office. The leaks tend to cluster in a few predictable spots.

Silent rework at the station. An operator notices a burr, a short shot, or a loose torque, fixes it in a few seconds, and keeps moving. It never reaches a defect log, so the reported FTR stays high while the real one drops.
Setup and first-article drift. The first few parts after a changeover are often adjusted by feel until the process settles. On paper those early parts are frequently counted as good once the run stabilizes, which buries a recurring first-pass loss inside every changeover.
Re-inspection loops. A part fails at the gauge, goes back, gets re-checked, and passes on the second or third look. The paperwork usually records only the final pass, so the effort of getting there disappears.
Handoff mismatches. A spec revision, a material substitution, or a work-instruction change reaches one shift and not the next. The night crew makes parts to the old rule, and the miss is not caught until a downstream station or a customer sees it.
Copy-forward paperwork. When a traveler is filled in at the end of a run from memory, the numbers get rounded toward what the operator expected rather than what actually happened.

Each of these is small on its own. Added up across a shift, they are usually the difference between the FTR on the whiteboard and the FTR a customer experiences as a return or a complaint.

Why paper hides your true first time right number

Paper does not lie on purpose. It just records what a person had time to write down, at the moment they had time to write it. That is the core problem for first time right. The event you most want to measure, a part that needed a correction, is exactly the event that happens fastest and gets documented least. The operator is solving the problem, not narrating it.

There is also a timing gap. Cycle counts, scrap tickets, and inspection results are often reconciled hours later, sometimes at the end of the shift. By then the story has smoothed out. A run that had three bad setups and a jammed feeder becomes “ran a little slow.” The FTR that gets reported is an average of memory and hope, not a count of first-pass outcomes. This is why two plants with identical scrap rates can have very different true FTR, and why the plant that looks cleaner on paper is sometimes the one leaving the most on the table.

The practical effect is that improvement projects get aimed at the wrong station. If the reported first time right is 96 percent everywhere, there is no signal telling the team that one press, one shift, or one material lot is quietly running at 82. The data needed to make that call never existed in a form anyone could sort.

Measuring FTR from machine and system data

The shift that changes the decision is measuring first time right from what the machine and the systems actually did, rather than from what someone remembered. A press knows its cycle count, its reject kicks, and its dwell times. A gauge knows how many times a serial number was measured. An inspection station knows whether a part was scanned once or three times. A scheduling system knows when a changeover started and stopped. When those signals sit in one live data layer, first-pass yield stops being a story and becomes a count.

With machine and system data feeding the number, FTR can be broken down the way the floor is actually organized.

Per operation. You can see that the assembly cell runs first time right in the high nineties while a single upstream forming step sits ten points lower and forces the rework you feel everywhere else.
Per shift and per operator. A recurring first-pass loss on nights, or on one crew, usually points to a training or a work-instruction gap rather than a machine problem.
Per part and per lot. When a specific material lot or a specific product variant drags FTR, the pattern shows up in hours instead of surfacing weeks later as a customer complaint.
Per changeover. Measuring the first-article window from the machine clock exposes how much first time right is lost in the minutes right after every setup, which is often where the largest recoverable loss lives.

Paperless manufacturing software matters here for a specific reason. Once the traveler, the inspection record, and the machine signal live in the same place, first time right is derived, not entered. Nobody has to choose to log the correction, because the count of re-measures, reject kicks, and re-scans already tells the truth. That is the difference between a first time right number you argue about and one you act on.

Building FTR into the operator’s moment

Better measurement only pays off if it reaches the person at the station while they can still do something about it. Building first time right into the operator’s moment means the current spec, the current revision, and the last few results are visible at the point of work, not filed in a binder two aisles over. When a torque reads low or a dimension drifts toward a limit, the station should flag it before the part moves, so the choice is to fix the process rather than quietly fix the part.

It also means closing the loop the other direction. When a spec changes, every shift should see the same instruction at the same time, which removes the handoff mismatch that quietly eats first-pass yield. Traceability underneath all of this lets the team walk a specific unit back through every operation, so when FTR dips the cause is a search rather than an investigation. The goal is not more paperwork. It is fewer first-pass misses, caught earlier, with a clear record of what actually happened.

Where Harmony fits

Harmony is an AI-native operating system for American manufacturing that gets plants off paper and spreadsheets and ready for AI, which is what makes an honest first time right number possible in the first place. Harmony connects at the PLC, Allen-Bradley and Rockwell, Siemens, Omron, Mitsubishi, over OPC UA or whatever protocol the machine already speaks, and unifies machine data, software and system data, and paper into one live data layer, so first-pass yield is counted from reject kicks, re-measures, and re-scans rather than reconstructed from memory at the end of a shift. That live layer is what turns manufacturing traceability software into a working record you can walk backward through, and it is the foundation that paperless manufacturing software needs to make first time right a derived number instead of a hand-written one.

On top of that layer Harmony adds AI, including AI search, agents, scheduling, predictive maintenance, and back-office automations across finance, sales, procurement, and logistics, and the AI proposes while a person approves, because in a plant a decision about scrap or a spec change should have a human name on it. Harmony is software and hardware agnostic, and the published pilot is about $15–20K one-time over 4–6 weeks with forward-deployed engineers on-site and working software by week three. Customers including Mossberg, MoonPie, and CLS run high-production lines where the difference between reported and real first time right is measured in hours and returns, which is exactly where measuring from machine and system data changes the decision.