Technician efficiency vs productivity comes down to two different questions. Productivity asks how much of a tech's paid time was spent working on cars. Efficiency asks how many hours were sold for the time actually spent on those cars. You need both numbers, and the second one only works if you measure real time on the car, not just clock punches.
Most shops get the hours sold part right, because it lives on the repair order. The weak link is "hours actually worked," which is usually a guess built from clock-in times.
Quick answer
- Productivity = hours working on vehicles ÷ hours clocked in. Is the tech on a car or waiting?
- Efficiency = hours sold (billed) ÷ hours actually spent on the job. Is the work beating book time?
- The gap: most shops measure "hours worked" from punches, so a car sitting on a lift while the tech waits for parts counts as work.
- The fix: log when each car is actually being worked on (bay cameras, job clocks or both), then compare that to hours sold per RO.
Technician efficiency vs productivity: what is the difference?
Here are the two formulas as AutoVitals writes them in its technician efficiency guide:
| Metric | Formula | What it answers | AutoVitals benchmark |
|---|---|---|---|
| Productivity | Hours spent working on vehicles ÷ hours clocked in | Is the tech busy on cars, or waiting? | Around 80% |
| Efficiency | Hours billed ÷ hours the tech spends on the job | Is the tech beating the time we sold? | Above 100% |
A tech can score well on one and badly on the other. A fast tech with nothing to work on is efficient and unproductive. A tech who is busy all day on jobs that take twice book time is productive and inefficient. They need different fixes: the first is a dispatch or car count problem, the second is a training, tooling or quoting problem.
Watch out: not everyone uses the same words
Some shop software uses "efficiency" to mean hours billed ÷ hours clocked, which mixes both ideas into one number. Workshop Software, for example, defines efficiency that way and puts a healthy workshop at 75–85%.
That number is useful as a headline (it's sometimes called proficiency), but you can't fix it until you split it. When someone tells you their techs run "80% efficient," ask which formula they mean before you compare stores.
Why clock punches make both numbers look better than they are
Productivity and efficiency both depend on one input: how long the tech actually spent on the car. Most shops get that from one of three places:
- Clock in and clock out for the day. Treats every paid hour as work. Productivity looks like 100%, and it tells you nothing.
- Job clocks on the RO. Better. But techs forget to punch, punch late, or leave a job open over lunch.
- Flagged hours only. No measured time at all, just book time. You can't calculate real efficiency from this.
The common gap in all three: a car sitting on a lift while the tech waits for parts, an approval or a road test looks the same as a car being worked on.
How to measure real time on the car
Camera-measured time on vehicle closes that gap. If you have cameras over your bays, they already see when a car is on the lift and when someone is working under it. The step-by-step:
1. Define the events you'll log
| Event | What it marks |
|---|---|
| Car in bay | Bay is occupied |
| Work starts | Hood up, wheels off, or tech under the car |
| Work pauses | No one at the car for more than a few minutes |
| Work ends | Hood down, wheels on, car ready to move |
| Car out | Bay is free |
"Car in to car out" is bay time. "Work starts to work ends, minus pauses" is time on the car. The difference between them is waiting, and that's where most of the lost hours hide.
2. Tie each visit to the repair order
Match each bay visit to its RO by bay and time window, then by plate or VIN where you capture it. That's the same matching we use for off-book oil change audits, just pointed at labor instead of missing tickets.
3. Attach the tech
Use whoever is assigned on the RO, or the job clock if techs punch per job. Cameras show work happening. The RO says who it belongs to.
4. Compare to hours sold
For each RO line, you now have hours sold and real time on the car. Add them up per tech, per day, per store.
5. Review weekly, not daily
One bad day is noise. A tech who runs at 70% efficiency on brakes for four weeks straight is a pattern you can coach.
Example calculation: one tech, one week
This is a made-up example to show the math. None of these numbers come from a real shop.
| Line | Example value |
|---|---|
| Hours clocked in (paid) | 40.0 |
| Hours the car was in the tech's bay | 34.0 |
| Hours actually working on the car (camera) | 27.0 |
| Hours sold on the tech's ROs | 30.0 |
| Productivity (27.0 ÷ 40.0) | 67.5% |
| Efficiency (30.0 ÷ 27.0) | 111% |
| Clock-based "productivity" (34.0 ÷ 40.0, if bay time counted as work) | 85% |
On clock punches alone, this tech looks fine. Measured properly, the tech beats book time but spends a third of the paid week not working on a car. Seven of those hours had a car on the lift with nobody at it.
That points away from the tech and toward the shop: parts runs, waiting on approvals, or one shared tool. The fix is in dispatch and the front counter, not a talk with the tech.
Decision table: what each gap usually means
| What you see | Likely cause | First thing to check |
|---|---|---|
| Low productivity, high efficiency | Not enough work, or too much waiting | Car count and dispatch; waiting time between work start and parts arrival |
| High productivity, low efficiency | Jobs taking longer than sold | Job type: is it one category (diag, electrical)? Training or tooling |
| Bay time far above time on car | Cars parked on lifts waiting | Approval turnaround, parts delivery, road test time |
| Hours sold above time on car by a lot, every week | Book time generous, or work skipped | Spot-check ROs with the clip; flat-rate jobs done fast is normal, steps missed is not |
| Time on car with no RO | Unbilled work or comebacks | Run the visit vs ticket match and sort false positives first |
| One store far behind the others on similar car counts | Process, not people | Compare waiting time by store before comparing techs |
Be careful how you use it
Measured time on the car is a coaching tool. If techs think the cameras are there to catch them, they'll start gaming the job clock and you'll lose the number. Share the shop-level numbers first. Fix the waiting problems the data shows you. Bring individual numbers into one-on-ones only once the team has seen it used fairly.
Service advisors play a part here too: slow approvals show up as waiting time on the tech's numbers. Our service advisor coaching guide covers how to coach that side.
How Trilix sets this up
We build bay camera analytics that run on the cameras most shops already have. They log bay time and time on car for every visit, match visits to your POS or shop software ROs, and roll productivity, efficiency and waiting time into one daily view per store. It sits on top of your shop software rather than replacing it.
If you also track the store-level numbers from our quick lube KPIs guide, these labor numbers slot right next to car count and ticket average. For repair shops, see how this fits on our tire & auto repair page.
Want to see real time on the car for your bays?
We'll check your camera coverage and an RO export and show you what a week of measured labor would look like.