In a lot of plants, that one phrase carries a remarkable amount of hope. Work that can't be done online, or work that keeps getting pushed in routine maintenance, gets mentally parked in the next major outage. The turnaround becomes the promise that everything important will finally get handled.

Sometimes that's exactly what happens.

And sometimes the turnaround comes and goes, the window tightens, scope gets squeezed, and a surprising amount of that debt survives the event. Or comes out bigger than it went in.

That's why turnarounds sit at the center of the maintenance debt story. They're one of the few times you can truly pay down years of accumulated asset risk at scale. They're also one of the easiest places to pile on more without meaning to.

For a lot of critical assets, the work that matters most simply can't be done with the plant running.

Internal inspections. Major overhauls. Tie-ins. Vessel entry. Invasive integrity checks. Exchanger work. Valve campaigns. All of it needs the planned downtime, isolation, and access that only a turnaround or major outage provides. That makes an STO more than a scheduling event. It's a debt-management event.

If routine maintenance is where debt usually gets created, through deferral, thinning, and temporary fixes, then the turnaround is your best shot at reducing it in a way that actually moves the needle. A well-run STO doesn't just close out a schedule. It resets the condition of the plant and restores margin in systems that have been quietly carrying risk. That's why turnaround quality matters far more than the event metrics suggest.

A turnaround pays down debt when it does more than finish the schedule.

It pays down debt when the event protects the critical integrity and reliability scope, goes after the known bad actors instead of just the loudest symptoms, runs inspections deep enough to actually learn something, and captures what it finds clearly enough to feed the next cycle. That means the event isn't judged only on duration and cost. It's judged on whether it retired real risk.

In debt language, a good turnaround does two things at once. It pays principal, by completing the deferred work that genuinely needed the outage. And it cuts future interest, by improving asset condition, restoring integrity margin, and leaving behind better information than it inherited. That's a far stronger way to measure STO value than "did we finish on time?"

Here's the other side. A turnaround can just as easily become a debt factory, and the ways it happens are painfully familiar:

This is where debt grows in the dark. The dashboard says the event was a success, while the plant walks out the door carrying more unresolved risk than leadership realizes. And deferred work doesn't stay quiet. It comes back as higher operating cost, unscheduled downtime, and expensive emergency repairs under worse conditions than you'd have faced in the outage.

"We'll get it next time" sounds harmless right up until you remember what next time means in turnaround work.

For routine maintenance, a deferral buys you weeks, maybe months. For major turnaround scope, next time can mean four to six years, depending on the asset and the event cycle. That changes the whole decision. You're not pushing a task a quarter down the road. You may be signing up for years of extra risk exposure, years of degraded performance, or years of rising odds that the asset forces an unplanned intervention long before you cycle back to it.

Turnaround-created debt carries a very long compounding period. That makes it some of the most expensive debt a plant can hold.

If an STO is going to cut maintenance debt, that intent has to be built into how the event is run. It won't happen by accident.

Put a debt lens into scope setting, asking not only "what has to be done for start-up?" but also "what debt are we trying to retire in this window?" Track every de-scoped and deferred job visibly, logged with its reason, its asset risk, and its next action, not just quietly dropped from the active list. Document findings and partial fixes in a way the next planner can actually use, so degradation discovered in the field and any temporary repairs accepted under pressure don't vanish when the crews leave. And run a post-event review that looks past schedule and cost to the real question: how much known risk did we retire, and how much new debt did we create through de-scoping, compression, and incomplete work?

This is where execution discipline decides the outcome. Planning, field coordination, document control, and clean post-event closure are what separate a turnaround that genuinely reduces debt from one that just rearranges it. It's a lot of where we focus with clients, because the difference rarely shows up in the schedule and almost always shows up two years later.

A turnaround is one of the few moments when you can actually change the debt profile of a plant. Handled well, it retires years of accumulated risk, restores reliability margin, and hands the next operating cycle a stronger plant than it inherited. Handled poorly, it just shuffles debt around, hides it under a green event scorecard, and sends the plant back into service more fragile than anyone in the room believes.

So stop treating STO decisions as schedule and budget decisions alone. They're decisions about what risk gets retired, what risk gets carried forward, and what kind of plant you're sending into the next four to six years.

Next in the series, we cross back to complexity and a quieter version of this same problem. Your EAM says green. Your dashboards look clean. And the field tells a completely different story. We'll get into the illusion of control, and the gap between system reality and plant reality.