Deferred maintenance is the backlog of work that was identified, was not done, and has not gone away. Every site has some, and having some is not a failure. The failure is not knowing how much, because a backlog nobody has quantified cannot be argued for in a budget and cannot be prioritised, it simply resurfaces as emergencies in an order set by chance.
What the term actually means
The deferred maintenance meaning is narrower than general untidiness: it is work that was specified, was due, and was postponed, with the need still outstanding. That excludes work you decided not to do on purpose, which is a strategy decision rather than a deferral, and it excludes work nobody has identified, which is simply unknown. Keeping those three separate is what makes the backlog a number rather than a mood, and only the middle one belongs in it.
Why it compounds rather than waits
Deferred work does not sit still. A postponed roof repair admits water, which damages what is underneath; a postponed bearing replacement takes the shaft with it when it fails. So the cost of the same job rises with time, and the rise is uneven and hard to predict per item, which is precisely why it is easy to defer: nothing visibly worsens this month. Recording the deferral with a date and a reason at least makes the accumulation visible when somebody eventually asks.
Making the backlog usable
A deferred maintenance list is only useful with three things attached to each entry: what it costs to do now, what happens if it is not done, and when it becomes urgent. With those, the list is a budget argument and a priority order. Without them it is a wish list, and it will be treated as one. Building the habit of recording those three at the moment of deferral is much easier than reconstructing them a year later for a budget round.
Questions people ask about deferred maintenance
What does deferred maintenance mean?
Work that was identified and due, was postponed, and is still needed. Work you decided not to do on purpose is a strategy choice, and work nobody has identified is simply unknown, neither belongs in the backlog.
Why does deferring cost more than doing?
Because the deferred item usually damages something else while it waits: water gets in, a bearing takes the shaft with it. The rise is uneven and invisible month to month, which is what makes deferral easy.
What makes a deferred maintenance list useful?
Cost to do now, consequence of not doing it, and when it becomes urgent, recorded per entry at the moment of deferral. Without those three it is a wish list and gets treated as one.