Scheduled downtime: the planned price of healthy equipment
On Thursday afternoon the planner locks in next week's schedule. On it: a compressor service, a pump bearing replacement, a conveyor alignment. Each will take its machine offline for a measured block of time, and every one of those blocks is time ...

On Thursday afternoon the planner locks in next week's schedule. On it: a compressor service, a pump bearing replacement, a conveyor alignment. Each will take its machine offline for a measured block of time, and every one of those blocks is time the line will not be producing. But this is lost time of a very different kind from a breakdown. It was chosen, prepared for, and known to operations in advance.
Scheduled downtime is the productive face of lost time. It is the price you agree to pay, on purpose, to keep equipment healthy.
What it actually measures
Scheduled downtime is the actual hours an asset could not run because of work that was on the finalised weekly maintenance schedule, committed, as a rule, three or four days before the week began. Planned preventive maintenance, condition-based repairs, turnarounds and set-ups all count.
One detail matters more than it looks: you record actual hours, not the estimate. If a job planned for 20 hours runs to 30, you log 30. Anything else quietly understates what your maintenance strategy really costs in capacity, and a metric that flatters itself is worse than none.
How to work it out
Scheduled downtime = Sum of actual asset downtime hours on the weekly schedule
In a month, the schedules carried 30 hours of preventive maintenance, 10 of repairs and 10 of set-up.
Scheduled downtime = 30 + 10 + 10 = 50 hours
Across a 720-hour month that is 6.9% of available time spent, deliberately, on planned work. That figure now joins your trend line and rolls up into total downtime.
What good looks like, and why the trend is subtle
There is no universal target for scheduled downtime on its own, and chasing one would miss the point, because planned work is cheaper, safer and far less disruptive than the unplanned kind it prevents. A reactive repair typically costs around three times the same job done on a schedule, so hours spent in this column are usually buying you out of much costlier hours in the other one.
That makes the trend genuinely two-sided, and worth reading with care. A rising scheduled-downtime figure can be exactly what success looks like: a plant climbing out of firefighting deliberately moves work from the unscheduled column into the scheduled one, so its planned downtime grows even as its reliability improves. The same rise can also be a warning, an ageing asset base needing ever more attention, or a preventive programme bloated with tasks that no longer earn their place. The number alone cannot tell you which. The way to read it is always alongside unscheduled downtime: scheduled rising while unscheduled falls is a plant getting control of its work; scheduled and unscheduled both rising is a plant in trouble.
Where it can mislead you
- Record actual hours, never planned ones. Estimates understate the true capacity cost and quietly corrupt your trend.
- If you have no formal weekly schedule, treat any downtime known at least a week ahead as scheduled, and apply that rule consistently.
- Norms vary by industry, so be wary of comparing your raw figure with another sector's.
- Never read it in isolation. The same upward trend is a triumph or a red flag depending entirely on what unscheduled downtime is doing beside it, so always look at the pair.
Planned downtime is one of the few costs in a plant that pays you back, in the failures that never happen. Tracking it on its own is how you make sure it stays an investment, growing for the right reasons rather than drifting upward as a habit nobody questions.



