Ask ten superintendents what their three-week look-ahead is for and you'll get ten answers. Some treat it as a report they print Friday afternoon to keep the PM off their back. Some genuinely run their job off it. The difference between those two isn't the tool or the template — it's whether the super understands what each of the three weeks is actually supposed to do. The horizon isn't three copies of the same week. Each week has a distinct job, and mastering the look-ahead means running each one on purpose.
Here's the framework that separates the supers who firefight from the ones whose jobs feel almost boring: week one is commit and execute, week two is make-ready, and week three is scout ahead. Get the roles straight and the rest follows.
Why three weeks, not two and not six
Two weeks is too short to remove real constraints. Most of the things that kill a schedule — a submittal stuck in review, a long-lead fixture, an inspection you didn't book, a sub who quietly de-staffed your job for a bigger one — take longer than two weeks to surface and fix. If your planning window only sees two weeks out, you're finding those problems the week they hit you, which means you're not planning, you're reacting.
Six weeks out, on the other hand, is fiction. Nobody can tell you with a straight face exactly what crew is doing what on a Tuesday five weeks from now. Push your detailed planning too far and you spend your Fridays maintaining a beautiful schedule that reality bulldozes anyway. Three weeks is the sweet spot: far enough out to actually clear constraints before they become emergencies, close enough in that your commitments mean something. Keep a longer master schedule for milestones, sure — but the working horizon lives at three weeks.
Week one: commit, don't just list
Week one is the promise. Every activity in it should be fully constrained-free: crew confirmed, materials on site or with a hard delivery date inside the week, prerequisite work complete, access clear, and the inspection or sign-off it depends on already booked. If any of that is still open, the activity does not belong in week one — it belongs in week two with a name and a due date attached to whatever's blocking it.
The discipline that makes week one real is that you and each foreman commit to it out loud, together, before the week starts. Not "we'll try to get the east wing framed." Either it happens or it doesn't, and if it doesn't, you both want to know why so it doesn't happen again. That's the whole idea behind the weekly work plan and the Last Planner reliability metric (PPC — percent plan complete). You measure what percentage of the things you promised actually got done, and more importantly, you write down the reason for every miss. Track those reasons for a month and you'll see the same three or four causes over and over — that's your real problem list, not the noise.
A concrete tell that a week-one plan is honest: it should survive a walk. Take the plan out on the site with you Monday morning and physically verify that the work in front of you matches what the paper says is ready. If the drywall crew is scheduled to start Wednesday but the MEP rough-in still isn't signed off and the wall's open, that activity was never a week-one item. It was wishful thinking someone promoted too early.
Week two: the make-ready engine
Week two is where the actual scheduling work happens, and it's the week most supers skip. This is the make-ready week — the activities here are not ready yet, and your job is to make them ready before they roll into week one. Every week-two line item should have a short constraint list hanging off it, each constraint with an owner and a date.
Run through the standard constraint categories on every activity: materials (ordered? confirmed delivery?), information (RFI answered, submittal approved, latest drawing revision in hand?), prior work (predecessor complete and inspected?), labor (right crew, right headcount, actually available?), equipment (lift, pump, crane time booked?), and permits/inspections (called in with enough lead time?). Most misses trace back to one of those six. If you clear all six on an activity, it graduates to week one. If you can't clear one, that's your make-ready to-do list, and you chase the owner until it's closed.
A hard-won rule of thumb: build buffers between trades that hand off to each other. Frame-to-rough-in usually wants a day or two of slack for cleanup, layout verification, and the framing inspection before the electricians and plumbers descend. Rough-in to insulation-and-close wants a buffer for the rough inspections to actually pass — and they don't always pass the first time. Don't butt those activities end-to-end on the plan just because the durations technically allow it. A schedule with zero float between inspected handoffs is a schedule that fails the first time an inspector red-tags anything.
Week three: scout the long-lead trouble
Week three isn't about detail — it's about early warning. You're not resourcing week-three activities down to the crew yet. You're scanning for the things that need a running start: long-lead materials, equipment that has to be reserved, permits with real lead time, specialty subs you have to book weeks ahead, and any spot where two trades are going to want the same area at the same time.
The classic week-three save is the long-lead item. Electrical gear, custom glazing, elevators, certain mechanical units — these can carry lead times measured in months, and if you only notice the gap when the activity is two weeks out, you're already sunk. Week three is your recurring prompt to ask, "Is anything three weeks out waiting on something with a lead time longer than three weeks?" If yes, that constraint should already be tracked way upstream on the master schedule — but the look-ahead is your last-chance tripwire to catch what fell through.
Week three is also where you spot the trade-stacking collisions. Two subs both planning to be in the same corridor the same day, one needing the floor clear while the other needs to load it out — that's a fight you want to referee three weeks early over coffee, not the morning it happens with both foremen already on site and burning payroll.
The daily habit that ties it together
The look-ahead is a weekly document, but the best supers touch it daily. Not a full rebuild — a two-minute glance during the morning walk to confirm today's work still matches the plan and to catch tomorrow's problem while there's still time to fix it. This is exactly where a mobile look-ahead tool earns its keep: foremen can see the current plan on their phones, confirm their crews are aligned, and flag a slip the moment it shows up instead of surfacing it at Friday's meeting when it's too late to react. A weekly work plan that lives only on a printout in the trailer is stale by Tuesday.
The weekly update: roll it, don't rewrite it
Once a week — pick a consistent day, usually late in the week so you head into the next one clean — you roll the whole thing forward. Completed work drops off. Week two becomes the new week one, and everything you cleared during make-ready had better actually be ready. A fresh week three appears at the far edge and gets its first constraint scan. Then you sit down with your foremen and get real commitments for the new week one.
That foreman meeting is the point of the whole exercise. Your look-ahead is only as good as the commitments feeding it, and commitments only mean something when the person making them helped build the plan and believes the work in front of them is genuinely ready. A super who fills in the plan alone and hands it down is guessing. A super who builds it with the trades — and holds everyone, themselves included, to the reasons for any miss — is actually scheduling. This is where tools like LookAheadWall fit naturally: laying out the location-based weekly plan visually, wiring up the trade-flow sequences so a slip in one trade shows its ripple downstream, and putting the same plan in every foreman's hand so the commitments and the schedule stay in one place instead of scattered across texts and printouts.
Connecting the window to the master schedule
Your three-week window can't drift off on its own. Every week or two, hold it up against the master schedule and ask whether the work you're planning actually feeds the next milestone. It's easy to stay busy inside a look-ahead and slowly wander off the critical path — everyone's working, the plan's full, and yet the milestone quietly slips because the look-ahead was optimizing local activity instead of milestone progress. The three-week horizon is your execution engine; the master schedule is the destination. Check the heading regularly.
What mastery actually looks like
You'll know you've got it when the job goes quiet. Fewer 6 a.m. scrambles, fewer subs standing around waiting on predecessor work, fewer inspections missed for lack of a phone call. The look-ahead stops being a report you produce and becomes the way you run the job — three weeks of commit, make-ready, and scout, rolled forward every week, driven by real commitments from the people doing the work.
That's the whole trick, and it isn't a secret: know what each week is for, clear constraints before they become fires, and never let a commitment be a maybe. Do that consistently and you stop reacting to your job and start running it.