Project management

How to Plan a Maintenance Shutdown Without a Spreadsheet

12 Jun · 7 min read · by the Phaselo team

Most planned shutdowns are tracked across three Excel files, a WhatsApp group, and someone’s notebook. The shutdown itself might run for 48 hours, but the planning starts months earlier, involves a dozen trades, and the cost of overrunning is measured in lost production per hour. Here is a planning structure that holds up under that pressure.

Why spreadsheets break down for shutdown planning

A spreadsheet is fine for a task list. A shutdown is not a task list. It is a hierarchy: the shutdown has phases (isolation, mechanical works, electrical works, recommissioning), each phase has work packages, and each work package has tasks owned by different people, often different companies. The moment two people edit the same sheet, or a contractor emails through a revised scope, your single source of truth splits into five versions.

• No rollup: you cannot see at a glance whether the electrical phase is 40% or 80% done.
• No ownership: a cell with initials in it is not an assignment anyone gets notified about.
• No dates that move together: when isolation slips a day, every downstream row is wrong.
• No history: nobody knows who changed the scope or when.

Step 1: Structure the shutdown as a hierarchy

Start with the phases as top-level items, then break each phase into work packages, then tasks. A typical structure looks like this:

1. Pre-shutdown: scope freeze, long-lead parts ordered, contractor inductions, isolation plans approved.
2. Isolation and access: lockout-tagout, scaffolding, confined space permits.
3. Mechanical works: each major equipment item is its own work package.
4. Electrical and controls: switchboard work, instrument calibration, loop checks.
5. Recommissioning: function tests, safety system proofs, handover to production.

The discipline that matters: every task has one owner and one due date. Work packages roll their progress up to phases, and phases roll up to the shutdown. When the plant manager asks how it is going, the answer is a number, not a feeling.

Step 2: Schedule backwards from production restart

Shutdowns are scheduled backwards. Production needs the line back at a fixed time, so recommissioning gets a fixed window, which fixes the end of electrical works, and so on back to day one. Build the schedule on a Gantt timeline so every phase is visible against the calendar, and so that when one bar moves you can see exactly what it collides with.

Put a buffer between mechanical completion and recommissioning. Every experienced shutdown planner does this, and every overrun report says the same thing: the buffer was consumed by discovery work, the extra scope you find once equipment is opened up.

Step 3: Coordinate contractors with a shared plan

The riskiest interfaces in a shutdown are between companies, not within them. Your electrical contractor finishing late delays your instrument techs, who belong to a different company and have other jobs to get to. The fix is unglamorous: one shared plan that everyone can see, with statuses that are updated from the floor, on a phone, the moment work completes. If status updates wait for the evening toolbox meeting, your plan is always half a day stale.

Step 4: Track quotes and scope in the same place

Attach contractor quotes, scope documents, and isolation drawings to the work packages they belong to. When a variation comes in, it lands on the item it affects, with a note saying who approved it. Six months later, when finance asks why the shutdown cost 12% over budget, the answer is in the plan, not in an inbox.

The tooling question

You do not need enterprise maintenance software for this. You need a hierarchical plan, a Gantt view, a board for the floor, and budget fields on each work package. That is exactly what Phaselo does: it is project planning software built for operations teams, at $8 per user per month with a 14-day free trial. Set up your next shutdown as a real plan and retire the spreadsheet.