First-time fix rate: the metric that quietly runs your margin

Every service manager knows the feeling. A tech closes a no-cool call at 4:40, and two days later the same address is back on the board. Nobody invoices the second trip. The customer is a little less sure about you. And the slot that visit takes is a slot you can't sell to someone new.

First-time fix rate (FTFR) is the number that captures all of that. It rarely shows up on an owner's dashboard next to revenue and average ticket, but it sits underneath both. This post covers how to define it precisely, how to measure it honestly, what actually moves it, and how to put a dollar figure on a few points of improvement.

What first-time fix rate actually measures

A working definition:

FTFR = first visits that resolved the problem, with no related return visit within 30 days ÷ all first visits on repair work in the period.

Three parts of that sentence do the heavy lifting.

"First visits." The denominator is the first appointment on a job, not every appointment. If you count every visit, a job that took three trips adds three entries and the math gets muddy.

"Resolved, with no related return within 30 days." A job the tech marked complete is not the same as a fix that held. Closing the ticket is easy. The 30-day window catches the callbacks that look like fresh calls: "the AC stopped again" a week later is the same problem, even if the office booked it as a new job. Some shops use 14 days, some 60. Pick one window and keep it, because the trend matters more than the exact number.

"Repair work." Leave out work that is planned to take more than one visit: maintenance tune-ups, installs with a scheduled second day, estimate-only sales visits. Including them flatters or punishes the number for reasons that have nothing to do with fixing things.

Two numbers worth tracking separately

Most shops benefit from splitting the idea in two:

• First-visit completion: did the job close on the first visit at all? This is mostly a parts and scheduling question.
• Callback rate: of jobs that closed, how many came back within 30 days for the same issue? This is mostly a diagnosis and workmanship question.

A shop with high completion and a high callback rate has techs closing jobs that aren't really fixed. A shop with low completion and almost no callbacks probably has a truck stock problem. Same FTFR, very different fixes.

Measuring it honestly: what counts as a return visit

This is where most FTFR numbers fall apart. If the rules are vague, the number drifts upward over time without anything in the field getting better. Write the rules down.

Counts as a return (hurts FTFR):

• A second trip because the part wasn't on the truck, including "I'll be back tomorrow with the motor."
• A callback within the window to the same address for the same system or symptom.
• A second trip because the first tech lacked the skill, license or tool to finish.
• A second trip because the diagnosis was wrong or incomplete.

Doesn't count (excluded from both sides):

• Planned multi-visit work that was scoped that way when it was sold.
• Maintenance visits and membership tune-ups.
• A new, unrelated request at the same address ("while you're here, the water heater is leaking").
• A customer who declined the repair and called back later to buy it. That's a sales outcome, not a fix failure. Track it, but somewhere else.

The gray zone, which needs a rule: customer not home, gate locked, or the decision-maker unavailable for approval. Many shops exclude these from FTFR and track them as an office metric, because the fix lies in confirmation calls and booking questions, not in the field.

Finally, require a return reason on every return visit. A short fixed list works: parts not on truck, misdiagnosis, needed different skill, workmanship, access or approval, equipment on order. After a month, the reasons will tell you more than the rate does.

The four drivers

When you sort a few months of return reasons, they almost always cluster into four groups.

1. Diagnosis

Wrong or partial diagnosis is the most expensive kind of return, because it often comes with a part that didn't need replacing. What helps:

• A standard diagnostic sequence per system type, so the tech checks the same things in the same order every time.
• Recording the measurements behind a conclusion (pressures, temperatures, amp draws), not just the conclusion.
• Pairing newer techs with a senior tech on callbacks, so the review happens on the job, not in a meeting.

TradesWork puts 10 HVAC calculators in the technician app for this reason: the arithmetic behind a diagnosis should be quick to do on site, not skipped.

2. Parts on the truck

"The part wasn't on the truck" is usually the single largest return reason, and the most fixable. Three habits make a difference:

• Set min/max levels per truck for the parts that fail most on your common job types, and restock against them every week.
• Look at your return reasons quarterly and add the parts that keep causing go-backs.
• At dispatch, check whether the likely parts are on the assigned truck. If they aren't, either send a tech whose truck has them or plan a supply-house stop before the job, not after.

3. Matching skills to the job

Sending a tech who has never worked on a ductless system to a ductless call is a likely return. Keep a simple skills list per tech (system types, brands, commercial vs residential, certifications) and use it when assigning. That's easy on paper and hard at 7:15 a.m. with three people out sick, which is why it belongs in the dispatch tool rather than in someone's head.

4. Information before arrival

Every question answered before the truck rolls is one less surprise on site. Useful information:

• Equipment make, model and age from the last visit.
• The previous tech's notes and photos.
• What the customer said on the phone, in their words.
• Booking questions that narrow the problem: "Is the outdoor unit running? Is there ice on the line?"

A good booking script and an equipment history for each home do more for FTFR than most tools. In TradesWork, every home has an equipment passport that the tech can open before arriving.

What a few points are worth: a worked example

All numbers here are hypothetical. Replace them with your own.

Say a 10-tech shop runs about 4 repair calls per tech per day, 250 working days a year. That's 10,000 first visits a year.

• At 75% FTFR, 2,500 of those need a second trip.
• At 85% FTFR, 1,500 do.
• The difference is 1,000 return visits a year.

Say each return visit costs 1.5 hours of tech time including drive.

That's most of one technician's working year. Now put money on it:

• Direct cost. At a loaded labor cost of $55 an hour plus $25 of vehicle cost per trip, each return visit costs about $108. Across 1,000 visits that's about $108,000 a year, usually unbilled.
• Capacity. If an average new call takes 2 hours, 1,500 hours is room for about 750 more calls. Even if only half of that gets filled with paying work at a $450 average ticket, that's about $169,000 in revenue that a return visit was occupying.

The customer side doesn't fit a spreadsheet as neatly, but it's real: the second visit is the one that makes people try another company next time.

The point of the exercise isn't the exact totals. It's that FTFR multiplies through labor cost, capacity and reputation at once, which is why a 10-point move is often worth more than a price increase.

Turning the number into a weekly habit

A metric only helps if someone looks at it on a schedule and can see the jobs behind it.

• Weekly, by tech. Look at FTFR and return reasons for each tech, with a minimum sample (say five first visits) so one bad day doesn't define anyone.
• Monthly, by job type. Find the job types with the lowest FTFR and work out whether the cause is parts, skills or diagnosis.
• Quarterly, by return reason. Adjust truck stock, booking questions and training against the biggest reason.

Make sure every number can be opened up into its jobs. "Why is it 72%?" should take one click to answer, not an afternoon of exports. In TradesWork, first-time fix and callback rate sit in the coaching scorecards with their formulas shown and the jobs behind each number one tap away.

Frame it as coaching, not punishment. Techs who feel judged on FTFR will find the go-back workaround. Techs who see their own trend and a concrete tip tend to fix the underlying problem.

A first-time fix checklist

Use this as a starting point and adapt it to your trades.

• Write down your FTFR definition, window and exclusions, and share it with the team.
• Require a return reason on every return visit, from a short fixed list.
• Track first-visit completion and callback rate separately.
• Set min/max truck stock for your top failure parts and restock weekly.
• Review return reasons each quarter and adjust truck stock to match.
• Keep a skills and certification list per tech and use it at dispatch.
• Check parts on the assigned truck before the job, not after the diagnosis.
• Ask two or three diagnostic questions at booking for each common call type.
• Make equipment history and the last tech's notes available before arrival.
• Review callbacks with a senior tech on site where you can.
• Show each tech their own FTFR trend with the jobs behind it, weekly.