Reactive vs Preventive Maintenance Costs

The reactive vs preventive maintenance comparison is usually run on the wrong numbers. The invoice for an emergency repair is visible and easy to argue about; the water damage under it, the after-hours premium, the tenant credit and the shortened asset life are spread across four other budget lines and nobody totals them.

Total them, and the argument normally ends. Below: where the money goes, when running to failure is genuinely cheaper, and how to move a building's mix without asking for a larger budget.

Key takeaways

The repair invoice is the smallest part of a reactive event. Secondary damage, downtime and administration usually exceed it.
Reactive maintenance is cheaper for low-consequence, cheap, replaceable items with no safety exposure. Those are real.
Some failures are not deferrable at all: life safety, water ingress and anything that fails into a hazard — critical
The ratio of reactive to planned work is the cheapest diagnostic a manager has.
Preventive work reduces cost by removing emergencies, not by making trades cheaper.
Moving the mix needs triage and a calendar, not a bigger budget.

What does reactive maintenance actually cost?

Five cost buckets, and only one of them appears on the work order. Direct labour and parts. Secondary damage to the building or to tenant property. Lost use — tenant inconvenience, credits, lost rent, overtime on other duties. Administration — the phone calls, quotes, approvals, escalations and re-inspection that an unplanned event drags behind it. And asset life, which shows up years later as a capital item that arrived early.

Cost bucket	Reactive	Preventive	Who notices first
Labour and parts	Emergency rate, after-hours premium, minimum call-out	Scheduled rate, bundled visit	Accounts
Secondary damage	Water, mould, electrical, tenant contents	Avoided by early detection	Tenant or insurer
Lost use	Comfort complaints, closures, credits	Planned outage, notified	Tenant
Administration	Quotes, approvals, escalation, rework	One work order in a schedule	Manager
Asset life	Shortened, unpredictable	Realised as designed	Owner, years later

The pattern is consistent: the bigger the secondary damage, the smaller the repair invoice looks. A failed sump pump is a pump; the flood it causes is a flooring, drywall, electrical and insurance file.

A worked example: the pump seal

Numbers vary by market, so treat these as illustrative arithmetic rather than a claim about your building. The structure is the point.

Planned: seal replaced during a scheduled pump service, daytime rate, one work order, no downtime beyond a notified hour. The building never notices.
Reactive: seal fails at 2 a.m. on a Saturday, emergency call-out, overtime rate, staff called in to move tenant property, wet-vac and drying, one damaged ceiling tile grid, an insurance notification, a complaint from the tenant below, and a re-inspection report.

The direct difference is a multiplier on the labour rate. The total difference is a multiplier on the whole event. That is why maintenance budgets built on invoices never capture the real number: the invoices that arrive are only the ones somebody chose to send you.

Why does reactive maintenance feel cheaper?

Three reasons, all management artefacts rather than economic facts.

It hides in three budgets. Maintenance pays the repair, operations absorbs the cleanup, capital absorbs the early replacement, and the insurance deductible resets every year. No single person adds those up, so no single line looks alarming.

Emergencies get approved; improvements get deferred. A $4,000 emergency is an operational necessity nobody argues about. A $4,000 preventive programme line is a discretionary spend that gets negotiated. The asymmetry in approval friction is enormous, and it pushes every building toward reactive work.

The cost lands on someone else's year. Shortened asset life and tenant dissatisfaction are slow variables. The manager who defers wins this year's budget meeting and loses in three years, usually after a transfer.

When is reactive maintenance the right answer?

Run-to-failure is a legitimate strategy, not a failure of management. It is correct when all of the following hold: the item is cheap relative to the cost of inspecting it, its failure causes no safety or compliance exposure, its failure is not progressive and does not damage anything else, and you hold a spare or can get one quickly.

Typical candidates: non-critical lamps in low-use areas, door closers in storage rooms, signage, small fixtures in unoccupied spaces, and components on equipment that is scheduled for replacement within a year. Reactive is also right for one-off events — storm damage, vandalism, a tenant-caused failure — where there is nothing to prevent.

It is never right for anything on the following list:

Fire and life safety devices, exits and emergency lighting — critical
Anything that fails wet: domestic water, drainage, sumps, condensate, roof penetrations — critical
Electrical equipment showing heat or arcing signs — critical
Gas appliances, refrigerant circuits and pressure equipment, which fail into a regulated hazard — critical
Equipment serving occupied space in extreme weather: heating, cooling, domestic hot water
Anything failing repeatedly in the same way, because repetition is a diagnosis, not bad luck

How do you decide which assets get preventive treatment?

Score two things: the consequence of failure and the likelihood of failure, then treat the score as a spending priority rather than a label.

	Low likelihood	High likelihood
High consequence	Condition monitoring; planned replacement at a defined interval	Act now; this is your next emergency
Low consequence	Run to failure, keep a spare	Cheap preventive task or a bulk replacement batch

Consequence includes safety, compliance, water damage, tenant impact and building closure. Likelihood comes from age, duty cycle, service history and what your inspections are finding. Write both down for the top twenty assets in the building; most portfolios find that two or three assets carry most of the risk, and that they have been absorbing the entire reactive budget for years.

Asset-level history is what makes this scoring honest. Failure trends and patterns shows how to read repeated failures, and asset registers with condition data gives you the fields to record them against.

What does the failure curve mean for intervals?

Most equipment failure follows a bath-tub shape rather than a straight line: early failures from installation and commissioning faults, a long middle of random failures, then a rising wear-out slope. Each region wants a different response, and using one interval for all three wastes money in one place and misses risk in another.

Early life: commissioning checks, warranty inspections and a short first-year review — critical
Random middle: condition monitoring, operator observation, and interval-based tasks only where the manufacturer specifies them
Wear-out: planned replacement or overhaul on a condition trigger, not on a calendar date

This is why "increase all frequencies" is a bad answer to a reactive problem. It raises cost without moving risk. Intervals should be set from evidence — preventive maintenance for property managers sets out how to choose and justify them.

How do you move the mix without a bigger budget?

Six moves, in order of effort. None requires a new system.

Triage last year's reactive work orders into three piles: preventable, not preventable, and unknown. Expect a third of them to be preventable. That list is your business case.
Convert the top three recurring emergencies into scheduled work with a defined interval and a named contractor, then put them on the year's calendar — building an annual maintenance plan covers that step.
Fix access and approval so scheduled work actually happens. A preventive visit that cannot get into the room becomes a reactive visit within a year.
Batch visits by trade and location. The labour rate is not where the saving sits; the visit count is.
Defer cosmetic work deliberately and say so in writing, rather than letting it quietly disappear.
Report the ratio monthly so the shift is visible before the budget conversation.

Move five of those and the budget rarely grows. It redistributes.

Which numbers show whether the shift is working?

Four, all available from your existing records. Leading indicators describe what you are doing; lagging indicators describe what happened, and the CCOHS fact sheet on leading and lagging indicators makes the useful point that lagging measures cannot tell you whether you are preventing anything — only what already occurred.

Reactive share of work orders, by month. Falling share means the mix is moving.
After-hours premium as a proportion of maintenance labour. This is the cleanest single cost signal.
Repeat failures per asset, rolling twelve months. Two or more means the fault is not being diagnosed.
Preventive completion on or before the due date, with overdue critical items reported separately — critical

Pair each cost number with a completion number: spend down with completion down is an underspend, not a success.

What is outside a manager's scope here?

The cost argument does not change the licensing boundary. Electrical work, gas appliances, refrigerant circuits, elevator maintenance, fire system testing, asbestos work and legionella sampling and treatment remain commission-and-verify, however attractive a cheaper reactive arrangement looks on paper.

Two traps. A contractor offering "as-needed" servicing on gas or refrigerant equipment is offering to skip the inspection that finds the leak first. A "call us when it breaks" arrangement on fire and life safety equipment is not a saving; it is an uninsured risk with your name on the contract.

Scope note: the licensed trades and regulated systems above sit outside a property manager's remit. Specify the interval, commission the licensed supplier, verify the certificate, and report rather than act.

Frequently asked questions

Is preventive maintenance always cheaper than reactive?

No. For low-consequence, cheap, replaceable items with no safety exposure, running to failure is rational. Preventive work wins where failure causes secondary damage, downtime, a compliance breach or a hazard — and there the gap is usually large.

What ratio of preventive to reactive work should a building aim for?

A common working target is 70% planned and 30% reactive or better, with reactive trending down year over year. The direction matters more than the absolute number; a building moving from 50/50 to 60/40 is improving even if it is not yet at target.

How do I prove the saving to an owner?

Compare total cost per event, not per invoice: labour, secondary damage, lost use, administration and any tenant credit, for the preventive route and the reactive route on the same failure. Two years of work orders give you the sample. Present the trend and the avoided events, not a projection.

Does running to failure work for anything important?

Only where failure is safe, cheap and non-progressive — a lamp, a signage item, a fixture in an unoccupied space. Never for life safety equipment, water systems, electrical equipment showing heat damage, gas appliances or refrigerant circuits.

Where does the money come from if the budget is already fixed?

Usually from within the reactive line, by triaging preventable emergencies and converting the top three into scheduled work. It also comes from batching visits and deliberately deferring cosmetic items in writing. A programme that starts with a budget request rarely starts.

Start with last year's work orders

Sort last year's reactive work orders into preventable and not preventable. The preventable list is the case for change, in your own building's numbers, and it is far more persuasive than any general argument about maintenance strategy.

NeatScore gives you the records the argument needs: area-specific checklists with critical items flagged, APPA 1–5 scoring, photos per item, offline inspections that sync, deficiency tracking with closure dates, portfolio dashboards and branded PDF reports for owners. Try it free for 14 days, or see pricing.