Billable vs Non-Billable Tech Hours and Why Your Utilization Looks Wrong

The Four Hours That Disappeared

Run the math on a single tech for a single day. You pay for nine hours. Then you look at what got invoiced.

Five.

So where did the other four go? They didn’t disappear. They went into the drive to the first call, the 40-minute run to the supply house for a part the truck didn’t have, the wait while a customer hunted for the breaker panel, the callback to fix last week’s job you can’t bill again, and the half hour at the shop restocking. All of it real. All of it paid. None of it on an invoice.

That gap between paid hours and billable hours is the single most important number in a service business. And most owners can’t see it, because their records only show the two ends — never the middle.

This isn’t a compliance question like drive-time pay or on-call rules. It’s a margin question. And it’s specific to trades that send people out in trucks, because the non-billable time hides in the spaces between jobs that an office business simply doesn’t have.

Billable, Non-Billable, and Why the Gap Is the Business

Billable hours are the time a customer pays for — usually hands-on work at the job. Non-billable hours are everything else you pay the tech for that never reaches an invoice: drive time, parts runs, shop time, training, warranty rework, and waiting.

Both come out of your pocket at the same hourly cost. Only one brings money in. So your margin on labor isn’t really set by your hourly rate. It’s set by what fraction of the hours you pay for actually convert to revenue. A shop billing 5 of 9 paid hours and a shop billing 6.5 of 9, at the same rate, are running completely different businesses. The second one isn’t working harder. It’s leaking less.

That fraction — billable hours over paid hours — is utilization. It’s the lever most service businesses never actually pull, because they never measure it cleanly enough to act on.

Why Utilization “Looks Wrong”

When owners do calculate utilization, the number often comes out lower than they expect, and they assume it’s an error. It usually isn’t. Two things distort the picture.

First, the fantasy baseline. Owners mentally assume a tech is billable most of the paid day. In field service, with travel and parts and rework, the real figure routinely lands well under that — not because techs are slacking, but because the structure of the work inserts unbillable time between every billable block. The number isn’t wrong. The expectation was.

Second, and more fixable: the non-billable time is undifferentiated. If your records show only total hours and invoiced hours, the difference is one mystery gap. You can see four hours went somewhere. You can’t see whether it was drive time, parts runs, or rework — so you can’t tell which problem to solve. The utilization number “looks wrong” because it’s unexplained, and unexplained numbers feel like errors even when they’re dead accurate.

The fix isn’t a better gut feel. It’s breaking the non-billable bucket into named categories so the gap becomes a list of specific, attackable problems.

Make the Non-Billable Time Visible

The move is to have techs log time against a category, not just clock in and out. Here are the categories that matter most in the trades.

• Billable on-site work — the hours tied to a work order that go on the invoice.
• Drive time — travel between calls. Often the single biggest non-billable category, and the one routing can actually shrink.
• Parts runs — trips to the supply house. A proxy for how well your trucks are stocked; a lot of parts-run time is a stocking problem in disguise.
• Shop / admin time — restocking, paperwork, morning staging.
• Warranty / rework — callbacks you cannot re-bill. This is the expensive one, because it burns paid hours on a job you already billed once, quietly cutting that job’s margin in half.
• Training and apprentice supervision — genuinely non-billable but valuable, and worth seeing as its own line rather than buried (it also overlaps with the apprentice-hour records you may need for licensing).

Once a week’s hours are split this way, utilization stops being a mystery. You can see drive time is 18% of paid hours, or that one tech’s rework is double everyone else’s. Now you have something specific to fix, instead of a vague sense that the day is leaky.

Turning the Categories Into Decisions

Each category points at a different lever:

• High drive time is a routing and scheduling problem. Clustering jobs by area and sequencing the day better converts windshield time back into billable time, without anyone working longer.
• High parts-run time is an inventory problem. The fix is on the truck, not the tech — better standard stock means fewer trips to the supply house mid-job.
• High rework is a quality or training signal. Tracking callbacks by cause and by tech surfaces whether it is a skills gap, a materials issue, or one recurring failure, and rework is worth attacking first because it costs you twice — once unbillable, and once in the customer relationship.
• Low billable across the board may mean you are simply overstaffed for current demand, or that estimating is off and jobs are running long against what you quoted.

None of these are visible without the category data. With it, the weekly question shifts from “are the guys busy?” to “which specific non-billable category is biggest, and what shrinks it?” That second question, you can actually answer.

Where the Data Comes From

All of this depends on capturing time by category as the work happens, attributed to the job — not reconstructing a tech’s day from a one-line timesheet on Friday. The same clean clock events that keep payroll and job costs accurate are what make utilization measurable. A tech marks drive time, on-site work, a parts run, and rework as separate blocks tied to the work order, and the week rolls up into a breakdown you can actually read.

A time clock built for field-service trades like ShiftFlow captures those categorized, job-tagged hours and exports them as PDF or CSV. It’s not a dispatch or routing suite, and it won’t optimize the routes for you. What it gives you is the measurement layer — an honest picture of where the paid day actually goes — so the decisions about routing, stocking, and rework run on real numbers instead of a hunch. You can’t shrink a non-billable category you can’t see, and most service businesses are flying blind on the four hours that quietly decide their margin.

Frequently Asked Questions

What is the difference between billable and non-billable hours for a service tech?

Billable hours are the time a customer pays for — usually hands-on work at the job. Non-billable hours are paid time that doesn’t appear on an invoice: drive time between calls, parts runs, shop time, warranty rework, training, and waiting. You pay the tech for both, but only one generates revenue, and the gap between them is where your service-business margin is won or lost.

What is a good utilization rate for a service technician?

Utilization is billable hours divided by paid hours. Real-world rates for field service techs commonly land well below the 100 percent owners imagine, because drive time, parts runs, and rework eat into the day. The right target depends on your trade, service area, and job mix, so measure your own baseline first and improve it rather than chase a generic number.

Why does my technician utilization look wrong?

Usually because the non-billable time is invisible. If you only track total hours and invoiced hours, the difference shows up as a vague gap you can’t explain. Until drive time, parts runs, shop time, and rework are each captured as their own category, you can’t see why utilization is low — only that it is, which makes the specific leak impossible to fix.

How do I increase billable hours without overworking techs?

Attack the biggest non-billable categories instead of pushing longer days. Tighter routing cuts drive time, better truck stock cuts parts runs, and tracking rework by cause surfaces the callbacks that quietly burn paid hours twice. Measuring where the non-billable time goes comes first, because you can’t shrink a category you can’t see.