Technician Efficiency vs Productivity: The Difference and How to Measure Both

Technician efficiency and productivity in plain words: the formulas, a worked example with three made-up techs, why a shop needs both numbers, and how to raise each one without turning it into a whip.
Technician efficiency is hours billed divided by hours spent on jobs. Technician productivity is hours spent on jobs divided by hours paid. Efficiency shows how the work went against the billed time. Productivity shows how much of the paid day went to customer work. Track both, because each one points to a different fix.
Technician efficiency compares the hours you billed for a tech's work to the hours the tech spent on those jobs. Technician productivity compares the hours the tech spent on jobs to the hours you paid them. Efficiency tells you how the work went against the quote. Productivity tells you how much of the paid day went to jobs at all. You need both, because they point to different fixes.
This guide is for owners and service managers at diesel and heavy-equipment shops, in the bay or on the road. It gives both formulas in plain words, works through three made-up techs, and covers how to raise each number without turning it into a whip.
The two numbers in plain words
Every tech's week has three kinds of hours:
- Hours paid. The time on the clock for the shift, from payroll.
- Hours on jobs. The time the tech actually spent working on customer jobs.
- Hours billed. The labor hours that landed on invoices for that work.
The two measures compare them in pairs:
| Measure | Formula | What it answers |
|---|---|---|
| Efficiency | Hours billed ÷ hours on jobs × 100 | Did the work take more or less time than we billed? |
| Productivity | Hours on jobs ÷ hours paid × 100 | How much of the paid day went to jobs? |
| Overall | Hours billed ÷ hours paid × 100 | How much of the paid day ended up on an invoice? |
The overall number is efficiency times productivity. Some shops call it proficiency. The diesel shop profitability guide calls it labor efficiency, because it's the number that sets your effective labor rate.
Names get swapped between shops and between software. Write down which formula your shop means by each word, so everyone reads the numbers the same way.
A worked example (made-up numbers)
Three fictional techs, one week each:
| Tech | Hours paid | Hours on jobs | Hours billed | Efficiency | Productivity | Overall |
|---|---|---|---|---|---|---|
| Tech A, in the bay | 40 | 34 | 30 | 88% | 85% | 75% |
| Tech B, in the bay | 40 | 26 | 32 | 123% | 65% | 80% |
| Tech C, on the road | 45 | 28 | 28 | 100% | 62% | 62% |
Here's the math for tech A. Efficiency is 30 billed ÷ 34 on jobs = 88%. Productivity is 34 on jobs ÷ 40 paid = 85%. Overall is 30 ÷ 40 = 75%, which is also 88% × 85%.
Read the overall column alone and tech B looks better than tech A. The other two columns tell a different story:
- Tech A is on jobs most of the day but takes longer than the time billed. Look at how those jobs were quoted, whether time went unbilled, and whether A needs training or tools for that kind of work.
- Tech B beats the billed time but spends a third of the day off jobs. That's usually a shop problem: waiting on parts, waiting on approvals, or no next job ready.
- Tech C bills every hour spent on jobs, but long drives eat the day. That's a dispatch and routing problem, or a sign travel time should be on the invoice.
Each tech needs a different fix, and the overall number alone would hide which one.
Why efficiency can go over 100%
Billed hours usually come from a quote or a flat-rate time for the job. A tech who knows the job, has the right tools and doesn't hit a seized bolt can finish faster than the time billed. That pushes efficiency over 100%.
If your shop bills the hours on the clock instead, efficiency sits near 100% by design. Then the number mostly shows time that never got billed: comebacks, warranty work, unbilled diagnosis or hours someone wrote off. In that case, also compare quoted hours to actual hours on each job, so you learn which quotes run long.
Decide what counts before you measure
The numbers mean nothing until you settle a few rules:
- Drive time. If you bill travel time, count it as hours on jobs and hours billed. If you don't bill it, it's paid time off jobs, and it lowers productivity.
- Comebacks and warranty work. Count the time as hours on jobs. Count what you actually billed as hours billed.
- Shop work. Cleanup, training, meetings and moving trucks are paid time off jobs. That's fine. Just know how much there is.
- Two clocks. You need a shift clock for hours paid and a job clock for hours on jobs. Without the job clock you can't split efficiency from productivity.
How to raise productivity
Productivity is mostly a management job. The tech can't work a job that isn't ready.
- Have the next job ready. A board everyone can see, with the next job lined up before the current one ends.
- Stage parts first. Pull or order parts before the tech starts, so nobody stands at the counter.
- Get approvals fast. Send the estimate to the customer's phone the moment the tech finds the problem.
- Cut drive time. For mobile techs, send the closest qualified tech and group jobs by area.
- Match shifts to the work. Schedule techs for when the trucks show up.
- Keep the information with the job. Complaint, history and photos on the tech's phone, so they don't walk to the office to ask.
How to raise efficiency
Efficiency is shared between the tech and the shop.
- Quote the same job the same way. Use the same labor time for common repairs, so billed hours mean the same thing on every job.
- Bill all the time. Diagnosis, extra work found mid-repair and the second trip to the truck all belong on the invoice when the customer approved them.
- Train on the jobs that run long. Look for repairs where quoted and actual hours keep drifting apart.
- Buy the tool. The right lift, scan tool or puller often pays for itself in hours.
- Cut comebacks. A comeback is worked twice and billed once. Watch comebacks next to efficiency. A tech who beats the quote and then has a comeback loses the time they saved.
Use the numbers without wrecking the crew
Use these numbers to find problems in the shop before you use them to judge a tech. A few ground rules:
- Look at a month, not a day. One bad job can swing a week.
- Fix the shop problems first. Low productivity is usually about parts, approvals and dispatch.
- Compare techs doing similar work. A road tech and a bay tech will never look alike.
- Share the numbers with the techs. Ask what slows them down. They see the delays before you do.
The guide to managing technicians without micromanaging covers how to give that kind of visibility without hovering.
Where MetaFleet fits
In MetaFleet, techs log their time on the job from any phone browser, and each order shows quoted hours next to clocked hours. Owners and admins get a Technician Scorecard under Reports › Dashboard. For any period, it shows how much of each tech's shift went to jobs, their billed hours against their hours on site, and their share of revenue. Click a tech to see the orders behind the numbers, or download it as a CSV. Suggested labor hours on repair lines are on the wayComing soon. See the Technician Scorecard release notes for more.
FAQs
Ready to see where your techs' hours go?
See MetaFleet in Action
Book a demo and we'll walk through how your techs log time and how you bill it today, show you where MetaFleet fits, and build a simple rollout plan your team can follow.
Not ready to talk? Try a free shop tool
Related Articles

Flat Rate vs Actual Hours in Diesel Repair
Book time or clock time? How each way of billing customers and paying techs works in a diesel or heavy-equipment shop, who carries a job that runs long, how road calls differ from bay work and how to decide job by job.

Truck Repair Invoice: What to Include, Plus a Free Template
Every field a diesel truck or heavy-equipment repair invoice should carry, from the unit number and engine hours to complaint, cause and correction lines, plus road-call extras, the mistakes that hold up payment and a free template.
