Reactive vs Planned Maintenance Explained

Reactive and planned maintenance are the two fundamental approaches to keeping buildings and assets running. Reactive maintenance fixes things after they break; planned maintenance services and checks them before they do. Most organisations use a mix of both, but the balance between them has a big impact on cost, reliability, safety, and compliance. Understanding the difference is the starting point for an effective maintenance strategy.

What reactive maintenance is

Reactive maintenance (also called "run-to-failure" or corrective maintenance) means responding to faults and breakdowns as they occur. The boiler stops, a light fails, a door breaks — and you fix it. It's unavoidable to some degree (things break unexpectedly), and for some low-criticality, low-cost items, running them to failure is a legitimate strategy.

The downside: failures are disruptive, often happen at the worst time, can cause consequential damage, and may be more expensive to fix than a planned intervention. A reactive-heavy operation is constantly firefighting.

What planned maintenance is

Planned (preventive) maintenance means servicing and checking assets on a schedule to keep them working and catch problems early — before failure. It's proactive: replacing the filter before the unit fails, servicing the boiler before winter, testing the fire alarm on schedule. It trades a predictable planned cost for fewer unexpected failures, longer asset life, and better safety and compliance.

The trade-offs

The two approaches trade off differently:

• Reactive — no scheduled spend, but unpredictable costs, more downtime, shorter asset life, and reactive scrambling. Cheap until something important breaks.
• Planned — predictable, scheduled spend and effort, but fewer failures, longer asset life, better budgeting, and crucially, the ability to ensure statutory and safety-critical maintenance happens on time.

For critical and safety-related assets, planned maintenance isn't really optional — many systems (fire, lifts, electrical, water) have statutory maintenance requirements that a purely reactive approach would miss.

Finding the right balance

The goal isn't to eliminate reactive maintenance — some failures will always happen — but to shift the balance toward planned, so reactive work becomes the exception rather than the norm. A common measure of maintenance maturity is the ratio of planned to reactive work: more planned generally means a better-run, more reliable, more compliant operation.

Beyond the two: condition-based

Many operations also use condition-based and predictive maintenance — using monitoring and data to maintain assets based on their actual condition rather than just a fixed schedule. This is a refinement that targets effort where it's most needed, but it builds on the same proactive principle as planned maintenance.

Records tie it together

Both approaches generate records — reactive work orders and planned task completions — and analysing them together is powerful. If an asset keeps needing reactive repairs, that's a signal to change its planned regime or replace it. The data turns maintenance from firefighting into informed asset management.

Capturing it digitally

A maintenance system handles both: logging and tracking reactive work orders to completion, scheduling and recording planned tasks, and bringing the data together so you can see the planned/reactive balance, spot problem assets, and shift toward proactive maintenance.

Key takeaways

Reactive maintenance fixes things after they fail; planned maintenance prevents failures through scheduled servicing and checks. Reactive is unavoidable for some items but disruptive and costly when relied on; planned is predictable and essential for critical and statutory maintenance. The aim is to shift the balance toward planned, use condition data where useful, and analyse records to manage assets well.