The best four-week look-ahead I ever ran wasn't built by me. It was built by seven crew leaders standing around a plotter print on a folding table, arguing about whether the north stair could be poured before the elevator pit was signed off. I mostly held the marker. That's the part nobody tells you when you get handed the schedule: the superintendent's job isn't to know how long every task takes. It's to know who does know, and to get it out of their heads and onto the wall before the work hits.
Crew leaders and foremen are the richest source of scheduling truth on the job, and most of that truth never makes it into the plan. This is about how to change that — what to actually ask them, what they see that you don't, and how to fold their input into a look-ahead that holds up.
Why the office schedule is always a little bit fiction
The baseline CPM schedule that came out of the office is a hypothesis. It was built months ago by someone estimating durations from a spec book, not from the actual crew, the actual access, or the actual weather you're staring at this Monday. It's not wrong on purpose — it just can't see the field.
The crew leader sees the field. He knows the drywall hangers on this job are a hair slower than the estimate assumes because the ceilings are 14 feet and half the work is off a rolling scaffold. He knows the mason won't touch the south elevation before 9 a.m. because that's when the sun clears the frost off the block. Those are the details that turn a plausible schedule into an achievable one, and the four-week look-ahead is exactly the horizon where you can still do something about them.
Durations: ask for the real number, not the brave number
When you ask a foreman how long something takes, you'll get one of three answers: the number he thinks you want to hear, the number that protects him if it goes long, or the real number. Your job is to get the third one.
The way to get it is to ask in production terms, not calendar terms. Don't ask "how long to frame level three?" Ask "how many crew, how many walls a day?" A foreman will lowball a duration to look good but he'll almost never lie about his own production rate, because that's his craft and he's proud of it. Do the multiplication yourself: 42 walls at 6 a day with a crew of four is seven days, not the five that's on the bar chart.
Then pressure-test it against what you've actually seen. If your look-ahead tool holds a history of planned-versus-actual, use it — a crew that has finished the last three floors two days late every time is going to finish this one late too, and no amount of optimism in the meeting changes that. Good short-interval scheduling software makes that comparison visible instead of relying on your memory. But the number still starts with the person doing the work.
Constraints: the stuff that kills you is the stuff you can't see from the trailer
This is where crew leaders earn their weight. The office schedule links Activity B to Activity A. The foreman knows that Activity B also needs a 200-amp temporary feed that isn't hooked up yet, a lift that's currently on the other side of the building, and a hole in the deck that the concrete crew was supposed to leave and didn't.
Every week, walk the next four weeks of work with the relevant leads and force the question: what will stop you from starting this on the day it's scheduled? Make them name it. The categories that come up over and over:
- Prerequisite work — the wall has to be closed before I can trim it, and it isn't.
- Access and space — I can't run pipe in that corridor while the drywall boom is parked in it.
- Material lead time — the fixtures are an 8-week order and nobody's placed it.
- Information — there's an open RFI on that detail and I'm not building it twice.
- Equipment — one lift, three trades that all need it Tuesday.
- Inspection and sign-off — I can't cover this until the rough-in is signed.
A task with an open constraint doesn't belong on the "ready to work" list, no matter how much the CPM wants it there. The whole point of pulling planning out to four weeks is that you have time to knock those constraints down before the crew shows up to a task they can't actually start. A constraint found four weeks out is a phone call. The same constraint found the morning of is a crew standing around getting paid to do nothing.
Sequence and trade flow: let the guys downstream draw the lines
Predecessors on paper and predecessors in the field don't always match. The schedule might show "MEP rough-in" as one bar, but the plumber, the electrician, and the sheet-metal crew all have opinions about who goes first, and those opinions come from twenty years of stepping on each other.
The rule most crews will tell you if you ask: overhead before walls, and biggest pipe first. Sanitary and storm want the gravity slope so they claim the ceiling space first; then the larger ductwork; then the conduit and the smaller lines that can bend around what's already up there. Get that pecking order wrong and you'll watch the electrician pull his conduit twice because the plumber needed the same six inches of plenum.
Have the crew leaders literally sequence the work with you — location by location, not just trade by trade. Location-based look-ahead planning, where you plan by area and let the trades flow through it in order, catches the collisions that a trade-by-trade Gantt chart hides. When you can see that framing, MEP, and finishes are all pointed at the same room in the same week, you've found next Thursday's argument today. Tools built for weekly work plans and trade-flow sequencing — LookAheadWall among them — exist mostly to make that flow visible, but the sequence itself has to come from the people who've had to unbuild each other's work before.
Build in the buffers the crews already know about
Foremen carry a mental library of the gaps between activities, and a schedule that ignores those gaps is a schedule that's already behind. A few that come up constantly:
- Frame to rough-in usually wants a 1–2 day buffer for cleanup, layout, and the framing inspection — you don't start pulling wire the same hour the last stud goes in.
- Rough-in to cover lives and dies on inspection scheduling. If your jurisdiction is running a two-day lag on inspection requests, that lag belongs in the look-ahead, not in your prayers.
- Concrete and mud need cure and dry time that no crew can compress. Slab has to be dry enough for flooring; you don't schedule the tile the day after the pour and call it a plan.
- Weather-sensitive work — pours, roofing, exterior paint, waterproofing — should carry crew-leader-flagged float in the shoulder seasons. The mason knows he loses mornings to frost; put those lost mornings in the plan instead of acting surprised.
When a crew leader says "give me a day between those," he's not padding. He's telling you about a handoff that fails every time it gets squeezed. Believe him the first time and you won't have to learn it the hard way.
Run the conversation like a commitment, not a status report
The mechanics matter as much as the questions. A four-week look-ahead review is not you reading the schedule at the crew leaders. It's them making commitments to each other, out loud, in the same room. That shift is the entire idea behind pulling the field into planning: the plumber commits to being out of corridor C by Wednesday so the drywall crew can start Thursday, and now that handoff has two names on it instead of a dotted line on a chart.
A few things that keep those meetings honest:
- Keep it short and standing. Twenty to thirty minutes at the wall, once a week. The moment it turns into an hour-long sit-down, the foremen check out and you've lost them.
- Make them read their own work back. If a lead can't tell you what he's doing in week two and what he needs to be ready, that task isn't planned — it's just a hope with a date on it.
- Close the loop on last week. What did we say we'd finish, and did we? Tracking that completion rate — the percent of planned work actually completed — is the single best early warning you have. When it slides, your plan is drifting from reality, and the crew leaders will tell you why if you ask.
- Give them a way to update from the field. A foreman who can flag a slip or a cleared constraint from his phone through the day keeps the plan alive between meetings. A companion mobile view for crew leaders is worth more than any office feature, because the update happens where the work is.
What the crew leader gets out of it
There's a fair question buried in all this: why should a foreman spend his Monday morning feeding your schedule? The honest answer is that a good look-ahead protects his crew. It means his guys show up to work that's actually ready, with the material staged and the area clear, instead of burning the morning waiting on somebody else. Foremen hate few things more than sending skilled hands home early because the task in front of them wasn't ready. A plan they helped build is a plan that respects their time.
And the leaders who get good at this get noticed. The foreman who can look four weeks out, name his constraints, and make a commitment stick is the one who ends up running bigger scopes and, eventually, the whole job. Planning is a superintendent skill, and the look-ahead is where you learn it in public.
The short version
Your four-week look-ahead is only as good as the field knowledge inside it, and that knowledge lives in your crew leaders' heads. Get the real production rates, not the brave ones. Force the constraint question every single week. Let the trades sequence their own flow location by location. Build in the handoff buffers the crews already know about. And run the review as a set of commitments people make to each other, not a report you deliver. The software — LookAheadWall or whatever you run — is just the wall you all draw on. The plan itself is a conversation, and the crew leaders are the ones who actually know what's true.