Overview
Shutdown and Turnaround Planning is the disciplined process used to decide what work belongs in a major planned outage, prepare that work before the event, control scope growth, and prove that the event is ready to execute.
Major shutdowns are different from routine weekly maintenance. The execution window is finite, expensive, resource-intensive, and difficult to recover once the asset is down. Missing a long-lead material, incomplete engineering package, weak isolation plan, or unconfirmed contractor crew can create immediate schedule and cost consequences.
The planning objective is therefore not to accumulate as much work as possible. It is to build a challenged, justified, frozen, and executable scope.
What It Is
A shutdown, turnaround, or major planned outage is a bounded event in which an asset, production line, process unit, or system is deliberately taken out of normal service so work can be performed that cannot reasonably be completed while operating.
Shutdown and Turnaround Planning owns:
- event definition;
- work nomination;
- scope challenge;
- scope freeze;
- budgeting and estimate development;
- long-lead material planning;
- engineering-package readiness;
- contractor and work-front preparation;
- readiness review;
- planning-to-execution handoff.
It does not own detailed critical-path scheduling or utility-specific continuity planning.
Why It Matters
Strong shutdown planning supports:
- better scope control;
- lower exposure to late material and engineering surprises;
- safer work preparation;
- better contractor utilization;
- clearer cost estimates;
- controlled post-freeze changes;
- better startup confidence;
- better lessons learned for the next event.
The largest planning failures often become visible only after the equipment is already down, when options are expensive and limited.
When to Use It
Use this process for major planned events where:
- equipment must be intentionally removed from service;
- multiple crafts or contractors must coordinate;
- significant work cannot be performed while operating;
- long-lead materials are involved;
- engineering packages or inspections are required;
- a finite downtime window must be protected;
- scope growth could materially affect cost or duration.
The scale can range from a multi-day food-manufacturing shutdown to a large process-plant turnaround. The phase gates remain useful even when the calendar horizon is much shorter.
Core Principles
- Scope is a decision, not an accumulation.
- Challenge work before investing heavily in detailed planning.
- Set the freeze date early enough to support the slowest material, engineering, or contractor lead time.
- Prove readiness with evidence rather than “on track” statements.
- Make every post-freeze addition visible.
- Do not trade away safety, integrity, or required compliance work to protect cost or schedule.
- Planning determines what is ready; scheduling determines sequence and timing.
- Lessons learned should change the next event’s planning process.
Process or Lifecycle
- Event Driver Identified leads to Define Event Boundary and Objectives.
- Define Event Boundary and Objectives leads to Collect Work Nominations.
- Collect Work Nominations leads to Challenge Each Item.
- Challenge Each Item leads to Accept?.
- Accept?, when Reject, leads to Document Rejection.
- Accept?, when Defer, leads to Return to Backlog or Future Event.
- Accept?, when Accept, leads to Candidate Scope.
- Candidate Scope leads to Scope Freeze.
- Scope Freeze leads to Detailed Planning and Procurement.
- Detailed Planning and Procurement leads to Engineering and Contractor Readiness.
- Engineering and Contractor Readiness leads to Final Readiness Review.
- Final Readiness Review leads to Ready?.
- Ready?, when No, leads to Close Gaps or Delay.
- Close Gaps or Delay leads to Final Readiness Review.
- Ready?, when Yes, leads to Execution Handoff.
- Execution Handoff leads to Execute Event.
- Execute Event leads to Closeout and Lessons Learned.
Roles and Responsibilities
| Role | Responsibility |
|---|---|
| Event Sponsor | Defines objectives, approves scope freeze, owns major exceptions |
| Event / Turnaround Manager | Coordinates the overall planning process |
| Planning Lead | Develops work packages and readiness evidence |
| Challenge Board | Accepts, defers, or rejects nominated work based on evidence |
| Engineering | Provides technical packages and repair requirements |
| Materials / Procurement | Secures long-lead and event materials |
| Contractor Coordinator | Confirms contractor scope, staffing, equipment, and mobilization |
| Operations | Defines access, shutdown, startup, and production constraints |
| Safety / Quality | Reviews applicable controls and hold points |
| Scheduler | Receives frozen, readiness-approved scope for execution scheduling |
Required Inputs
- Event charter or driver
- Asset condition and inspection findings
- Deferred backlog
- Predictive-maintenance findings
- Regulatory or required work
- OEM overhaul requirements where applicable
- Proposed capital work to be bundled into the event
- Prior event lessons learned
- Long-lead material information
- Contractor availability
- Engineering requirements
- Safety, environmental, quality, and operations constraints
Required Outputs
- Approved event charter
- Challenged work list
- Frozen scope of record
- Scope-exception register
- Budget and estimate basis
- Job plans
- Engineering packages
- Long-lead material status
- Contractor mobilization plan
- Readiness-review record
- Go/no-go or execution-handoff decision
- Post-event closeout and lessons learned
Step-by-Step Implementation
1. Define the event
Establish:
- event boundary;
- objectives;
- target execution window;
- sponsor;
- initial budget envelope;
- major operating constraints.
2. Collect candidate work
Typical nomination sources include:
- inspections;
- condition monitoring;
- deferred backlog;
- statutory or required inspections;
- known defects;
- OEM requirements;
- engineering modifications;
- capital projects proposed for bundling.
3. Challenge the scope
Every nomination should be accepted, deferred, or rejected with a documented rationale.
Ask:
- Must this work be done during this event?
- What happens if it is deferred?
- Can it be done safely while operating?
- Is the technical scope sufficiently understood?
- Does the event provide a unique access opportunity?
- Is the work safety-, integrity-, or compliance-required?
- Does the value justify consuming event capacity?
4. Set the freeze date
Work backward from the longest credible lead time among:
- materials;
- fabricated components;
- engineering packages;
- contractor mobilization;
- permits;
- specialty equipment.
Do not set freeze based only on administrative convenience.
5. Freeze the scope
Preserve the original frozen scope as the record of commitment. Any later addition should follow an exception process and remain distinguishable from original scope.
6. Complete detailed planning
Finish job plans, labor estimates, material reservations, technical documents, safety requirements, inspection needs, tools, lifting, and work-front preparation.
7. Confirm contractors and resources
Confirm that contracted crews, equipment, supervision, onboarding, and work fronts are real and available—not merely assumed.
8. Conduct the readiness review
Review evidence for:
- materials;
- engineering;
- permits;
- isolation planning;
- contractors;
- tools and equipment;
- acceptance criteria;
- contingency provisions;
- unresolved risks.
9. Hand off to scheduling and execution
Only readiness-approved scope should move into detailed turnaround scheduling and field execution.
10. Close out and learn
Reconcile actual scope, cost, schedule, exceptions, and readiness failures. Feed the findings into the next event.
Decision Rules
Scope challenge
- Work Item Nominated leads to Required for Safety, Integrity, or Compliance?.
- Required for Safety, Integrity, or Compliance?, when Yes, leads to Retain Unless Authorized Risk Decision Says Otherwise.
- Required for Safety, Integrity, or Compliance?, when No, leads to Must Be Done During This Event?.
- Must Be Done During This Event?, when No, leads to Defer to Routine Work or Future Event.
- Must Be Done During This Event?, when Yes, leads to Technical Scope and Value Justified?.
- Technical Scope and Value Justified?, when No, leads to Reject or Return for Development.
- Technical Scope and Value Justified?, when Yes, leads to Accept into Candidate Scope.
- Accept into Candidate Scope leads to Lead Time Supports Current Event?.
- Lead Time Supports Current Event?, when Yes, leads to Eligible for Frozen Scope.
- Lead Time Supports Current Event?, when No, leads to Defer or Escalate Expedite Decision.
Post-freeze work
A new item after freeze should not be silently absorbed. Evaluate whether it meets defined exception criteria and record owner, rationale, cost impact, schedule impact, and approval.
CMMS Considerations
Useful CMMS fields include:
- shutdown/turnaround event identifier;
- nomination source;
- challenge decision;
- challenge rationale;
- freeze date;
- frozen-scope flag;
- exception flag;
- engineering-package status;
- material/procurement status;
- contractor assignment;
- work-front assignment;
- readiness status;
- closeout result.
Reporting should distinguish original frozen scope, post-freeze exceptions, rejected work, and deferred work.
SAP PM Considerations
SAP PM environments may use a shutdown/turnaround revision or another controlled event identifier to group notifications and orders. Larger events may also use Project System structures where appropriate.
Milestones can represent planning gates such as freeze, mobilization, and readiness review. Material reservations, purchase requisitions, and order links should make long-lead status visible. Exact configuration varies by site and SAP release.
Metrics and KPIs
Post-Freeze Scope Addition Rate
Definition: Relative amount of scope added after the original freeze.
Formula:
Scope Items Added After Freeze ÷ Total Frozen Scope Items × 100
Units: Percent
Interpretation: A rising rate can indicate weak challenge, late scope identification, or a freeze date set too early or too late.
Limitations: Some emergent integrity work is legitimate; the metric should not encourage hiding required discoveries.
Long-Lead Material Readiness at Freeze
Definition: Share of long-lead items with confirmed procurement/delivery status at freeze.
Formula:
Long-Lead Items with Confirmed Status ÷ Total Long-Lead Items in Frozen Scope × 100
Units: Percent
Interpretation: Tests whether procurement readiness supports the event plan.
Limitations: “Confirmed” must be defined consistently; an unverified supplier promise should not automatically equal readiness.
Contractor Mobilization Readiness
Definition: Share of planned work fronts with contracted, staffed, and confirmed crews at the defined mobilization checkpoint.
Formula:
Ready Contractor Work Fronts ÷ Total Planned Contractor Work Fronts × 100
Units: Percent
Interpretation: Tests whether external capacity is actually available.
Limitations: Headcount alone does not prove competency, access, tools, or supervision readiness.
Planning Milestone Adherence
Definition: Share of planned phase gates completed on their planned dates.
Formula:
Phase-Gate Milestones Met on Time ÷ Total Planned Phase-Gate Milestones × 100
Units: Percent
Interpretation: Indicates whether the planning horizon is holding.
Limitations: Milestones should not be moved after the fact to protect the metric.
Challenge Yield
Definition: Portion of nominated work rejected or deferred through challenge.
Formula:
Rejected or Deferred Nominations ÷ Total Nominations × 100
Units: Percent
Interpretation: Shows whether challenge is functioning rather than automatically accepting all nominations.
Limitations: There is no universal ideal yield. A high number can indicate poor nomination quality just as easily as strong challenge.
Common Failure Modes
- No defined event boundary
- Accepting every nomination
- Setting freeze too late for long-lead materials
- Treating freeze as optional
- Adding scope after freeze without recording it
- Mobilizing contractors before work is ready
- Declaring readiness based on intent rather than evidence
- Allowing cost pressure to remove required safety or integrity work
- Mixing planning and detailed scheduling responsibilities
- Failing to feed closeout lessons into the next event
Best Practices
- Establish the sponsor and event charter early.
- Make nomination and challenge visible.
- Set freeze from actual lead-time constraints.
- Keep original frozen scope immutable.
- Track every post-freeze exception.
- Manage long-lead items as leading indicators.
- Confirm contractor readiness by work front.
- Use evidence-based readiness reviews.
- Preserve safety and inspection hold points.
- Separate planning KPIs from execution schedule KPIs.
- Update future planning standards from event closeout.
Maturity Levels
| Level | Practice |
|---|---|
| 1 — Ad hoc | Work list grows until execution; no meaningful freeze |
| 2 — Defined | Charter, challenge process, and freeze exist |
| 3 — Managed | Long-lead, engineering, contractor, and readiness evidence tracked |
| 4 — Integrated | Cross-functional decisions and controlled execution handoff are routine |
| 5 — Learning | Closeout evidence improves future challenge, freeze timing, and readiness |
Real-World Example
A food manufacturing plant plans a multi-day annual shutdown. Candidate work includes gearbox overhauls, conveyor alignment, a bearing replacement identified through vibration monitoring, and several cosmetic improvement requests.
The challenge review keeps the bearing replacement because failure during production would create significant downtime and potential product-containment consequences. Cosmetic work that can be performed during routine downtime is deferred.
The freeze date is then set by the longest-lead gearbox material and contractor requirement rather than by the plant’s normal four-week maintenance cycle. Before execution, the readiness review confirms material receipt, job packages, contractor staffing, isolation planning, and acceptance criteria.
The event enters scheduling with a smaller but executable scope instead of a larger list filled with uncertain work.
Audit Questions
- Is there an approved event charter?
- Does the event have a named sponsor?
- Was every frozen-scope item challenged?
- Are challenge decisions documented?
- Was the freeze date based on real lead times?
- Is original frozen scope preserved?
- Are post-freeze additions logged separately?
- Are long-lead materials actively tracked?
- Are engineering packages complete?
- Are contractor work fronts staffed and confirmed?
- Does the readiness review use evidence?
- Are safety and integrity items protected from inappropriate challenge?
- Is the handoff to scheduling controlled?
- Are closeout lessons incorporated into the next event?
Related Reliability Method Topics
Shutdown and Turnaround Planning is one of three specialist methods inside the event family. It owns pre-event scope development, challenge, and freeze. Its siblings own the other phases: Turnaround Scheduling owns execution scheduling, and Outage Planning owns utility/continuous-process continuity. Shutdowns, Turnarounds & Outages is the program-level umbrella that governs all three.
- Shutdowns, Turnarounds & Outages (program umbrella)
- Turnaround Scheduling (sibling method — execution scheduling)
- Outage Planning (sibling method — continuity)
- Maintenance Planning
- Maintenance Scheduling
- Backlog Management
Related Tools and Assets
Potential future assets include:
- Shutdown Event Charter
- Work Nomination Form
- Scope Challenge Worksheet
- Scope Freeze Register
- Post-Freeze Exception Log
- Long-Lead Material Tracker
- Contractor Mobilization Checklist
- Shutdown Readiness Review Checklist
- Shutdown Planning Dashboard
These assets are not created by this document.
References
- RM-MKS-6015 — Shutdown & Turnaround Planning
- RM-MKS-6002 — Maintenance Planning
- RM-MKS-6003 — Maintenance Scheduling
- RM-MKS-8018 — Outage Planning
- RM-MKS-8019 — Turnaround Scheduling
- RM-MKS-10009 — Shutdown & Turnaround Management
Public derivative source: Draft. Publication status: Not Authorized.