Most crew leaders learn the look-ahead schedule from the receiving end. Somebody hands you a printout in the Monday huddle, tells you where your guys are working that week, and you go run your work. You are treated as a consumer of the plan, not a builder of it. That is a waste, because the crew leader standing in the middle of the work has information nobody in the trailer has. You know your production rates cold. You know that the third floor east wing is still full of the plumber's material. You know your best hanger is out for a knee surgery next week. The look-ahead is only as good as the field knowledge that goes into it, and you are the field knowledge.
This guide is about how the schedule actually gets built, so you can push back intelligently, contribute the details that matter, and stop getting handed plans that were doomed before Monday.
What a Look-Ahead Actually Is
The master schedule (the big Gantt chart with a thousand bars) tells everybody the shape of the whole job — foundations in March, topped out by August, turnover in December. It is a promise to the owner. It is not a work plan. Nobody frames a wall off a master schedule.
A look-ahead schedule is the bridge between that master plan and what your crew does tomorrow morning. It takes the next three to six weeks of work and breaks it down to a level you can actually execute against: which crew, which area, which activity, in what order. Most jobs run a three-week or four-week window. Three weeks is tight and honest — you can see far enough to line up materials and remove blockers, but not so far that you are guessing. Six weeks starts to get fuzzy at the back end, but it is useful for spotting the material lead-time problems before they bite you.
The key word is rolling. The look-ahead is not built once and printed. Every week you drop the completed week off the front and add a new week on the back. What was speculative three weeks ago becomes firm as it moves toward the front of the window, and by the time an activity hits week one it should be fully vetted, fully supplied, and ready to go with no surprises. If your look-ahead is a document that gets made once and then ignored, you don't have a look-ahead. You have a wish.
Breaking Work Down to the Right Grain
The single most common mistake in look-ahead construction is activities that are too big. "Drywall — Level 3" as a single line covering two weeks tells you nothing. You can't tell if it's on track until it's already late.
Break work down to pieces that can be completed inside the planning window and, ideally, that you can call done or not-done at the end of a day or two. "Hang rock, Level 3 east, rooms 301–318" is a real activity. It has a location, a scope, a crew, and a duration you can defend. When your superintendent asks Wednesday whether you're on track, you can look at the board and know.
Good rules of thumb for sizing activities:
- If an activity is longer than about five working days in the look-ahead, split it by area or by phase. Long bars hide slippage.
- Tie every activity to a physical location — a floor, a wing, a unit, a grid line. Location is how trades stay out of each other's way, and it's how you measure real progress.
- One crew per activity where you can manage it. When two crews share a line item, nobody owns the completion.
This is exactly where a location-based look-ahead tool earns its keep. When you build the week visually — activities laid out against areas of the building rather than as an abstract list — you can see your own crew's flow and where you're about to run into another trade. LookAheadWall is built around that location grid for this reason: the plan looks like the building, not like a spreadsheet.
Constraints: The Part That Separates Real Planning From Guessing
Here is the discipline that makes a look-ahead worth building. Before an activity is allowed to move into the near-term window, somebody has to confirm it is actually ready to be worked. An activity is not ready just because its predecessor is done on paper. It is ready when every constraint on it has been removed.
The standard constraint checklist — the things that block work from starting — comes down to a handful of categories. Walk every upcoming activity against these:
- Design/information — Are the drawings released for construction? Any open RFIs on this scope? An unanswered RFI is a constraint, and it is the one most likely to get ignored until the crew is standing there.
- Materials — Is it on site, or does it have a lead time that runs past your start date? This is where a six-week look-ahead saves you, because it surfaces the long-lead problem while there's still time to expedite.
- Predecessor work — Is the work in front of you actually complete, or just "mostly"? "Mostly done" is the killer.
- Prerequisite inspection/sign-off — Rough-in has to pass before you close the wall. If the inspection isn't scheduled, the activity isn't ready no matter how good your crew is.
- Labor and equipment — Do you have the headcount and the lift/scaffold/tools that day?
- Space/access — Is the area cleared out, or is another trade's material still stacked in it?
The whole point of running constraints two and three weeks out is that you have time to remove them. If you find on Monday morning that the wall can't close because inspection isn't booked, you've already lost the day. If you found it two weeks ago, you booked the inspection and nobody noticed there was ever a problem. That process of clearing blockers ahead of the work is what the Last Planner folks call "make-ready," and it is the real reason a look-ahead exists. Everything else is scheduling theater.
Sequencing and Trade Flow
The second half of good look-ahead construction is sequence — the order trades move through the building. On a repetitive job, floors or units, you want trades flowing through in a train, each one following the last through the same areas at a steady pace. Framers, then rough-in (plumbing, electrical, mechanical), then insulation and inspection, then rock. When that flow holds, everybody has room to work and nobody's tripping over the crew behind them.
Where it goes wrong is the buffers between trades — or the lack of them. A few hard-won ones:
- Leave a buffer between frame-out and rough-in, usually a day or two, for cleanup, punch of the framing, and any framing inspection. Rough-in trades that start into a wall that isn't really done end up back-charging and re-working.
- Don't close a wall the same day rough-in finishes. You need the rough-in inspection to pass first, and on the electrical side you want the runs meggered before anybody hangs rock over them — finding a bad run after the wall is closed is a bad day for everybody.
- When you sequence exterior work, build in weather slack. Don't put a critical exterior pour or a roof-dry-in with zero float in a week the forecast is against you. A three-week window gives you room to shuffle exterior and interior work as the weather turns; use it.
Connecting these trade-flow sequences visually — so you can see that the rock crew is riding two days behind rough-in through the same rooms — is where the look-ahead stops being your crew's private plan and becomes a coordination tool the whole job runs on. When the flow is drawn out and shared with the subs, the arguments about who's supposed to be where happen in the planning meeting instead of on the floor.
The Weekly Work Plan: Where the Look-Ahead Meets Monday
The near week of the look-ahead is your weekly work plan — the commitment. This is the level where you, as crew leader, put your name on it. And the discipline here is simple and brutal: only commit to work that is genuinely ready. Do not let anyone (including yourself) load the week with activities that still have open constraints. A weekly work plan full of blocked tasks is how crews end up standing around at 9 a.m. wondering what to do.
Every activity you commit to for the week should pass a quick test: is it the right size, is it in a location that's clear, are the materials there, is the crew there, and has everything upstream of it actually cleared? If yes, commit. If no, it stays in the look-ahead as a candidate and you spend the week removing what's blocking it.
At the end of the week, measure what you promised against what you delivered. If you planned five activities and finished three, the question isn't "who do we blame" — it's "why did those two fail, and is that a reason that's going to bite us again?" Missing materials, a late inspection, a predecessor that ran over. Track the reasons and the same three or four will show up over and over, and now you know exactly what to fix on your job.
Why the Crew Leader's Input Is the Whole Ballgame
Here's the part the trailer often forgets. The durations in a look-ahead are estimates until a crew leader confirms them. The superintendent might pencil in three days to hang a floor. You know it's four because you've hung that exact layout and there's a mechanical room full of soffits that eats a day. If you don't say so in the planning meeting, the plan ships with a one-day error baked in, and it compounds down the flow.
So show up to the look-ahead conversation with real numbers: your actual production rate on this kind of work, the constraints you can already see from the field, the manpower you'll really have. When the plan is built on the field's numbers instead of the office's hopes, it holds. When it's built on optimism, it fails in week one and everybody loses faith in the whole exercise.
Modern look-ahead tools — including the mobile companion apps that put the week's plan in your pocket on the floor — make this two-way. You're not just receiving the plan; you're feeding back what you see, marking what's done, flagging what's blocked, all from where the work is happening. That closes the loop between the trailer and the field, which is the loop that was broken on every badly run job you've ever been on.
Learn how the look-ahead is built, contribute the field knowledge only you have, and hold the line on constraints and honest durations. Do that and you stop being a crew leader who gets handed a plan. You become one of the people the plan can't be built without.