Most crews don't fail at weekly planning because they're lazy or don't care. They fail because nobody ever showed them what a good weekly work plan actually looks like, or how to build one that survives contact with a real jobsite. You can buy the best scheduling software on the market and it won't move the needle if your foremen treat the weekly plan as paperwork they fill out after the fact to keep the office happy.
So if you're the one running the training — a superintendent, a scheduler, a Lean coordinator, whoever got handed the job — this is about how to actually teach it. Not a slide deck full of theory. A working session that sends people back to the field able to plan their own week and mean it.
Start by fixing the mental model, not the software
The first mistake trainers make is opening the laptop and walking through the tool. Screens, buttons, where to click. Do that and you'll spend the whole session teaching software and none of it teaching planning. The foreman learns how to enter a plan he doesn't believe in.
Spend the first thirty minutes with no computer at all. Get across one idea and get it across hard: a weekly work plan is a set of commitments, not a wish list. The difference between "we should get the second floor rough-in going next week" and "Tuesday, Rodriguez's crew starts unit 204 rough-in, and it can start because the framing inspection passed Monday" — that's the entire game. The look-ahead tells you what's coming. The weekly plan is where you decide what you'll actually commit to, because every prerequisite is in place.
Teach them the word constraint early and never let it go. An activity only belongs in the weekly plan if it's clear to run — materials on site, prior work complete, inspection signed off, access available, crew assigned, equipment lined up. If any of those is missing, it's not a plan, it's a hope. Most of your training is really teaching people to spot constraints before they bite.
Send pre-work, but make it real work
Don't waste session time on things people can do at their desk or in the gang box the day before. A day or two out, hand each participant the actual look-ahead for a job they know — ideally their own. Ask them to come with three things written down:
- Two or three activities they think are ready to run next week
- For each one, what has to be true for it to start (the prerequisites)
- One activity that looks ready on paper but they suspect isn't
That last one is the money question. The foreman who can already smell that the "ready" drywall hang is going to get blocked because the electrical inspection hasn't been called — that guy is halfway to being a good planner. The session's job is to make that instinct explicit and repeatable for everyone else in the room.
Structure the session so people plan, not watch
A session that's mostly you talking will not change behavior. Aim for something like a third instruction, two-thirds hands-on. A ninety-minute block that works:
- Frame it (10 min). The commitment vs. wish-list idea, the constraint checklist, one war story of a week that blew up because a prerequisite got skipped.
- Walk one plan together (20 min). Put a real look-ahead on the screen and build next week's plan live, out loud, so they hear the reasoning — "can this start? No, because…"
- They build their own (40 min). Everyone builds a real weekly plan from their real job. You float and coach. This is where the learning happens.
- Pressure-test in pairs (15 min). Each person hands their plan to a neighbor whose only job is to attack it: "How do you know the deck's ready? Did anyone confirm the crane's available Thursday?"
- Debrief (5 min). Collect the constraints people missed. Those become next week's teaching examples.
The peer pressure-test in step four is worth more than anything you'll say from the front of the room. People will accept from a fellow foreman a challenge they'd resent from the superintendent, and they learn to anticipate the question by having to answer it.
Teach the constraint checklist until it's muscle memory
Give them a short, physical checklist they run against every activity before it earns a spot in the week. Keep it to things you can actually answer yes or no:
- Prior work complete and accepted? Not "mostly." Complete, and if it needs an inspection, signed off.
- Materials on site and staged? On a truck three states away doesn't count.
- Access and space clear? Can the crew physically get in and work without tripping over another trade?
- Crew and hours assigned? A named crew and a realistic day count, not "when we get to it."
- Equipment and tools available? The lift, the crane window, the specialty tool that's shared across three areas.
- Info in hand? Approved shop drawings, the RFI answered, the layout confirmed.
Drill this with bad examples on purpose. Put up an activity that looks fine and let them find the hole. "Install rooftop units — crew's assigned, RTUs delivered." Great. Who confirmed the crane and the street closure permit for the pick? Nobody. That activity is a constraint waiting to become a schedule slip. When they start catching those themselves, you're winning.
Use real jobs, real failures — including your own
Case studies from a textbook land flat. What lands is a story from a job everyone in the room knows. Bring the week the tile went in before the plumbing inspection and had to come back out. The Friday the concrete showed up with no pump scheduled. The month three trades all planned to work the same corridor and none of them got a full day.
Be willing to use your own screw-ups. A superintendent who stands up and says "here's a week I planned that fell apart, and here's the constraint I should have caught" earns more credibility than any polished success story. It also tells the room that missing a constraint is a normal, fixable mistake — not something to hide, which is exactly the culture you want around a weekly plan.
Teach the follow-through, because a plan you don't measure is a suggestion
Building the plan is only half of it. The other half — the part most training skips — is checking at the end of the week what you actually completed versus what you committed to, and asking why the misses happened. In Last Planner terms this is your percent-plan-complete, but you don't need the jargon to teach it. You need the habit.
Train people to run a two-minute post-mortem every Friday: which commitments did we make good on, which didn't happen, and what got in the way. The reasons are the gold. If "waiting on inspection" shows up three weeks running, that's not bad luck, that's a scheduling problem you can fix upstream. The point of tracking completion isn't to grade the foreman — make that clear or you'll get gamed plans full of easy wins. The point is to find the recurring constraints so the whole operation gets tighter. A crew that hits 55% one month and 80% two months later has genuinely gotten better at planning, and you can show them the number to prove it.
Then, and only then, bring in the software
Once people understand the thinking, the tool becomes obvious instead of intimidating. Now when you show them how to pull activities from the look-ahead into a weekly plan, flag constraints, assign crews to locations, and share the plan out to the subs, they see it as leverage — it's doing the bookkeeping so they can spend their attention on the judgment calls. This is where a purpose-built tool like LookAheadWall pays off: a visual, location-based weekly plan that ties back to the trade-flow sequence means a foreman can see at a glance where his crew collides with another, and the crew leaders get the current plan on their phones instead of a printout that's a week stale.
But keep the order straight. Teach the discipline first, the buttons second. A foreman who understands commitments and constraints will use any tool well. A foreman who only learned the clicks will produce a beautiful, well-formatted plan that's still just a wish list.
Make it stick after everyone goes home
One session doesn't build a habit. Plan the reinforcement before the training even happens:
- Same-week application. Everyone leaves the session and builds next week's real plan within 48 hours, while it's fresh. No homework, no delay.
- Ride along on the first live weekly meeting. Sit in, don't take over. Nudge when someone commits to work with an open constraint.
- Short refreshers, not a repeat. Fifteen minutes at a foremen's meeting a month later, built entirely around the misses people actually hit. Real problems from your job beat any generic curriculum.
- Grow facilitators. Your best planners should start running the weekly meetings and coaching the newer foremen. That's how the practice outlives you and doesn't collapse the week you're on vacation.
Done right, this training changes something you can feel on site. The weekly meeting gets shorter and sharper. Fewer crews show up Monday to find they can't start. The subs stop hedging because the plan they're handed actually holds. That's the whole return — not that people learned a scheduling app, but that they learned to make commitments they can keep, and to catch the constraints that used to catch them.