There's one number most garage owners don't have: the percentage of technician hours paid that actually end up on a customer invoice. It's the most important metric in workshop economics — and in garages without time tracking, it's a complete guess.
The typical independent garage pays technicians for 40 hours per week and bills somewhere between 26 and 34 of those hours to customers. The rest — 15–35% of the total wage bill — disappears into parts waiting, between-job gaps, rework, admin, and untracked downtime. Not because technicians are lazy. Because the systems around them don't capture where the time goes.
This article covers what the gap typically looks like, where the unbilled time goes, how to track it without creating a surveillance culture, and the revenue impact of closing even part of the gap.
The Gap You Can't See
Here's the core problem, visualised for a 4-technician workshop paying 160 hours per week:
30% is typical for a garage without time tracking. Some are better — 20–25%. Some are worse — 35–40%. But almost every garage owner who sees their number for the first time says the same thing: "I knew it wasn't perfect, but I didn't think it was that bad."
What "Good" Looks Like — The Benchmarks
Efficiency is measured as a percentage: billed hours divided by paid hours. Here's what the numbers mean in practice:
| Efficiency | Rating | What It Means |
|---|---|---|
| 85–95% | Excellent | Industry-leading efficiency. Well-scheduled workshop with pre-ordered parts, minimal gaps, and experienced technicians. Realistic ceiling for most independents is 85–90%. |
| 75–84% | Good | Solid performance. Some room for improvement in scheduling and parts management, but fundamentally well-run. Most garages with digital scheduling reach this range. |
| 65–74% | Average | The typical independent garage. Significant time lost to parts waiting, scheduling gaps and between-job downtime. Plenty of low-hanging fruit to improve. |
| Below 65% | Needs Attention | More than a third of paid time is unbilled. Usually caused by structural issues — no bay-level scheduling, no parts pre-ordering, high rework rates, or one technician significantly underperforming. |
The goal isn't 100% — that's unrealistic. Legitimate breaks, cleaning, admin, tool maintenance and unavoidable delays account for 10–15% of paid time in any workshop. The goal is to minimise the avoidable waste and get the efficiency into the 80–85% range — where the business is capturing maximum value from its wage bill.
Where the Unbilled Time Actually Goes
Time tracking doesn't just measure the gap — it shows you exactly what fills it. Here's the typical breakdown for a 4-technician garage with 48 unbilled hours per week:
The immediately fixable categories — parts waiting, between-job gaps, and collection delays — account for roughly 24.5 hours per week. Rework is fixable but requires a different intervention (training or job reallocation). Breaks, cleaning and admin are legitimate and expected. The "other/untracked" category typically shrinks once time tracking itself is in place — the act of measurement reduces unmeasured waste.
Per-Technician Data — Where It Gets Actionable
Overall efficiency is useful. Per-technician efficiency is transformative. Here's what the data typically reveals in a 4-technician workshop:
Without per-technician data, the garage owner sees an overall efficiency of 70% and applies a blanket approach — "everyone needs to work harder." With per-technician data, the picture is completely different. Techs A and B are performing well. Tech C has room for improvement. Tech D has a specific problem — likely concentrated rework on certain job types, or consistently slow on unfamiliar tasks.
The fix for Tech D isn't a lecture about productivity. It's examining which job types they're slow on, checking their comeback rate, and either providing targeted training or reallocating certain work to technicians who are faster at it. The data tells you exactly what to do — and it's almost never "work harder."
How to Track It Without Creating Resentment
This is the make-or-break question. Time tracking done badly creates a surveillance culture that drives good technicians away. Done well, it improves everyone's working day by fixing the systemic problems that waste their time.
❌ The Wrong Way
- Framing it as "watching you." If technicians feel they're being monitored for the purpose of criticism, they'll resent the system and find ways around it.
- Using data to punish. Publishing league tables or disciplining based on efficiency numbers creates a toxic environment and encourages gaming — clocking on to jobs they're not working on.
- Tracking without acting. Collecting data but never using it to fix parts delays, scheduling gaps or training needs. The team sees the tracking as pointless because nothing improves.
- Requiring detailed timesheets. Manual time-logging on paper adds admin work and is universally hated. The system should capture time automatically from job card actions.
- Obsessing over individual minutes. Scrutinising whether a tea break was 12 minutes or 15 minutes. This is micromanagement. The goal is systemic improvement, not policing bathroom breaks.
✅ The Right Way
- Frame it as "fixing the system." The message: "We're tracking where time goes so we can fix parts delays and scheduling — not so we can watch you." Make it about improving the workflow, not judging individuals.
- Use data to remove friction. When the data shows 11 hours/week lost to parts waiting, pre-order parts. When it shows 8 hours in between-job gaps, improve scheduling. Technicians see their day get smoother — that's the buy-in.
- Share the data openly. Show the team the overall efficiency number and the breakdown. Let them see where the time goes. Most technicians already know parts delays waste their time — the data validates what they've been saying.
- Automatic, not manual. Clock-on happens when the technician opens a job card. Clock-off happens when they close it. No separate timesheet. No additional effort. The tracking is a by-product of using the system.
- Discuss individual data privately. Per-technician numbers are for one-to-one conversations, not team announcements. Focus on which job types are slower and why — training, tools, or experience.
How to Introduce It to Your Team
The conversation matters. Here's a script that works — tested across hundreds of UK garages:
The Team Conversation — What Actually Works
What Changes After 8 Weeks
Garages that implement time tracking and act on the data typically see these improvements within 8 weeks:
The Metrics to Watch Weekly
Once time tracking is active, review these numbers every Friday afternoon. It takes 5 minutes and tells you everything you need to know:
- Overall billed vs paid hours — the headline number. Is it improving week over week? If it stalls, look at the breakdown to find what's blocking progress.
- Per-technician efficiency — are individual numbers converging upward, or is one person dragging the average? If one tech is consistently below 65%, investigate job allocation and rework rates.
- Parts waiting hours — should be trending toward zero as pre-ordering becomes consistent. If it spikes, the receptionist may have missed pre-orders for a specific day.
- Rework hours — should be low and stable. If it spikes for a specific technician, identify the job types and address with targeted coaching rather than blanket criticism.
- Average between-job gap — the time between one job closing and the next opening. Should be under 15 minutes. If it's consistently over 30 minutes, the workflow for preparing the next job needs attention.
What About Small Garages?
If you're a solo technician or a 2-person workshop, per-technician comparison doesn't apply — but the overall efficiency number is just as valuable. Even for a one-person garage, tracking billed vs paid hours reveals how much time is consumed by admin, parts runs, customer calls and other non-billable activity. Many solo operators discover they're billing only 5–6 hours of an 8-hour day — and the tracking shows exactly where the other 2–3 hours go.
For solo operators, the fix is usually about delegation (hiring a part-time receptionist), automation (letting the CRM handle communications) and batching (doing all admin in one block instead of interrupting throughout the day). The data makes the case for each of these changes far more convincingly than a gut feeling.