Factory shutdowns compress weeks of maintenance into days. A Gantt chart is the only way to sequence hundreds of tasks across dozens of contractors without losing a day.
A planned five-day shutdown that runs to eight days costs a discrete manufacturer $300,000 to $1 million in lost production, depending on the line. The overrun almost never comes from the maintenance tasks themselves — it comes from sequencing failures. Two contractors show up to work in the same space. A critical part wasn't on-site and has to be overnighted. An electrical permit wasn't pulled and the work can't start until day 3. The Gantt chart was right. The coordination wasn't.
Shutdowns are compressed projects. They have more parallel workstreams, tighter task dependencies, and less slack than any other project type in manufacturing. A task that slips one day in a normal project is noise. In a five-day shutdown, a one-day slip on a critical path task means the line doesn't restart on time — and every production manager downstream adjusts their forecast for the next three weeks.
Managing a factory shutdown without a Gantt chart is like directing a film with no script. gantt-chart.io lets you build the shutdown timeline, assign tasks to contractors and internal crews, and track daily progress so you know at 7am whether you're on schedule to restart on Sunday night.
1. Not kitting parts before the shutdown. Sending a technician to the storeroom to find a part during a shutdown wastes an hour per occurrence. Every part for every work order should be staged and ready before the shutdown starts.
2. Optimistic task duration estimates. Maintenance tasks in an actual plant take longer than the textbook estimate — flanges that are seized, insulation that has to be removed and replaced, confined space entry protocols that add 30 minutes. Add 20% to every task estimate.
3. No daily critical path check. The Gantt shows the critical path. Checking it once at the start and once at the end is not enough. Check it every morning. If a critical path task slips, you need to know at 7am, not at 4pm.
4. Accepting scope additions without analysis. "While we're in there" is the most expensive phrase in shutdown management. Every scope addition competes for the same labor and contractor hours. Approve or defer — never auto-accept.
5. Not completing work orders before restart. Starting up with open work orders is how you create the next emergency maintenance event. No restart until all must-do work orders are signed off by the responsible person.
How long should a factory shutdown take?
Depends on scope. Annual PMs for a mid-size process line typically run 5–10 days. Major capital work, vessel inspections, or refractory replacements can run 3–6 weeks. The Gantt forces you to estimate realistically before committing to a restart date.
How many contractors can you effectively manage during a shutdown?
The shutdown manager can directly coordinate 4–6 crew leads. Beyond that, you need crew leads managing sub-crews. Add a coordinator for every 6 contractors if the shutdown exceeds 50 total personnel.
What do you do when an inspection uncovers unexpected damage?
Stop, assess, and bring in the decision-makers immediately. Some unexpected findings can be repaired within the shutdown window (adds scope but doesn't delay restart). Others may require extending the shutdown — the earlier you make that call, the cheaper it is.
Should we track contractor costs in the Gantt?
Track scope and progress in the Gantt. Track costs in your maintenance management or ERP system. Link them by work order number. Combining both in one tool usually makes the Gantt harder to read.
How do we handle a shutdown that's running behind schedule?
Identify what's on the critical path and add resources there first. Parallel work that's not on the critical path can slip — focus labor on the tasks that gate the restart. Daily critical path review is the only way to catch this early.
Factory shutdowns are the highest-stakes maintenance events you'll manage all year. Build the Gantt before parts are ordered, assign every task to a named owner, and run daily critical path checks. Start your shutdown plan at gantt-chart.io.