A shutdown is not a maintenance event but a controlled business risk. The duration is fixed, the exposure is high, and the financial stakes are significant. Yet many turnarounds fail long before execution begins during scoping.
The critical question is not, “What can we do while the plant is down?”
It is, “What work is truly necessary for this shutdown, and what can wait until the next operating cycle?”
The answer depends entirely on how scope is approved.
Scoping is about exclusion
Most organizations are good at identifying work but far less disciplined at rejecting it.
Requests come from operations, maintenance, engineering, and projects. Many are technically justified. Some are convenient. A few are strategic. All compete for the same limited window.
If there is no structured approval workflow, scope grows incrementally. Each addition appears reasonable in isolation. Over time, the cumulative impact destabilizes planning, stretches resources, and increases execution risk.
Turnarounds rarely fail because of one major decision, they fail because of multiple small approvals that were never assessed in context.
The system impact of “small” work
Consider a late request to replace a minor valve ; the task itself may require only a few hours. However, the system impact can be far greater.
The change may require additional isolations, modified scaffold access, crane rescheduling, extended testing, or rework of the sequence. If the task touches the critical path, even a short activity can affect the overall duration of the event.
Without a structured review process, these effects remain invisible at the approval stage. They only become visible during execution, when correction is expensive.
What a standardized approval workflow actually changes
A standardized workflow does not add bureaucracy. It introduces clarity and consistency into decision-making.
Every scope request should answer a small number of essential questions:
- What specific risk does this activity mitigate?
- What is the consequence if the work is deferred?
- Is engineering sufficiently mature?
- Are materials available within the shutdown window?
- Does the activity affect the critical path or resource loading?
Equally important, authority levels must be defined. Cost thresholds, schedule impact limits, and escalation paths should be explicit. When these rules are clear, discussions shift from personal preference to structured trade-offs.
The result is not fewer decisions. It is better decisions.
Scope freeze must be enforced
Most turnarounds declare a scope freeze date. The effectiveness of that freeze depends on governance.
If additional work can be added without formal impact assessment and baseline adjustment, the freeze has little value. Late scope should require documented evaluation of cost, schedule, and safety impact, along with approval at the appropriate level of authority.
Exception handling must remain the exception. Otherwise, the event gradually shifts from controlled execution to reactive management.
The operational reality
If scope is unstable, planning becomes unreliable. If planning is unreliable, execution becomes corrective rather than controlled.
A standardized scoping approval workflow protects more than the schedule. It protects safety exposure, budget integrity, and organizational alignment across functions.
Scoping is not an administrative step in turnaround preparation. It is the mechanism that determines whether the event will remain controlled.
Continue the discussion
This article outlines the principle behind disciplined turnaround scoping.
In the webinar “Scoping the foundation of STO”, we explore the practical structure in more detail, including approval gates, decision criteria, and governance models that prevent late scope from eroding performance. You can access the webinar via this link.
Controlling costs remains one of the toughest challenges in construction projects. Without clear insight into when and where…
Most projects do not run into budget overruns overnight. There are several warning signs long before overruns occur,…
Related resources
Cleopatra Cost Management: Tight integration with Primavera P6
Cleopatra Enterprise offers an out-of-the-box integration with scheduling software Oracle Primavera to bring your cost management to the next level.
Read blog article
Why Clear Roles Matter in Turnaround Planning
In STO and turnaround (TA) environments, tasks like QA/QC, scheduling, work planning, coordination, and supervision are critical. But in many organizations, these roles blur, overlap, or go unassigned, leading to friction during execution.
Read blog article