Menu
About Us Contact
Login Join the Waitlist

The Science Behind 6 Week Lookahead Schedule Effectiveness

Related Dashboard Feature: Lookaheads

The Science Behind 6 Week Lookahead Schedule Effectiveness

Why anyone bothers looking six weeks out

Most jobs run just fine on a three-week look-ahead. Three weeks is close enough that you can trust the crews, close enough that a delivery date means something, and short enough that you can rebuild the plan Monday morning without hating your life. So why would you ever stretch the window to six?

Because some problems can't be solved in three weeks. If a switchgear lead time is nine weeks and you only see the mechanical room energization when it lands three weeks out, you've already lost. The whole point of a longer horizon isn't better planning for its own sake — it's buying enough runway to remove a constraint before it becomes a crisis. Six weeks is roughly the distance at which the slow-moving problems on a commercial or multi-family job first become visible while you can still do something about them.

That's the honest case for the six-week look-ahead: it's a constraint-removal window, not a fortune-telling exercise. Weeks one and two are commitments. Weeks three and four are where you're clearing the path. Weeks five and six are early warning — soft, still moving, but far enough out that a long-lead item or a tricky inspection has time to get sorted. Treat those last two weeks as a watch list, not a promise, and the format works. Treat them as gospel and you'll burn trust every time the far end slides.

Where six weeks comes from — the Last Planner logic

This isn't a number someone made up. The look-ahead sits inside the Last Planner System that Ballard and Howell built out in the '90s, and the layers matter:

  • Master schedule — the milestones the owner and the contract care about, months out.
  • Phase schedule — how a phase gets pulled, built collaboratively with the trades who actually do the work.
  • Look-ahead — the make-ready window, where you hunt down and kill constraints week by week.
  • Weekly work plan — what crews actually commit to this week, and only what's genuinely ready.

The look-ahead is the make-ready layer. Its one job is to make sure that by the time an activity hits the weekly work plan, every constraint — material, manpower, prerequisite work, information, inspection, access — is already cleared. Six weeks tends to be about how long it takes to clear the average constraint on a typical build. That's the whole theory, and it holds up on site.

Long-lead material is the number-one reason to stretch the window

Walk a mechanical room backward and you'll see why three weeks isn't always enough. Say the air handler needs eight weeks from release to delivery, the fabricated pipe racks need four, the housekeeping pads and their embeds need to be poured before any of it, and the roof curbs have to be set before the roofer is off the building. If the first time energization surfaces on your plan is three weeks out, the AHU order is already six weeks late and you're renting a temp unit or eating a month of delay.

A six-week horizon lets you see the trigger dates while they still mean something. The move is to walk every activity in weeks four through six backward to its longest lead item and ask one question: has this been released, and does the ship date land before I need it? If the answer is no, that's this week's problem, not next month's. This is exactly the kind of thing a proper look-ahead tool earns its keep on — LookAheadWall keeps the sequence and the trade flows connected so the far-out activities stay tied to the work that feeds them, instead of you rediscovering the dependency the hard way. But the discipline comes first; the software just keeps you honest.

The inspections and approvals nobody schedules until it's too late

Here's a failure mode I've watched sink weeks: the work gets built, the crew's ready to close it up, and then somebody remembers the special inspector needs 48 hours' notice, or the AHJ won't do a rough-in inspection until the deputy inspector's report is in, or the fire marshal only comes Tuesdays. On a three-week look-ahead the activity requiring the inspection often shows up after the notice window has already closed.

Six weeks gives you room to see these coming. Some real ones to build into the plan:

  • Third-party and deputy inspections that need scheduling days ahead — special inspection for structural welds, high-strength bolting, epoxy anchors.
  • Commissioning and startup that need the agent booked weeks out and the equipment actually running on temp power.
  • Utility crews and the power company, which run on their own calendar and don't care about yours.
  • Health-department or infection-control sign-offs on healthcare work, which have their own lead time entirely.

The rule of thumb: any activity that ends in an inspection or an approval needs its scheduling lead time backed out just like a material lead time. Put the "call the inspector" task on the look-ahead as its own line, not as an assumption living in your head.

Coordination that can't be arranged on short notice

Some sequences are just slow to choreograph. Healthcare renovations with ICRA barriers, phased shutdowns, and a dozen trades threading a live floor. Data centers where power, cooling, and the IT rooms all have to land in a specific order or the commissioning falls apart. Occupied multi-family where you're coordinating tenant access weeks ahead. You can't sequence that on Friday for Monday.

The value of the longer window here is meeting cadence. When the trades can see four to six weeks out, your weekly coordination meeting stops being a fire drill and becomes a real conversation — the plumber flags that his overhead has to be in before the ductwork drops, the electrician says he needs the walls one-sided before he can pull, and there's still time to resequence. Sharing the look-ahead with your subs so they're looking at the same board is what makes that possible; a plan that lives only on the super's laptop coordinates nobody.

Resource leveling you can actually act on

Master-schedule leveling is coarse — total headcount per week, crane hours, big buckets. The look-ahead is where you catch the specific collisions. When you can see that your one certified welder, your rough-in crew, and a demo push all want week four, you've got time to slide one earlier, one later, and leave the third alone. Discover that same conflict three days out and someone's working a weekend or the sequence breaks.

Same with the single-resource bottlenecks that never show up in aggregate: the one manlift, the one crane pick everybody needs, the elevator you're using as a material hoist. Those are worth walking the whole six-week window for specifically, because they're invisible until two trades show up for them the same morning.

Weather, and the buffers that keep it from wrecking you

Forecasts past ten days aren't worth much, but the six-week window still helps because it lets you stage interior fallback work. If the ten-day shows a wet stretch, you want interior activities already made-ready so you can flip to them without losing a beat — not scrambling to find something for the crew to do in the rain.

While we're on buffers, a few that experience has beaten into me and that belong in any horizon:

  • Frame to rough-in usually wants a 1–2 day buffer for cleanup, layout, and the framing inspection to clear.
  • Concrete needs its cure before you load it — don't schedule the trade that stresses the slab the morning after the pour.
  • Underground and anything getting covered up: build in the day for the survey, the photos, and the inspection before backfill, because there's no do-over once it's buried.
  • Megger your feeders and home runs before the drywall goes up. Finding a nicked conductor with an open wall is an afternoon; finding it after paint is a demolition.

Managing the phase transitions

The ugliest weeks on any job are the transitions — foundations to structure, structure to dry-in, rough-in to finishes. Everybody's mobilizing, demobilizing, or changing floors at once. The six-week window is where you detail that handoff: who's leaving, who's coming, what has to be complete and inspected before the next trade gets access, and where the crews physically pass each other. Run that off the phase plan the trades pulled themselves and the transition goes quiet instead of chaotic.

When six weeks is the wrong answer

More horizon is not automatically better. Plenty of times it's worse:

  • Short or fast jobs. On a six-month project, six weeks is a quarter of the whole thing — the far end is pure guesswork and you'll spend real effort maintaining a fiction. Stick with three.
  • A team new to look-ahead planning. If the crews aren't yet in the habit of making genuine commitments and hitting them, don't pile six weeks on top of that. Get three weeks working and measured first.
  • Simple, repetitive work. A straightforward tilt-up or a repetitive podium wrap doesn't need extended visibility; three weeks coordinates it fine and costs you less to maintain.

The tell that your horizon is too long: the last two or three weeks of the plan change so much every week that nobody trusts them, and the trades stop reading past week two. When that happens, shorten up. The right window is the shortest one that still catches your longest constraint — for a lot of commercial work that's three or four weeks, and only the genuinely long-lead, heavily-coordinated jobs need the full six.

Rolling it out without blowing up your Mondays

If you're extending from three weeks to six, don't jump. Add a week, let the team absorb the extra make-ready work, then add another. The discipline doesn't change — weekly updates, constraint hunting, trades in the room, measuring your plan-percent-complete — it just covers more ground. Whatever you're planning in, whether that's LookAheadWall or a whiteboard that works, the tool matters far less than whether the crews believe the plan and the constraints are actually getting cleared. Six weeks of visibility is only worth anything if you use the extra runway to remove the constraints it reveals. Otherwise you've just built a longer list of problems you can see coming and still aren't fixing.