Improving utilisation

Utilisation is the share of paid hours that are billed to a customer. A technician paid for forty hours and billing thirty is at seventy-five per cent, and the whole of their labour cost is carried on those thirty.

Raising it means converting unbilled paid time into billed time. There are three places it goes.

Travel

The largest, and the one most within reach. Time between jobs is paid and invoiced to nobody.

It falls with route density: jobs grouped by area rather than in the order they were booked. See tickets per route.

Waiting

Time lost to parts not on the van, a customer not home, access not arranged, or the job not being what was booked.

Each has a process fix ahead of the visit rather than a productivity fix during it: stock the common parts, confirm the appointment, and capture enough detail at booking to send the right person with the right equipment.

Rework

Return visits to correct work already done are paid twice and billed once — see callbacks and return visits.

Common errors

Utilisation can be raised on paper by cutting paid hours, which lowers the denominator without producing more revenue. It can also be raised by charging for time that was not worked, which is a different problem entirely.

The measure only means something alongside job margin. Utilisation at ninety per cent on underpriced work is a business working flat out for nothing.

A realistic ceiling

Full utilisation is not achievable and not a target. Travel, training and administration are real. The useful question is the trend against the business's own history rather than a benchmark.

Last reviewed 2026-07-30

Improving utilisation — Omnyra Wiki | Omnyra