Most jobs already run a three-week look-ahead. It's the workhorse of short-interval planning: near enough that the work is real, far enough that you can still fix what's broken. So why stretch it to six? Because three weeks is where you fight fires, and six weeks is where you keep them from starting. The extra runway is what turns "we're waiting on the switchgear" into "we ordered the switchgear five weeks ago and it lands Thursday."
This guide is about actually running a six-week horizon on a live job — not the theory, but how to structure it, what belongs in which week, and where crews get it wrong. If you've ever printed a beautiful six-week schedule that nobody looked at twice, this is for you.
Why six weeks, and why not more
The value of a longer horizon isn't scheduling — it's lead time. Six weeks is roughly the sweet spot for the things that kill construction jobs when they arrive late: long-lead material, inspections that need a week of notice, engineered submittals coming back from the architect, temporary power, crane picks, and trade partners who need their own three-to-four weeks to staff up.
Go much past six and you're back in CPM territory — a plan detailed enough to feel precise but far enough out that it's fiction. Field conditions, weather, and change orders will rewrite anything past week six before you get there. Keep the six-week view coarse on the back end and sharp on the front, and you get the procurement warning without pretending you can predict the exact day a drywall crew hangs a specific corridor forty days from now.
Build it as a funnel, not a flat grid
The single biggest mistake is planning all six weeks at the same level of detail. You end up with a wall of tasks, most of them wrong, and the crew tunes it out. Treat the horizon as a funnel where detail increases as work approaches:
- Weeks 5–6 (the outlook): Big blocks by area and phase. "East wing MEP rough-in," "Level 3 slab pour," "roof dry-in." No hour-by-hour anything. This band exists for one reason — to surface constraints early enough to clear them.
- Weeks 3–4 (the make-ready zone): Break blocks into trade-and-area activities. This is where you actively remove constraints: chase the submittal, confirm the material ship date, book the inspector, coordinate the deliveries. Nothing should reach week two unless it's clean.
- Weeks 1–2 (the commitment): This is your weekly work plan. Specific crews, specific locations, specific durations, and real commitments the foremen made in the coordination meeting. If it's in week one, it should be ready to build with everything on hand.
The discipline that makes this work comes straight out of the Last Planner System: work doesn't advance into the commitment weeks until its constraints are gone. A location-based look-ahead tool makes the funnel visible — you're planning by area and trade flow, not by a flat task list, so it's obvious when two crews are stacked in the same room in week two.
Load the back end with the things that have lead time
Weeks five and six earn their keep on procurement and make-ready, not sequencing. When you populate that band, walk it with a specific question for every block: what has to already be moving for this to happen on time?
- Long-lead material. Switchgear, elevators, curtain wall, custom AHUs, and structural steel routinely run 8–20+ weeks. Those don't live inside a six-week window — but the delivery confirmation does. Week six is where you verify the ship date lands when you need it, while there's still time to expedite or resequence.
- Submittals and RFIs. A submittal that hasn't come back approved is a constraint on everything downstream. If you're roughing-in in week two, that submittal should have cleared in week five.
- Inspections. Many jurisdictions want 24–72 hours' notice, and a failed inspection costs you a re-inspection slot that can be days out. Put the inspection on the schedule, not just the work that precedes it.
- Third-party and utility work. Power company energization, fire alarm monitoring hookups, and special inspections have their own calendars you don't control. Six weeks is often the minimum notice they need.
A useful rule of thumb: if something takes longer to get than to install, it belongs on your radar in the back weeks. The install might be a two-day event, but the getting is where jobs slip.
Trade flow across six weeks
Short-interval scheduling lives or dies on the handoffs between trades, and a longer horizon lets you see the whole relay instead of one baton pass. Map the flow through a typical area and hold buffers between the trades that need them:
- Frame-to-rough-in usually wants a 1–2 day buffer for cleanup, layout, and the framing inspection before MEP starts drilling and hanging.
- Rough-in-to-cover (insulation and drywall) needs every trade's inspection signed off first — and don't close a wall until the electrician has meggered the runs and the plumber's held pressure on the lines. Covering unverified work is the most expensive thirty seconds on the job.
- Finishes stack tightly and fight over the same rooms. Paint, flooring, trim, and casework in the wrong order means somebody's protecting or redoing work. Sequence by room, not by trade.
Seeing this across six weeks is what lets you catch a pileup before it happens — when three finish trades are all pointed at the same corridor in the same week and only one can win. Connecting trade-flow sequences visually, the way LookAheadWall lays them out by location, turns that collision from a Tuesday-morning argument into a planning decision you make with time to move somebody.
Run it on a weekly cadence, or don't bother
A six-week look-ahead is a rolling plan. Every week the whole thing shifts forward one column: last week's commitments get scored, week two becomes week one, and a fresh week six appears on the back. Skip a week and the plan rots — the back weeks go stale, constraints quietly miss their window, and by the time you notice, the thing you needed is already late.
The cadence that works on most jobs:
- Superintendent updates the outlook ahead of the meeting — rolls the window, pulls in new blocks, flags new constraints.
- Weekly coordination meeting with the foremen. Walk the make-ready weeks, assign who owns each open constraint, and let the last planners — the people who'll actually do the work — make the week-one and week-two commitments. Commitments you impose don't get met; commitments they make do.
- Score last week. Track your Percent Plan Complete: of the tasks you committed to, how many finished? PPC in the 50s early is normal. If you're stuck there after a couple of months, your constraints aren't really clearing before work hits the commitment weeks — which almost always means the make-ready band is being skipped.
The meeting is the product. The schedule is just the artifact that makes the meeting honest. A shared, always-current plan the foremen can pull up on a phone in the field — rather than a PDF that was true last Monday — is the difference between a plan people run and a plan people humor.
Phase transitions are where six weeks pays off
The one place a six-week horizon consistently beats a three-week one is spanning a phase change — structure to skin, rough-in to finishes, one building to the next. Those transitions carry a stack of constraints that all come due at once: a certificate for temporary occupancy, a fire-rated assembly that has to be inspected before anything covers it, a crane that has to come down before the next trade can stage. Three weeks doesn't give you room to line those up. Six does — you can see the transition coming a month out and clear the runway instead of hitting it flat-footed.
Common failure modes
- Same detail everywhere. If week six is as granular as week one, you built a fantasy. Keep the back end coarse.
- Planning without make-ready. A look-ahead that lists work but never tracks and clears constraints is just a prettier wish list. The middle weeks are the whole point.
- The superintendent's private schedule. If the foremen and subs don't see it and didn't help build it, it's not a plan — it's your opinion. Share it, and let the people doing the work make the near-term commitments.
- Set-and-forget. Miss the weekly roll and the horizon collapses back to three weeks of reality plus three weeks of decay.
- No scorekeeping. Without PPC and a reasons-for-variance list, you never learn why work slips, so you make the same misses next month.
Getting started without blowing up the job
Don't roll out a six-week horizon across a whole program at once. Extend your existing three-week look-ahead by adding weeks four through six as a coarse outlook band, and use them for exactly one thing at first: constraint and procurement warning. Once the crew is comfortable making and clearing constraints in the make-ready weeks, the rest follows. Whether you run it on a plotter-printed grid or in software built for location-based short-interval scheduling, the mechanics are the same — funnel the detail, clear constraints before work reaches the commitment weeks, roll it every single week, and keep score. Do that, and six weeks stops being a longer schedule and becomes an earlier warning system. That's the whole point.