Skip to content

Decommissioning and Restoration Runbook

Post-exit closure protocol — instantiates Managed Retreat

The step-by-step procedure for safely closing, salvaging, and restoring a relinquished zone after exit, so the vacated position leaves no stranded hazard, no lost value, and no false promise of return.

A Decommissioning and Restoration Runbook governs what happens after the subject has left: the ordered procedure for shutting down, disconnecting, removing hazards, recovering salvageable value, restoring the site, and transferring records — so a relinquished position is genuinely closed rather than merely abandoned. Its defining concern is the tail of retreat that everyone is tempted to skip once the move looks done: an exit without decommissioning leaves stranded hazards, strands recoverable value, and — most corrosively — leaves the door open to creeping re-occupation of a zone that was supposed to be given up. It executes closure and captures salvage value; the standing rule forbidding rebuilding is a separate policy it enforces against.

Example

An operator is retreating from an aging offshore platform whose maintenance cost and risk now exceed its output. Leaving it in place is not an option — it is a navigation and environmental hazard — and simply walking away would strand both the liability and recoverable steel. The Decommissioning and Restoration Runbook sequences the tail: safe shut-in and flushing of the wells; disconnection and making-safe of risers and power; a plugging procedure that meets the governing regulator's abandonment standard; a salvage value map that identifies which topside modules and steel are worth recovering versus what costs more to remove than it returns; controlled removal; seabed restoration and survey; and archival transfer of well records to the regulator with a defined post-exit monitoring period. Crucially, the site is recorded as relinquished under a no-reoccupation status, so the cleared location is not quietly recommitted. The retreat is complete only when the runbook is — not when the last worker leaves.

How it works

  • Sequence the shutdown for safety first. Make-safe, disconnect, and hazard removal come before value recovery, so salvage never competes with safe closure.
  • Map salvage value explicitly. What is worth recovering — and what costs more to remove than it returns — is decided deliberately, not by whatever is convenient to grab.
  • Restore and hand off the record. Site restoration and archival/record transfer are part of "done," so the zone does not become an orphaned liability.
  • Close against re-occupation. The zone is recorded as relinquished and monitored, enforcing the standing no-rebuild rule rather than leaving a vacuum that invites return.

Tuning parameters

  • Restoration standard — from make-safe to full return-to-natural. Higher standards reduce residual liability and community harm but cost more and take longer.
  • Salvage aggressiveness — how much value is recovered before closure. Recovering more offsets cost but can delay make-safe and restoration; recovering less is faster but strands value.
  • Monitoring duration — how long the relinquished zone is watched post-exit. Longer catches latent hazards and creeping re-occupation but extends the obligation.
  • Reversibility of closure — how hard it is to ever re-enter. Hard, irreversible closure prevents backsliding but forecloses legitimate future exceptions; soft closure keeps options but invites lock-in to return.
  • Record-transfer completeness — how thoroughly state and history pass to the successor custodian. Complete transfer preserves accountability; thin transfer saves effort but orphans the liability.

When it helps, and when it misleads

Its strength is that it prevents the two quiet failures that turn a completed retreat into a lasting problem — stranded hazards and creeping re-occupation — and it recovers value that would otherwise be abandoned, funding part of the exit. It is the mechanism that makes a retreat final.

Because it comes last and after the visible win, decommissioning is the first thing cut when money and attention run out — producing orphaned assets: hazards left in place, restoration deferred indefinitely, records lost.[1] Run cynically, a "restoration plan" is announced to secure permission to exit and then quietly defunded once the subject has moved. The disciplines are to fund the tail up front — bonded or escrowed against the exit, not paid from whatever remains — and to treat the retreat as unfinished, not merely relocated, until the runbook's closure and monitoring are complete.

How it implements the components

  • decommissioning_and_no_reoccupation_rule — it executes the safe closure, removal, restoration, and record transfer of the relinquished zone, and records it as relinquished so re-occupation is barred.
  • salvage_value_map — it identifies what is worth recovering from the vacated position versus what costs more to remove than it returns.

It executes closure and enforces relinquishment on this zone, but the standing, forward-looking policy that forbids rebuilding in still-exposed zones is No-Rebuild or Reoccupation Rule; it also does not compensate or resettle the people leaving (that's Transition Support Plan).

Notes

The runbook executes decommissioning and enforces relinquishment on one specific vacated zone; the general, standing prohibition on re-committing to still-closing zones is the No-Rebuild or Reoccupation Rule, which this runbook applies at closure. Keeping the one-time procedure distinct from the standing policy is what stops "we'll restore it later" from becoming "it was never really closed."

References

[1] Orphaned assets — orphaned wells or mines whose responsible party has vanished or defunded closure, leaving hazards and restoration to the public — are the standard illustration of what happens when the decommissioning tail is not funded up front. ↩