Technician productivity vs efficiency: the difference

One of these is about the technician. The other is almost entirely about how the shop is run, and shops routinely blame the first for the second.

Two numbers, two very different meanings

Efficiency compares hours billed against hours actually spent on those jobs. A technician who books three hours of work and completes it in two is running above standard. This is a measure of the technician's speed and skill on the work in front of them.

Productivity compares hours billed against hours the technician was at the shop and available. A technician who was present for a full day and billed half of it is at partial productivity regardless of how quickly they did the work they were given.

The two answer different questions. Efficiency asks how good someone is at the job. Productivity asks whether the shop kept them supplied with work. Reporting only one of them, or averaging them into a general sense of how a technician is doing, is how the wrong person ends up being managed.

The combination that gets misread

The revealing case is a technician with high efficiency and low productivity. They finish everything quickly and still spend a large part of the week not billing.

This looks like an attitude problem from the front of the shop, because the technician is visibly not working for stretches of it. It is almost never an attitude problem. It means the work is not reaching them: waiting on parts, waiting on an approval, waiting on a dispatch decision, or simply not enough scheduled that day.

Coaching that technician to work faster will do nothing, because speed is not the constraint. Worse, it tends to push good technicians toward shops that keep them busy, and the ones who leave first are usually the ones you least wanted to lose.

What actually consumes a technician's day

When shops measure this properly for the first time, the size of the unbilled portion is usually the surprise, and it is rarely made of idleness.

• Waiting on authorization. The vehicle is diagnosed, the recommendation is written, and nothing can proceed until the customer answers a phone.
• Waiting on parts. Including the second trip, when what arrived was not what was needed.
• Diagnostic time that never made it onto a ticket. Real hours, no corresponding sale.
• Comebacks. Fully consumed hours generating no new billable work.
• Cleanup, moving vehicles, and general shop work. Necessary, unbillable, and worth knowing the size of.
• Explaining a job to an advisor who then explains it to a customer. Small each time, considerable in aggregate.

Why approval delay hits productivity hardest

Of everything on that list, waiting for authorization is the one with the worst shape, because it does not just consume time. It fragments it.

A technician waiting an hour for an answer cannot simply start a large job in the meantime, because the answer might come back mid-teardown. So they take something small, or they wait. Either way the bay is committed to a vehicle that cannot be worked on, and the technician is working below their capability.

This is also the delay that compounds across the shop. One vehicle stuck awaiting approval occupies a bay that the next appointment needed, so the delay propagates into the afternoon and the shop finishes the day having billed less than it had the capacity to bill.

Measuring it without making it adversarial

Technicians are reasonably wary of time tracking, usually because they have seen it used to build a case rather than to fix a process. How this gets introduced determines whether the numbers you get are real.

The framing that works is that you are measuring the shop, not the technician. If the data shows large unbilled blocks, that is a finding about dispatch, parts and approvals, and the technician is the person best placed to tell you which. Ask them.

It is also worth being explicit that efficiency and productivity will be reported separately and never blended. A technician who is confident that a slow week caused by a parts problem will not be recorded as poor performance will give you accurate data. One who is not confident of that will not.

What moving the number actually looks like

Because most of the loss is structural, most of the fixes are too, and they tend to be unglamorous.

• Shorten the approval loop , since it is usually the largest single block and the most fixable.
• Get parts verified before the vehicle is on the lift rather than after teardown.
• Dispatch with the technician's day in mind , not just the order things arrived.
• Track comeback hours so quality problems show up as the capacity cost they are.
• Separate the two metrics in reporting , permanently, so nobody manages the wrong one.

Where Today Mechanic fits

We work on one item on that list. Estimates go to the customer's phone with the inspection findings attached, and they approve or decline line by line without a phone call needing to connect.

The effect on productivity is indirect but real: less of the technician's day is spent on a vehicle that cannot be touched, and dispatch has a clearer picture of which jobs are actually cleared to proceed.

Parts, dispatch and staffing are the other levers, and they are bigger. Nothing here substitutes for them.