It happens when it suits you
A scheduled intervention gets slotted into a planned downtime or a low season. The same intervention after a breakdown happens when everything has to stop.
Guide
Planning isn't doing more maintenance: it's doing it when it's due
The difference between a maintenance programme and a list of pending tasks isn't the number of interventions. It's that some are decided in advance and others are decided by the breakdown.
What a planned maintenance programme is
It's the set of interventions an organisation decides to carry out on its assets in advance, with a frequency, scope and owner defined before they're needed. It's also called scheduled maintenance, and its distinctive trait isn't that it's preventive: it's that the date and content of the intervention are set when there's time to think them through, not when something has broken and there's a rush. That difference in timing explains almost all of its benefits.
Why planned maintenance is cheaper
Not by magic: for five fairly concrete reasons.
The part is there
You know weeks ahead what's going to be needed. In a reactive repair, half the downtime is usually spent waiting for material.
The right person does it
With time, it gets assigned to the right person and the work gets grouped. An emergency gets handled by whoever is free, who isn't always the one who knows most.
No emergency surcharges
The price of a subcontractor on a Tuesday morning and the price of the same subcontractor on a Saturday at eleven have nothing to do with each other.
Less damage
Replacing a worn part costs what it costs. Replacing it after it has damaged what was around it costs a lot more.
When to stop planning more
The reasoning above has a limit worth knowing, because taken to the extreme it produces the opposite problem. Every scheduled intervention costs hours, parts and often a negotiated shutdown, and past a certain frequency you're replacing material that still had life left and stopping lines that didn't need stopping. Where to stop adding inspections isn't a formula: it depends on how much it costs for that asset to stop and how often it actually fails. And that last part is only known through history. That's why the sensible sequence is to record what happens first and adjust the plan afterwards, instead of designing an exhaustive plan straight from the manufacturer's catalogue.
The benefits that don't show up in euros
There are three that rarely show up in the investment case and that in practice weigh as much as the savings. The first is the predictability of the team's work: an operation where eighty percent of interventions are planned can organise holidays, training and leave; one that lives off reactive work can't. The second is that planned work gets executed better, because it's done without the pressure of restoring service right now. And the third is that a plan that's followed leaves a trail, which in installations with regulatory obligations is the difference between being able to prove something and having to explain it.
Shall we look at it with your way of working?
Leave your details and we will get in touch to see whether we fit. No commitment, no lock-in period.
Where to start if there's nothing yet
Not with the full plan. What works is choosing the assets whose failure hurts the most — not the most expensive ones, the ones that cause the most stoppages — and building their plan first, with the bare minimum: what to check, how often and who does it. With that, real orders start flowing within weeks, the team gets used to it, and the first data appears. Everything else gets added afterwards, and the plan for the first assets gets adjusted based on what the history shows. An exhaustive programme designed in a meeting room and rolled out all at once has good odds of ending up ignored and discredited, which is worse than not having one.
The indicator that shows whether the programme is real
Almost every company that says it has a maintenance plan has one on paper. Whether they really have one comes down to a single number: what percentage of the preventive tasks scheduled for the month got carried out by their due date. It's an uncomfortable indicator because it usually starts low, and that's precisely why it's useful: it can't be argued with. If compliance sits at forty percent, the plan isn't badly designed, it's oversized for the team that has to execute it, and the right move isn't to push harder but to cut it down to a size that can actually be sustained. A plan at seventy percent of a realistic scope performs far better than one at thirty percent of an ideal scope, partly because the first one is trusted and the second one stops being looked at after two months.
When the urgent eats the planned
Every day there's a breakdown that justifies postponing an inspection, and that's the exact mechanism by which maintenance programmes die. They don't die from one decision, they die from two hundred reasonable decisions made one at a time. The only thing that stops it is making sure postponing leaves a trail: that the preventive task isn't erased from the calendar but rescheduled with a new date, and that at month's end you can see how many were moved and why. When that's visible, the conversation changes tone, because it stops being an impression that "we're firefighting" and becomes a figure someone has to explain.
Frequently asked questions
How much do you save with a planned maintenance programme?
It depends so much on the case that any general percentage is just marketing. What can be stated is where the savings come from: downtime slotted in when convenient, parts on hand, no emergency surcharges and less collateral damage. How much that adds up to at your site gets calculated with your data.
Is planned maintenance the same as preventive maintenance?
Almost. Preventive is the maintenance done before a failure; planned or scheduled maintenance is decided in advance, which also includes scheduled corrective work that doesn't require immediate intervention.
Can there be too much planned maintenance?
Yes, and it's more common than it seems. Past a certain frequency you start replacing parts that still had life left and stopping lines unnecessarily. The balance point depends on the cost of downtime and the real failure frequency, and only the history can tell you that.
Where do I start?
With the assets whose failure hurts most, not the most expensive ones. Build their plan with the bare minimum — what to check, how often, who — and extend it afterwards. An exhaustive programme rolled out all at once tends to end up ignored.
Start with what stops you the most
In the demo we pick two or three of your critical assets and build their plan, to see the effect before rolling it out further.