The four-week lookahead is usually built in an office. Somebody sits down with the CPM schedule, pulls the next twenty working days, and lays out what should happen and in what order. That's fine as far as it goes. But the person who actually knows whether that plan survives contact with the jobsite is the crew leader standing in the work, and too often nobody asks him until the plan has already failed.
A lookahead is a prediction. Every prediction is only as good as the information feeding it, and the freshest, most accurate information on a jobsite lives in the heads of the foremen and lead men running the crews. If you want a schedule that hits, you have to pull that knowledge out of the field and into the plan before the week starts, not after. Here's where crew leaders actually move the needle.
Durations: the field number beats the estimate every time
The single biggest source of a blown lookahead is a duration that came off a spreadsheet instead of off the wall. The office might carry drywall hang at a certain rate per man-day because that's what the estimate assumed. The crew leader knows that on this building, with these ceiling heights, this much soffit, and a two-man crew because the third guy is out, it's going to take a day and a half longer than the schedule says.
Get that number from him before the week is committed, not in the Monday recovery meeting. A good habit: when you're laying out the next week, walk the specific area with the crew leader and ask, "How many days does this take you, honestly?" The word honestly matters, because foremen learn to tell superintendents what they want to hear. You want the real number, including the parts that always eat time and never show up on a bar chart:
- Layout and staging before the productive work starts
- Material handling — getting stock to the floor you're working
- The cleanup and protection at the end of the activity
- The inspection hold, if one applies
Those "invisible" tasks routinely add 15 to 30 percent to a raw production duration, and they're exactly what a crew leader accounts for instinctively and an office estimate forgets. A short-interval plan built on field-verified durations is a plan you can actually make commitments against.
Constraints: the crew sees them first
A constraint is anything that has to be true before an activity can start — material on site, prior trade complete, an inspection signed off, a permit in hand, an RFI answered. The whole point of a lookahead is to find these far enough out that you can clear them. And the person who spots most of them first is the crew leader, because he's the one who walks up to the work and finds it's not ready.
The classic example: the schedule says electrical rough-in starts Monday, but the framer knows the backing isn't in for the panel and the top plate isn't fireblocked yet. If the electrical foreman flags that on Wednesday of the prior week, you fix it. If he shows up Monday with three men and finds it, you've eaten a half-day of standby and thrown off the whole float. Multiply that across a dozen crews and you understand why jobs fall behind a day at a time.
Make constraint-spotting part of the crew leader's job and give him a fast, low-friction way to report it. In a mobile-first tool like LookAheadWall, a crew leader looking at his week can flag "not ready" against a specific activity the moment he sees it, and it lands in front of the superintendent while there's still time to act. The technology only matters because it shortens the distance between the guy who sees the problem and the guy who can solve it.
Verifying the work in front of it is actually done
Related but distinct: the schedule assumes predecessors are complete. Paper says the deck is poured and cured, so the next trade can load. The crew leader knows the pour happened but a corner got missed, or the finish isn't right, or the layout marks got buried. "Complete on the schedule" and "complete enough for me to build on" are two different things, and only the field knows the difference.
Train crew leaders to physically verify the handoff before they commit to a start date, not to trust the bar chart. On a location-based plan this is easier to enforce because the sequence is visual — you can see that Trade B's zone butts right up against Trade A's, so B's leader has an obvious reason to go look at what A left him. That handoff inspection, done a few days ahead, is one of the cheapest pieces of insurance on the whole job.
Resource reality: men, equipment, and the tool that's still down
Office plans assume full crews and working equipment. Crew leaders know the truth: two guys are on vacation next week, the scissor lift's been red-tagged, the second crew is committed to punch on another floor. A lookahead loaded with resources that won't actually be there is fiction dressed up as a plan.
Before you commit a week, the crew leaders should confirm the assumptions:
- Are the bodies you're counting on actually going to be here, and skilled for this work?
- Is the equipment available, certified, and not double-booked with another activity?
- Is the material staged, or is it still on a truck that hasn't shipped?
None of that shows up in the office. All of it determines whether the week happens. This is the difference between a schedule that's feasible and one that merely looks good in a meeting.
Flagging the plan that's already wrong
Sometimes the lookahead itself is broken — the sequence is out of order, two trades are stacked in the same zone, a duration is flatly impossible. A crew leader reading his week should be able to say so, and it should cost him nothing to speak up. Cultures where the field stays quiet because "that's the super's problem" produce schedules that everybody privately knows are wrong and nobody fixes.
The fastest jobs I've run had a simple rule: if you see something on the plan that won't work, you tell me before Monday, and you never get chewed out for it. That single norm turns a static schedule into a living one. A weekly work plan that the crews have poked holes in on Thursday is worth ten that look pristine and collapse by Tuesday.
Feeding real production data back into the next plan
Every completed week is data. How long did the activity actually take? How many men, over how many days, to cover how much area? Crew leaders are the source of that number, and it's gold for the next lookahead. Over a few weeks you build a real production rate for this crew on this project — which beats any published rule of thumb, because it already bakes in your access, your details, and your crew's actual pace.
The practical version: track planned versus actual on each activity and let the crew leaders confirm the actuals. After a month you stop guessing at durations and start pulling them from what your own crews have proven they can do. That's how a rolling lookahead gets more accurate as the job goes rather than less.
Explaining the variance — the reason the office can't guess
When a committed task doesn't finish, the number that matters isn't just that it slipped — it's why. This is the heart of the Last Planner mindset: measure your Percent Plan Complete, then chase the reasons for every miss. And the reason almost always lives with the crew leader.
Was it a missing prerequisite? A late material delivery? Weather? A design change mid-week? A crew pulled off to firefight somewhere else? Each reason points to a different fix. If you learn that 40 percent of your misses trace to material not being staged, you fix your procurement and staging, and next month's plans hit harder. Without the field explaining the variance, the office is just staring at red bars with no idea which lever to pull. A one-line reason code from the crew leader — "waited on inspector," "sub no-show," "RFI 214 still open" — is what turns a failed week into a lesson.
Sitting in the planning conversation
The best lookaheads get built with the crews in the room, not handed down to them. When a crew leader helps set the sequence and the dates, two things happen: the plan gets better because his knowledge is in it, and he owns the commitment because he made it, not because it was assigned. A schedule someone helped write is a schedule someone will fight to hit.
This doesn't require a two-hour meeting. A tight fifteen-minute pull-planning conversation where each crew leader confirms his week, flags his constraints, and commits to his starts is worth more than an hour of one-way status reporting. Put the plan on a screen everyone can see, walk the coming weeks zone by zone, and let the field talk. The mobile companion app matters here for the crew leader who can't make the trailer meeting — he sees the same plan on his phone and can commit or push back from wherever he's standing.
Making the commitment stick
Finally, all of this is theater if the commitments don't hold. The value of a crew leader saying "I'll have the north wall roughed by Wednesday" comes entirely from him treating that as a promise, protecting his crew's focus, and raising his hand early if it's going sideways rather than going quiet and hoping. Reliable promises from the field are what make the whole short-interval system work; the schedule is just the scoreboard.
The bottom line
A four-week lookahead built in the office and never touched by the field is a guess. The same plan, run past the crew leaders for real durations, live constraints, verified handoffs, honest resource counts, and hard commitments, becomes something you can actually build to. Crew leaders don't need to author the schedule — they need to be pulled into it early and given a fast way to tell you what they see. Give them that channel, take their input seriously, and close the loop on why things missed, and you'll watch your plan reliability climb week over week. That's not software magic. That's just letting the people closest to the work help plan it.