Planning for Shutdown: Lessons from Multidisciplinary Delivery

Planned shutdowns compress months of work into days or weeks, across multiple disciplines working in the same physical space under significant time pressure. The projects that run smoothly are rarely the ones with the most resource — they're the ones with the clearest sequencing.

Sequencing Before Scheduling

It's tempting to jump straight into a detailed schedule once a scope is agreed. In our experience, the more valuable step comes first: mapping genuine sequencing dependencies between disciplines, separate from calendar dates. Which mechanical work must complete before electrical isolation can proceed? Where do access constraints create hidden bottlenecks?

Only once that logic is understood does a schedule become meaningful, rather than an optimistic arrangement of tasks that ignores real-world dependencies.

Where Shutdowns Go Wrong

The recurring themes we see across delayed shutdowns are consistent:

• Underestimating isolation and permit-to-work turnaround time

• Insufficient contingency for discovery-driven scope (issues only visible once plant is opened up)

• Communication gaps between contractors working adjacent but interdependent tasks

A Multidisciplinary Response

BESAT's industrial delivery teams plan shutdowns with engineering, commercial and delivery functions represented from the earliest planning meetings — not brought in once the schedule is fixed. This means constraints are identified while there's still time to plan around them, not discovered mid-shutdown when the only options are delay or risk.

The best shutdown plans are the ones that assume something will go wrong — and have already decided what happens next.