The "good tech" everyone knows is often the wrong one
Ask any shop owner to rank their technicians and they'll do it instantly, with total confidence, off pure gut. The trouble is that the gut is a terrible measuring instrument. It rewards the tech who's loud about his wins and forgets the quiet one whose jobs simply never come back. It confuses "fast" with "good" right up until the callbacks land. It remembers the dramatic save and forgets the six months of steady, unremarkable, profitable work. The tech everyone "knows" is the best is frequently the one who's best at being seen as the best — and the genuinely excellent tech, the one whose customers never call back angry and whose jobs quietly make money, gets overlooked because excellence done right is invisible.
A technician scorecard exists to fix that — to replace the vibe with a handful of honest numbers so you're managing reality instead of reputation. But a scorecard is a loaded tool, and pointed the wrong way it does more damage than the gut ever did. Build it carelessly and you get a leaderboard that rewards corner-cutting, punishes the tech who takes the hard jobs, and teaches everyone to game the metric instead of doing the work. Build it well and you get something rare: a fair, shared picture of how each person is actually doing, and a coaching tool that makes the whole team better. The difference is entirely in which numbers you pick and how you use them.
The numbers that actually mean something
A good scorecard is short. A handful of metrics that each measure something real beats a dashboard of thirty that measures noise:
- First-time fix rate. The share of a tech's jobs finished in one visit, no callback needed. This is the closest thing to a single measure of craft — it captures diagnosis, preparation, and thoroughness at once. It ties straight to your first-time-fix work and it's hard to fake, because faking it produces callbacks.
- Callback rate. The mirror image: how often a tech's completed jobs come back as warranty callbacks. A tech who's "fast" but generates callbacks isn't fast — he's doing the job twice and hiding half of it in next week's schedule.
- Billable-hours ratio. How much of the tech's paid day turned into billable work, from their utilization. This catches the productive-versus-idle picture — but read it carefully, because a low ratio is often a dispatching problem, not a tech problem.
- Job profitability. Whether the jobs a tech runs actually make money after labor and parts. A tech whose jobs consistently come in profitable is doing something — accurate quoting, tight parts use, honest hours — that a pure speed metric would never see.
- Cycle time. How long the tech's jobs take from start to done, from the cycle-time report. Useful — but the single most dangerous number on the list if you read it naked, for reasons that are the whole next section.
Notice what's not here: raw revenue, raw job count, raw speed. Those reward the tech who grabs the easy, lucrative jobs and dodges the hard ones — exactly the behavior a good scorecard should discourage.
Compare like with like, or you're just measuring the schedule
Here is the discipline that separates a scorecard that's fair from one that's a lie with decimal places: the raw numbers are almost never comparable, because no two techs get the same jobs. The tech with the best cycle time might just get handed the easy maintenance calls. The tech with the "worst" first-time-fix rate might be your only one who takes the gnarly diagnostic jobs nobody else can solve — so of course more of his come back, they were the hard ones to begin with. Rank those two techs against each other on raw numbers and you'll promote the one dodging hard work and put your best diagnostician on a performance plan. You won't have measured skill. You'll have measured the dispatch board.
This is why the honest boundary of a scorecard matters so much: the tool surfaces the numbers, but you supply the context, because only you know what kind of work each tech was actually handed. In Hosting Field the reports let you see these metrics per technician, but the reason they're worth trusting is that the same platform carries the skill tags and job types that tell you what each tech was assigned. Read the scorecard next to the work: if your lowest first-time-fix tech is also the one carrying every hard job in the shop, that's not a weak tech, that's your strongest one absorbing the difficulty — and the number is praising him, not damning him, once you read it right. A scorecard without job context isn't a performance measure. It's a measure of who got the easy route, dressed up as merit.
Use it to coach, never to rank-and-yank
Even a perfectly fair scorecard becomes poison the moment you staple it to a wall as a competitive leaderboard. Publicly ranking techs against each other teaches exactly the wrong lessons: hoard the easy jobs, refuse the hard ones, cut the corner that doesn't show up until the callback lands next month on someone else's number. You'll optimize your team straight into the behavior that wrecks customers — and you'll lose your best people, because the genuinely skilled tech who takes the hard work will not stay somewhere that punishes him for the callbacks the hard work generates. Rank-and-yank in a trade with a brutal labor market is a way to fire yourself slowly.
The productive use is private and forward-looking:
- Coach the individual against their own trend, not against the star. "Your first-time-fix rate slipped this quarter — what changed?" is a conversation that helps. "You're fourth out of five" is a conversation that makes an enemy. Each tech competing with their own last month gets you improvement without the war.
- Use the numbers to find the teaching, not the villain. A tech with a high callback rate on one job type doesn't need a warning — he needs the checklist or training for that specific work. The scorecard points at the gap; your job is to fill it, not to punish it.
- Surface the quiet excellence and actually reward it. The scorecard's best trick is finding the tech whose steady, callback-free, profitable work never made noise. Seeing that person clearly — and paying and promoting accordingly — is how you keep them and signal to everyone what "good" actually means here.
- Feed it back into onboarding. What your top techs do differently is a curriculum. Reading the scorecard tells you what to teach the next new hire so they ramp toward the right behaviors instead of learning the shop's bad habits.
What to watch
- Each tech's own trend over time. The only fully fair comparison is a tech against their own past. Rising first-time-fix and falling callbacks quarter over quarter is real improvement, whatever the person's absolute rank.
- Metrics read against job mix. Always check a "bad" number against what the tech was assigned before you act on it. A red cell next to a stack of hard jobs is a different story than a red cell next to easy ones.
- Whether the scorecard changed behavior for better or worse. After you start using it, do callbacks fall and hard jobs still get taken — or do techs start dodging the difficult work? If it's the latter, your metrics are rewarding the wrong thing, and the tool needs fixing, not the team.
A technician scorecard is one of the highest-leverage tools a field-service operation has and one of the easiest to turn into a weapon. Pick the few numbers that measure craft and profit rather than raw speed, read every one of them against the work the tech was actually handed, and use the whole thing to coach individuals against their own trend instead of ranking them against each other on a wall. Done that way, it finds your quiet stars, turns your gut into evidence, and makes the whole team better. Done as a leaderboard, it teaches your best people to cut corners and then to leave. The numbers are identical. The outcome depends entirely on whether you built a coaching tool or a firing squad.