Why shutdown readiness depends on applying lessons before the next major event
A major shutdown is one of the most expensive and complex events an asset-intensive organisation will undertake. Effective shutdown readiness is built long before the plant goes offline. The plant may be offline for several weeks, production stops, contractors arrive in large numbers and multiple teams try to complete work within the same limited window.
Yet you never really get an opportunity to practise the whole event. The cost and operational consequences are simply too high.
It is a bit like preparing for a marathon. You do not train for a marathon by running a marathon every week. You build capability through shorter runs, test what works, make adjustments and gradually become better prepared for the main event.
Shutdowns should be approached in much the same way.
Good work packages do not guarantee shutdown readiness
Engineers naturally go deep into the technical detail. Reliability teams develop improvement work. Capital teams plan upgrades. Maintenance teams prepare repairs, while operations identify cleaning and optimisation activities that can only happen while the plant is offline.
Each team may produce detailed shutdown plans and a beautiful Gantt chart. The problem is that these packages are often developed in separate pockets. What’s often missing is the helicopter view of how everything will come together.
Will two teams need to work in the same area at the same time? Does the shutdown quality plan require the same inspector at four different work fronts? Does a contractor have sufficient supervision to manage several jobs simultaneously? Where will cranes be positioned, and which access or evacuation routes will they obstruct? How will large components reach the area where they are needed? These are not minor logistical details. They are the points at which well-planned work can stop.
A shutdown lesson has to go somewhere
The 2026 State of Asset Management in Australia and New Zealand report1 makes an makes an important observation: lessons-learned processes are widespread, but they rarely result in meaningful improvement. Organisations conduct reviews and document what happened, yet often repeat the same problems during the next shutdown.
The difficulty is not necessarily identifying the lesson. Engineers are generally very good at recording what went wrong. The difficulty is applying it.
A shutdown lesson has not been learned because it appears in a close-out report. It has been learned when it changes a work practice, checklist, contractor requirement, job plan, risk control or preparation activity, and when that change is tested in a shutdown situation.
This is why shutdown management plans are so useful. They capture site-specific practices for managing matters such as transport routes, crane positions, laydown areas, medical access and other high-risk interfaces. After every shutdown, these plans can be reviewed and updated, creating a practical library of knowledge suited to that operation. With Pragma’s structured approach to effective shutdown governance, the shutdown management plan provides continuity between events by bringing together the risks, responsibilities and lessons that span individual work packages.
Without such a repository, the organisation depends on people remembering what happened last year. When those people retire or leave, the knowledge leaves with them.
The value of seeing the risk early
We saw the value of early visibility at one mining operation, where we were asked to conduct a shutdown-readiness assessment roughly five months before a planned shutdown.
The individual teams had worked hard. Their work packages were detailed, and their technical preparation was progressing well. We identified a lack of integration between the reliability, capital, maintenance, and operations scopes. There was no single view showing how all the work would be pulled together.
Because the assessment happened early enough, the organisation had time to address the integration risks before execution began. A few practical changes and an additional pair of eyes helped them achieve a successful shutdown.
That timing matters. Finding an integration problem during the shutdown leaves very few good options. Finding it five months earlier gives the organisation time to respond in a practical and cost-effective way.
Build shutdown readiness through shorter turnarounds
Organisations may not be able to rehearse a four- or six-week shutdown, but many have weekend shutdowns or shorter three- and four-day turnarounds.
These are opportunities to practise the habits required for the major event: integrated planning, clear responsibilities, escalation, resource coordination and disciplined close-out.
The lesson is simple. Do not wait for the major shutdown to discover whether your approach works. Document what happened. Incorporate it into the shutdown management plans. Test it during the smaller opportunities, then carry what works into the next major shutdown.
Because a shutdown lesson has not been learned until it has been applied.
Reference:
- MAINSTREAM. 2026. The State of Asset Management in Australia & New Zealand 2026. Research partner: KPMG. Accessed 21 July 2026
