ServicesHow We WorkSectorsAcademyLibraryAboutContactOpen the Toolbox →
Maintenance · Strategy · Corrective

Corrective maintenance: fixing it after it fails

Corrective maintenance is the work you do after a failure has happened โ€” to restore the item to working order. It sounds like the thing to avoid, and often it is, but it has a legitimate, planned place in every maintenance program. The key is getting the definition right, because the line between corrective and preventive is the single most useful distinction in maintenance โ€” and it is not where most people draw it.

ReactiveBreakdownRun-to-failureEN 13306
Strategies
1Corrective (CM)You are here 2Preventive (PM)Before failure 3Predictive (PdM)Data-driven
⚡ TL;DR

Corrective maintenance (CM) restores an item after it has failed. The defining line is the failure event: work done after the breakdown is corrective; work done before it โ€” even if triggered by a rumbling bearing or a rising temperature โ€” is preventive.

CM splits into immediate (breakdown) corrective โ€” drop everything, the machine is down โ€” and deferred corrective โ€” the failure happened but you can schedule the repair. Deferred is far cheaper.

Reactive CM isn't always wrong: for cheap, non-critical, fail-safe items, run-to-failure is the rational choice. It's only a problem when it's the default for things that matter.

1 · The distinction that matters

The words "corrective" and "preventive" get muddled constantly, usually because people anchor on how planned the work was rather than when it happened. Here is the clean rule, and it's worth memorising:

If the work is done to prevent a failure / production disruption, it is preventive โ€” even if you only acted because a bearing started to rumble or a temperature rose. If you refit it before it breaks down, that's preventive. Corrective maintenance is the work done after the failure has occurred, to correct it. The dividing line is the failure event, not how much warning you had.

This matters because it changes how you classify โ€” and therefore measure โ€” most of your work. A condition-triggered bearing change done while the machine still runs is preventive, not corrective, because it stopped the breakdown. Only once the bearing has actually seized, and you're repairing the consequences, is it corrective. Get this right and your reactive-vs-proactive metrics finally mean something.

Preventive vs corrective on the condition timeline Condition declines over time. Everything done before the failure event is preventive (including condition-triggered work); everything after the failure is corrective. Condition Time โ†’ PREVENTIVE โ€” before failure CORRECTIVE โ€” after CBM detects (rumble / heat) refit now = preventive FAILURE repair = corrective
The line is the failure, not the warningDetecting a fault and refitting before the breakdown is preventive โ€” condition data just lets you do preventive work later and more precisely. Only the repair done after the failure is corrective.

2 · Two kinds of corrective

The whole art of running corrective work well is converting immediate into deferred wherever possible โ€” through redundancy, standby units, and fail-safe design โ€” so that even after-failure work can be planned rather than panicked.

3 · The true cost of breakdown

Unplanned corrective work is the most expensive way to maintain anything, and the repair bill is only the visible part:

CostPlanned (deferred / PM)Unplanned (breakdown CM)
LabourScheduled, normal hoursOvertime, call-outs, idle waiting
PartsStaged, in stockExpedited freight, premium price
ProductionPlanned outage / standbyLost output, missed deliveries
Secondary damageAvoidedCollateral โ€” seized shaft, wrecked rotor
Safety / environmentControlledHigher risk under pressure

Rules of thumb in the industry put unplanned work at 3–5× the cost of the same job planned. That multiple is the entire economic case for the other two strategies.

4 · When run-to-failure is right

Reactive maintenance gets a bad name, but deliberately choosing to run an item to failure is a perfectly valid strategy โ€” when the maths supports it. Run-to-failure makes sense when:

Deciding which items those are is exactly what criticality and RCM are for. Run-to-failure should be a chosen strategy for low-consequence items โ€” never the accidental default for everything.

The goal isn't zero corrective โ€” it's zero surprise. A mature program still does corrective work, but most of it is deferred and planned, and the unplanned breakdowns are confined to items where that's the deliberate, economical choice. You get there with preventive and predictive maintenance.

Key takeaways

The strategies