Reactive Maintenance: Are You Managing Your Assets, or Just Fixing Things When They Break?

Something breaks. Someone logs a call. A contractor is contacted, a part is sourced, the equipment is repaired and operations continue. That's reactive maintenance — and there's nothing inherently wrong with it. No organisation can predict or prevent every failure.

The problem starts when reacting to failures becomes the main way an organisation manages its assets.

In February 2026, Consulting Engineers South Africa (CESA) warned that the country faces a deepening infrastructure maintenance crisis, driven by years of underinvestment, reactive asset management and a growing shortage of engineering skills. CESA noted that many local and provincial authorities still manage assets reactively, responding only once systems fail — and pointed to the Minister of Public Works and Infrastructure's estimate of a R30 billion maintenance backlog across more than 56,000 state-owned properties.

That's a public infrastructure story, but the lesson will be familiar to facilities, maintenance and operations teams in every sector: when maintenance is driven mainly by failure, you're always one breakdown away from the next problem.

The maintenance firefighting cycle

An asset fails and becomes urgent. The urgent job jumps ahead of planned work, someone is called out, and the immediate problem is resolved. Then everyone moves on — until the same asset fails again.

This is where reactive maintenance gets expensive. Not necessarily because each repair is costly, but because the organisation never has the time or the information to step back and understand what's actually happening. Recurring failures become normal. Ageing assets keep receiving short-term fixes because replacement has never been properly evaluated. Planned inspections get postponed because something else is more urgent. And while the team deals with today's problems, tomorrow's quietly build up.

The real cost of a breakdown

The obvious cost of a failure is the repair. The less obvious costs are broader: emergency call-out charges, overtime, expedited parts, temporary equipment, interrupted production or services, unhappy tenants or customers, knock-on damage and management time.

Depending on the business, the consequence might be a closed facility, a failed cold room, a security system that's down, or a compliance issue.

Writing about Africa's industrial sector, Thava Govender, CEO: Engineering at Babcock, argues that uptime is no longer just a maintenance metric but a business strategy — because every hour of unplanned downtime has consequences that reach well beyond the maintenance department.

Maintenance may sit within the technical function, but the consequences of maintenance decisions sit across the business.

When the same asset keeps failing

Consider an air-conditioning unit that has failed four times in 18 months. Each repair may have looked reasonable at the time: the contractor attended, the faulty part was replaced, the system came back on.

But after the fourth failure, the question should change from "How do we fix it?" to "Why does this keep happening?"

What has already been replaced? How much has been spent? Is the unit nearing the end of its useful life? Would replacement now make more financial sense than another repair?

Those questions are hard to answer if the history isn't there — and often it isn't.

Maintenance teams carry a great deal of practical knowledge: which pump has always been troublesome, which contractor knows the generator, which building has recurring electrical faults. But when that knowledge lives in people's memories, email threads, spreadsheets, WhatsApp groups and old paperwork, it's difficult to share or act on.

A new facilities manager can inherit an asset base without inheriting its history — and the organisation ends up rediscovering the same problems.

Not every asset should be treated equally

Reactive maintenance also lets urgency set priority. The asset that's broken gets attention because it can't be ignored — but the asset that hasn't failed yet may matter more.

A generator that's running today but overdue for critical maintenance may be a bigger operational risk than a non-critical aircon that has just stopped working. A refrigeration system may be working fine, but its failure could affect stock, production or food safety. A pump may still be running while repeated faults point to an approaching failure.

That's why maintenance decisions need to consider criticality, not just whether something is broken right now.

Which assets are essential to operations, safety, compliance or customer service — and what happens if they're unavailable?

Not every asset needs the same level of maintenance, but you should know where your greatest exposure lies.

The hidden problem with deferred maintenance

When resources are tight, planned work gets pushed back because something more urgent has come up. One delay may not matter. Repeated delays create a backlog, and backlogs can eventually become failures.

In its response to the 2026 State of the Nation Address, CESA described infrastructure deteriorating under years of underinvestment and deferred maintenance, with outdated systems and fragmented procurement among the root causes.

The lesson for businesses isn't that every item must be dealt with immediately. It's that deferred work needs to be visible and deliberately managed: a reason for postponing it, an understanding of the risk, and a date when the decision will be reviewed.

Otherwise, "we'll deal with it later" quietly becomes the maintenance strategy.

Moving from firefighting to control

The objective isn't to eliminate reactive maintenance. It's to reduce how much of it has to be reactive — and that starts with good asset information and disciplined processes, not sophisticated technology.

(We covered the foundations in Four Things You Should Know About Your Assets.)

A useful starting point is to ask:

• Which assets fail repeatedly?
• Which critical assets have overdue maintenance or inspections?
• Where are you paying for the same repairs over and over?
• How much of your maintenance workload is planned versus reactive?
• Can you quickly establish what work was done, when and by whom?

The answers can be revealing.

You may find an asset that needs replacing rather than repairing again, a recurring contractor or equipment issue, or a critical inspection that has been deferred more than once. Or you may discover you don't have a complete enough picture to decide with confidence — which is useful to know in itself.

The goal isn't fewer maintenance jobs. It's fewer surprises.

Reactive maintenance will always have a place. The difference is whether you're managing the unexpected or living from breakdown to breakdown.

That's the gap Axario Business was built to close: an asset register that brings together asset history, work orders, inspections, sign-offs and photos, alongside recurring maintenance schedules and a downloadable evidence pack.

So you can know your risk, control your assets and prove your compliance.

Because you can't prevent every breakdown.

But you can stop being surprised by the same ones.

Related reading: Four Things You Should Know About Your Assets, Rather Than Try to Remember, The maintenance happened. Can you prove it?, and Insured, but not necessarily covered?.

Sources

• CESA warns of national infrastructure maintenance crisis — Consulting Engineers South Africa, 3 February 2026
• CESA Responds to SONA 2026: South Africa Must Move Beyond Reactive Governance — Consulting Engineers South Africa, February 2026
• Uptime is no longer a maintenance metric. It's a business strategy — Thava Govender, Babcock (CBN)