How to Get Out of Reactive Maintenance
Most plants do not have a reactive maintenance problem. They have a reactive maintenance habit, and the plant rewards that habit every single shift.
Here is the uncomfortable part. Reactive work keeps winning because it is the only work with a deadline attached to it. A breakdown screams. A planned job whispers. So when the pressure is on, the planned job is the one that gets bumped, and the breakdown is the one that gets the people. Do that for long enough and the whole plant learns a quiet lesson: planned work is optional, reactive work is real. That lesson is the actual disease. The breakdowns are just the symptom.
If you are sitting at a 60 to 70 percent reactive rate and wondering why throwing bodies at it never sticks, this is why. You cannot hire your way out of a habit. You change what the plant rewards, or you stay reactive. There is no third option.
Why reactive work keeps winning
Walk onto any reactive site and watch what gets praised. The fitter who pulled an all-nighter to get the crusher back online is a hero by smoko. The planner who quietly prevented that breakdown three weeks ago gets nothing, because nobody can see a failure that did not happen.
That is the trap in one sentence. Reactive work is visible and urgent. Planned work is invisible and important. Urgent beats important every time the schedule gets tight, and the schedule is always tight. I have written more about why this dynamic is so sticky in [why reactive maintenance keeps winning](https://www.ridgwayresilience.com/insights/why-reactive-maintenance-keeps-winning-and-how-to-break-the-cycle), but the short version is this: the plant is not broken, it is behaving exactly as it has been trained to behave.
Every time a planned job gets displaced from the schedule, you are not just losing one job. You are teaching the supervisor, the planner, and the crew that the schedule is a suggestion. The next displacement is easier. Then it is automatic. That is how a one-off bad week hardens into a culture.
The reactive trap, and why it feeds itself
The cycle is mechanical, and once you see it you cannot unsee it.
Less planned maintenance gets completed, because reactive work keeps eating the hours.
Equipment degrades faster, because the planned work that would have caught the early failure never happened.
More breakdowns follow, because degraded equipment fails.
Which leaves even less capacity for planned work.
Round and round. A site sitting at a 60 to 70 percent reactive rate can run this loop for years, convinced the answer is more people, more overtime, more heroics. It is not. More people inside a broken loop just gives the loop more fuel. You feel busier and the reactive rate does not move.
If you want to see where this quietly bleeds into your labour bill, the loop shows up first as overtime you cannot explain. I have unpacked that in [structural overtime and what it really costs](https://www.ridgwayresilience.com/insights/structural-overtime-maintenance-costs). It also shows up as a [maintenance backlog that keeps growing](https://www.ridgwayresilience.com/insights/why-your-maintenance-backlog-keeps-growing) no matter how hard the crew works, because in a reactive plant the backlog is never controlled, it is just survived.
What actually breaks the cycle
I have watched plants try to break this with a kickoff meeting, a new slogan, a poster in the crib room. None of it holds, because none of it changes what the plant rewards. You do not break a reactive culture with a speech. You break it by changing the cadence, one week at a time.
In every site I have seen come out of chronic reactive, three things were true. Not two. Three.
1. A real planning function that finds work before it fails. Someone whose job is to identify the work ahead of the breakdown and prepare it fully: parts staged, isolations sorted, scope clear, so the job can actually be executed on the day. Not a person who prints work orders. A planner who removes every reason a job would slip.
2. A protected schedule that management actually defends. A schedule is only worth the authority behind it. If a supervisor can pull a planned job off the board because the morning got noisy, you do not have a schedule, you have a wish list. Protecting the schedule is a management act, not a planning act. This is the one most sites skip, and it is the one that matters most. If you only measure one thing, measure [schedule compliance](https://www.ridgwayresilience.com/insights/maintenance-schedule-compliance-guide), because that single number tells you whether the plant is keeping its promises to itself.
3. A controlled backlog that drives the priority. Backlog is not a graveyard for jobs nobody will ever do. Used properly it is the tool that decides what gets done next and what can wait. An uncontrolled backlog is just anxiety in a spreadsheet. A controlled backlog is a steering wheel.
Miss any one of these and the cycle quietly reassembles itself. You can have a brilliant planner and a gutless schedule and you will still be reactive by Christmas.
What the numbers look like when it works
Here is the move you are aiming for: from a 60 to 70 percent reactive rate down to 30 to 40 percent reactive. That is not a fantasy number. I have stood in plants running at 30 percent reactive, and they did not get there with more headcount. They got there by protecting the cadence until the cadence protected them.
When a plant makes that shift, the changes stack up in a predictable order:
Overtime drops, because fewer unplanned callouts means fewer people dragged in at 2am to chase a failure that planning should have caught.
Equipment availability improves, because planned work is finally getting done before things break.
Technician productivity climbs, because a prepared job with the right parts and a clear scope gets finished in a fraction of the time a scrambled one does.
And the part nobody expects: supervisors stop managing chaos and start managing performance. Their day stops being a series of fires and becomes a series of decisions.
That last one is the real prize. A supervisor buried in reactive work is not leading, they are surviving. Give them a protected schedule and they get their job back.
If you want to know what your current reactive rate is costing in overtime, lost availability, and wasted labour before you change anything, pull 12 months of data and total it honestly. Seeing the annual figure in black and white tends to end the debate about whether this is worth fixing.
How long does it actually take
Breaking a chronic reactive cycle takes 8 to 16 weeks with proper structure and consistent management commitment. Not a weekend. Not a quarter of drifting. A focused stretch where the cadence is held every single week.
Here is what that stretch feels like from the inside, because the shape of it matters and most people quit before it pays off:
The first four weeks are the hardest. This is where it feels worse before it feels better. You are protecting planned work while breakdowns are still arriving, so it feels like you are fighting on two fronts. You are. This is the part where weak leadership caves and pulls the planned job to chase the fire, and resets the clock to zero.
By week six to eight, the shift becomes visible. The early planned work starts catching failures before they happen. The breakdown rate eases. People start to believe it.
By week twelve, the new operating rhythm is the default. Nobody is white-knuckling the schedule anymore. Protecting planned work has stopped being a fight and started being just how the plant runs.
The plants that fail do not fail at week twelve. They fail at week four, when it is hard and the results have not arrived yet. If you know that going in, you are far more likely to hold the line long enough to win.
The real barrier is not technical
None of this is hard to understand. Planning, a protected schedule, a controlled backlog. You knew the words before you opened this article.
The barrier is not technical. It is cultural, and it lives in leadership. The single hardest step is the decision, made out loud and meant, that the current state is no longer acceptable. Not "we should do better someday". A line in the sand. Because everything downstream of that decision is just discipline, and discipline is easy once the decision is real. It is the decision that people dodge.
The fitters did not choose the reactive culture. The schedule that keeps getting raided did not raid itself. Reactive is a management outcome, and that is good news, because management outcomes can be changed by management. You do not need a bigger crew. You need to change what the plant rewards, and then hold it for twelve weeks.
Where to start
You cannot fix a reactive rate you have never measured, so start by getting an honest read on where the hours are actually going.
If that read looks like the loop described above, it is worth a phone call. Ring 0493 262 725, or start at www.ridgwayresilience.com, where the Schedule Reset is laid out in full: a fixed-price, two-week engagement, delivered remotely, that gives you the consolidated schedule and labour-loading view this whole discipline hangs off. No forms, no funnel, and if there is not a sensible way out for your operation, I will tell you that too.
Reactive is a habit the plant rewards. Change the reward, hold the line, and in twelve weeks the habit changes. That is the whole game.