Maintenance backlog
Maintenance work that has been identified and approved but not yet completed.
How it is measured
Backlog is usually counted in labor hours, then expressed in weeks of work for the crew:
Backlog (weeks) = estimated labor hours of open work / crew hours available per week
Example: open work orders add up to 600 hours. Five technicians have 32 hours a week each for planned work, so 160 hours a week. The backlog is 600 / 160 = 3.75 weeks.
Why it matters
The size and trend of the backlog show whether the team keeps up with the work. A backlog that grows month after month means work is coming in faster than it gets done, and some of it will turn into breakdowns. A backlog that is nearly empty can mean the team is overstaffed, or that problems are not being reported.
Planners often cite a rule of thumb of a few weeks of backlog as healthy, enough to plan ahead without letting work go stale. The right number depends on the site.
In practice
A backlog is only useful when it is clean. Teams review it regularly, close duplicates, remove work that is no longer needed, and check that estimates are realistic. They also separate work that is ready to schedule from work waiting on parts, shutdowns, or approvals.
Related terms
For pitfalls and more examples, see Maintenance backlog.