The two definitions, precisely
Breakdown maintenance is reactive: you repair an asset after it has failed. The machine has already stopped, so the work is unplanned, urgent, and carried out under pressure — often with an emergency spare and overtime. Preventive maintenance is planned: time- or usage-based work carried out before failure — inspection, lubrication, adjustment, part replacement — governed by a schedule, a checklist and, where the job is hazardous, a safety work permit. One responds to failure; the other tries to prevent it.
The instinct in many plants is that breakdown maintenance is the cheap default and preventive maintenance is a nice-to-have you fund when there is spare time. That instinct is backwards, and understanding why is the whole point of this guide. For the wider context of where these two sit among reactive, preventive, predictive and reliability-centred approaches, see the full types of maintenance strategies, and the pillar, what is CMMS software.
The true cost of breakdown maintenance
Breakdown work looks cheap because the only obvious line item is the repair itself — you spend when something breaks and not before. But the visible repair is the smallest part of the bill. The hidden costs stack up fast:
- Unplanned downtime — production stops without warning, dispatches slip, and idle operators are paid to wait.
- Emergency spares — parts bought at premium prices with expedited freight because there was no time to plan.
- Secondary damage — a failure caught early is a bearing; caught late it is a bearing, a shaft and a gearbox.
- Quality and safety risk — a machine that stops mid-run can scrap a batch or injure an operator.
- Shortened asset life — wear runs unchecked, so the machine reaches replacement sooner.
Preventive maintenance converts these unpredictable, expensive events into predictable, cheaper ones. You choose the window, you have the spare on the shelf, and you catch the fault while it is still small. The trade you are making is a little planned labour and spares now against a lot of unplanned cost later.
Side by side comparison
| Aspect | Breakdown (reactive) | Preventive (planned) |
|---|---|---|
| Timing | After the asset has failed | Before failure, on a schedule |
| Downtime | Unplanned — stops production without warning | Planned — done in a chosen window |
| Spares | Often emergency, expedited, premium-priced | Stocked ahead against reorder levels |
| Cost profile | Low until it fails, then multiplies | Predictable planned labour and spares |
| Effect on the asset | Wear runs unchecked; life shortens | Condition maintained; life extended |
| Labour | Overtime, firefighting, interruptions | Scheduled into normal working hours |
| Right for | Both have a place — run-to-failure suits low-criticality assets; preventive protects the critical ones | |
Where corrective maintenance fits
People often use "breakdown" and "corrective" as synonyms, but the distinction matters. Corrective maintenance is any work that fixes a known defect — and it comes in two flavours. Reactive corrective work is the breakdown: the fault has already stopped the machine. Planned corrective work is when an inspection or a preventive check finds a developing fault — a not-OK checklist item — and you schedule the repair before the asset actually fails.
That planned-corrective path is one of the biggest wins a CMMS unlocks. During a preventive job, a technician records each checklist item as OK, not-OK or a measured value; a not-OK finding can spawn a corrective job that is done calmly, in a chosen window, with the right spare — not as a 2 a.m. emergency. So the honest hierarchy is: all breakdown maintenance is corrective, but not all corrective maintenance is a breakdown. The goal of a good programme is to move as much corrective work as possible out of the breakdown column and into the planned one.
Curious what your real planned-to-reactive ratio is?
We can show a live maintenance calendar and a breakdown ticket with downtime capture on your own assets, so the ratio stops being a guess — in 30 minutes.
When run-to-failure is the right call
Here is the part generic advice skips: preventive maintenance is not always worth it. Deliberately letting an asset run until it breaks — run-to-failure — is a legitimate, cost-rational strategy for the right assets. The candidates share a profile: low criticality, cheap to replace, quick to swap, no safety or quality consequence when they fail, and — crucially — the failure does not stop a production line. A spare light fitting, a non-critical hand tool, or a redundant pump that has a standby ready are classic examples.
For those assets, spending planned labour to inspect and pre-empt failure costs more than the failure itself. Run-to-failure becomes the wrong choice the instant a stoppage causes line downtime, a safety hazard, secondary damage, or an expensive expedited spare. The skill is not choosing one philosophy for the whole plant; it is sorting assets by criticality and applying the cheapest strategy that is safe for each. That sorting is exactly what asset criticality in an asset register is for.
The right ratio, and how to shift it
So what balance should you aim for? There is no single universal figure, but reliability practice often cites a rough 80:20 split of planned to reactive work by labour hours on critical assets as a healthy target — while acknowledging that many plants start closer to 20:80 and improve from there. The exact target depends on your asset mix: you concentrate preventive effort where failure hurts most and accept more reactive work on the assets you have chosen to run to failure.
What matters more than the number is that the ratio is a decision, not an accident. To move it deliberately you need three things: a criticality rating on each asset, a preventive schedule on the ones that warrant it, and an honest count of planned versus reactive hours. A CMMS supplies all three. It also gives you the breakdown history — which assets fail most, how often, and why — so you can point preventive effort where the data says it will pay back, rather than spreading it evenly and thinly.
An Indian plant example, in INR
Consider a CNC machine in a Pune auto-component shop. Suppose an unplanned breakdown costs roughly ₹4,000 per hour in lost output and idle labour, a typical unplanned failure runs eight hours (part hunted for, expedited, fitted), and the machine fails six times a year on a reactive regime — about ₹1.9 lakh a year in downtime alone, before premium spares. Now suppose a modest preventive programme — scheduled inspections, timely belt and filter changes, spares stocked to reorder level — cuts failures to two a year and, because the right spare is on the shelf, trims each repair to three hours. Downtime cost falls to around ₹24,000.
The preventive labour and spares are not free, but they are a fraction of the ₹1.6 lakh saved on that one machine — and the software cost is spread across the whole plant. (Figures here are illustrative, to show the arithmetic; model it with your own downtime cost, and confirm any tax treatment with your CA.) This is why the ROI of a CMMS is almost always an uptime story: see the full benefits of CMMS software.
How a CMMS runs both sides
Fast Maintenance Software is built to run preventive and breakdown work as two halves of one system, on the shared Fast Suite platform, cloud or on-premise:
Frequently asked questions
What is the difference between preventive and breakdown maintenance?
Breakdown maintenance is reactive — you repair an asset after it has already failed, which means unplanned downtime, emergency spares and the risk of secondary damage. Preventive maintenance is planned — time- or usage-based schedules, checklists and safety work permits carried out before failure to keep the asset healthy and extend its life. A good CMMS runs both: it captures breakdowns fast when they happen and drives a preventive calendar to make them rarer. The aim is not to eliminate breakdown work entirely, but to shift the ratio toward planned maintenance on the assets that matter most.
Is breakdown maintenance the same as corrective maintenance?
They overlap but are not identical. Breakdown maintenance is corrective work triggered by an unexpected failure — the machine has stopped and you must restore it now. Corrective maintenance is the broader category: any repair that fixes a known defect, which also includes planned corrective work scheduled after an inspection finds a fault but before the asset actually fails. In short, all breakdown maintenance is corrective, but not all corrective maintenance is a breakdown; some is planned, calmer and cheaper.
When is run-to-failure the right maintenance strategy?
Run-to-failure — deliberately letting an asset run until it breaks — is a valid strategy for low-criticality assets that are cheap, quick to replace, have no safety or quality consequence when they fail, and where a failure does not stop a production line. A spare light fitting or a redundant pump with a standby are classic candidates. It becomes the wrong choice the moment a failure causes unplanned line downtime, safety risk, secondary damage or an expensive expedited spare — which is exactly when preventive maintenance earns its keep.
What is the ideal ratio of preventive to breakdown maintenance?
There is no single universal number, but a widely used benchmark in reliability practice is roughly an 80:20 split of planned to reactive work by labour hours on critical assets — many plants start closer to 20:80 and improve from there. The right target depends on asset criticality: you invest preventive effort where failure hurts most, and accept more reactive work on assets that are cheap to let fail. A CMMS lets you measure your current ratio honestly and move it deliberately rather than by luck.
How does a CMMS help balance preventive and breakdown maintenance?
A CMMS drives the preventive calendar — time- or usage-based schedules with checklists, work permits and PM-due alerts by email, SMS or WhatsApp — so planned work actually happens on time. At the same time it captures every breakdown as a ticket with downtime, feeding MTTR and MTBF. Because both sides live in one system, you can see your planned-to-reactive ratio and each asset's breakdown history, then move preventive effort onto the machines that fail most. That is how the balance becomes a decision instead of an accident.