Owners of service businesses want to know who is doing well and who needs help, and they are rightly nervous about measuring it. Technicians have seen "performance tracking" before: GPS reports, timesheets, and a weekly conversation that feels like an accusation. The result is a crew that games the number or resents it, and an owner who stops looking.
The version that works has two properties. The numbers come out of the work itself, as a by-product of closing jobs on the phone, not from a separate act of monitoring. And the technician sees their own numbers, at the same time as the owner, framed as a scoreboard they can move.
Five numbers, all from the job record
| Number | Where it comes from | What it tells you |
|---|---|---|
| Jobs closed per day | Job close on the phone | Pace, and whether the schedule is realistic |
| Revenue per job and per day | Invoice at completion | Whether options are being offered, not just repairs |
| Callback rate | Return visits linked to the original job | Quality, and the one number a tech cannot argue with |
| Review mentions | Review requests sent with the tech's name | Customer experience, from the customer |
| Record completeness | Photo and note present at close | Whether the next visit will start informed |
None of these need a timesheet, a check-in, or a tracker. Every one is created by the technician doing the normal thing: closing the job, sending the invoice, taking the photo. That is what makes them feel fair. The tech is not being watched; the work is being counted.
TARGETS
What to leave off
- Minutes per job. It punishes the technician who does the job properly and rewards the one who leaves a callback behind. The callback rate already measures what minutes were trying to.
- GPS idle time. It measures traffic and lunch, not performance, and it is the single fastest way to lose a good technician's trust.
- Upsell targets by dollar. They produce pressure and bad reviews. Measure whether options were offered, and let revenue per job follow.
How to share it
- 01The technician sees it first
Their own numbers, on their phone, updated as jobs close. Nobody should learn their callback rate from the owner; they should already know it.
- 02The team sees the team
Aggregate numbers in the weekly meeting: callback rate for the business, review count, revenue per job. Individual numbers stay between the individual and the owner unless the crew asks to see the board, which good crews often do.
- 03The conversation is about one number
In a one-to-one, pick the number that is furthest from where it should be and talk about that. Five numbers at once is a review; one number is coaching.
- 04Tie pay to the ones that measure quality
If there is a bonus, attach it to callback rate and review mentions before revenue. Rewarding quality first is how revenue per job rises without the pressure that produces complaints.
What it does for the business
A scorecard built this way does three things the owner was trying to do by instinct. It shows which technician should be training the others, because the numbers say so. It shows which one is struggling before the customers do. And it turns "I think Mike is slipping" into "Mike's callback rate doubled in September, let's look at those four jobs," which is a conversation that can actually go somewhere.
A scoreboard is a number the player can see and move. Surveillance is a number collected about them. Same data, opposite effect.
Common questions
What KPIs should I track for a field technician?
Jobs closed per day, revenue per job and per day, callback rate, review mentions, and record completeness (photo and note at close). All five come from the technician closing jobs on the phone, so they need no timesheet or tracker, and all five can be improved by doing the job better.
How do I measure technician performance without micromanaging?
Use numbers that are by-products of the work rather than of monitoring, show the technician their own numbers before anyone else sees them, discuss one number at a time, and leave off anything they cannot improve by doing the job well, such as GPS idle time or minutes per job.
Should technician pay be tied to the scorecard?
If there is a bonus, attach it to quality measures first (callback rate, review mentions) and revenue second. Rewarding revenue alone produces pressure selling and bad reviews; rewarding quality raises revenue per job without the complaints.
How does Kaizen produce technician scorecards?
Every job closed on the phone, invoice sent, photo taken, and review request sent with the technician's name feeds a per-person grade card automatically. The technician sees their own numbers on their phone; the owner sees the team and each individual on the analytics view.