Technician Productivity Calculator

Three numbers get called productivity, they mean different things, and most shops quote the wrong one.

Before the arithmetic, so you are not reading a sales pitch disguised as a guide: LeadLocate does not sell shop management software. There is no technician time clock, no dispatch, no shop loading, no repair order management, no parts inventory, no warranty claim handling and no digital vehicle inspection. We are not a dealer management system.

The numbers on this page are calculated from data that lives in whatever system runs your shop. We are publishing this because the definitions get confused constantly, including by vendors who should know better, and because a manager who understands the three formulas asks much sharper questions in a demo.

What we do sell sits next to the shop rather than inside it: customer communication, follow up, retention campaigns and the handoff from a service visit to a vehicle sale. That is covered at the end, and only at the end.

All three are ratios of hours, and the confusion comes from which hours sit on top and which sit underneath.

Productivity measures attendance on paid work. It is hours a technician was clocked onto jobs divided by hours they were available to work, expressed as a percentage. It answers whether your technician had work in front of them. A low number is usually a management problem: not enough traffic, slow dispatch, waiting on parts, or waiting on customer approval.

Efficiency measures speed against the book. It is flat rate hours produced divided by the clock hours actually spent producing them. It answers how fast the technician works relative to the labor time allowed. A low number can mean skill, or it can mean the tough jobs all land on one bay.

Proficiency combines the two. It is flat rate hours produced divided by hours available. This is the number that most directly connects to money, because it tells you how many billable hours came out of a technician's paid day regardless of where the losses occurred.

The reason the distinction matters is that the fixes are different. Productivity problems are fixed by the service drive and the dispatcher. Efficiency problems are fixed by training, tooling and job assignment. Confusing them means treating a dispatch failure as a technician failure, which is how good technicians leave.

These figures are illustrative only. They are made up to show the arithmetic, not drawn from any store's actual results, and your numbers will differ.

Take one technician over one week. Say they were scheduled and available for 40 hours. Their time records show they were clocked onto repair orders for 34 of those hours. The jobs they completed carried 44 flat rate hours in total.

Productivity is 34 divided by 40, which is 85 percent. That is reasonable, and the missing 6 hours are the interesting part: that is roughly three quarters of a day where a technician was paid and had no job in the bay.

Efficiency is 44 divided by 34, which is about 129 percent. The technician is beating the book comfortably.

Proficiency is 44 divided by 40, which is 110 percent. So the shop billed 44 hours against 40 hours of availability.

Now look at what changes if you close the productivity gap without changing anything else. At the same efficiency, 40 clocked hours would produce roughly 51 flat rate hours instead of 44. Seven hours a week from one technician, purely from keeping work in front of them. Multiply across a shop and the size of the dispatch problem becomes obvious. This is why productivity, the number most shops ignore in favor of efficiency, is usually where the money is.

Every calculation above depends on time data, and time data in a shop is collected under pressure by people who did not sign up for data entry. Common distortions, all of which we have heard from service directors rather than invented.

Clocking happens in batches. A technician clocks on and off three jobs at once at eleven and again at four, from memory. The totals may be roughly right, but the distribution across jobs is fiction, which ruins per job analysis while leaving weekly totals plausible.

Non billable time disappears. Shop cleanup, moving cars, helping a colleague, a customer walk around, waiting for a part. If none of that is captured, your productivity number silently blames the technician for time the shop consumed.

Availability is defined loosely. Does 40 hours include vacation, training, a half day for a certification class? Different definitions produce different percentages for identical work, which is why comparing your numbers against an industry benchmark is close to meaningless unless the definition matches.

Warranty and internal mix is uneven. Warranty times are frequently tighter than customer pay times for the same operation. A technician loaded with warranty work will look slower than one loaded with customer pay, and neither fact is about the technician.

Before you act on any of these numbers, spend a week watching how time is actually captured in your shop. Almost everyone who does this discovers the report they have been managing by describes something slightly different than they assumed. Our page on technician labor time tracking goes deeper on capture.

A ratio is a starting point for a conversation, not a verdict, and treating it as a verdict is where shops damage their own bench.

It cannot tell you about job mix. A technician doing diagnostics on intermittent electrical faults will never post the efficiency of one doing tires and brakes, and diagnostics is worth more to your store than the ratio suggests.

It cannot tell you about comeback rate. A fast technician who produces returns is more expensive than a slower one who does not, and comebacks rarely appear in the productivity report at all.

It cannot tell you about mentoring. The experienced technician who spends four hours a week helping two apprentices looks worse on paper and is holding your shop together.

It cannot tell you about the customer experience, which is where the rest of this page eventually goes. A shop can be highly productive and still lose customers because nobody told them what was happening to their car for six hours.

Use the numbers for trends and for questions, and pair them with the ones that describe the whole department: hours per repair order, effective labor rate, comeback percentage and absorption. If absorption is on your list, our service absorption calculator page covers that math separately.

Since the data comes from your shop system, evaluate that system on how honestly it captures time rather than on how attractive the dashboard is.

Ask to see an ugly repair order in the demo: a job that splits across warranty, customer pay and internal, with a parts backorder and a technician reassignment partway through. Clean demonstration data hides everything that matters.

Ask how time is captured and whether technicians actually use it, because a clock that gets bypassed produces worse data than no clock. Ask whether non billable time can be recorded against a category, since that is the only way productivity becomes a management tool rather than an accusation. Ask how the system behaves when three advisors book against the same capacity at once.

Then ask the commercial questions. What does the connection to the rest of your systems cost, who maintains it, and what happens to your history if you leave. Ask that last one before you sign, because your leverage is never higher than the moment before signature. Our page on technician dispatch software covers evaluating the dispatch side.

Here is where a communication platform legitimately affects these numbers, and it is not by making anyone turn a wrench faster.

A meaningful share of lost productive time is waiting on the customer. The vehicle is diagnosed, the estimate is ready, and the technician sits while an advisor plays phone tag for two hours. Text collapses that wait. SMS and MMS with real threading means a photo of a worn component lands in the same conversation as the estimate, and approvals come back in minutes instead of at the end of the day. RCS messaging with SMS fallback keeps the message readable on modern handsets without leaving anyone out.

Inbound calls are the other drag. The phone rings constantly during the morning rush, calls get abandoned, and every abandoned call is either a lost appointment or a customer who will call back at the worst possible moment. AutoMail provides interactive voice response, call routing and forwarding so calls are answered and directed rather than ringing into a busy drive. Call recording with transcription lets a manager review a difficult conversation in half a minute.

None of this is shop management. It is the layer around it, and it is the layer that decides how long your technicians wait. See service texting software for that on its own.

The other place we are genuinely useful is after the visit. Every shop generates declined recommendations daily, and most of those declines are timing rather than refusal. The record sits in the shop system, the advisor moves to the next car, and six weeks later the work gets done somewhere cheaper.

Follow up processes and automations fix that without adding headcount. Build the cadence once and it runs: a message a few weeks after the decline, a reminder as the season turns, a note when a related item comes due. The same applies to customers drifting out of your service cycle, who are unattended rather than gone. Email and phone validation matter here more than most people expect, because service databases are old and a campaign to dead contact data damages your sending reputation for everything else. More on declined service follow up.

And the service drive is full of vehicles you already own the relationship on. A customer whose repair estimate is uncomfortable relative to their car's value is a trade conversation, and the shared customer profile carries vehicle detail across departments so it is one conversation rather than two disconnected ones. Our service CRM page covers that handoff.

Stated plainly one more time: no repair orders, no scheduling against shop capacity, no technician time clock or dispatch, no shop loading, no parts, no warranty claims, no digital vehicle inspection, and no dealer management system. What we do costs from $199 a month on CRM Only, month to month with no long term contract. Figures are on the pricing page, and we cannot guarantee revenue from any campaign, because that depends on your customers, your pricing and your market.

What is the formula for technician productivity?

Hours clocked onto jobs divided by hours available, as a percentage. Efficiency is a different calculation: flat rate hours produced divided by clock hours spent producing them. Proficiency is flat rate hours produced divided by hours available.

Which of the three numbers should a service manager watch?

All three, because they point at different fixes. Low productivity is usually a dispatch, traffic or approval delay problem. Low efficiency points at training, tooling or job assignment. Proficiency ties most directly to billable output.

Are the numbers in your example real?

No. They are illustrative only, chosen to show the arithmetic clearly. We do not publish invented statistics or benchmarks, and any figure you compare against should use the same definition of available hours you do.

Does LeadLocate track technician time?

No. There is no time clock, dispatch, shop loading, repair order management or parts inventory, and we do not sell a dealer management system. Those numbers come from whatever system runs your shop.

How can a CRM affect technician productivity at all?

Mostly by shortening customer wait. Texting estimates with photos and getting approvals back in minutes stops a technician sitting on a diagnosed car, and answering inbound calls properly stops the drive from being buried during the morning rush.

What do you provide around the service department?

Customer communication and follow up: texting with threading, interactive voice response and call routing, recording with transcription, declined work cadences, retention campaigns, contact validation, a shared customer profile, and the handoff from a service visit to a sales conversation.

See estimate texting with photos, tracked inbound calls and declined work cadences running together. Month to month, no long term contract.