Loading...

Plant Shutdown Turnaround Workspace

A Plant Shutdown Turnaround Workspace keeps scope, permits, contractors, and start-up readiness in one place so the team can run the outage without losing control of changes or handoffs.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Oil & Gas · Chemicals · Power Generation · Manufacturing

Overview

The Plant Shutdown Turnaround Workspace template is built for the full lifecycle of a planned plant outage: scope freeze, contractor mobilization, safety and permit control, execution, mechanical completion, and start-up readiness. It gives the turnaround team a shared workspace structure with role-based members, stage-based task lists, milestone tracking, dedicated channels, and recurring check-ins so the work stays visible as the shutdown moves from planning into field execution.

Use this template when the outage involves multiple functions that must stay aligned on schedule, permits, isolation control, budget, and handover. It is a strong fit for refinery turnarounds, chemical plant shutdowns, power generation outages, and other industrial maintenance events where the work is time-bound and coordination failures are expensive. The pinned resources support the practical artifacts teams actually use: the master schedule, scope freeze register, safety plan, LOTO matrix, permit pack, contractor mobilization checklist, and start-up readiness checklist.

Do not use this template for routine maintenance queues, isolated work orders, or projects that do not have a defined shutdown window. It is also not the right fit if you do not need milestone-based governance or if one person can manage the work informally. The value of the workspace comes from Conway’s Law in practice: the structure mirrors the turnaround team, so each role, channel, and task list maps to how the outage is actually run.

What's inside this template

Members

Role-based members define who owns turnaround decisions, execution, safety, and handover without tying the template to specific people.

Channels

Dedicated channels separate kickoff planning, day-to-day execution, safety control, decisions, and closeout so each conversation stays in the right workflow.

  • #kickoff-planning
    Scope definition, turnaround objectives, freeze dates, constraints, and readiness planning.
  • #day-to-day-execution
    Daily field coordination, progress updates, blockers, contractor sequencing, and shift handoffs.
  • #safety-permits
    LOTO, permit-to-work, SIMOPS, hazard controls, incident reporting, and stop-work escalations.
  • #decisions-approvals
    Scope changes, budget approvals, schedule tradeoffs, risk acceptances, and management sign-off.
  • #retrospective-closeout
    Punch list closure, lessons learned, performance review, and start-up/handover feedback.

Check ins

Recurring check-ins create the operating rhythm for leadership, execution, and safety reviews during a time-sensitive outage.

  • Weekly Monday turnaround leadership check-in
  • Daily execution standup
  • Daily safety and permit review

Milestones

Milestones mark the approval gates that matter in a turnaround, from scope freeze through start-up readiness.

  • Scope freeze approved
    Approved work scope and baseline schedule locked.
  • Contractor mobilization complete
    All required contractors are inducted, staged, and ready.
  • Shutdown window begins
    Plant is taken offline and isolation execution starts.
  • Mechanical completion
    All planned maintenance and inspection work is complete.
  • Start-up readiness approved
    Operations, maintenance, and HSE sign off for restart.

Task lists

Stage-based task lists organize the work by phase so every item has a clear DRI and a visible place in the shutdown sequence.

  • 1. Scope Freeze and Planning Baseline
    Define the approved work scope, assumptions, constraints, and baseline plan before execution begins.
  • 2. Contractor Mobilization and Readiness
    Prepare contractor onboarding, access, permits, equipment staging, and workface readiness.
  • 3. Safety, Permits, and Isolation Control
    Manage safety-critical controls, permits, isolations, and field execution readiness.
  • 4. Execution, Progress, and Issue Management
    Track daily execution, blockers, schedule variance, and decision escalations during the outage window.
  • 5. Start-Up Readiness and Closeout
    Verify mechanical completion, punch list closure, handover, and start-up readiness before restart.

Hill charts

The hill chart gives leadership a quick view of whether turnaround work is still being discovered, actively executed, or nearing completion.

  • Turnaround execution hill chart
    Tracks the major workstreams from planning through restart readiness.

Default apps

Default apps should point the team to the tools they already use for schedules, documents, reporting, and work orders.

Integrations

Integrations connect the workspace to systems like Teams, Drive, Excel, SAP, and Power BI so status and source files stay linked.

  • Microsoft Teams
  • Google Drive
  • Microsoft Excel
  • SAP
  • Power BI

Pinned resources

Pinned resources keep the master documents one click away during planning, execution, and handover.

  • Turnaround master schedule
  • Scope freeze register and change log
  • Safety plan, LOTO matrix, and permit pack
  • Contractor mobilization checklist
  • Start-up readiness and handover checklist

How to use this template

  1. 1. Assign the turnaround manager, operations lead, maintenance lead, engineering lead, HSE lead, procurement lead, and contractor coordinator to the member roles before the planning meeting.
  2. 2. Load the master schedule, scope freeze register, safety plan, LOTO matrix, permit pack, and handover checklist into the pinned resources and confirm each file has a clear owner.
  3. 3. Use the Scope Freeze and Planning Baseline task list to lock the work scope, record change requests, and approve the first milestone before mobilization starts.
  4. 4. Move contractor onboarding, access, and readiness tasks into Contractor Mobilization and Readiness, and use the daily execution standup to surface blockers, dependencies, and DRI handoffs.
  5. 5. Run the Safety, Permits, and Isolation Control task list during the shutdown window, update the daily safety review, and log any permit or isolation exceptions in the decisions channel.
  6. 6. Close the workspace by confirming mechanical completion, start-up readiness, and handover actions, then capture lessons learned in the retrospective closeout channel and hill chart.

Best practices

  • Keep the scope freeze register as the single source of truth for additions, deletions, and deferred work.
  • Assign one DRI to every task list item so contractor issues, permit delays, and readiness gaps do not bounce between roles.
  • Use the decisions and approvals channel for scope changes, hold points, and sign-offs instead of burying them in execution chat.
  • Update the hill chart daily during the shutdown window so leadership can see whether work is still in discovery, in progress, or nearly done.
  • Tie each milestone to a concrete gate, such as contractor mobilization complete or start-up readiness approved, rather than to a vague date.
  • Separate safety and permit review from general execution discussion so isolation control gets focused attention every day.
  • Link the SAP work order view, Excel schedule, and Power BI progress report rather than copying the same status into multiple places.
  • Capture lessons learned in the retrospective closeout while the outage is still fresh, especially for scope growth, permit friction, and handover delays.

What this template typically catches

Issues teams running this template most often surface in practice:

Scope creep after freeze because late work requests were not routed through a formal change log.
Unclear ownership for contractor readiness, which delays mobilization and access control.
Permit or LOTO gaps discovered late because safety review was not run daily during execution.
Milestones marked complete before the plant is actually ready for mechanical completion or start-up.
Status updates scattered across chat, spreadsheets, and email instead of one shared workspace.
Closeout notes missing key lessons learned, which causes the same turnaround issues to repeat next cycle.

Common use cases

Refinery Turnaround Leadership
A turnaround manager uses the workspace to coordinate operations, maintenance, engineering, and contractors across a fixed shutdown window. The milestone gates help leadership confirm scope freeze, mechanical completion, and start-up readiness before the unit returns to service.
Chemical Plant Permit Control
An HSE lead and operations lead use the daily safety and permit review to track isolations, confined space permits, and hot work approvals. The workspace keeps the permit pack, LOTO matrix, and exception decisions visible to the full turnaround team.
Power Generation Outage Execution
A project manager runs the daily execution standup and hill chart to track outage work packages, vendor access, and critical path tasks. The structure makes it easier to see which items are blocking mechanical completion and which are ready for handover.
Contractor Mobilization for Heavy Maintenance
A contractor coordinator uses the mobilization checklist and readiness task list to confirm site access, onboarding, tools, and work package alignment. This reduces first-day delays and gives the leadership team a clear view of contractor readiness before shutdown begins.

Frequently asked questions

What is this template for, exactly?

This template is for planning and running a plant shutdown turnaround from scope freeze through start-up readiness. It gives you a workspace structure for leadership check-ins, daily execution, safety and permit control, milestone tracking, and closeout. Use it when the outage has multiple workstreams, contractors, and approval gates that need one shared operating rhythm.

Who should run the workspace?

The turnaround manager or project manager usually owns the workspace, with the engineering lead, maintenance lead, operations lead, and HSE lead filling role-based member slots. Each task list should have a clear DRI so decisions do not stall in the channel. If contractor coordinators or planners are involved, they should be added as consulted roles rather than replacing the core ownership structure.

How often should the check-ins run?

This template includes a weekly Monday turnaround leadership check-in, a daily execution standup, and a daily safety and permit review. That cadence matches the pace of a shutdown where conditions change quickly and approvals need same-day visibility. If your outage is smaller, you can reduce the daily meetings, but keep at least one execution review and one safety review during the shutdown window.

What kinds of teams is this template best for?

It fits refinery turnarounds, chemical plant shutdowns, power generation outages, and heavy industrial maintenance events. It is especially useful when work spans operations, maintenance, engineering, procurement, contractors, and safety. It is less useful for routine maintenance tickets or small single-trade jobs that do not need milestone-based coordination.

How does this differ from ad-hoc email or chat coordination?

Ad-hoc coordination tends to bury scope changes, permit issues, and readiness gaps across scattered messages. This workspace keeps the master schedule, scope freeze register, safety plan, LOTO matrix, and handover checklist in one place so the team can trace decisions and status. The result is clearer ownership, fewer missed dependencies, and a better record for closeout.

What should be customized before using it?

Replace the placeholder roles with your actual turnaround roles, define the shutdown window dates, and tailor the task lists to your plant units and work packages. Update the milestone names to match your approval gates and add any site-specific permit or isolation steps. You should also connect the pinned resources to your live schedule, document repository, and reporting files before kickoff.

Can this workspace integrate with our existing tools?

Yes. The template is designed to connect with Microsoft Teams, Google Drive, Microsoft Excel, SAP, and Power BI. Those integrations are useful for pulling in schedules, contractor lists, work orders, budget views, and progress reporting without duplicating the same data in multiple places. Keep one system of record for each artifact and link it into the workspace.

What are the most common setup mistakes?

The biggest mistakes are using a generic channel for everything, leaving ownership unclear, and starting execution before scope freeze is truly approved. Another common issue is treating safety and permit review as a one-time step instead of a daily control during the shutdown window. The template works best when the team follows the stage-based task lists and updates the milestone status as decisions are made.

Ready to use this template?

Get started with MangoApps and use Plant Shutdown Turnaround Workspace with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?