Productivity is hours worked ÷ hours available. Efficiency is flat-rate hours produced ÷ hours actually worked. Proficiency combines both: hours produced ÷ hours available. They answer three different questions, and most shops track one of them while calling it the other.
Here’s the practical version of why this matters. A tech shows up, clocks in for 40 hours, and bills out 44 flat-rate hours. Great efficiency, right? Depends. If he was only actually turning wrenches for 30 of those 40 hours because he spent the rest waiting on parts and hunting for a socket, then he’s a very efficient technician inside a shop that’s wasting a quarter of his day. Fix the wrong number and you’ll go after the tech when the problem is the parts counter.
Three formulas, three questions, one worksheet at the end.
The short version
- Productivity = hours worked ÷ hours available. Asks: is the shop keeping this tech busy?
- Efficiency = flat-rate hours produced ÷ hours actually worked. Asks: how fast is this tech against book time?
- Proficiency = flat-rate hours produced ÷ hours available. Asks: what did I get for what I paid?
- Utilization is used two ways in this business: as a synonym for productivity when talking about people, and as bay utilization when talking about the building. Say which one you mean.
- Low productivity is a management problem. Low efficiency is a skill, tooling, or job-mix problem.
- We’re not publishing target percentages, because there’s no primary benchmark data worth quoting. Track your own trend.
Definitions first, because the terms get swapped constantly
Three kinds of hours. Get these straight and the rest is arithmetic.
Available hours. The hours you’re paying the tech to be there. Forty for a full-time tech on a standard week.
Worked hours. The hours he was actually on a job, clocked onto a repair order, hands on a vehicle. Always less than available hours, in every shop, forever. The question is by how much.
Produced hours. The flat-rate or book hours you billed for completed work. A job that pays 2.4 hours produces 2.4 hours, whether it took 90 minutes or four hours.
If your shop doesn’t distinguish worked hours from available hours, you cannot calculate efficiency correctly. You can only calculate proficiency and call it efficiency, which is exactly the mistake in most of what’s written about this.
Technician productivity formula
Productivity % = hours worked ÷ hours available × 100
Worked example. Tech is on the clock 40 hours. He was clocked onto repair orders for 31 of them. The other 9 went to waiting on parts, waiting on approvals, cleaning up, a staff meeting, and helping the new guy.
31 ÷ 40 = 77.5% productivity
What it tells you: whether your shop is feeding this technician work. Productivity is mostly your number, not his. A tech can’t make himself productive if the writer hasn’t sold anything and the part hasn’t landed.
When it’s low, look at: parts availability, approval turnaround, scheduling gaps, and whether one tech is the bottleneck for a whole category of work. None of those are fixed by talking to the technician.
Technician efficiency formula
Efficiency % = flat-rate hours produced ÷ hours actually worked × 100
Same tech, same week. He worked 31 hours and produced 34.5 flat-rate hours of billed labor.
34.5 ÷ 31 = 111% efficiency
What it tells you: how fast this technician performs against book time when he’s actually working. This one is about the tech, but with two large asterisks.
Asterisk one: job mix. A tech doing brake jobs and maintenance on familiar vehicles will beat book time regularly. A tech on intermittent electrical diagnostics will not, because diag time is not what flat rate is good at pricing. Comparing a driveability tech’s efficiency to a maintenance tech’s efficiency is comparing two different jobs.
Asterisk two: efficiency can be gamed, and it’s expensive when it is. Beating book time by skipping steps produces a comeback, and a comeback occupies a bay twice and gets paid once. If efficiency climbs and comebacks climb with it, you don’t have a fast tech, you have a bill arriving later. Worth reading alongside how to reduce comebacks.
Technician proficiency formula
Proficiency % = flat-rate hours produced ÷ hours available × 100
Same tech: 34.5 produced ÷ 40 available = 86% proficiency.
What it tells you: the bottom line on that technician. It’s the only one of the three that’s directly comparable to what you’re paying, because “available hours” is what you’re buying.
Note what happens: the tech shows 111% efficiency and 86% proficiency. That gap is entirely the 9 hours he wasn’t working. Nine hours a week, on one tech. Multiply by your tech count and your hourly cost and you’ve got the actual size of your parts and approval problem, in dollars, this week.
That’s the whole reason to run all three instead of one.
Where “utilization” fits
The term causes the most confusion, because it’s used for two different things.
Technician utilization is normally a synonym for productivity: how much of the available time was spent working. Some shops and some software use “utilization” where we wrote “productivity” above. Same formula. Just make sure everyone in your building means the same thing by it.
Bay utilization is a different measurement: productive bay hours ÷ available bay hours. That one measures your building, not your people, and you can be low on one and high on the other. Covered separately in the bay utilization formula.
If someone hands you a “utilization” number, ask what’s in the denominator before you act on it.
Reading the three together
Four common patterns, and what each one actually means.
High productivity, low efficiency. The tech is busy all day and still under book. Look at skill fit, tooling, and job mix before you look at attitude. Are you handing a maintenance tech diagnostic work? Is he sharing a scan tool with two other people? Is he walking to the parts room eleven times a day because nothing is stocked where it’s used?
Low productivity, high efficiency. The most common pattern in small shops, and the most expensive. You have a good technician and you’re not feeding him. This is a scheduling, parts, or sales problem. The tech is not the variable to change.
Both low. Start with productivity anyway. Fix the flow of work first, then measure efficiency again on a clean week. Efficiency measured during a week of chaos isn’t measuring the tech.
Both high, comebacks rising. Slow down. You’re borrowing against next month.
About benchmark percentages
You’ll find articles that state confidently that the industry average efficiency is some range, that 100% is the floor, or that top shops run at a particular number. We looked for a primary source for those figures and could not find one. They circulate between blogs without methodology, sample size, or a publisher who collected the data.
So here’s what we’ll say instead: the formulas are stable and the benchmarks aren’t. Your own number from four weeks ago is a better comparison than anyone’s published average, because it’s from your shop, your job mix, your labor rates, and your book times.
Measure weekly. Manage the direction.
The worksheet
Six columns per technician per week. That’s it.
| Column | Where it comes from |
|---|---|
| A. Available hours | Scheduled hours you’re paying for |
| B. Worked hours | Clocked time on repair orders |
| C. Produced hours | Flat-rate hours billed on completed jobs |
| D. Productivity | B ÷ A |
| E. Efficiency | C ÷ B |
| F. Proficiency | C ÷ A |
Add a seventh column for comebacks, because without it columns E and F can lie to you for about six weeks.
If you’re not currently capturing column B, that’s the one to start with. It’s the difference between knowing your techs are fast and knowing whether your shop lets them be.
Getting clean numbers here depends on repair orders that record who worked on what and for how long. That’s what shop software is for, and if you’re currently running this off memory and a whiteboard, the reconstruction is where the errors come from. We compared the two approaches in spreadsheet vs software for an auto repair shop.
Frequently asked questions
What’s the difference between technician productivity and efficiency?
Productivity is hours worked ÷ hours available: it measures whether the shop kept the tech busy. Efficiency is flat-rate hours produced ÷ hours actually worked: it measures how fast the tech performs against book time. Productivity is mostly a management number, efficiency is mostly a technician number.
Can technician efficiency be over 100%?
Yes. Flat-rate work is priced against book time, so a technician who completes a 2.4-hour job in 1.8 hours produced more hours than he worked. Sustained high efficiency is normal in maintenance-heavy work and unusual in diagnostic-heavy work.
Which number should I track if I only track one?
Proficiency, produced hours ÷ available hours, because it’s the one that maps directly to what you pay. But it won’t tell you why it’s low, which is why the other two exist.
Does technician utilization mean the same thing as productivity?
When applied to people, usually yes: both mean the share of available time actually spent working. Bay utilization is a different measurement about your building. Ask which one someone means before comparing numbers.
Bottom line
Three formulas, ten minutes a week, one worksheet. Productivity tells you whether the shop is working. Efficiency tells you whether the tech is working. Proficiency tells you what you got for the payroll. Skip the published benchmarks and beat your own number from last month.
Garage records repair orders, labor, and who did the work, which gives you the billed side of this worksheet without an evening of archaeology. Clocked time is the column you’ll need a habit for: have techs note start and stop on the ticket. Premium adds cost-vs-profit reporting and employee commissions, which is where these numbers stop being trivia and start affecting a paycheck. The Premium plan adds cost-vs-profit reporting and employee commissions, which is where these numbers stop being trivia and start affecting a paycheck.
Seven-day free trial, no credit card. $39/mo for one user, $69/mo for up to seven.
