Guides

Technician Efficiency vs Productivity: Formulas, Examples

Productivity, efficiency and overall (proficiency) explained with formulas, a worked week for three technicians, how to track the hours, and the pitfalls: comebacks, unapplied time and pay plans.

Ijharul Islam October 21, 2026 10 min read

Technician efficiency vs productivity is the difference between how fast a tech works once a job is in the bay and how much of the paid day goes to jobs at all. Efficiency is a technician's number; productivity is mostly the shop's. Mix them up and you end up coaching a fast tech who was really waiting on parts.

More on this topic: Pricing and shop numbers, every guide in one place.

Our shop KPI guide and our flat rate vs hourly pay guide define these in a line or two. This post goes further: the three formulas side by side, a worked week for three technicians, how to capture the hours, what moves each number, and how comebacks and pay plans distort them.

The short answer

Technician efficiency vs productivity, in short: productivity = hours on jobs ÷ hours clocked in (34 of 40 hours is 85%); efficiency = hours billed ÷ hours worked on jobs (42.5 billed in 34 is 125%); overall = billed ÷ clocked (106%). Low productivity is usually a workflow problem; low efficiency, a skill or pricing one.

Key takeaways

Productivity measures how much of the paid day goes to jobs; efficiency measures billed hours against the time the jobs actually took; overall (often called proficiency) is billed hours against clocked hours, the two multiplied together.
You need three numbers per tech per week: clocked hours, hours on jobs and billed (flagged) hours. Without the middle one you can only see overall.
Names vary: some sources call billed ÷ clocked "productivity" or "proficiency", so label your formulas before comparing with anyone.
Published targets are old or come from software vendors (a 2000 MOTOR article cites 90% productivity and 125% efficiency); your own trend is the better yardstick.
Comebacks, unapplied time and pay plans all bend the numbers; track rework separately and read efficiency alongside comeback rate.

Disclosure: we make BayRobin, an AI receptionist and front office for independent repair shops, and show where it fits. Everything here works without it. Figures from other companies come from their public pages, checked in October 2026 and linked at the end.

What is the difference between technician efficiency and productivity?

Productivity is about time on jobs; efficiency is about speed on those jobs. A 2000 MOTOR magazine article by shop consultant Bob O'Connor laid out the split most shops still use, and software vendor AutoVitals gives the same two formulas today:

Measure	Formula	What it tells you	Who mostly controls it
Productivity	Hours worked on jobs ÷ hours clocked in (paid)	How much of the paid day goes to customer cars	The shop: car count, scheduling, parts, approvals
Efficiency	Hours billed (flagged) ÷ hours worked on jobs	How fast the work is done against the hours sold	The technician: skill, tools, training, plus how the job was priced
Overall (proficiency)	Hours billed ÷ hours clocked in = productivity × efficiency	Billed output per paid hour	Both

The names are not standard. MOTOR called billed ÷ available hours "proficiency" and described it as "the measurement of productivity and efficiency combined". A 2013 Trucking Info article quotes a consultant defining proficiency the same way. Our own KPI guide uses "productivity" as a shortcut for billed ÷ clocked. None of that matters as long as you write your formulas at the top of the sheet and stick to them.

How do you calculate technician efficiency and productivity?

Collect three numbers per technician for the week, then divide. A worked example for a three-tech shop (names, hours and pay are illustrations, not benchmarks):

Tech	Clocked	On jobs	Billed	Productivity	Efficiency	Overall
Ana (flat rate)	40	34	42.5	34 ÷ 40 = 85%	42.5 ÷ 34 = 125%	42.5 ÷ 40 = 106%
Ben (hourly)	40	30	27	30 ÷ 40 = 75%	27 ÷ 30 = 90%	27 ÷ 40 = 68%
Cal (hourly)	40	36	36	36 ÷ 40 = 90%	36 ÷ 36 = 100%	36 ÷ 40 = 90%
Shop	120	100	105.5	83%	106%	88%

Three different stories. Ana is quick and well fed with work. Cal is steady. Ben spent 10 of his 40 hours off jobs and billed less than the time his jobs took. Before anyone talks to Ben, look at his unapplied time (below) and his job mix: a week of diagnostic work that was billed at an hour but took two will drag efficiency down, and that's a pricing problem, not a speed problem. Our diagnostic fee guide covers charging for diagnosis properly.

Shop totals use the summed hours, not an average of the percentages. Check: 83% × 106% ≈ 88%. The free technician efficiency calculator does this for you: enter each tech's flagged hours, hours on jobs and hours at work, and it totals the shop from the summed hours.

What does low productivity cost a shop?

Every clocked hour that isn't on a job is wages with no labor sale behind it. In the example, 20 of 120 paid hours went to no job. At the BLS median technician wage of $24.34 an hour (Occupational Outlook Handbook, May 2025), that's about $487 of wages in the week before taxes and benefits.

The bigger cost is the labor you didn't sell. If those 20 hours had gone on jobs at the shop's 106% efficiency, they'd have produced about 21 billed hours. At an assumed $135 effective labor rate (Tekmetric's Shop Index national average is $134.92), that's roughly $2,850 of labor sales in one week, plus the parts that go with it. That's why our labor rate guide divides by billed hours, not clock hours: a low overall number quietly raises the rate you need.

How do you track technician hours accurately?

You need a clock for the day, a clock for each job, and the billed hours from the invoice. A weekly sheet with these columns is enough:

Clocked hours from the timesheet or time clock: everything the tech is paid for.
Hours on jobs: the tech starts and stops a job clock on each repair order, including diagnosis and road tests.
Billed (flagged) hours: labor hours on the closed invoices assigned to that tech. Split jobs shared by two techs by the hours each did.
Unapplied hours = clocked − on jobs, with a reason code: waiting on parts, waiting on approval, no work, shop work (cleanup, shuttle, parts runs), training, meetings.
Rework hours: time on comebacks, kept apart from billed work.

The reason codes are the point. "Ben: 6 hours waiting on approval" sends you to the service desk, not to Ben. Use the same week (Monday to Sunday) for every number, and count a job's billed hours in the week the invoice closes.

What moves technician productivity and efficiency?

Productivity moves with the flow of work to the bay; efficiency moves with the tech, the tools and the way jobs are priced:

Lever	Moves	What to do
Car count and scheduling	Productivity	Book the next job before the bay empties; stagger drop-offs so techs aren't idle at 8 am
Approvals	Productivity	Send estimates as soon as inspections finish and call when there's no reply
Parts	Productivity	Order at approval, check parts on arrival, keep common filters and pads in stock
Dispatching	Both	Give each tech the work they're best at; don't hand the quick, well-paid jobs to one person
Training and tools	Efficiency	Scan tool updates, service information access, ASE training
Labor times you sell	Efficiency	If billed hours are always below actual on a job type, the price is wrong, not only the tech
Comebacks	Both	Rework adds hours with no billed time; fix the cause and track it apart

MOTOR's article cited an "industry benchmark" of 90% productivity and 125% efficiency; AutoVitals (2023) suggests keeping productivity "around 80%" and efficiency "above 100%". Those are a consultant's figure from 2000 and a vendor's rule of thumb, not survey data, so treat them as reference points and judge each tech against their own last eight weeks.

How do pay plans affect efficiency and productivity?

Pay plans decide who carries the cost of unapplied time. Using the same week and assumed rates:

Tech	Pay plan (assumed)	Weekly pay	Pay per billed hour
Ana	$30 per flagged hour	42.5 × $30 = $1,275	$30.00
Ben	$28 an hour	40 × $28 = $1,120	$1,120 ÷ 27 = $41.48
Cal	$28 an hour	40 × $28 = $1,120	$1,120 ÷ 36 = $31.11

Under flat rate, the tech absorbs low productivity and the shop's cost per billed hour stays fixed; under hourly pay, the shop absorbs it. Either way, three things to watch:

Rushing. Flat rate rewards efficiency, so read it next to the comeback rate. Many shops subtract rework hours from flagged hours or pay rework at zero; write that rule down before you need it.
Minimum wage and overtime. A flat-rate tech's total pay for the week divided by hours worked still has to reach minimum wage (DOL opinion letter FLSA-785), and overtime for pieceworkers is figured from the week's earnings divided by hours worked (29 CFR 778.111). In California, Labor Code 226.2 requires rest periods and other nonproductive time to be paid separately from piece-rate pay. This isn't legal advice: rules change and states, cities and counties add their own, so check the current text or ask a lawyer or your state association before you rely on it.
Gaming. If a bonus pays on efficiency alone, expect job clocks to start late. Bonus on overall (billed ÷ clocked) or on team billed hours, as our pay plan guide suggests.

What are the common mistakes with these numbers?

Using only billed ÷ clocked. It can't tell a slow tech from a starved one.
Averaging percentages. Sum the hours across techs, then divide.
Counting rework as billed. A free comeback with labor hours on a zero invoice inflates efficiency.
Comparing across shops. Unless you know their formula and job mix, a "120%" elsewhere means little.
Judging one week. Job mix swings week to week; use a four-week rolling figure for conversations about pay.

Frequently asked questions

What is the technician efficiency formula?

Billed (flagged) hours divided by the hours the technician actually spent working on those jobs. A tech who bills 42.5 hours on jobs that took 34 hours is 125% efficient. Over 100% means they beat the hours sold.

How do you calculate technician productivity?

Hours spent working on customer jobs divided by hours clocked in. A tech on jobs for 34 of 40 paid hours is 85% productive. Low productivity usually means waiting on cars, parts or approvals.

What is the difference between flagged hours and clock hours?

Flagged (billed) hours are the labor hours sold on the invoices a tech worked; clock hours are the hours they're paid for. Billed ÷ clocked gives overall productivity, sometimes called proficiency.

What is a good technician efficiency percentage?

There's no current public survey. A 2000 MOTOR magazine article cited 125% as an industry benchmark, and AutoVitals (2023) suggests aiming above 100%. Compare each tech with their own recent weeks and with comeback rate.

Can efficiency be over 100%?

Yes. If a job is sold at 2.0 hours and the tech finishes in 1.5, efficiency on that job is 133%. Productivity can't go over 100%, because time on jobs can't exceed time clocked in.

Where BayRobin fits

BayRobin's dispatch board gives each technician one row, so you can see who's empty and drag the next job across, and techs tap Start and Complete on each job on My day, a phone-friendly web page. The Shop plan adds payroll, with technicians' job hours on their timesheets. Repair orders hold labor hours at your rate. Keep the three ratios in a spreadsheet; this post's formulas work the same in any system. BayRobin is free until your first 10 booked jobs, no card up front. Start free or see pricing.

Sources

Competitor details in this post were checked against these public pages in October 2026. Products and prices change, so confirm with each vendor before you decide.

#technicians #kpis #shop management #pay plans