Teaching someone to build a look-ahead is the easy part. You sit them down, walk them through a three-week plan, show them how the trades hand off, and they nod along. Everybody nods along. The hard part is finding out whether they actually absorbed it or whether they just watched you do it and can now describe the process without being able to run it themselves. Those are very different things, and the gap between them shows up on the jobsite at the worst possible moment.
I've handed off scheduling duty to plenty of foremen and young project engineers over the years. The ones who blew up on me weren't the ones who couldn't answer questions in the trailer. They were the ones who could answer every question and still couldn't sequence drywall behind a rough-in that wasn't signed off yet. Knowing the words isn't the same as being able to do the work. So if you're going to train people to build and maintain look-aheads, you need a real way to check whether it stuck. This is how I do it.
Separate what they know from what they can do
The first mistake people make with training assessment is testing recall when they should be testing capability. A written quiz that asks "what is the purpose of a three-week look-ahead?" tells you almost nothing. Anyone who's been on a job for six months can recite that a look-ahead breaks the master schedule down into what's actually about to happen and gets the trades talking about it before the work hits the field.
Split your assessment into two lanes and grade them separately. The first lane is understanding: does the person grasp why we plan the way we do? The second, and the one that actually matters, is execution: can they sit down in front of a blank plan and produce something a crew could build from tomorrow? You want both, but if you only have time to test one, test execution. A foreman who can build a clean weekly work plan but is fuzzy on the theory will be fine. A foreman who aces the theory but can't produce a usable plan is going to hurt you.
What "understanding" actually looks like
When I'm checking whether someone understands the concepts, I'm not looking for definitions. I'm looking for judgment. Ask questions that only have a right answer if the person understands the reasoning, not the vocabulary. A few I come back to:
- "Framing on level three finishes Thursday. Why wouldn't I schedule MEP rough-in to start Friday?" (Good answer: inspection and any framing corrections need to clear first, and you usually want a buffer for punch and cleanup. A one- or two-day gap between framing complete and rough-in start is normal, not lost time.)
- "The GC's master schedule says drywall starts the 14th. My look-ahead says the 18th. Which one is wrong?" (Good answer: neither is automatically wrong — the look-ahead reflects field reality and the master reflects contract intent. The point of the look-ahead is to surface that four-day drift now, while there's still time to react, instead of discovering it when the drywall crew shows up to a wall that isn't ready.)
- "Why do we only commit to work in the near term and leave the back weeks looser?" (Good answer: constraints resolve as you get closer. Committing hard to work three weeks out is how you make promises you can't keep. The plan rolls forward and firms up as reality comes into focus.)
Notice these aren't trivia. Someone can memorize that a look-ahead is "rolling" and still not understand that the whole reason it rolls is because certainty increases as you approach the work. If they get the reasoning, they'll make good calls in situations you never trained them for. If they only got the label, they'll freeze the first time the field doesn't match the textbook.
The practical test: build one from scratch
This is the core of any honest assessment. Give the trainee a realistic slice of a real project — a set of drawings or a section of the master schedule, a list of the trades involved, and whatever constraints you'd normally be dealing with (a late material delivery, an inspection that hasn't been scheduled, a sub who's short-handed). Then have them build a three-week look-ahead from it, start to finish, while you watch.
Watching matters. Don't just grade the finished plan — grade how they got there. The finished plan can look fine and still have been built by luck. What you're looking for as they work:
- Do they sequence by trade flow, or do they just list tasks? A real plan reads as a chain of handoffs — layout, then framing, then top-out inspection, then rough-in, then insulation, then board. If they're dropping activities on days without thinking about who has to finish before the next crew can start, they've missed the entire point.
- Do they build in buffers, or do they schedule everything nose-to-tail? A plan with zero slack between trades is a plan that fails the first time anything slips, and something always slips. I want to see them leave a day here and there for inspection, cleanup, and the inevitable "we found something in the wall."
- Do they catch the constraints you planted? If you told them the light fixtures are six weeks out and they cheerfully schedule the electricians to trim out in week two, that's a fail — not because the plan looks bad, but because they didn't check whether the work could actually be done.
- Is the plan legible to a crew leader? A look-ahead nobody can read is decoration. Can a foreman glance at it and know where his people are Monday morning?
A location-based tool like LookAheadWall makes this part easier to grade, because the trade-flow connections are visual — you can see at a glance whether the handoffs are wired up correctly or whether someone just stacked bars on a calendar. But the skill you're testing exists independent of any software. If they can't sequence it on a whiteboard, they can't sequence it in an app either. The tool speeds up a competent planner; it doesn't create one.
Watch them run a real meeting
Building a plan alone at a desk and defending it in front of the trades are two different skills, and the second one is where a lot of otherwise-capable people fall apart. The best way to assess this is to let them run an actual weekly coordination meeting — or at minimum a realistic role-play where a couple of you play difficult subs.
What you're watching for: Do they get commitments, or do they just read the schedule out loud? A weak facilitator narrates the plan. A strong one goes around the room and makes each trade say what they're going to get done and confirm nothing's blocking them. Do they surface constraints instead of papering over them? When the plumber says he's waiting on a fitting, does the trainee log it and chase it, or nod and move on? Can they hold the line when a sub tries to commit to work that clearly isn't ready? That last one takes a spine, and you can't teach it in a classroom — you can only watch for it.
Set competency levels so "passing" means something
"Did they pass?" is the wrong question. People are at different places, and you want to know where. I use three bands:
- Assisted. Can maintain an existing look-ahead — update progress, slide dates, mark completions — but needs help building one from a blank sheet or handling a curveball. Fine for a green PE. Not someone you leave alone on a fast job.
- Independent. Can build a plan from scratch, sequence the trades correctly, catch obvious constraints, and run a routine coordination meeting without you in the room. This is the bar for a foreman owning their own area.
- Coaching-level. Does all of the above and can teach it, spot a bad plan across the trailer, and untangle a sequence that's gone sideways mid-job. This is who you want running the look-ahead process across a multi-building site.
Write down what each level requires before you assess anyone, so you're grading against a standard instead of a gut feeling. And be honest about the band — promoting an "assisted" planner to run a job solo because you're short-handed is a decision you'll pay for in missed handoffs and angry subs.
When someone comes up short, be specific
A failed assessment that produces "needs more work" is useless. The value of testing capability instead of recall is that the gaps are specific and fixable. Someone who sequences well but schedules everything with no buffer needs one targeted conversation about slack, not a whole retraining. Someone who builds a clean plan but can't hold a room during coordination needs reps in front of the trades with you standing behind them, not another exercise at a desk.
Match the fix to the gap. Sequencing problems get solved by building more plans and reviewing the trade flow every time. Meeting-facilitation problems get solved by facilitating, with feedback, until they stop reading the schedule and start driving it. Constraint-blindness gets solved by making them walk the job and physically verify that the work they're about to schedule can actually be done. The whole reason you assessed the way you did is so you know exactly which of these to prescribe.
Keep a record, and re-check
Note where each person landed and what they need to work on. It doesn't have to be formal — a line in your own notes is plenty on most jobs. But it matters, because competency isn't permanent. A foreman who was independent on a straightforward tenant improvement may be back to "assisted" the first time you put them on a complex phased job with six trades stacked in the same area. Re-check when the difficulty jumps, and re-check anyone who's been off the scheduling process for a while.
The point of all this isn't to build a bureaucracy around training. It's to make sure that when you hand someone the look-ahead and walk away, the plan keeps getting built right and the trades keep getting coordinated — because you actually verified they could do the work, not just talk about it. That verification is the difference between delegating and gambling.