Glossary
Work order backlog
Work order backlog is the count, and average age, of open work orders that are unscheduled, unassigned, or otherwise not yet completed, tracked to see how much demand is outpacing dispatch capacity.
The two views.
- Benchmark
- None. There is no universal figure; track it against your own baseline.
Why work order backlog matters for commercial contractors
Backlog is the clearest early-warning signal that demand has outrun capacity, and it's usually visible in the numbers before it shows up as missed SLA windows or customer complaints. It's also a direct input into hiring and capacity planning decisions — a backlog that's growing steadily rather than seasonally is a signal to add crew or rebalance branches, not just push harder on dispatch.
What causes backlog to grow
Understaffing relative to demand is the obvious cause, but poor dispatch sequencing and seasonal demand spikes — a heat wave hitting a commercial HVAC book all at once — are just as common. A backlog that spikes seasonally and clears afterward is a different problem than one that trends upward year over year regardless of season.
Where it lives, and what to read with it
The dispatch board shows live backlog count and age by branch, status, and priority, so it doesn't require a separate report to pull. Because backlog is calculated from the same work orders that run day-to-day dispatch, it's current the moment a work order is scheduled or completed, not as of last night's export.
Straight answers.
How is backlog age measured?
Typically as calendar days since the work order was created and left unscheduled or unassigned, though some contractors measure from the customer's requested date instead if it's later than creation date.
What's a healthy backlog size?
It depends heavily on crew size, season, and job mix — treat any published target as general guidance and watch the trend against your own historical baseline rather than a fixed number.
Does backlog include PM visits?
It can, depending on how you configure it — some contractors track reactive-call backlog separately from PM backlog since the two have very different urgency profiles and staffing implications.
Can backlog be viewed at the branch level?
Yes — branch-level backlog is usually more actionable than a company-wide number, since it points directly at where capacity is short rather than averaging that signal away across the whole operation.