Workforce and Labor

Technician Utilization: Billable, Productive, and the Gap Between

Every service business quotes a utilization number and almost none of them mean the same thing by it. The decomposition takes ten minutes and usually changes the conversation about hiring.

Utilization is the headline metric of every service organization and one of the least standardized. Three definitions circulate: billable hours over paid hours, billable hours over available hours, and wrench time, the share actually spent working on equipment. They can differ by twenty points or more on identical performance, and the version quoted to a board is reliably the flattering one. The useful exercise is not choosing a definition but decomposing the year so all three fall out of the same arithmetic.

Decompose the paid year

Start with 2,080 paid hours. Subtract 200 hours of paid time off and 80 hours of training, both genuinely paid and genuinely unavailable. Subtract 260 hours of administration, quoting, and parts chasing, and 340 hours of travel. What remains is about 1,200 hours of hands-on work. Billable utilization against available hours is 64%. The same technician measured against total paid hours is 58%. Neither number is dishonest and the gap between them is entirely definitional.

Travel is the bucket worth attacking

In most field service operations travel is the largest non-productive category and the one with the clearest levers: territory design, scheduling density, and whether the dispatch system optimizes routes or merely assigns tickets. A modest improvement in route density converts directly into billable hours without hiring anyone, which is why it is usually the highest-return project available to a service manager. Administration is second, and there the lever is usually mobile data capture replacing evening paperwork.

Utilization targets set against the wrong denominator do not motivate better performance. They motivate better categorization.

Why chasing the number backfires

Utilization above the high seventies tends to come with side effects: no slack for emergency calls, rushed diagnostics, rising callback rates, and technicians who leave. A service organization running at very high utilization has usually stopped being able to absorb the variability that is intrinsic to unplanned work, and the first symptom is response-time failure rather than any utilization metric moving. Pair the number with callback rate and first-time-fix rate permanently, because those are where the cost of over-utilization actually shows up.

What to report

Report all three definitions with their denominators named, plus the non-productive breakdown. That last part is what makes the metric actionable: knowing utilization is 62% tells a manager nothing about what to do, while knowing that 340 hours went to travel and 260 to administration names the two projects worth funding. A single percentage is a scorecard entry. The decomposition is a plan.

Use the technician utilization calculator to decompose your own paid hours. Model your utilization

Published 2026-08-08.