Technician utilisation
What is technician utilisation: technician utilisation explained
Technician utilisation is the share of a technician's available paid hours that are booked to customer work, calculated as billable or job hours divided by total available hours. It is the capacity metric field service managers are judged on, and it describes how full the diary is rather than what happened once the technician arrived.
For field service
Know what the job needs before the van rolls
Venta Capture, a product of VentaVid, lets the customer show you the fault first, so the engineer arrives with the right part or does not need to arrive at all.
Spelled utilisation in the UK and most of Europe, utilization in the US. Also called billable utilisation, engineer utilisation, or labour utilisation. Same metric.
How is technician utilisation calculated?
Utilisation equals hours booked to jobs, divided by total available hours, times 100.
The denominator is where the arguments start. Available hours can mean paid hours, contracted hours, or contracted hours minus holiday, sickness and training. Each choice moves the result by several points, so a utilisation figure without its denominator stated is a number you cannot use.
- Billable utilisation counts only hours a customer or a contract pays for. Warranty and rework fall out, which flatters nobody but the invoice.
- Productive utilisation counts all job hours including warranty and internal work.
- Scheduled utilisation counts what the dispatcher planned, before anything went wrong on the day.
Technician utilisation and wrench time: the distinction that matters
These two get used interchangeably in service meetings, and they measure different things.
- Utilisation counts booked hours. The technician is assigned to a job and the clock is running against that job.
- Wrench time counts hands-on-tool time. The technician is physically working on the asset.
The space between the two numbers is travel, waiting for access, waiting for parts, waiting for authorisation, and paperwork. All of it sits inside a booked job, so all of it counts as utilisation and none of it counts as wrench time.
This is why a team can post 85 percent utilisation and still be slow. The diary is full. The tools are not in anyone's hands. Managing utilisation alone drives you to book more hours, which is the opposite of the fix when the gap is the problem.
A worked example
A technician works a 40-hour week and is booked to jobs for 34 of those hours, giving 85 percent utilisation. Inside those 34 hours: 9 hours driving, 3 hours waiting for a site contact and an isolation permit, 4 hours on reports and van stock, and 18 hours with tools in hand. Utilisation reads 85 percent. Wrench time is 45 percent of the shift. The 16-hour gap is the actual improvement target, and utilisation reporting alone will never point at it.
What the benchmarks say
TSIA reports billable utilisation in field service averaging 75 to 85 percent, with pacesetter organisations at roughly 90.2 percent, and engineer utilisation averaging 83 percent against 90.6 percent for pacesetters (TSIA field services benchmarks). Service management vendors publish lower working bands, commonly 70 to 80 percent, because they typically measure against paid hours rather than contract-available hours. FieldEdge is one example of that lower framing.
The two ranges are not in conflict. They are answering different questions, which is the recurring theme with this metric.
How technician utilisation gets gamed or misread
- Shrinking the denominator. Excluding training, holiday, admin days and standby lifts the percentage without a single extra job being done.
- Booking travel to the job. Perfectly legitimate accounting, and it means a route with two hours of driving reports the same as one with twenty minutes.
- Counting rework as utilisation. Every callback is a booked job. A team with a bad quality problem can look busy precisely because it is fixing its own work twice.
- Pushing past the sustainable range. Above the high eighties there is no slack for emergencies, so the first urgent call breaks the schedule and the day after collapses. Sustained high utilisation is also the standard route to overtime, rushed jobs and resignations.
- Treating it as a technician scorecard. Utilisation is mostly determined by dispatch, routing, parts availability and job mix. Holding an individual accountable for it rewards optimistic timesheets.
- Comparing across teams. An urban service round and a rural one are not measurable against each other, and neither is planned maintenance against emergency breakdown work.
Reading utilisation properly
Utilisation is a capacity signal, not a productivity one. Read it against wrench time to see how much of the booked day was real work, against first-time fix rate to see whether that work landed, and against truck roll volume to see whether the visit needed to happen at all. A visit that should never have been dispatched is 100 percent utilised and completely wasted.
The largest single lever on the gap is knowing what the job is before the van leaves. Accurate pre-visit assessment cuts the waiting, the wrong-part return trip, and the second visit, none of which show up as a problem in a utilisation report.
