Every schedule you've ever seen is built on promises. The bar chart in the trailer says drywall finishes Friday because somebody, somewhere, agreed drywall finishes Friday. The trouble is that most of those agreements were never really promises at all. They were guesses dressed up in a Gantt bar, or numbers a PM backed into so the critical path would close, or a foreman nodding in a meeting because it was easier than arguing. Then Friday comes, drywall isn't done, and everybody acts surprised.
The Last Planner System exists to fix exactly that. Strip away the jargon and it comes down to one discipline: the people who will actually do the work make specific commitments they intend to keep, and the crew tracks how often those commitments come true. That last part — Percent Plan Complete, or PPC — is just a batting average for your promises. If your PPC lives around 50%, half of what your team swears they'll finish this week won't happen, and every downstream trade is planning around fiction.
So the real skill isn't running the software or drawing the pull plan. It's making promises that hold. Here's what that actually takes on a jobsite.
What makes a promise reliable
A reliable commitment isn't about the person being trustworthy in some general sense. Your best foreman will blow a commitment he never should have made in the first place. Reliability is a property of how the promise gets made, and it rests on a handful of things being true before anyone says "yes."
The person promising has to understand exactly what they're on the hook for. They have to be capable of doing it — right crew, right skills, enough hours in the week. The conditions have to be clear: the work in front of them is done, the area's accessible, materials are on site, the drawings aren't three RFIs deep in limbo. And the commitment has to be theirs — offered, not extracted. A promise you squeeze out of a sub by staring at him until he caves is not a promise. It's a hostage statement, and it'll fail like one.
Miss any one of those and you don't have a reliable promise. You have a wish with a date on it.
Get specific or don't bother
Vague commitments can't be reliable, because nobody can agree on whether they were kept. "We'll work on the HVAC this week" is not a promise. Worked on it? Sure. Done? Who knows. There's nothing to verify and nothing to learn from.
Compare that to: "Set and connect the VAV boxes in rooms 101 through 108 by Thursday." Now everyone knows the scope, the location, the deadline, and how you'll check it. On Friday you either walk 101–108 and see eight boxes hung and ducted, or you don't. Binary. That's the whole point.
A good weekly work plan commitment answers four questions with no wiggle room:
- Who — the specific crew or trade, not "someone."
- What — the deliverable, scoped tight enough to verify.
- Where — the actual location: level three east, gridlines 4–7, units 210–218.
- When — a day, or end of week. Not "soon," not "early next week."
Location-based tools like LookAheadWall push you toward this naturally, because you're placing work in a specific area on a specific day rather than typing a fuzzy task into a list. But the tool only enforces the format. The specificity has to come from the conversation.
The promising conversation
This is where most weekly plan meetings go wrong, and it's usually the super's fault, not the sub's. If you walk into that meeting and tell each trade what they're going to do, you'll get compliance and no commitment. People don't own numbers you handed them. When it slips — and it will — they'll shrug, because it was never really theirs.
Flip it. Instead of "You need to have the deck poured Wednesday," ask "What can you commit to this week, and what's in your way?" Then shut up and let them answer. Give them room to think. Let them look at their crew size and their material deliveries and tell you what's real. When a foreman says "I can get you three of the four pours, the fourth is waiting on the plumber's underground," that's gold — you just found a constraint two days before it would have bitten you.
And here's the hard part for a lot of supers: when someone gives you a conservative number, take it. If your electrician says he'll only commit to two floors of rough-in this week, resist the urge to push him to three. A kept promise for two beats a broken promise for three every single time, because the broken one takes the drywall crew's plan down with it. You can always pull ahead. You can't un-break a handoff.
Check the conditions before you accept
Half of all broken promises were doomed before the work ever started, because the conditions weren't there. This is what the look-ahead is for. A rolling three- to six-week look-ahead isn't a prettier schedule — it's a machine for surfacing constraints early enough to clear them.
Before you let a task become a committed promise on this week's plan, run it against the usual suspects:
- Predecessor work — is the trade before them actually finished, or "finished except for a punch list they'll get to eventually"?
- Access — can they physically get to the work, or is the lift tied up on the other side of the building?
- Materials — on site, or on a truck that's "supposed to" arrive Tuesday?
- Information — approved drawings, closed RFIs, no open ASIs that would change the scope mid-task.
- Inspections and permits — you don't close a wall that hasn't passed rough inspection, and you don't promise to close it either.
Any task with an open constraint doesn't belong in the weekly commitment. It belongs in the look-ahead as a task to make ready, with a name and a date attached to clearing the blocker. Mixing unready work into your committed plan is the fastest way to tank your PPC and teach your crew that the plan is optional.
Coordinate the handoffs, not just the tasks
Individual promises don't win the job. Handoffs do. The framer's promise to finish a wall only matters if it lines up with what the electrician needs to start his rough-in, which only matters if it clears in time for insulation and inspection before the drywallers show up.
So when you're building the week, look at the seams between trades, not just the trades. A useful rule of thumb: build a small buffer into tight handoffs. Frame-to-rough-in usually wants a day or two of daylight for cleanup, backing, and the framing inspection before the next trade climbs in — jam them back to back and one slip cascades. Underground-to-slab, MEP-rough-to-cover, substrate-to-finish: same idea. The buffer isn't slack you're wasting; it's the shock absorber that keeps one broken promise from becoming five.
This is where seeing the trade-flow sequence visually earns its keep. When you can look at the week and see that the drywall commitment depends on an inspection that depends on a rough-in that's still constrained, you catch the domino before it falls. That's the entire argument for planning location by location instead of trade by trade in isolation.
When a promise breaks — and it will
Nobody hits 100% PPC. The good crews run in the 80s and treat the misses as information, not crimes. How you handle a broken promise determines whether your team keeps making honest ones.
Two things kill a promise culture fast. The first is punishing honest failure — the moment a foreman gets chewed out for a miss he flagged early, he stops flagging. He'll pad every commitment or go quiet, and now you're blind. The second is letting people quietly not-commit, absorbing every task with a shrug and no real intent behind it. Both leave you managing a schedule that describes a jobsite you don't actually have.
So when something slips, run it flat and factual. Acknowledge it plainly. Capture the reason — not "we ran out of time," but the actual root cause: material short, predecessor late, inspection failed, weather, manpower pulled to another area. Those reasons are the most valuable data on the whole project. Track them over a few weeks and patterns jump out. If "waiting on predecessor" shows up in a third of your misses, your problem isn't the trade that missed — it's your make-ready process upstream. If it's always the same sub, that's a capacity or a commitment conversation, not a scheduling one.
Then plan the recovery honestly, and roll the reason into next week's planning. That loop — commit, measure, learn, adjust — is the engine. The software's job here is unglamorous but real: capture the commitment clearly, track it through the week so you see trouble by Wednesday instead of Friday, and log the variance reasons so they're sitting in front of you at the next planning meeting instead of lost to memory.
Calibrating over- and under-promising
Your PPC trend tells you something the raw number doesn't. If a crew is consistently at 95%+ week after week, that sounds great, but it often means they're under-committing — sandbagging, hiding capacity, leaving production on the table because a low bar is a safe bar. If they're stuck in the 50s, they're over-committing, promising more than the conditions or the crew can deliver.
The target isn't 100%. The target is honest, right-sized commitments that stretch the crew a little but stay achievable — and a trend that's climbing as the team gets better at reading their own capacity. A foreman who's blown three commitments in a row to the plumber should be making a smaller promise this week, and both of you should know why.
The habit under all of it
The tooling — the look-ahead, the weekly work plan, the PPC dashboard, the trade-flow view — exists to make this discipline easier to hold when the job gets loud. It won't make the promises for you. What it does is force the specificity, keep the constraints visible, and remember the variances so you're not relying on a legal pad and a good memory in the middle of a 40-trade job.
But the whole system is only as good as the commitments feeding it. Get the promising conversation right — request instead of assign, verify conditions before you accept, take the conservative number, and treat misses as lessons rather than ammunition — and everything downstream starts to firm up. Reliable promises are the one thing the Last Planner System can't run without. Build that habit into your team, and the schedule finally starts telling the truth.