Reactive Maintenance

Fixing equipment after it has already broken down — the unplanned, run-to-failure work that a maintenance program tries to shrink.

Definition

Reactive maintenance — also called breakdown or run-to-failure maintenance — is any repair carried out after an asset has already failed or stopped performing. There is no schedule and no warning: a machine goes down, a work order is raised, and a technician scrambles to fix it. It is the default mode every maintenance team starts in, and the mode a good preventive program is designed to escape.

What reactive maintenance really costs

The repair bill may be only part of the consequence. Depending on the asset and failure, reactive work can add unplanned downtime, lost output, overtime, expedited parts, secondary damage, safety exposure, and schedule disruption. Quantify those costs from the operation's own events rather than applying an unsupported universal multiplier to every repair.

When reactive maintenance is the right call

Not every asset deserves a preventive schedule. For cheap, non-critical, easily replaced items — a light fixture, a $20 pump, a redundant component with a standby — running to failure is often the rational choice. The skill is deciding deliberately: reactive maintenance should be a strategy you chose for low-stakes assets, not a condition you are stuck in for critical ones.

How to reduce reactive maintenance

Start by measuring it: tag every work order as planned or reactive using a documented rule, then review the assets generating repeated emergency calls. Move suitable failure modes onto approved preventive or condition-based tasks, track whether breakdowns change, and repeat. Set the target from your own baseline, asset risk, production needs, and staffing rather than copying an unsupported universal ratio.

Is reactive maintenance always bad?

No. For low-cost, non-critical assets it can be the cheapest strategy. It becomes a problem when critical equipment is run to failure by accident rather than by choice.

How do I know if I have too much reactive maintenance?

Track reactive labor and event counts with a documented rule, then segment by asset class and consequence. Set the target from the operation's own baseline, risk, staffing, and production needs rather than copying a universal 30% threshold.