Planned maintenance beats reactive every time

Reactive maintenance has one great advantage, and it is the reason it persists: the cost of doing nothing arrives later, and on someone else's watch. A planned programme asks for money and attention now, for problems that have not happened yet. Put like that, it is no surprise which one wins the budget argument in a difficult year. In our view, that argument is usually being lost on the wrong terms, because reactive work is rarely cheaper once the full bill is counted.

Reactive looks cheap because the cost is deferred

The appeal of running things to failure is that the invoice is invisible until the failure happens. A pump runs until it seizes. A roof is left until it leaks. A lift limps along until it strands residents. Each of these feels like a saving right up to the moment it is not, and at that moment the cost is almost always higher than the planned alternative would have been.

It is higher for a simple reason. Failure does not schedule itself for a convenient time, and it does not stay contained. A pump that fails takes out a service. A leak that is ignored becomes a damp problem and then a structural one. Emergency call-outs cost more than planned visits, collateral damage costs more than the original part, and a building out of action costs more than any of it. The saving was always borrowed against a larger future payment.

The hidden costs reactive work tends to carry

When we look at where reactive maintenance actually hurts, the same items recur. They are worth naming because they rarely appear on the line of the budget that gets cut.

• Emergency premiums on labour and parts that planned work would have bought at ordinary rates.
• Consequential damage, where a small unaddressed fault becomes a large one in an adjacent system.
• Disruption to residents or occupiers, which carries its own reputational and sometimes legal cost.
• Lost evidence, because work done in a panic is often poorly recorded, if it is recorded at all.
• Shortened asset life, as equipment run to failure tends to be replaced sooner than equipment maintained.

The first three are felt immediately. The last two are slower, which is exactly why they are underweighted in the decision.

Safety does not respond to budget timing

There is a category of maintenance where the reactive approach is not merely expensive but indefensible, and that is anything touching life safety. Fire systems, lifts, structural elements and the building envelope do not fail politely. They fail when they are loaded, which tends to be when they are most needed. A fire damper that has never been checked is a hazard discovered at the worst possible moment.

Several of these obligations are not discretionary in any case. Lifting equipment, for instance, carries statutory examination intervals under LOLER, and rented homes have electrical inspection requirements under the relevant landlord rules. Treating safety-critical maintenance as a thing to address when something goes wrong is, in our reading, both a financial mistake and a governance failure. The right posture is planned, scheduled and recorded, with no exceptions for the items that can hurt people. We make the specific case for one of these in the lift inspection you cannot skip.

Evidence is the quiet third benefit

The argument for planned maintenance is usually made on money and safety. The third benefit is less discussed and, we think, undervalued: a planned programme produces a clean record almost as a by-product. Work done on a schedule is work that gets logged, dated and signed off, because the schedule prompts it. Work done in an emergency is work that gets done first and documented later, if ever.

That matters because the question a regulator, an insurer or an incoming manager asks is rarely just whether the work happened. It is whether you can prove it happened, when, and by whom. A building with a planned programme can answer that. A building run reactively usually cannot, even where the work itself was sound. Keeping the schedule and its evidence together is the point of a compliance calendar that records what was due and what was done, rather than a wall planner that only shows intentions.

The honest comparison

The fair way to weigh the two is not planned cost against zero, which is how the reactive case is usually smuggled in. It is planned cost against the true, fully loaded cost of failure: the emergency premium, the collateral damage, the disruption, the shortened asset life, and the missing evidence. Set out that way, the planned programme is not the expensive option. It is the cheaper one whose costs are simply easier to see.

Our position is straightforward. For anything that can fail dangerously or expensively, plan it, schedule it, and record it. Keep a small, honest reactive budget for genuine surprises, because no programme catches everything. But do not let the deferred nature of reactive cost disguise it as a saving. The building does not forget the maintenance it was owed. It only sends the bill later, with interest.