A backlog that means something
Most maintenance backlogs are a mixture of real work, duplicates, resolved jobs nobody closed, and things that will never be done. That mixture cannot be managed.
Ask a maintenance manager how big the backlog is and the number comes with a qualification: it includes some things that are already done, some duplicates, and a long tail nobody has looked at in a year. For a separate product-side perspective on employee awareness of monitoring practices, this employee-focused guide provides additional detail.
A backlog with those properties is not a work list. It is an archive of intentions, and its main effect is to make the department's real position invisible — including to the people who would fund a solution.
Clean it once, properly
Before a backlog can be managed it has to be made true. That means going through it item by item, once, and putting every job into one of four categories. For a wider operational and compliance reference, consult the Better Buildings O&M guide.
- Already done — close it, with a note that it was closed on review.
- Duplicate — merge into the surviving record so the history stays intact.
- No longer applicable — the asset was replaced, the tenant left, the area was refurbished. Cancel with a reason.
- Genuinely outstanding — keep, and re-assess the priority, because the original priority was set in different circumstances.
This is a few days of unglamorous work for a mid-sized site. It is also the only way to reach a number that can be quoted without a qualification.
A cancelled job with a recorded reason is evidence of a decision. A deleted one looks identical to a job that was never raised, and the pattern of what gets cancelled is useful information.
Measure it in hours, not in jobs
A count of open jobs is nearly meaningless because jobs are not comparable. Forty lamp changes and forty plant overhauls are the same number and completely different problems.
Backlog measured in estimated labour hours is directly comparable to available capacity, which makes it an operational figure rather than a statistic. 'Three hundred hours of outstanding work against a team supplying a hundred and twenty productive hours a week' is a sentence that supports a decision.
Split it by category
A single total hides everything that matters. The splits worth reporting separately are statutory or compliance work outstanding, safety-related work, planned work overdue, and reactive work outstanding.
These behave differently and warrant different responses. Overdue statutory work is a compliance exposure with a deadline attached; an ageing tail of low-priority reactive jobs is a resourcing question. Reported as one number, the first hides inside the second.
Watch the trend, not the level
The absolute size of a backlog is partly an artefact of how thoroughly work is recorded — a department that logs everything looks worse than one that logs selectively. What is not an artefact is the direction of travel.
Track incoming jobs against completed jobs each week. Consistently more in than out means the backlog grows regardless of how hard anyone works, and no amount of effort inside the department resolves an arithmetic problem of that kind.
Age it, and act on the old items
Every backlog develops a tail of jobs that have been open long enough that nobody remembers them. Review anything past a defined age — six months is a reasonable trigger — and make an explicit decision: do it, schedule it, or cancel it with a reason.
The point is that all three outcomes are acceptable and indefinite waiting is not. A job open for two years is telling you it will never be done, and leaving it open only obscures the jobs that will be.