Shutdowns and major outages compress weeks of work into days. When workforce planning is late or unclear, the cost shows up fast: lost schedule, safety exposure, and rework.
This guide gives you a practical timeline and checklist you can use to plan labour needs, mobilisation, and “site-ready” onboarding. The recurring theme is lead time: the constraints that derail shutdowns—onboarding capacity, ticket verification, accommodation, supervision—are almost always known in advance and fixable if you start early. Treat the timeline below as a backward plan from your start date, not a list of tasks to begin once the window is confirmed.
Shutdowns and major outages services: Shutdowns and Major Outages
Key takeaways
- Start with a clear role plan (numbers, dates, rosters, mandatory tickets).
- Define “site-ready” and protect onboarding capacity (inductions, medicals, D&A if required).
- Plan fatigue and supervision coverage early (it’s a safety and productivity lever).
- Run daily KPIs during shutdown (starts vs plan, gaps, onboarding delays, safety).
- Sequence sourcing from the longest lead-time roles backward, so onboarding capacity—not the calendar—sets your pace.
What makes shutdown workforce planning different?
Shutdowns usually have:
- High headcount swings (rapid ramp up and down)
- Safety-critical tasks and permit dependencies
- Tight windows and limited tolerance for delays
- Travel/accommodation constraints
- A need for consistent supervision and fatigue management
Because the window is fixed and the tolerance for delay is low, small planning gaps don’t average out the way they might in steady-state operations—they compound. A queue at induction on day one, a handful of unverified tickets, or a supervisor ratio set too thin can each cost critical-path hours you can’t recover later in the outage.
The planning timeline (copy/paste)
12–8 weeks out: define scope and peak demand
- Confirm scope and critical path tasks.
- Build the role plan: role titles and numbers, start dates and peak days, roster pattern and shift times, mandatory tickets/licences.
- Confirm constraints: access windows/permits/shutdown sequence, accommodation capacity, onboarding capacity (inductions, medicals, D&A testing if required).
- Lock the governance: who approves roles and numbers, daily reporting cadence during shutdown.
8–4 weeks out: build the labour pipeline
- Start sourcing longest lead-time roles first.
- Standardise role profiles so suppliers don’t guess requirements.
- Pre-qualify a bench (tickets verified, availability confirmed).
- Confirm supervisors/leads and ratios.
- Finalise logistics: travel, accommodation, muster points, PPE requirements.
4–2 weeks out: make people “site-ready”
- Run compliance checks: right-to-work verification, ticket/licence verification, medical/fitness requirements (if applicable).
- Schedule and complete inductions.
- Confirm start details: location, time, supervisor contact, what to bring.
- Finalise fatigue management plan: breaks, max hours, shift handovers, escalation process.
2 weeks → start: confirm the plan and remove bottlenecks
- Validate headcount vs schedule daily.
- Confirm onboarding throughput (avoid a queue on day 1).
- Set up timekeeping, cost codes, and reporting.
- Brief supervisors on scope priorities, safety expectations, and escalation paths.
During shutdown: manage to KPIs (daily)
Track:
- Attendance and starts vs plan
- Onboarding issues and delays
- Safety observations and incidents
- Critical role gaps and replacements
Run a daily rhythm: pre-start, progress review, next-day workforce confirmation. A short, fixed daily cycle is what lets you catch a gap while there’s still time to backfill it, rather than discovering it at the next shift. Keep the reporting light enough that supervisors can complete it without stepping away from the work front.
Post-shutdown (week after): retain learnings and reduce churn
- Capture: what caused delays (and fix the top 2), role profiles that were hard to fill, suppliers that performed well/poorly.
- Decide redeployment/stand-down strategy to retain the best workers where possible.
The week after a shutdown is when the lessons are still fresh and worth more than a formal review months later. A short debrief that records the two or three things that actually cost time—and what you’d change—turns each outage into a better starting point for the next one. Holding onto your strongest performers through redeployment or a clear stand-down plan also shortens mobilisation next time, because proven, site-ready workers are the hardest part of the pipeline to rebuild from scratch.
The shutdown workforce checklist (use this as your QA gate)
Work scope and schedule
- Critical path tasks identified and resourced
- Daily plan matches role plan (by shift)
Roles and competency
- Role profiles defined (title, tasks, tickets, supervision requirements)
- Competency verification process defined (who checks what)
Mobilisation and onboarding
- Induction plan (dates, capacity, materials)
- Right-to-work and licence verification completed
- Medical/fitness and D&A process confirmed (if applicable)
- PPE requirements and supply confirmed
- Travel/accommodation confirmed (if applicable)
Safety and fatigue
- Supervisor coverage and ratios set
- Fatigue plan documented (max hours, breaks, handover)
- Permit-to-work coordination defined (interfaces, approvals)
- Incident reporting and escalation path clear
Operations and reporting
- Timekeeping and approvals defined
- Cost codes and reporting ready
- Daily reporting template agreed
Where workforce planning fits
If you need a broader forecast beyond a single outage (or you have multiple outages/projects), workforce planning can sit above the shutdown plan: Workforce planning
Related services (often used together)
- Energy and resources overview
- Production and maintenance on hire
- Managed workforce
- Workforce Planning Template (90 Days)
Related reading
Also see: How to Get Shutdown Work: Tickets, Safety, Common Roles.
Also see: Manufacturing Maintenance Shutdown Resourcing: Plan, Mobilise, Execute Safely.
FAQ
How early should we start planning labour for a shutdown?
Start as soon as the window and scope are known. Long lead-time roles (and onboarding capacity) are usually the limiting factor. Working backward from the start date makes those constraints visible early, while you still have time to act on them.
What’s the most common shutdown workforce failure point?
People arriving not “site-ready” (tickets, inductions, medicals) or approvals slowing down mobilisation.
What should we track daily during the shutdown?
Keep it to the few measures that drive a decision: starts vs plan, onboarding delays, safety observations and critical role gaps. Reviewed each day in a fixed rhythm, they give you enough warning to backfill a gap before it reaches the critical path.
Next step
If you need help sourcing and mobilising shutdown labour safely and quickly: Shutdowns and Major Outages
General information only: this article provides general information and is not legal advice.
