Turnaround scope discipline: an asset management best practice

Turnaround scope discipline is the single best practice that separates asset-intensive organisations whose major outages run roughly to plan from those that habitually overspend, overrun, and trip on start-up. Industry data is unflattering: more than two-thirds of large refining and petrochemical turnarounds exceed planned cost and schedule by 10 per cent or have a trip after start-up, and roughly 40 per cent overrun by more than 30 per cent. The numbers are similar in upstream, power, chemicals, and large process manufacturing. Yet very few of those overruns are caused by the trades on the night shift. They are decided much earlier, in the months when scope is set, frozen, and quietly allowed to grow.

This piece is written for asset management leaders, heads of reliability, and operations directors who are tired of post-event critiques that conclude “we needed better planning.” The actual problem is almost always upstream of planning. It is the absence of a controlled, evidenced, organisation-wide method of deciding what work belongs in the next turnaround and what does not. Get scope discipline right and the rest of the outage starts to behave. Skip it and no amount of execution heroics will save the event.

Why scope is the controlling variable

Turnaround outcomes correlate more strongly with scope than with any other planning variable. AP-Networks, drawing on more than 1,350 turnaround observations across refining, petrochemicals, gas processing, and power, reports that scope-optimised turnarounds required around 30 per cent fewer direct field labour hours than turnarounds that planned more scope than the industry norm for comparable assets. The same dataset shows industry-average scope growth from scope freeze to execution of about 19 per cent, with top-quartile performers holding growth to roughly 7 per cent. The gap between average and top quartile is not a planning gap. It is a discipline gap.

Three patterns sit behind that gap.

The first is the absence of an authoritative challenge process. Engineering, operations, integrity, and projects all have legitimate interests in adding work. Without a structured Risk Based Scope Review, every legitimate request is also an unchallenged one. The default answer becomes “fit it in,” and the worklist swells.

The second is the absence of a meaningful scope freeze. Many sites declare a freeze date, then quietly accept additions for weeks afterwards on the basis that “we are still pre-execution.” If the freeze is not enforced by both the operations manager and the maintenance manager, with a written approval requirement for any late add, the freeze does not exist.

The third is treating discovery work as inevitable. Some discovery is genuine: pre-shutdown inspections will always reveal new findings. The rest is poor scope definition dressed up as discovery. The honest test is whether the same “discovery” themes appear at every event. If they do, the upstream process is the problem.

What good looks like

A defensible turnaround scope discipline has the same backbone whether the asset is a refinery, a CCGT, a pulp mill, an LNG plant, or an offshore platform. The mechanics matter less than the governance.

A long horizon, not a one-cycle plan

Top performers run a rolling three to five year turnaround schedule, agreed across operations, engineering, and finance, and refreshed annually. That horizon lets reliability engineering align inspection-driven work with capital projects and regulatory commitments, instead of treating each event in isolation. It also makes deferral conversations honest, because everyone can see where deferred work actually lands.

A risk-based work selection method

Every candidate item should pass through a defined challenge: what is the consequence of not doing this work, can it be done safely outside the outage, can the scope be reduced, and is the data behind the request good enough to justify inclusion? Risk Based Scope Reviews routinely strip 20 to 30 per cent of candidate scope from a draft worklist when applied properly. The key word is properly. Reviews that the same engineers who proposed the work also chair are not reviews.

A single, governed worklist

The worklist must be the only source of truth for what will be executed. Parallel spreadsheets, side conversations, and “we will sort it on the day” lists are signals that the governed process is not trusted. Treat them as defects in the operating model, not as harmless workarounds.

A real freeze with a real cutoff

A useful pattern is a hard cutoff at least eight weeks before execution for an annual turnaround, longer for major events. After the cutoff, additions require joint operations and maintenance manager sign-off and an explicit risk justification. The volume of post-cutoff additions is one of the most diagnostic metrics a turnaround steering group can look at.

An evidence loop back into strategy

Every turnaround should produce three artefacts beyond the closeout report: an updated maintenance strategy for any asset class where the event changed the picture, a refreshed criticality view if consequence or likelihood shifted, and a list of items moved from outage scope to on-the-run execution for the next planning cycle. Without that loop, the next event repeats the same arguments.

The asset management connection

Turnaround scope discipline is not a turnaround team problem. It is an asset management problem, and ISO 55001 frames it that way explicitly. Clauses on planning, operation, and performance evaluation expect organisations to translate strategic intent into controlled decisions on real assets, and to evidence that the system is being run that way. A site that cannot defend the worklist for its next turnaround against a structured challenge does not, in any meaningful sense, have a working asset management system at the level the standard contemplates. Programmes that already invest in criticality assessment that changes behaviour and in data governance that holds up under audit usually find scope discipline easier to bolt on, because the underlying registers and decision rules are already in shape.

The link to the capital cycle is just as direct. Scope decisions taken at outage planning are also capital decisions, even when they are coded as opex. A deferred inspection is a bet on remaining life. A retained run-to-fail position on a critical rotating asset is an implicit reliability investment decision. Treating these as quiet operational choices, rather than as part of the asset management contribution to the capital plan, is one reason the function so often arrives late at the investment table.

A short diagnostic

Most asset leaders can score their own turnaround discipline in ten minutes. Honest answers to the following five questions usually predict the next event better than the formal readiness review.

Is there a documented three to five year outage and major maintenance schedule, refreshed in the last twelve months, that operations, engineering, and finance all sign?
Does every candidate work item pass through a structured Risk Based Scope Review, chaired by someone independent of the requestor?
Is there a published scope freeze date, and what was the percentage growth between freeze and execution at the last two events?
After execution, is there a controlled record of items that were moved out of outage scope, and is that list visible at the next planning cycle?
Does the asset management function bring turnaround scope decisions into the annual capital conversation, or are they handled entirely inside operations?

Where the answers are weak, the cost of fixing them is small relative to the avoided overrun on a single major event. Programmes that take this seriously typically formalise the operating model first, then improve the supporting data and tooling. Sequencing matters: tooling without governance produces tidier dashboards on top of the same chaos. Where modernisation is on the agenda, aligning the operating model with the platform at the same time gives both pieces of work a better chance of sticking.

The bottom line

Turnaround scope discipline is unfashionable. It does not generate slide decks about transformation, and it rarely shows up in vendor demonstrations. It does, however, separate the asset estates that run predictably from the ones that do not. For asset management leaders looking for a single best practice that returns value out of all proportion to its cost, this is the one that consistently pays.