Software doesn't run the Last Planner System. People do. The tool just holds the plan, keeps everyone looking at the same picture, and remembers what got promised last week so nobody can pretend they didn't say it. I've watched crews run a beautiful pull plan on butcher paper and Post-its and hit 85% reliability, and I've watched teams with a five-figure software subscription hit 55% because they treated the software like a filing cabinet instead of a planning discipline. The practices below are what separate the two. None of them are about which buttons to click.
Get the Plan on a Wall Everyone Actually Looks At
The Last Planner System is a wall-planning method before it's a software feature. The whole point is that the schedule is visible, shared, and argued over by the people doing the work — not buried in a Gantt chart only the PM opens. So the first practice is dead simple: the plan has to live somewhere the crew leaders see it every day.
Whether that's a big monitor in the trailer, a projected screen in the weekly meeting, or the app open on every foreman's phone, the schedule stops being real the moment it's out of sight. If your make-ready and weekly work plan live in a file nobody opens between Monday meetings, you've built a calendar, not a planning system. Good look-ahead scheduling software earns its keep here by putting the same live plan in front of the trailer, the field, and the office at once — but only if you insist people use it. Pick one source of truth and kill the shadow spreadsheets, or you'll spend every meeting reconciling three versions of the truth.
Plan Backward From What "Done" Looks Like
The strongest thing the Last Planner System does, and the thing teams get wrong most often, is pull planning — building the sequence backward from a milestone instead of forward from today. When you plan forward, everybody protects their own float and the handoffs get sloppy. When you plan backward from "drywall ready to hang," the electrician, plumber, and HVAC foreman have to negotiate who's in the wall in what order, and the software just records the sequence they agree on.
A practical rule: run your pull planning session at the phase level — say, the interior rough-in phase — and let the trades define the handoffs, not the scheduler. Your job is to capture their trade flow, not invent it. The classic gotcha is the overhead-MEP dance above the ceiling. If you don't force the sequence conversation, you get plumber, then electrician, then HVAC discovering the main duct run is exactly where the sprinkler main already went. Frame-to-rough-in usually wants a one-to-two-day buffer built into the flow anyway — for cleanup, layout, and the framing inspection to clear before the trades start drilling holes in it. Bake those buffers into the connected sequence so they travel with the plan.
Make-Ready Is the Whole Ballgame — Work It Six Weeks Out
Here's the part most teams underuse. The weekly work plan gets all the attention, but the make-ready process — the look-ahead where you screen work for constraints and clear them before the work is due — is where reliability is actually won or lost. Work that isn't ready doesn't belong on the weekly plan, full stop.
Run a rolling look-ahead, six weeks is a good window for commercial and multi-family, and screen every activity against the standard constraint categories before it can advance:
- Prerequisite work — is the predecessor actually complete, not "90% done"?
- Design/RFI — is the detail resolved, or is there an open RFI that could change it?
- Submittals & approvals — approved shop drawings in hand?
- Materials — on site or with a confirmed delivery date inside your window? Long-lead items get flagged months out, not weeks.
- Labor & equipment — right crew size, right lift, right access?
- Permits & inspections — is the inspection scheduled, or are you assuming it?
Every constraint needs a name and a date — one owner, one due date, tracked to closure. "The team is handling it" is not an owner. The single highest-value habit I can give you: pull the constraint log every single day, not just at the weekly meeting. Constraints that surface Monday and aren't chased until the next Monday are how a six-week runway collapses into a Friday fire drill. Software helps here because it can flag which upcoming activities still carry open constraints and roll them forward automatically, so nothing quietly ages past its due date.
Only Promise Work That's Ready — and Make the Promise Voluntary
The weekly work plan should contain only activities that have cleared make-ready. That's the discipline. If it isn't ready, it stays in the look-ahead, not on this week's commitment list. The temptation to shove unready work onto the plan because "we're behind" is exactly what destroys your reliability numbers — you're just scheduling a broken promise in advance.
And the commitment has to come from the person doing the work. The difference between "I'm assigning you the east stair rail this week" and "Can you commit to the east stair rail by Thursday?" is the difference between a schedule and a to-do list. When the foreman makes the promise out loud, in front of peers, with the resources to keep it, you get a reliable commitment. Keep them specific and time-bound — "grid line 4 to 8, done Wednesday," not "keep working on the east side." Vague promises can't fail cleanly, which means you can't learn from them.
Track PPC Honestly — the Number Is Useless If You Fudge It
Percent Plan Complete is the heartbeat metric: of the tasks you promised this week, what fraction finished as committed? It's binary — 100% done or it didn't count. No partial credit, no "basically done." The instant a crew starts rounding up to protect their numbers, the metric is worthless and you've lost your early-warning system.
A healthy team lands in the 70–85% range. If you're consistently above 90%, you're not planning aggressively enough — you're sandbagging. If you're stuck below 60%, either make-ready is broken or people are committing to work they can't control. But the PPC number itself is not the prize. The prize is the second question: for every task that missed, why? Log a reason — prerequisite late, material short, RFI open, weather, crew pulled, changed scope — and let those reasons pile up over a few weeks. The pattern that emerges is your project's actual disease. Chase the reasons, and PPC follows. The software's job is to make that reason-tracking one click instead of a spreadsheet chore, because a variance analysis nobody fills out teaches nobody anything.
Get the Right Subs in the Room — With Authority to Commit
The plan is only as good as the people making the promises. That means the foreman who actually runs the crew, not the sub's PM phoning in from another job, and not an estimator who's never set foot on site. The person in the room has to be able to say "yes, Thursday" and mean it.
Bring trades in from the start of the phase, not once you're already behind and looking for someone to blame. And be honest that the system asks something of them — they have to plan and expose their commitments in front of everyone. What you give back is a jobsite where they're not standing around waiting on a predecessor that's three days late, where their material is staged when they arrive, and where they get paid for the work they mobilized to do. That's the trade you're offering: predictability for transparency. Make it worth their while and they'll show up prepared. Treat the meeting as a beating and they'll send the new guy.
Keep the Meetings Short, and Split Look-Ahead From Weekly
Two different conversations, two different rhythms. The weekly work planning meeting reviews last week's PPC and variances, then locks this week's commitments — keep it tight and facilitated, not a war-story session. The look-ahead / make-ready review is a separate working session focused entirely on the next few weeks: what's coming, what's in the way, who's clearing it. Jamming both into one meeting means the near-term firefighting always eats the make-ready time, and make-ready is what keeps you out of the fire.
Then there's the daily huddle — ten, fifteen minutes at the gang box, standing up, no chairs, no laptops. What are we doing today, what's in your way, who do you need to talk to. Same time, same spot, every morning. The daily huddle is where a two-day-old constraint gets caught before it eats the week, which only works if yesterday's plan is already in everyone's pocket. That's where a mobile companion app for crew leaders actually pays off — the foreman checks the day's committed work on their phone at the gang box instead of walking to the trailer to read a printout that's already stale.
Facilitate Like a Referee, Not a Boss
Whoever runs the planning session guides the conversation; they don't dictate the plan. The moment the superintendent starts assigning durations and sequences from the front of the room, the trades stop owning their commitments and you're back to a push schedule with extra steps. Draw out the quiet foreman who's about to get steamrolled. Park the rabbit-hole argument and move on. End on time — a meeting that runs long trains everyone to dread the next one. The facilitator's real job is to make it safe to say "no, I can't commit to that," because an honest no this week is worth ten optimistic yeses that blow up on Friday.
Roll It Out Small, Then Make It the Standard
Don't flip the whole company to a new system overnight. Pick one project, ideally one with a superintendent who's actually bought in, and run it as a pilot. Give it a champion whose job is to keep the discipline alive when the novelty wears off in week three. Train everyone who'll touch the plan, including the subs, and keep the tool simple enough that a foreman with muddy boots and reading glasses can update it on a phone. Complexity is the quiet killer here — the fanciest software on earth is worthless if the field won't touch it.
Once the pilot proves out, institutionalize it. Same expectations on every job, the practice baked into how you run work, more than one person who can carry it. The goal is a culture where planning the week and clearing constraints is just how the job runs, not a program that fades when the champion moves on.
The Short Version
The best practice underneath all the others: use the software to enforce a discipline, not to decorate a schedule. Plan backward from milestones. Screen work for constraints weeks before it's due and clear them daily. Only commit to work that's ready. Let the people doing the work make the promises. Measure whether the promises held, and when they don't, dig into why — every single time. A tool like LookAheadWall makes the location-based weekly plan visible in the field and keeps the trade-flow sequence and constraints connected, but the reliability comes from you working the process honestly, week after week, until it's just how the crew thinks. Get that right and the software is a force multiplier. Skip it and the software is a very expensive place to store your excuses.