You can hand a new engineer the cleanest three-week lookahead in the world and they'll still stare at it like it's a bus schedule in a language they don't speak. Reading a lookahead, building one, and running the meeting off of it are three different skills, and none of them get learned in a classroom. They get learned by doing the thing badly a few times where it doesn't cost you a pour.
So that's what this is: a set of exercises I've used to bring assistant supers, project engineers, and green foremen up to speed. Run them in order. Each one builds on the last, and each one maps to something they'll do for real in about a week. You don't need a live job to practice on — an old schedule, a set of drawings, and a whiteboard or a laptop will do. If you want the reps to feel like the real thing, build them in the same tool you plan in so the muscle memory transfers.
Exercise 1: Read a Schedule Cold
Before anyone builds anything, they need to read one without help. Pull a real three-week lookahead from a past job — ideally one with a few trades stacked in the same area — and give it to the trainee with no explanation. Their job is to answer, out loud, from the schedule alone:
- What crews are on site each of the next three weeks, and where are they working?
- What has to finish before Trade B can start Activity X? Point to the predecessor.
- Which activities are on the critical path this window, and which have float to burn?
- Where do two trades overlap in the same location, and is that a conflict or a handoff?
The point isn't speed. It's teaching their eye to see sequence and location instead of a wall of bars. Nine times out of ten a rookie reads the schedule left to right like a book and completely misses that the drywall crew and the overhead MEP crew are both booked in Corridor 2 the same day. When they catch that on their own, they've learned the single most useful thing a lookahead does — it makes trade collisions visible before they happen on the floor.
Exercise 2: Break a Master Schedule Down to Work
Master schedules lie to you at the level of detail they're written. "Level 3 Interiors — 4 weeks" is not a plan a foreman can execute. Give the trainee one fat summary bar from a CPM schedule and have them break it into activities small enough that a specific crew could show up Monday and know exactly what to do.
The rule of thumb I teach: an activity in a weekly work plan should be one crew, one location, and one to five days of work. If it's longer than a week or it spans multiple areas, it's still a summary — keep chopping. "Rough-in Level 3" becomes "Wall rough-in, Rooms 301–308," "Overhead rough-in, east corridor," "Set panel and pull feeders," and so on. Have them do it for framing, then MEP rough-in, then finishes, and you'll watch the light come on. The skill you're building is granularity — knowing when a task is small enough to actually commit to and measure.
Exercise 3: Find the Constraints
Now hand back their broken-down activities and ask the only question that matters in a lookahead: what would stop each one from starting on time? Every activity gets checked against the standard constraint categories, and they should be able to rattle these off:
- Design — RFI open, detail unresolved, conflicting dimensions
- Materials — long-lead items, submittals not approved, nothing on site
- Prior work — the predecessor trade isn't actually done, or done wrong
- Manpower — the sub can't crew it this week
- Equipment — lift, crane, or hoist time not reserved
- Permits & inspections — no rough-in sign-off, so you can't close the wall
- Access & conditions — area not turned over, temp power/heat not ready
Make them write a constraint on every activity, even the ones that look clean. The lesson buried here is that "no constraint" is a decision, not a default. The activities that blow up your week are almost always the ones nobody flagged because they looked ready. A good drill: have them find the one activity where the constraint is another trade's incomplete work, because that's the constraint people forget to log and the one that stalls the most crews.
Exercise 4: Build a Make-Ready Plan
Finding constraints is easy. Clearing them is the job. For every constraint from Exercise 3, the trainee writes a make-ready line: what has to happen, who owns it, and the date it must be resolved by — which is not the activity start date, it's earlier, with a buffer.
Drill the buffer into them. If wall rough-in needs an inspection before it can proceed, the inspection can't be scheduled for the morning work is supposed to start. Frame-to-rough-in usually wants a day or two of slack for punch, cleanup, and the inspector's actual availability. Long-lead material shows up the week before you need it, not the day of. Teach them to work backward from the activity and plant the make-ready date with room to fail once and recover.
The owner column is where most make-ready plans die. "The schedule" doesn't order the switchgear — a person does. If a make-ready item doesn't have a name next to it, it doesn't have an owner, and it won't get done. Have the trainee read their plan back with names attached and no bare passive verbs allowed.
Exercise 5: Build a Lookahead From Scratch
Now put it together. Give them a scope, a start date, and a set of drawings, and have them build a full three-week lookahead cold — activities, sequence, durations, crews, and constraints all in one shot. This is where the earlier exercises either stuck or didn't.
Watch for the classic rookie mistakes so you can name them in the moment:
- Durations with no crew logic. "Three days" for what crew size? A duration without a headcount is a guess. Make them state the crew and the production rate behind every bar.
- Everything starts Monday. Real work has staggered starts because predecessors finish on different days. A lookahead where twelve activities all start Monday is a wish list, not a plan.
- No location logic. They'll sequence by trade instead of by area. Push them to think in trade flow — one crew moving through Rooms 301 to 308 in order, with the next trade following a room or two behind. That's how work actually moves down a floor, and building the schedule around location instead of trade is what keeps two crews out of the same room.
Building it in a purpose-made planning tool helps here, because a good lookahead app makes the location-and-trade-flow view the default instead of forcing everything into Gantt bars. LookAheadWall was built around exactly this — planning by location so the handoffs between trades are the thing you see first. But the skill is the point; the tool just stops them from fighting the format while they learn it.
Exercise 6: Roll the Schedule Forward a Week
A lookahead is a rolling document, and rolling it is a discipline most people underestimate. Give the trainee last week's schedule plus a sheet of "what actually happened" — some activities finished, some slipped, one got rained out, a sub no-showed — and have them produce this week's version.
They have to mark actual progress honestly, drop the completed work off the back, pull a fresh third week onto the front from the master schedule, and re-baseline the constraints. The hard part, and the part worth coaching, is what to do with the slips. A slipped activity doesn't just move — it shoves its successors, and if the trainee doesn't chase those downstream effects, next week's plan is already wrong. Make them trace one slip all the way through its successors and adjust every affected date. That "ripple" is the whole reason you roll weekly instead of quarterly.
Exercise 7: Coordinate the Trades
Take a lookahead with four or five trades stacked in overlapping areas and have the trainee find every collision and every dependency. Two crews in one room, an inspection that has to land between two trades, a ceiling that can't close until three trades above it sign off — these are the moments a lookahead earns its keep.
Teach them the handoff logic explicitly. The overhead work — duct, pipe, conduit, then the "above-ceiling" inspection — has to sequence and finish before the ceiling grid goes in, which finishes before the drywaller can close hard-lid areas. Get that order wrong on paper and you're tearing out ceiling to chase a missed damper. Have them redraw the sequence so each trade has a clean, inspected surface to work on when they arrive, and no two crews are fighting over the same square footage on the same day. When they can look at a congested corridor and stagger the trades so it flows, they've got the skill that separates a scheduler from a clerk.
Exercise 8: Run the Meeting
The plan is only as good as the commitments you get behind it, and those come out of the weekly planning meeting. Run a mock one. Put the trainee at the front with the lookahead on the screen and have a few people play subs — including one who's evasive and one who over-promises, because you'll get both.
What they're practicing:
- Walking the plan by location and asking each trade to commit to specific work, not nod vaguely.
- Catching the soft "yeah we'll try to get to it" and converting it to a real yes or a logged constraint.
- Confirming that make-ready is actually done before letting an activity stay on the plan — "is your material on site?" beats assuming it is.
- Capturing every commitment and every new constraint in writing before anyone leaves the room.
The lesson is that a planning meeting is a commitment meeting, not a status update. If the trainee walks out with a list of what people reported instead of what they promised, they ran a status meeting and the week will drift. Coach them to slow down and pin each trade to a real answer.
Exercise 9: Analyze What Went Wrong
The last skill closes the loop. Take a completed week where several planned activities didn't finish, and have the trainee compute the percent of commitments completed — how many activities that were promised actually got done — and then dig into the misses.
The number itself matters less than the reasons. For every missed activity, they trace it back to a root cause, and here's the discipline: the root cause is almost never "the sub was slow." It's usually a constraint that wasn't cleared, a predecessor that wasn't really done, a make-ready date with no buffer, or a commitment that was soft in the meeting. Have them sort the misses into those buckets. When the same reason shows up three weeks running — say, inspections consistently landing late — that's not a scheduling problem, it's a process problem, and they've just found the thing worth fixing. That feedback loop is what turns an average planner into one whose weeks actually hold.
Putting It Together
Run these nine in sequence and you take someone from "I can't read this" to "I can build it, roll it, run the meeting, and tell you why last week slipped" in a handful of sessions. Don't rush it. The reading and constraint exercises feel slow and basic, but they're the foundation the later ones stand on — skip them and you get a planner who can draw a pretty schedule and can't tell you why it fell apart.
And keep the reps close to the real thing. Practicing in the same location-based, trade-flow tool your team plans in for real means the skill transfers straight to Monday morning instead of getting relearned on a live job. The exercises build the judgment; the tool just gets out of the way. Either way, the goal is the same — a superintendent who looks three weeks out and sees the collisions coming while there's still time to move a crew.