Key takeaways
Short answer: A maintenance backlog is the queue of identified, planned work waiting to be scheduled — a healthy backlog of a few weeks is normal and gives planners something to optimise. Deferred maintenance is work that was due and consciously postponed, accruing risk of failure. Backlog is work waiting; deferred maintenance is risk accumulating. Tracking them separately is essential. See also preventive vs corrective maintenance.
A maintenance backlog is the healthy pool of identified, planned, ready-to-schedule work. A few weeks of backlog is a sign of good problem identification, not a problem — it gives planners the freedom to sequence work efficiently and batch jobs sensibly.
Deferred maintenance is different in kind: work that was actually due and was consciously pushed past its date. Every deferral is a small, accepted increase in failure risk — and unlike backlog, it does not just wait, it accrues danger the longer it sits.
A plant reports a "backlog" of 600 hours and leadership panics. Split it properly and the picture is clear: 520 hours are healthy backlog — identified work comfortably within schedule — while 80 hours are deferred maintenance, including a bearing replacement that was due six weeks ago on a critical asset. The 520 hours are fine; the 80 hours are the real risk. Reported as one number, the genuine danger was hidden inside a scary-but-harmless total.
A growing backlog may just mean good problem identification. Growing deferred maintenance means you are consciously running assets past their service point — a risk position leadership should see explicitly, not buried in a single backlog figure that mixes safe and dangerous work together.
1. Reporting one combined number. Real risk hides inside a harmless-looking total.
2. Panicking at healthy backlog. A few weeks of planned work is normal, not a crisis.
3. Deferring critical work silently. Postponement without a conscious risk decision.
4. No due-date tracking. You cannot tell backlog from deferred without it.
Deferred maintenance eventually surfaces as breakdowns — unplanned Availability loss at the worst time. Tracking it separately predicts where OEE will be hit next, turning a hidden risk into a visible, manageable one.
Fabrico ties planned work and due dates to assets, so deferred-past-due work is visible rather than buried in a backlog total. Book a demo to see real maintenance risk surfaced.
No — a healthy, plannable backlog of a few weeks is normal and useful.
It runs assets past their service point, accruing failure risk the longer it sits.
No — separate them so the real risk is visible, not hidden in a total.
It resurfaces as unplanned breakdowns and lost Availability.
By due date — backlog is within schedule; deferred is past its due date.
Programați o întâlnire individuală cu experții noștri sau înscrieți-vă direct în planul nostru gratuit.
Nu este nevoie de card de credit!
Login
Blog
