A maintenance backlog is the accumulated body of identified maintenance work that has been requested or planned but not yet completed. It includes overdue preventive tasks, pending corrective repairs, and inspection findings awaiting action. Measured in labor hours (or crew-weeks), it signals whether your team is keeping pace with the demands of your equipment.
Backlog is work that is identified, estimated, and ready or waiting, but not yet done. Being precise about scope keeps the number meaningful.
Exclude vague ideas, unestimated requests, and completed work. A reactive breakdown you fix within the hour never enters the backlog. Distinguishing this from ongoing unplanned downtime matters: downtime is lost production time, while backlog is pending labor. The two are linked, because a growing backlog of deferred repairs tends to drive more unplanned failures later.
A controlled backlog is healthy. It gives planners a buffer of vetted work to schedule efficiently, keeps technicians productive during production gaps, and lets you sequence jobs by priority rather than by panic.
The standard way to size a backlog is to express it in crew-weeks, so it is comparable across teams of different sizes. The formula is:
Backlog (crew-weeks) = Total outstanding maintenance labor hours / Weekly available crew hours
Many maintenance organizations target a total backlog of roughly 4 to 6 crew-weeks, with about 2 to 4 crew-weeks of that being ready-to-schedule work. At 8 crew-weeks, the example above is running hot and needs attention. Track this weekly so you can see the trend, not just the snapshot.
A single number hides direction and quality. Pair the size with two supporting measures.
Read together: if backlog is stable and PM compliance is high, the buffer is doing its job. If backlog is rising and compliance is falling, corrective work is crowding out planned work, and reliability will follow it downward.
Attacking a bloated backlog blindly wastes effort. Work it down systematically.
A modern CMMS underpins all of this by capturing every work order, tracking PM due dates, logging estimated hours, and surfacing backlog and compliance in one view. Fabrico's work order management keeps ready and waiting jobs visible and prioritized, so planners schedule from a clean, current list instead of a spreadsheet that drifts out of date.
Backlog is a leading indicator for the health of your whole maintenance program. A disciplined backlog is a foundation of total productive maintenance, where planned work steadily replaces firefighting. As backlog stabilizes and PM compliance rises, unplanned stops fall, and availability improves, which flows straight into your equipment effectiveness numbers. When production and maintenance data live together, teams can see how deferred work today shows up as lost output tomorrow.
Most maintenance organizations aim for a total backlog of about 4 to 6 crew-weeks, with roughly 2 to 4 crew-weeks of ready-to-schedule work. Below that suggests over-capacity or weak inspections; well above it means deferred work is accumulating faster than the team can clear it. The trend over time matters as much as the absolute figure.
Backlog is identified work that has not started yet, waiting to be scheduled or blocked on parts and access. Work in progress covers jobs technicians have already begun. Keeping them separate matters because a small in-progress count with a large backlog signals a scheduling or capacity gap, not a lack of identified work to do.
Review total backlog and PM compliance weekly so you catch trends early, and hold a deeper backlog cleanup monthly to close stale orders and re-prioritize. Weekly cadence lets you see whether completion is keeping pace with intake. Waiting for quarterly reviews usually means a backlog has already grown large enough to drive unplanned failures.
Book a Fabrico demo to see how real-time work order tracking, preventive maintenance scheduling, and backlog reporting come together, so you can measure your crew-weeks, protect PM compliance, and keep deferred work from turning into downtime.