Run-to-failure maintenance (also called run-to-fail or corrective maintenance) is a deliberate strategy of operating an asset until it breaks down, then repairing or replacing it, rather than performing scheduled preventive work or condition-based monitoring.
It is a legitimate maintenance strategy — not simply neglect — when applied intentionally to low-criticality assets where the cost and risk of failure are lower than the cost of a prevention program.
Run-to-failure is a choice, not a default
The label carries a stigma because most unplanned maintenance in poorly run operations is accidental run-to-failure: no PM program exists, so everything runs until it breaks, including assets where that’s genuinely the wrong call. That’s different from intentional run-to-failure, where a reliability team has looked at an asset and decided the numbers favor letting it fail.
The decision usually comes down to comparing:
- Cost of failure — replacement part cost, labor, and any downtime or safety consequence
- Cost of prevention — the labor, parts, and production interruption a PM program would require
- Criticality — whether the asset’s failure stops a production line, creates a safety hazard, or merely means swapping a cheap component
A backup water pump that’s inexpensive, has no safety implications, and doesn’t stop production if it fails is often a better run-to-failure candidate than a candidate for a scheduled PM program. A gearbox on the sole production line, by contrast, almost never is.
Where run-to-failure fits among maintenance strategies
Maintenance strategies exist on a spectrum from purely reactive to fully predictive:
| Strategy | Trigger | Best suited for |
|---|---|---|
| Run-to-failure | Asset breaks down | Low-cost, low-criticality, redundant assets |
| Preventive maintenance | Calendar or usage interval | Assets with predictable wear patterns |
| Condition-based maintenance | Sensor threshold crossed | Assets where degradation is measurable before failure |
| Predictive maintenance | Data-driven failure forecast | High-value, high-criticality assets with rich sensor data |
Most mature maintenance operations run a mixed portfolio: run-to-failure for the low-value, redundant, easily-replaced tail of the asset register, and progressively more proactive strategies as asset criticality and failure cost rise. Trying to apply a rich preventive or predictive program to every asset in a facility — including the ones that genuinely don’t need it — wastes labor and PM budget on the wrong equipment.
How CMMS supports intentional run-to-failure decisions
A CMMS makes run-to-failure defensible rather than accidental by capturing the data needed to justify the decision and catch it if it stops being the right call:
- Failure history and MTBF trends reveal whether an asset is failing more often than expected, which should trigger a strategy review
- Work order costs over time make the “cost of failure vs. cost of prevention” comparison concrete rather than a guess
- Asset criticality ratings, stored against each record in the asset register, flag which run-to-failure assets should be re-evaluated as they age or as their role in the operation changes
The risk with run-to-failure is not the strategy itself — it’s applying it to assets by default, without ever revisiting the decision as conditions change.
Related terms
Run-to-failure sits at the reactive end of the spectrum anchored by preventive maintenance scheduling and predictive maintenance, and the decision to use it should be informed by an asset’s lifecycle management profile and MTBF trend.