MAINT-WINDOW · SORT A · PLANNING BOARD WINDOW OPEN
WINDOW 08:00 HRS CREW 2 OT + 1 CONTRACTOR STAGED NIGHT SHIFT ✓ OPS NOTIFIED T-14 DAYS ✓ 06:00 08:00 10:00 12:00 14:00 PRODUCTION WINDOW — 8H NOW STAGE ✓ WEAR-STRIP REPLACEMENT — 4H BONUS PM BUFFER OPS RESUME CREW: 2 INTERNAL (06:00 OT) + CONTRACTOR (07:00)
Operations · OPS-201 8 min read · From the floor · Planning & management

Planning a maintenance shutdown without blowing the production window

Here's the truth about "blowing the window": you don't blow it by running long. You blow it by running long unannounced. The same overrun, communicated early, becomes a planned diversion. Discovered at 2 p.m., it becomes a crisis.

MVP-TOOL · WINDOW BLOWER · DOWNTIME SIMULATOR WINDOW HOLDING

Try it: drag the job until it blows the window.

The window is fixed. The job is what you estimate it to be. Watch what happens — and what it costs — when the estimate runs long.

◂ WINDOW ENDS — 8H
INTO PRODUCTION TIME
MAINTENANCE WINDOW PRODUCTION RESUMES ▸
◂ DRAG ▸
6.0hJob length
Job6h
Window8h
Overrun0h
Bleed rate$4,784/hr
Overrun cost$0
FITS — 2.0H OF MARGIN
THIS IS WHAT STAGED PREP AND HONEST ESTIMATES PROTECT

If this line stopped unexpectedly, it would bleed $4,784/hr — that's $80/min.

Estimate only. Real downtime cost varies with recovery, spoilage, and network effects — industry figures put unplanned downtime at 5–20x the hourly cost of planned work. Use your finance team's numbers where they exist.

Get the free PM checklist

Most shutdown-planning guides are written for refinery turnarounds — 18-month planning cycles, thousands of work packages. Useful, but that's not the world most maintenance managers live in. This is shutdown planning for the rest of us: recurring downtime windows, a small crew that's already fully committed to shift coverage, and jobs that have to get done whether they fit the window or not.

The stakes are real and measurable: industry figures put unplanned downtime at 5–20x the cost per hour of a planned window — and planned downtime only counts as lost capacity when it overruns its schedule. Everything below is about keeping your work on the right side of that line.

01People first, not the window

The instinct is to start with the clock: "we have an 8-hour window, what fits?" That's backwards. For a must-do job, the job is happening regardless — the timeframe bends around it. The first move is finding availability.

Picture the real constraint: nine technicians covering a 7-day operation on two 10-hour shifts. Every one of them already has a job — keeping the operation covered. There is no bench. Project labor has to be carved out of a schedule that's already fully committed, and that carving is the actual planning problem, before a single wrench is picked up.

The hierarchy that works:

  1. Who's off and can take overtime — without wrecking their rest or their next shift.
  2. Bring the incoming shift in early on OT — they start the job fresh and roll into their regular shift.
  3. Put the outgoing crew on staging and prep — end of their shift, they set up access and lay out parts so the job crew walks into a ready worksite.
  4. Protect the critical crew — the core coverage never gets raided, no matter how big the project is.
  5. Contractors close the gap — when the internal math doesn't work, a familiar contractor with the right skills fills it. Familiar matters: you want people who've seen this equipment class before, not just warm bodies.

02Complexity caps crew size — more hands isn't more speed

Here's the counterintuitive one that separates experienced planners from optimistic ones: every job has a maximum useful crew, and it's usually smaller than you'd like.

On a wear-strip replacement inside a sorter bed, four techs is about the max — add a fifth and they're literally working on top of each other. The job's physical footprint dictates how many hands can actually contribute. Past that number, extra people add congestion and cost, not speed.

So when the window feels tight, the answer usually isn't "throw more people at it." It's prep, sequencing, and an honest duration estimate — the three things that actually compress a job.

03Read the true job length before you commit

The industry's own post-mortems say the biggest overrun causes are discovered work and overly optimistic scheduling. The defense is reading the job's true length from its physical access difficulty before you commit to a plan.

The same wear-strip replacement is a ~4-hour job on the accessible top side of the sorter — and 12+ hours on the lower side, where every step is a fight. Same task, triple the duration, purely because of where the work sits. Estimate from access, not from the task name.

SAME JOB · DIFFERENT ACCESS TOP SIDE ~4H LOWER SIDE 12H+ ESTIMATE FROM ACCESS, NOT THE TASK NAME
Access difficulty sets the clock — triple the duration, same task

And pad it. The planning literature is blunt on this: slightly overestimate to build a buffer, because an unplanned overrun costs far more than finishing early. If you finish early, bundle in a PM task that was coming due anyway — the asset's already down.

04The split test: can you hand it back mid-job?

When a job is bigger than any single window, there's exactly one question that decides the plan: can the equipment be safely handed back to operations in a partial state?

✓ Yes → split it across windows

If the equipment can run safely mid-job, work to a legitimate stopping point, hand it back, and finish in the next window. Real example: a wear-strip repair where only part of the material had failed — the rest was intact, the sorter could run, so the job paused and resumed the next day.

✗ No → run it start-to-finish

Full replacements and hard-access work usually have no safe mid-state. Once you start, the equipment can't go back until it's done — even if that blows through the window into operational time. Which is exactly why the next section exists.

Job bigger than the window? Ask: can it be handed back mid-job? yes — safe mid-state no — no safe mid-state Split across windows Stop at a legitimate point, hand back Run start-to-finish Even into operational time Tell operations EARLY They divert volume to another building — your crew works uninterrupted to done
Fig. 1 — The split test, and the early-notification play

05The overrun play: renegotiate the window before it breaks

This is the move that gives the article its title. When you know a start-to-finish job will run past the window into operational time, you tell operations in advance — and they divert volume to another building so your crew keeps working uninterrupted until the job is done.

Think about what that changes. The production window doesn't get "blown" — it gets renegotiated ahead of time. Nobody's surprised at hour nine. The work never has to stop halfway, in the worst possible state, because somebody upstream is demanding the line back. The planning literature frames this as the schedule either fitting the window or "triggering a negotiation with production over acceptable extension risk" — the floor version is simpler: pick up the phone early, and the network absorbs it.

The real rule

An overrun communicated before the window opens is a plan. The same overrun discovered mid-window is an incident. The hours are identical — the difference is entirely in when operations finds out. Your credibility as a maintenance manager is built on which of those two you deliver.

06Prep buys back the window: the hour before the hour

Setup delay is a documented, chronic window-killer — crews standing around on the clock while access gets rigged and parts get tracked down. The industry fix is completing and verifying kits well before the window opens. The floor version is sharper:

The outgoing crew stages the job at the end of their shift. Access equipment set up the night before. Parts pulled and laid out at the worksite. The job crew comes in early and walks into a ready worksite — wrench time starts at minute one.

On a sorter wear-strip job, that prep is worth about an hour of window time. On an 8-hour window with a 4-hour job, that hour is your entire margin for surprises — the discovered work, the seized bolt, the part that doesn't fit. Prep isn't a nicety; it's where your buffer comes from.

Real case

How the sequencing actually ran

A wear-strip replacement needed 3–4 techs; one was on medical leave, only two day-shift techs were available for the morning window, and the other two had prior commitments. The night crew wasn't touchable — they'd just worked a full shift.

The plan: night crew set up the access equipment at the end of their shift. The two available techs came in at 6 a.m. instead of 9 — early OT, fresh, walking into a staged worksite. A familiar contractor with mechanically capable techs arrived at 7 a.m., after the internal crew had an hour to prepare. Top-side job, four hours, done inside the window with margin to spare.

Every piece of that is repeatable: stage with the outgoing crew, start the job crew early, layer the contractor in after your people are set.

Lockout / Tagout Safety first — always

A downtime window is not a de-energized machine. Every job in the window — staging included — starts with energy isolation. Lock out, tag out, and verify per your facility's energy-control policy before anyone reaches into the equipment, and account for LOTO time in the window plan. Multiple crews and contractors on one job means everyone is on the clock and on the locks — your facility's group-lockout procedure is the authority.

07By the book vs. on the floor

By the book

Define scope, build a sequenced schedule with dependencies and a critical path, secure labor and materials in advance, kit and verify parts before the window, model where parallel work compresses duration, and hold a lessons-learned afterward. For major turnarounds, planning starts months ahead.

On the floor

With recurring daily windows and a small crew, the same principles compress into instincts: availability first, complexity caps the crew, read duration from access, stage with the outgoing shift, protect the critical crew, and call operations early when it won't fit. Same discipline, human scale.

The book and the floor agree on more than they differ here. The difference is scale — you don't need a Gantt chart for a four-hour job. You need the five questions in the right order, answered honestly.

08The takeaway for your floor

The window-planning engine, in order:

1Availability first — carve labor without raiding critical crew
2Read true duration from access; complexity caps the crew
3Can't hand it back mid-job? Tell operations early

Stage the night before. Start the crew early. Keep the core coverage intact. Estimate from access, not optimism. And when the job won't fit the window, say so before the window opens — because an announced overrun is a plan, and an unannounced one is the thing that ends up in your performance review.

Plan your windows around what actually matters

Grab the free conveyor PM checklist — daily, monthly, and annual inspections.

Free · Unsubscribe anytime

Almost there — check your inbox

Click the confirmation link we just sent, and the checklist is yours. If it isn't there in a minute, check your junk folder.