On most jobs, "accountability" is a word that only comes out after something has already gone wrong. The slab pour slips, the inspector red-tags the rough-in, the drywall crew shows up to a room that isn't ready, and now there's a meeting where everyone explains why it wasn't their fault. That isn't accountability. That's a blame lottery, and everybody on site learns the same lesson from it: keep your head down and never commit to anything you might get pinned on later.
The Last Planner System flips that on its head. Done right, accountability stops being a stick you swing after a miss and becomes something people actually want to be part of, because it's built on promises they made themselves, tracked in the open, with the goal of getting better rather than getting caught. The software you use to run it is just the scoreboard and the memory — but the right scoreboard changes how the game gets played.
Accountability Is a Promise, Not a Punishment
Here's the distinction that trips up a lot of supers. A schedule handed down from the office is an assignment. When the framer misses a date on that schedule, you can point at the bar chart, but the framer never actually agreed to it — someone in a trailer decided it three weeks ago based on a duration a scheduler pulled out of a spreadsheet. There's no promise to hold anyone to.
The Last Planner System works because it moves commitment to the people doing the work. In the weekly work plan meeting, the framing foreman looks at the week ahead and says, "I'll have the north wing top plate done by Thursday." He said it. In front of the plumber, the electrician, and you. That's a commitment freely made, and it carries weight precisely because it wasn't imposed. A good foreman scheduling app captures that promise the moment it's made — who, what, and by when — so nobody's memory of the meeting drifts by Friday.
A few things separate a real commitment from a shrug:
- It's specific. "Work on the north wing" is not a commitment. "Top plate complete, north wing, ready for the electrician Thursday AM" is.
- It's screened for readiness. Nobody should commit to work that still has open constraints — no material, no RFI answer, no preceding trade done. More on that below.
- It's made out loud, to peers. A promise the whole room heard is a different animal than a line item on a printout.
Make-Ready: Accountability Before the Work Starts
Most missed commitments aren't a labor problem. The crew showed up ready to work — the work wasn't ready for them. That's why the make-ready look-ahead is where accountability really lives, and it's the part inexperienced teams skip.
Run a rolling three- to six-week look-ahead and, for every task heading into the window, ask a blunt question: what has to be true before a crew can start this? Those are your constraints — missing submittals, an unanswered RFI, material still on a truck in Ontario, an inspection that hasn't been scheduled, a preceding trade that isn't done. Each one gets a name and a date. Not "the team will handle it." A person, and a day they've promised to have it cleared.
The discipline is this: a task doesn't earn a spot in the weekly work plan until its constraints are actually removed and verified. Not "should be here by then" — confirmed. I've watched a crew stand around a locked electrical room for half a day because the make-ready meeting recorded "keys — Tuesday" and nobody checked that Tuesday actually happened. The look-ahead flagged it; the follow-through didn't. That's a coordination failure, not a labor failure, and it's exactly the kind of thing a shared look-ahead schedule is supposed to catch a week out instead of at 7 a.m. on the day.
A rule of thumb worth adopting: if a task is inside two weeks and still carries an open constraint, it's a red item and it gets talked about first in the next meeting — before anyone reviews last week's numbers. Constraints that go stale are how a smooth-looking schedule quietly rots from underneath.
PPC: The Number That Makes the Conversation Honest
Percent Plan Complete is the heartbeat of Last Planner accountability, and it's beautifully simple: of the commitments made for the week, what fraction were fully done? Twenty tasks promised, sixteen complete, that's 80% PPC. Partial credit doesn't count — a task is done or it isn't. That harshness is the point. It keeps the number honest and keeps people from talking themselves into "well, we mostly got there."
What PPC gives you is an objective starting point for a conversation that would otherwise dissolve into opinion. It's the same calculation for every trade, tracked the same way every week, so patterns surface. A crew that runs 55% one week isn't necessarily a problem. A crew that runs 55% for six weeks straight is telling you something — either they're over-committing, or there's a constraint upstream nobody's owning.
Two cautions from experience. First, don't chase 100%. A team hitting 100% every week isn't superhuman — they're sandbagging, committing to less than they can do so the number looks clean. Healthy PPC on a real commercial job usually lands somewhere in the 70s to high 80s, climbing as the team matures. Second, PPC is worthless without the reasons behind the misses.
Track the Reasons, Not Just the Failures
Every missed commitment gets a reason code — a short, honest note on why the promise didn't get kept. Prerequisite work not done. Material late. Weather. Manpower. RFI. Directive change. Bad estimate on the duration. Over a month, those reason codes are worth more than the PPC number itself, because they point straight at your recurring failure modes.
When you sort the misses and see that "prerequisite work not complete" accounts for a third of them, you've learned something concrete: your trade sequencing or your make-ready is leaking. If "material late" dominates, that's a procurement conversation, not a field one. This is where good look-ahead software earns its keep — it remembers every reason code across the whole job so you can actually see the pattern instead of relearning it each week. The scoreboard becomes a diagnosis.
Accountability Runs Both Directions
Here's where a lot of GCs lose the trades' buy-in: they want commitment from subs but won't be held to their own. It doesn't work. If you're asking the plumber to promise his rough-in by Wednesday, then the general contractor owes an equal promise — the room's framed and inspected, the layout's marked, the shaft is clear, and the GC-owned constraints are gone. When the GC's commitments show up on the same board, tracked with the same PPC discipline, the trades stop treating the meeting as management theater.
Subcontractor accountability under Last Planner comes down to four plain expectations: show up to the planning meetings and actually engage, make realistic promises instead of yes-to-everything ones, deliver what was promised, and — this is the big one — give early warning when something's about to slip. A sub who calls you Monday to say Thursday's at risk is a good partner. A sub who says nothing and no-shows Thursday is the problem, even if their PPC looks the same on paper. Reward the early warning or you train people to hide.
How to Actually Run the Conversation
The weekly review is where accountability either builds trust or burns it. The whole thing lives or dies on tone. Start with the data — PPC and the reason codes — because numbers are neutral and nobody can argue that the room was locked or the RFI came back late. Then get curious instead of prosecutorial. "The rough-in slipped — walk me through what got in the way" opens a door. "Why didn't you finish?" slams it, and next week that foreman commits to nothing.
Keep the focus on the system. When a promise fails, the most useful question is usually not "who screwed up" but "what let this happen, and what do we change so it doesn't happen again?" Most misses trace back to a broken handoff, a constraint nobody owned, or a duration that was never realistic — system problems, not character problems. Solve the system and the person's next commitment gets more reliable on its own.
That doesn't mean there are never consequences. A trade that over-promises and under-delivers for weeks, ignores the reasons, and won't engage is a real issue you escalate. But you escalate on a pattern, backed by weeks of objective data — not on one bad Thursday. When the record is right there in the system, that conversation is calm and fair instead of a shouting match over whose memory is correct.
The Part Everyone Forgets: Catch People Doing It Right
Accountability that only ever points at failures curdles into a blame culture no matter how carefully you word it. The crews notice. So spend real time on the wins. Call out the trade that ran 90% three weeks running. Share the story of the foreman whose early heads-up let you re-sequence and save the week. Post the PPC trend where everyone can see it climbing. Recognition is a form of accountability too — arguably the more powerful one, because it makes people want to keep their promises rather than fear breaking them.
Why the Software Matters Here
None of this requires software in theory. You can run Last Planner with sticky notes on a wall, and plenty of great teams started exactly there. What the sticky-note wall can't do is remember. It can't hold a season of PPC trends, sort three months of reason codes, show a foreman his own commitment history, or put the same weekly work plan in front of a sub who's across town. A look-ahead scheduling tool like LookAheadWall exists to be that shared memory — capturing commitments as they're made, tracking constraints to a named owner and date, computing PPC without anyone doing math on a Friday, and making the whole picture visible to every trade on the job, including on the phone in a foreman's pocket.
The tool doesn't create accountability — people making and keeping promises to each other creates accountability. But it removes the friction and the arguments-over-memory that quietly kill the practice, and it turns a wall of good intentions into a record you can actually learn from. Get the promise-making right, track it honestly, keep the conversations curious instead of punishing, and the software just makes the good habit stick. That's the difference between a team that assigns blame and a team that gets measurably better every week.