Crew performance metrics that are fair (and the ones that backfire)

The question gets asked carefully on forums because everyone has seen it go wrong: "How do you measure your techs without turning the place toxic?" The horror stories are consistent, leaderboards that made crews rush and hide mistakes, jobs-per-day targets that punished the tech who got the hard work, tracking rolled out as suspicion. But flying blind fails too: the quiet performer goes unrewarded, the coasting senior sets the pace, and reviews run on vibes. Job data solves this if, and only if, you measure the work, compare like with like, and share the numbers with the people they describe.

Measure outcomes, not motion

The metrics that correlate with a healthy trade business are outcome-shaped: first-time fix rate, callback and rework rate, quoted-versus-actual hours, photo and safety-form completion, and customer feedback where you collect it. The motion metrics, jobs per day, minutes between stops, drive time, mostly measure what kind of work someone was given, and optimising them rewards rushing. Our first-time fix guide shows why one good outcome metric beats five activity ones.

Compare like with like, or not at all

The tech doing warranty callbacks in old villas will lose every raw-numbers contest against the one doing new-build fit-offs, and both will learn the game is rigged. Normalise before comparing: by job type, by complexity band, by whether they carried the apprentice. Small crews often cannot normalise meaningfully, in which case compare each person against their own trailing baseline instead of each other. Trend beats league table at every size.

Data quality is a fairness issue

Metrics built on patchy records punish the honest. If hours come from memory-typed timesheets, the accurate logger looks slower than the generous rounder, which is exactly backwards. Event-based capture, clock-ons, photos, sign-offs from the field app, gives every tech the same instrument, and our timesheet disputes guide covers how that alone drains most of the poison from hours conversations.

Share the numbers with their owners

Secret metrics breed paranoia; shared ones breed professionals. Each tech should see their own trends, monthly, in a five-minute conversation: here is your callback rate, here is the crew average, here is what changed. Research on feedback, including the long-running findings summarised by Gallup's workplace practice, is unambiguous that regular specific feedback beats annual surprises. The metric review is also where the tech tells you the number is wrong because the van keeps breaking down, which is information you wanted.

Tie numbers to development, not just bonuses

Money-only metrics get gamed; growth-linked ones get owned. Use the data to route development: the tech with rising callbacks gets paired with the senior for a fortnight, the one smashing quoted-versus-actual gets the complex work and the pay bump that follows it, the apprentice's completion quality earns solo jobs. The message the crew hears matters more than the dashboard: these numbers exist to grow you and defend you, and the day a customer dispute lands, it is your geostamped, photographed job record that wins it.

Frequently asked questions

What is a good callback rate for a trade business?

Single digits as a percentage of completed jobs is the working band most service businesses target, but your trend matters more than anyone's benchmark: a rising rate flags rushing, materials issues or a training gap. Reason-code every callback and the number becomes a diagnosis, not a grade.

Should I show techs each other's numbers?

Show each person their own trends against the crew average, not a named league table. Leaderboards optimise for gaming and hide help-seeking; personal trends with a monthly five-minute conversation optimise for improvement. The exception: celebrating specific wins publicly, which names people for praise, not ranking.

Can metrics be used in disciplinary processes?

They can inform one, but only if capture was uniform, the tech saw their numbers along the way, and causes were explored first, the van that kept breaking down explains a lot of slow weeks. Metrics as ambush lose tribunals and trust; metrics as shared record support fair process.

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.