The first Last Planner meeting I ever ran was a disaster. I had the software up on the big screen, I had all the foremen in the trailer, and I proceeded to spend forty minutes telling them what their schedule was going to be. At the end I asked, "Any questions?" Silence. I thought that meant they agreed. What it actually meant was that they'd checked out around minute five and were waiting for the free lunch. Two weeks later almost nothing on that plan had happened the way I drew it up.
That's the lesson that took me years to fully absorb: the Last Planner System doesn't fail on the software, and it rarely fails on the concept. It fails on the facilitation. A pull plan or a weekly work plan is only as good as the conversation that produced it, and that conversation lives or dies on the person running the room. This is a guide to being that person — not the theory of the method, but the actual craft of standing at the front of the trailer and pulling a reliable plan out of a group of tired, skeptical tradespeople.
Your Job Is to Facilitate, Not to Dictate
The single biggest mental shift for a new facilitator is this: you are not the smartest person in the room about how the work gets built. The plumbing foreman knows more about his rough-in than you ever will. The electrician knows what he needs from the framer before he can pull wire. Your job isn't to have the answers — it's to make the people who do have the answers talk to each other and commit out loud.
A good facilitator says almost nothing declarative. You ask, you reflect, you write down what you hear, and you make the group resolve its own conflicts. If you find yourself narrating the plan, stop. The moment the last planners — the foremen and crew leads who actually make work-ready assignments — stop owning the plan is the moment your Percent Plan Complete starts falling.
Practically, that means you talk maybe twenty percent of the time. The rest is prompting: "Mike, what has to be done before you can start that wall?" "Does everybody agree that's a two-day duration, or is somebody padding?" "Who's making that promise, and when will it be ready?"
Make the Room Safe Enough to Tell the Truth
Reliable promising only happens when people aren't afraid to say no. If a foreman thinks he'll get chewed out for admitting he can't hit a date, he'll nod along and then miss it quietly — which is far more expensive than an honest "I can't get there until Thursday" said out loud in the meeting.
You build that safety deliberately. When someone raises a constraint that blows up your nice-looking schedule, thank them for it — genuinely — because they just saved you a failed week. When a task didn't get done last week, the question is never "whose fault is it," it's "what got in the way, and what do we change so it doesn't happen again." The first time you let a variance review turn into a blame session, you've taught everyone in that trailer to stop being honest with you, and you won't get it back easily.
A few concrete habits that build trust fast:
- Start on time and end on time, every single week. Respecting their hours is the most basic form of respect there is.
- Never let one loud trade run over a quieter one. Directly invite the crew that hasn't spoken.
- When you're wrong, say so in front of everyone. It gives them permission to be honest too.
- Keep the wall or the screen visible and shared. It's the group's plan, not your presentation.
Run the Cadence: Pull Plan, Look-Ahead, Weekly Work Plan
Facilitation gets a lot easier when you're clear about which conversation you're running, because the three core sessions have different jobs.
The phase pull plan is the big one — you work backward from a milestone (say, "drywall complete on level 3") and have each trade state what it hands off and what it needs to receive. This is where you catch sequencing problems weeks before they'd bite you. Facilitate it by physically moving through the handoffs, one trade to the next, and forcing the "what do you need from the person before you" question at every link. That linked chain of handoffs is exactly the trade-flow logic that a look-ahead tool like LookAheadWall is built to hold, so the sequence you pull on the wall doesn't evaporate when the sticky notes come down.
The look-ahead — usually a rolling three-to-six-week window — is where you do the real work of making tasks ready. Every task in that window gets screened against constraints: is the design released, are the materials on site, is the prerequisite work done, is the manpower there, is the area accessible and safe? A task with an open constraint does not belong in a weekly commitment. Your job in the look-ahead is to be relentless about surfacing those constraints early and assigning an owner and a date to clear each one.
The weekly work plan is where commitments get made. Only tasks that survived constraint screening — genuinely ready work — get promised here. This is the shortest, most focused meeting of the three, and the one most likely to drift into war stories. Keep it tight.
Screen Constraints Before You Screen for Volunteers
The most common rookie mistake is letting a trade commit to work that isn't actually ready. It feels productive in the room — everybody's making promises — but you're just manufacturing next week's failure. A useful discipline: nothing moves from the look-ahead into a weekly commitment until every constraint against it is closed. If the shop drawings aren't approved, that task stays parked no matter how much everyone wants to start.
Train yourself to run the same short checklist on every candidate task: information/design, materials, prerequisite work, manpower, equipment, and site/area readiness. If any one of those is open, it's not a commitment, it's a wish. Say so, assign someone to knock the constraint down, and move on.
Get Real Commitments, Not Polite Nods
A reliable promise has four parts, and your job is to make sure all four show up: someone specific requesting the work, someone specific performing it, a clear definition of "done," and a real completion time. "We'll try to get to the west wing this week" is not a commitment — it's a hope with a nice hat on. Push gently but firmly: "So can you commit that the west wing rough-in is complete and ready for inspection by Wednesday end of day?" Make them say yes or no.
And here's the part people forget: honor the no. If a foreman says he can't commit because he's short two guys, don't guilt him into a yes. A declined promise you can plan around beats an accepted promise that fails. Capture what he can do, note the constraint, and let the group re-sequence around it right there.
Handle Conflict on the Spot
Two trades want the same area on the same day. It happens every week. The wrong move is to make the call yourself from the front of the room — you'll be wrong half the time and you'll teach both trades to lobby you privately instead of solving it in the open. The right move is to name the conflict plainly, put it back to the two foremen, and let them negotiate the handoff while the rest of the room watches. "Okay, you both need the mechanical room Tuesday. You two work it out — who goes first, and what does the second guy need to see finished before he walks in?"
Ninety percent of the time they solve it faster and better than you would have, because they know the actual work. Your role is to keep it constructive, make sure the resolution is a real commitment and not a vague truce, and write it down so it's not re-litigated next week.
Facilitate the Variance Review Like a Learning Session
Every week you measure Percent Plan Complete — the fraction of last week's promises that actually got done — and you review the misses. This is the engine of the whole system, and it's the meeting most facilitators quietly ruin by letting it feel like an inquisition.
Track the reasons for the misses, not just the count. Over a month, patterns jump out: if half your variances trace back to "prerequisite work not complete," you have a sequencing or handoff problem. If they trace to "materials not on site," you have a procurement problem. If they trace to "changed priorities," your look-ahead screening is too loose and you're committing work that was never ready. The number tells you that you have a problem; the reason codes tell you where to fix it. A facilitator who runs a clean variance review turns every missed task into next week's improvement instead of this week's argument.
Coach the Room Over Time
You won't get reliable promising in week one. Early on, people commit to whatever they think you want to hear, durations are guesses, and constraints get discovered on Wednesday instead of the week before. That's normal. Your longer job is to coach the last planners into better planners — praising the foreman who declines a bad commitment for the right reasons, quietly showing a crew lead how to break a vague task into work-ready assignments, celebrating an honest miss that surfaced a real systemic problem.
Good software helps here in a way that's easy to underrate: when the look-ahead, the trade-flow sequence, and last week's commitments all live in one shared, visual plan instead of on a whiteboard that gets erased, the group can actually see its own patterns. That's the practical value of a purpose-built look-ahead scheduling app — it makes the reliability data and the handoff logic durable enough to learn from, meeting after meeting.
The Facilitator Sets the Ceiling
After twenty years I've watched the same crews go from cynical to genuinely bought-in, and the variable is almost never the tool or the trade — it's whether the person running the room asks instead of tells, makes it safe to say no, screens constraints ruthlessly, and treats every miss as a lesson instead of a crime. Get those right and the plan starts to hold. Get them wrong and the fanciest scheduling system on the market just gives you a prettier picture of work that isn't going to happen. The software is the wall. You're the reason the plan on it is true.