Diesel Mechanic Labor Efficiency: The Math Behind Why Your Techs Clock 40 Hours But Only Bill 27

Diesel mechanic labor efficiency is the percentage of a technician's clocked, paid hours that convert into hours actually billed to a customer, found by dividing billed labor hours by clocked labor hours. Most shops that have never measured it run somewhere between 55% and 70%. Shops that actively manage it run 85% or higher.

Efficiency, Productivity, and Utilization Aren't the Same Number

Every shop consultant who's ever pulled up a payroll report will tell you the same thing: "busy" and "billable" are not the same word, and confusing them is how a shop with a full parking lot still can't make payroll. There are three separate numbers hiding inside one clocked shift, and each one answers a different question.

• Utilization — of the hours a tech was clocked in and paid, how many were actually assigned to a repair order at all? A tech clocked 8 hours but spent 1 helping unload a parts truck and 30 minutes in a safety meeting has 6.5 hours of utilization, or about 81%.
• Productivity — of the hours actually attending to jobs, how many billed hours did those jobs produce? If that same tech's 6.5 hours on repair orders produced 5.5 billed hours, that's 85% productivity.
• Efficiency — of the actual clock time spent physically on a specific job, how many billed hours did that job produce? This is the number that catches a slow diagnostic process or an estimate that's chronically wrong, because it isolates a single job instead of averaging a whole day.

Put real numbers on it and the difference gets obvious fast. Say a tech clocks a full 10-hour day. He spends 45 minutes at the parts counter and in a shop meeting, leaving 9.25 hours of utilization (92.5%). Of those 9.25 hours, one job runs long — a diagnostic quoted at 1 hour that actually took 2.5 — while the rest of the day's jobs bill out close to estimate. Total billed hours for the day land at 7.75, for a productivity number of 84% (7.75 ÷ 9.25). But look at efficiency job by job and the picture changes: every job except that one diagnostic ran at 95%+ efficiency. The tech isn't slow — one estimate on one job type is wrong, and it's dragging the average down every time that job comes up.

Most shop owners only ever look at one blended number and call it "efficiency," which hides which of the three problems they actually have. A shop with poor utilization needs a scheduling fix. A shop with poor productivity needs a workflow fix. A shop with poor efficiency on one specific job type needs to look at that job type specifically, not lecture the tech.

What a Low Number Actually Costs You

Run the math on an ordinary 3-tech shop billing $145 an hour. Each tech clocks a standard 40-hour week, so the shop has 120 clocked labor hours available to sell every week.

• At 65% labor efficiency (typical for a shop that has never tracked it), that's 78 billed hours a week — $11,310 in labor revenue.
• At 85% labor efficiency (a realistic, well-run target), that's 102 billed hours a week — $14,790 in labor revenue.

That 20-point gap is $3,480 a week, or roughly $181,000 a year, from the exact same three techs clocking the exact same hours — no new hires, no rate increase, no extra bay. It's the single largest lever most independent heavy-duty shops never pull, because it's invisible without job-level time data. A day-level time clock or a paper timesheet can tell you a tech worked 8 hours. It can't tell you which of those hours actually made it onto an invoice.

Where the Missing Hours Actually Go

The gap between clocked and billed almost never comes from one dramatic cause — it's five or six small leaks that add up, and in shops that have never measured it, non-billable time commonly eats 20-30% of a tech's paid day. The usual suspects, roughly in order of how much they cost:

• Diagnostic time that never gets billed. A tech spends 45 minutes chasing a fault code, finds the problem, but the labor line only ever gets written up for the repair itself — the diagnostic time evaporates.
• Parts-chasing and waiting. A tech stands at the counter, walks to the parts room, or waits on a delivery, all while still clocked in on a job that isn't actually moving.
• Unbooked comebacks and warranty work. Redoing a job under warranty is real clocked time against a $0 labor line — necessary, but it drags the number down if it isn't tracked separately from billable work.
• Cleanup, paperwork, and job-to-job transition time. Five or ten minutes between every job doesn't feel like much until you multiply it by four or five jobs a day, every day, for a year.
• Off-the-clock helping. A second tech pitches in on a stuck bolt or a two-person lift and never gets a labor line of their own on that job.
• No labor line to charge time to at all. A tech starts a job before the estimate is written up, or works ahead on a truck that hasn't been formally opened as a work order yet — real time with nowhere to land on an invoice.

None of these are signs of a bad tech. They're signs of a shop that has no mechanism for capturing time at the level of the actual labor line, so all of it quietly rounds down to "clocked in, nothing to show for it."

The Exact Formula (And How to Read It Without Punishing Your Best Techs)

The formula itself is simple: Labor Efficiency = Billed Labor Hours ÷ Clocked Labor Hours, for whatever period you're measuring — a job, a week, or a pay period. The trap is treating it as a single scorecard number for each tech and stopping there.

• Measure it per labor line, not just per tech per week. A tech's aggregate number can look fine while one specific job type — say, DPF regen diagnostics — is quietly running at 40% efficiency every single time. You only see that if the software tracks actual vs. estimated hours on the individual line, not just the shift total.
• Expect real variance, and don't punish it. A genuine intermittent electrical fault or an unusual failure on an older truck will tank a single job's efficiency number even for your best diagnostic tech. Track trends over several weeks, not single bad days.
• Separate "the tech was slow" from "the estimate was wrong." If every PM service on a specific engine family consistently runs long, that's an estimating problem to fix in your labor guide, not a coaching conversation with every tech who's touched one.

A Quick Way to Sanity-Check Your Number This Week

You don't need new software to get a rough baseline before deciding whether this is worth fixing properly. Pull last week's paid hours from payroll or your time clock, and pull last week's total billed labor hours from your invoices — most shop management software will total this for you on a single report. Divide billed by clocked.

• Under 70%: there's real, immediate money on the table, and it's worth tracking down to the labor-line level before you do anything else.
• 70-85%: normal for a shop with no formal system, and usually fixable with better time-clock discipline alone.
• 85%+: you're already close to the top of what's realistic — the next gains will come from scheduling and estimate accuracy, not labor tracking.

Run this same math separately for each tech and each job type if you can. A shop-wide average of 78% can hide one tech running at 95% and another at 60% — and averaging them together means you never find out which one actually needs help.

How to Actually Raise the Number

Measuring labor efficiency is the easy part. Moving it takes a few concrete process changes, not a motivational speech at the Monday meeting:

• Clock in and out by labor line, not by shift. If a tech's time clock only knows "in at 7, out at 5," you have attendance data, not efficiency data. Time tracked against the specific labor line on the specific work order is the only version of this number you can actually act on.
• Review the number weekly, in writing, not annually at review time. A gap you catch in week two is a coaching conversation. The same gap discovered in December is a full year of lost revenue you can't get back.
• Show techs their own number. Most techs have never seen this figure about themselves. Framed as information, not a threat, it tends to change behavior on its own — nobody wants to be the one clocking hours that don't show up anywhere.
• Put actual and estimated hours side by side on every job. When a tech and an owner can both see "estimated 2.5 hours, actual 4.1 hours" on the same line, the conversation moves from "why is your number low" to "what happened on this specific job" — which is the conversation that actually fixes something.

Wrenchpod's built-in time clock tracks hours by individual labor line, not just by shift, and shows actual vs. estimated hours side by side on every work order — so a shop can see exactly where clocked time isn't converting to billed time, job by job, instead of guessing from a single blended number at the end of the month. The same data feeds Wrenchpod's AI Ops radar, which flags thin-margin and un-billed work automatically instead of waiting for someone to run the report by hand. Start a free 30-day trial to see your own shop's numbers.