Something on your next shutdown will go wrong. That's not pessimism, it's just the nature of compressing a year's worth of deferred work into a fixed number of days with contractors you don't manage day to day. The goal was never a perfect shutdown — it's one where the things that go wrong are small, caught early, and don't cascade into an extended outage. That difference comes down to how the scope was frozen, how the schedule was built, and whether the team actually knew what was happening on-site in real time. A platform like OxMaint keeps scope, schedule, and live shutdown status in one place, so problems surface while there's still time to react.
Run Your Next Shutdown With Real-Time Visibility
Track scope, schedule, contractor progress, and budget against plan, with issues surfaced the moment they happen, not at the next standup.
The Four Phases of a Shutdown
Every shutdown, regardless of size, moves through the same four phases — the difference between a smooth one and a painful one is almost always how well each phase was actually finished before the next one started.
Scope Freeze
Every job that will happen during the outage is locked, reviewed, and resourced weeks in advance.
Mobilisation
Contractors, parts, and permits arrive on-site, matched against the frozen scope before the plant goes down.
Execution
Work runs against the schedule, with daily progress tracked against plan and deviations flagged immediately.
Startup & Closeout
The plant restarts, punch list items get closed out, and lessons learned are captured before the team disperses.
Where Shutdown Budgets Actually Go
Most overruns don't come from one dramatic failure — they come from underestimating a category that quietly grows over the course of the outage.
Shutdown Risk Matrix
Schedule Risk
Work discovered once equipment is opened up that wasn't in the original scope, pushing the critical path.
Safety Risk
Unfamiliar contractors working in a compressed timeframe raise the stakes on permits and isolations.
Cost Risk
Day rate contractor costs and rush-ordered parts accumulate quickly once the schedule starts slipping.
Scope Creep
Small additions get approved on-site without going through the same review the original scope did.
A shutdown rarely fails because of one big mistake — it fails because small deviations from plan went unnoticed until they'd already cost days. Sign up free to track your next shutdown in real time, or book a demo to see how it fits your turnaround process.
Catch Shutdown Deviations Before They Cost You Days
One system for scope, schedule, and budget, with daily progress tracked against plan from mobilisation to startup.
Pre-Shutdown Checklist
Scope frozen at least six weeks out
Every job is reviewed, prioritised, and locked before contractors and parts are ordered against it.
Permits and isolations pre-planned
Isolation points and permit requirements are mapped to the schedule, not worked out on the day.
Contractor inductions scheduled
Safety inductions and site orientation happen before mobilisation day, not during it.
Spares kitted and staged on-site
Parts for every frozen scope item are confirmed on-site and ready before the plant comes down.
Frequently Asked Questions
How far in advance should shutdown scope be frozen?
A common benchmark is around six weeks before mobilisation, giving enough time to order parts and confirm contractor resourcing against the final scope.
What's the biggest cause of shutdown overruns?
Work discovered once equipment is opened up that wasn't in the original scope is one of the most common causes, since it pushes the critical path without the same planning the frozen scope received.
Should contingency budget be a fixed percentage?
It varies by site and shutdown complexity, but building in a defined contingency rather than treating overruns as unplanned spend generally leads to better cost control.
How often should shutdown progress be reviewed during execution?
Daily review against the schedule is standard practice, since it's the only way to catch a slipping task early enough to recover without extending the outage.
What should happen at shutdown closeout?
Punch list items should be tracked to completion, and a lessons-learned review should be captured while the details are still fresh, ready to inform the next shutdown.
