Shutdown and Turnaround Execution Playbook
A shutdown and turnaround execution playbook for planning a plant outage, freezing scope, coordinating work, and restarting safely on schedule. Use it to keep maintenance, operations, and contractors aligned through each phase.
Trusted by frontline teams 15 years of frontline software
Built for: Oil And Gas · Chemicals · Manufacturing · Power Generation · Utilities
Overview
This Shutdown and Turnaround Execution Playbook template defines the phased workflow for planning a plant outage, freezing scope, executing work, and starting back up safely. It is built for situations where many people and systems must stay synchronized: operations, maintenance, safety, contractors, materials, and approvals.
Use it when the shutdown has a fixed window, a critical path, and a restart that depends on multiple sign-offs. The template helps you turn a complex event into an execution plan with trigger phrases, clear ownership, confirm gates for risky actions, and failure handling when a step is blocked. It is especially useful when scope changes must be controlled and when work needs to be tracked across domains such as maintenance planning, permit-to-work, and shift handover.
Do not use this template for routine single-task maintenance or informal troubleshooting. It is also not the right fit when the work is exploratory and the sequence cannot be planned in advance. In those cases, a simpler SOP or task checklist is enough. This playbook is meant for planned outages where the cost of missed dependencies, late materials, or an incomplete startup review is high.
Standards & compliance context
- Use confirm gates and approval steps for lockout/tagout, confined space, hot work, and other high-risk activities to align with site safety procedures.
- Keep permit-to-work, isolation, and handback records linked to the execution plan so audit trails are easier to review.
- If the turnaround affects regulated equipment or environmental controls, include the required inspection and sign-off steps before restart.
- Follow site-specific contractor control, training, and access rules when assigning work across internal and external teams.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- 1. Define the outage inputs, including unit name, planned stop date, restart target, scope owner, and the systems that will receive task updates.
- 2. Map the execution plan into phases for pre-shutdown planning, scope freeze, execution, mechanical completion, startup readiness, and post-turnaround review.
- 3. Assign each step to the correct domain and tool, such as maintenance planning, permit approval, contractor coordination, or operations sign-off.
- 4. Add confirm gates before any destructive, isolating, or restart-critical step so the playbook pauses for explicit approval.
- 5. Run the playbook during the outage, monitor blocked steps and on_failure handling, and update the schedule when dependencies change.
- 6. Review punch-list items, close out reports, and capture lessons learned so the next turnaround starts with better scope and timing.
Best practices
- Freeze scope before the outage window starts, and route any late additions through a formal change-control step.
- Separate mechanical completion from startup readiness so the team does not treat equipment handback as the same thing as safe restart.
- Use one owner per step and one concrete tool per action, such as create_work_order, assign_checklist, or post_report.
- Add confirm gates before lockout, isolation, energization, and restart steps to prevent accidental execution.
- Reference prior outputs with $steps and required inputs with $inputs so the playbook stays traceable and reusable.
- Track permit, material, and contractor dependencies in the same execution plan instead of in separate spreadsheets.
- Capture punch-list items at the time they are found, not after the outage ends, so closeout does not drift.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this playbook template used for?
This template is used to manage a planned plant shutdown or turnaround from early planning through restart. It gives you a structured execution plan for scope freeze, work sequencing, permit coordination, and startup readiness. It is meant for outages where many teams must work from the same schedule and change control matters.
When should I use a turnaround playbook instead of an ad-hoc checklist?
Use this template when the outage has multiple workstreams, contractor involvement, or a hard restart date. Ad-hoc checklists break down when scope changes, permits overlap, or critical path tasks depend on other teams. A playbook is better when you need a repeatable sequence with clear ownership and failure handling.
Who should run this playbook?
It is usually run by the turnaround manager, plant operations lead, or maintenance planner, with input from safety, reliability, and contractors. The person running it should be able to coordinate approvals, confirm gates, and escalate blockers. If your site uses an orchestration tool, this playbook can trigger tasks across those domains.
How often is a shutdown and turnaround playbook used?
It is typically used for planned outages, which may be annual, semiannual, or tied to equipment condition and regulatory intervals. The same template can be reused for each event, with the scope and timing updated for the current outage. Many teams also use it during pre-shutdown readiness reviews before the actual stop date.
What are the biggest mistakes this template helps prevent?
Common mistakes include scope creep after freeze, missing permit dependencies, incomplete material staging, and restarting before punch-list items are closed. Another frequent issue is treating startup as a separate event instead of part of the same execution plan. This template keeps those steps connected so handoffs are explicit.
Can I customize this playbook for different units or plants?
Yes. You can tailor the input_schema, trigger phrases, approval gates, and step sequence for a specific unit, asset class, or site policy. Many teams clone the template and adjust the tool calls for their CMMS, permit system, contractor tracker, and shift handover process.
Does this template integrate with maintenance or workflow systems?
It is designed to fit no-code automation and orchestration patterns, so it can connect to CMMS, EAM, permit-to-work, ticketing, and messaging tools. Each step can call a concrete tool such as create_work_order, assign_checklist, post_report, or request_approval. That makes it easier to coordinate work across domains without manual follow-up.
How is this different from a standard maintenance SOP?
An SOP describes how a task should be done, while this playbook coordinates the sequence of tasks across teams and systems. It is built for trigger phrases, execution steps, confirm gates, and failure handling. If you need a reusable orchestration flow rather than a static procedure, this template is the better fit.
Related templates
Go deeper on the topic
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
A frontline employee app is a phone-first application that gives hourly, field, and deskless workers access to their schedule, pay, announcements, training,...
-
A frontline worker is any employee whose job happens away from a desk — on a production floor, in a patient room, behind a store counter, in a customer's...
-
On-premise intranet cost breakdown with real pricing ranges, implementation fees, and budget estimates for enterprises
-
Disconnected cloud apps create friction and waste time. Learn why unified work platforms improve productivity and retention.
-
Mobile capabilities help local government field teams stay connected, access SOPs offline, and boost productivity anywhere.
-
On-premise intranet explained: control, security, and compliance benefits for regulated organizations and IT teams.
Ready to use this template?
Get started with MangoApps and use Shutdown and Turnaround Execution Playbook with your team — pricing built for small business.
