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

Ask a forum why a profitable-looking month felt broke and the answer is hiding in the drive log: second visits. The part was not on the van, the job notes did not mention the recessed cylinder, the tech sent was not gas-certified, so somebody went back, unbilled. Enterprise field service has obsessed over first-time fix rate for decades because the economics are brutal: a return visit roughly doubles labour and travel on a job priced for one. Small trade businesses rarely measure it, which is exactly why lifting it is the fastest margin gain most of them have available.

Measure it simply or you will not measure it

Forget consultant definitions. Count: of jobs meant to finish in one visit, how many did? Your job records make this a filter, not a project, tag return visits with a reason code when you schedule them: no part, no access, no info, wrong skills, new fault. Two months of tags tells you precisely where your second visits come from, and the distribution is always lumpier than expected: most businesses find two causes driving 70 percent of returns.

Kill the information returns first

The cheapest returns to eliminate are the ones where the fix was known but the details were not: model numbers, access quirks, what the last tech found. That is a records problem, solved by job histories, arrival-visible notes and the photo habits from our handover guide. When the booking captures "what brand is the unit, send a photo of the label" and the tech reads the property's history on the drive over, the surprise rate on site collapses.

Parts: the van is a warehouse with a stock policy

No-part returns fall to van stock discipline: a defined baseline per trade, restocked on a schedule, plus job-type templates that list likely parts so the tech loads them before leaving. Track what each return visit cost against what the part costs to carry, the maths almost always favours carrying more, a case our van stock guide makes in detail. For jobs quoted in advance, materials allocate to the job at booking so the picker, even if that is you at 6am, works a list instead of a memory.

Skills matching and honest booking

Wrong-tech returns are scheduling misses: the job needed a ticket the tech did not hold, or two people, or four hours booked as two. Skills tags on people and requirements on jobs stop the first; honest duration templates from your quoted-versus-actual history stop the third, feeding the same data loop as crew metrics. Field-service benchmarks from analysts like Gartner consistently place skills-matched dispatch among the biggest FTF levers, and it is a filter your board should apply for free.

The compounding payoff

Lift FTF from 70 to 85 percent on ten jobs a day and you have removed roughly one return visit per day: unbilled hours, fuel, and the customer who tells the neighbourhood you had to come back. The freed capacity absorbs the emergency callouts without overtime and the scheduling slack every other guide on this blog keeps demanding. First-time fix is not one big fix; it is reason codes, records, van stock and matching, each boring, together transformative.

Frequently asked questions

What is a good first-time fix rate?

Mature field-service operations run high-seventies to high-eighties as a percentage; small trade businesses starting to measure usually discover they are in the sixties. The early wins come fast because the causes concentrate: two reason codes typically drive most returns.

How do I track FTF without enterprise software?

Tag every scheduled return visit with a reason code, no part, no access, no info, wrong skills, new fault, in your job system. Monthly, count returns against completed jobs and read the code distribution. Ten minutes of setup, and the improvement targets select themselves.

Does carrying more van stock really pay?

Run the comparison your records enable: cost of a return visit, unbilled hours plus fuel plus displaced revenue, against the carrying cost of the part that would have prevented it. For high-frequency parts the maths is rarely close; the van is your cheapest warehouse.

The bottom line

The pattern across every topic on this blog repeats here: the businesses that win are not working harder, they are keeping better records and letting systems carry the routine. Start with one change this week, measure it for a month, and let the results argue for the next one. And if you want the whole loop, scheduling, field app, safety and invoicing in one place, start a free SKEDS trial and test it on a real week of your own jobs.