Overview
A maintenance backlog is usually described as a capacity problem. Too much work, not enough technicians, not enough hours in the day. The typical response is to push harder: extend the workday, defer lower-priority jobs, add overtime.
It helps temporarily. Then the backlog comes back.
What rarely gets examined is where shop time actually goes. Research consistently shows that fleet technicians spend a fraction of their available shift on productive repair work. That number isn’t an indictment of technicians — it reflects what happens in a shop without clean workflows. Parts that have to be tracked down. Assignments that aren’t clear until someone asks. Vehicle history that requires digging through records. Paperwork completed at the end of the day instead of at the end of the job.
The shops that bring their backlogs under control usually don’t add headcount. They recover the hours that are already there.
Wrench Time: What It Measures and Why It Matters
Wrench time is the percentage of a technician’s available workday spent on actual repair and service activities — the time with hands on the vehicle. Everything else — parts retrieval, paperwork, waiting for approvals, finding a supervisor for a decision, searching for repair history — counts against it.
High-performing shops consistently outpace average operations on productive repair time — and that gap, multiplied across a full shop and a full week, represents recoverable capacity that doesn’t require hiring anyone new.
Closing that gap doesn’t require capital investment. It requires identifying where time is actually going — and addressing the specific friction points that pull technicians away from productive work.
The Assignment Problem
Shop productivity suffers when work assignment is informal. In many operations, supervisors assign jobs by walking the floor, verbal direction, or a whiteboard updated at the start of the day. Technicians who finish a job before the next one is queued up may have to find a supervisor before they can move to something else. Time spent waiting for an assignment is time not spent turning wrenches.
The problem compounds when skill matching is left to habit rather than data. A specialist who routinely gets assigned generalist work isn’t adding value at their skill level. A technician without experience in a particular system who’s assigned to it anyway takes longer and may require oversight that occupies another technician’s time.
Structured work order assignment — where jobs are queued in the system, technicians can see what’s next without waiting, and supervisors have a real-time view of the floor — removes these friction points. A supervisor can see which technicians have bandwidth, which jobs are ready to move, and match the two without a conversation.
FleetFocus work order management supports this through technician assignment and timecard tracking, giving shop supervisors a current view of workload distribution across the floor and building a documented record of hours per job that supports future capacity planning.
The Compound Effect of Stalled Jobs
Most shops have an open work order count that’s higher than it should be — not because work isn’t getting done, but because a portion of open orders are stalled at a bottleneck rather than actively being worked. Understanding this distinction matters because it changes the response.
A work order stalls waiting on a part. The technician moves on. A second order stalls waiting on an approval. The technician moves on again. A third is waiting on a vehicle that hasn’t been returned by the driver. The shop’s open work order count climbs, the supervisor adds hours to deal with the backlog, and the root cause — three separate bottlenecks affecting three separate jobs — never gets addressed.
When work order status captures where jobs are actually stuck, the picture changes. A shop that can see that 45% of its aging work orders are in “waiting on parts” status has a parts sourcing problem, not a capacity problem. One where 30% are in “waiting on approval” may have an authorization process that creates unnecessary delays. Each bottleneck type has a different fix — but without the data, they all present as the same symptom: the backlog is growing.
Parts and the Throughput Connection
Parts availability has a direct multiplier effect on shop throughput. A job that requires 90 minutes of labor can sit open for multiple days if the right part isn’t available when the technician is ready to work. Across a shop of any size, parts delays that affect multiple jobs simultaneously can stall throughput significantly without any reduction in technician effort.
The throughput solution isn’t just having more parts on the shelf. It’s knowing what each job needs before the vehicle arrives. When work orders are planned in advance — when an upcoming PM or a driver inspection report generates a work order before the vehicle is scheduled to come in — parts availability can be confirmed, shortfalls can be ordered, and the job is ready to execute when the technician is ready to work it.
FleetFocus connects parts and inventory management directly to work orders. When a technician opens a work order, parts requirements are visible alongside the job. When parts are pulled, inventory updates in real time. And because PM triggers generate work orders on a forward-looking schedule, service coordinators have time to confirm parts availability before a job hits the active queue rather than after it stalls.
Measuring Throughput, Not Just Volume
Traditional shop metrics focus on the queue — how many work orders are open, how many were completed this week, how many are past due. These are useful for understanding workload. They’re less useful for understanding whether the shop is functioning efficiently.
Throughput metrics ask a different question: how is work moving? Average age of closed work orders, return-to-service time per vehicle class, ratio of scheduled to unscheduled work completed, and jobs per technician per shift all speak to the speed and predictability of the shop’s output. A shop that completes 40 work orders this week but averages 6 days to close them is operating differently than one that closes 35 orders with an average age of 2 days.
Tracking throughput consistently catches backlog buildup early — when it’s still a process adjustment rather than a staffing crisis. FleetFocus KPI dashboards and configurable reports support these views, giving shop supervisors and maintenance directors a daily picture of where work is flowing and where it’s accumulating.
The shops that stay ahead of their backlogs tend to have one thing in common: they’re managing throughput, not just counting work orders.
