Every superintendent has sat in a Monday coordination meeting where the drywall foreman swears he'll have the west wing hung by Friday, the electrician nods along, and then Thursday afternoon you find out the framing inspection never got called and nothing moved. Nobody lied, exactly. Everybody just quietly assumed somebody else owned the piece that fell through. That gap — the space between what people say and what actually happens on the deck — is where schedules go to die. Accountability is how you close it.
The trouble is that "accountability" gets thrown around like it means chewing people out after the fact. On a real job it means something narrower and more useful: making commitments specific, making them visible, and making the follow-up routine enough that nobody's surprised by it. A well-run look-ahead schedule is the tool that turns that from a personality trait of the super into a system the whole team runs on.
Vague plans can't hold anyone accountable
You cannot hold a crew accountable to something that was never actually a commitment. "We should be getting close to rough-in on the second floor next week" is not a commitment — it's a weather report. There's no date, no owner, no clean way to tell later whether it happened.
The whole point of a weekly work plan is to force the fuzz out. A real commitment names the task, the location, the crew, and the finish. "Level 2 east wing plumbing top-out complete by Thursday, called for inspection Friday morning — Reyes's crew." Now there's something a person put their name on, in front of the other trades, and everyone in the room heard it. That's the raw material accountability is built from. No amount of tracking software fixes a plan made of weather reports.
This is also why the three-to-six-week look-ahead matters more than the master schedule for day-to-day accountability. The master schedule tells you the plumbing was supposed to be done by the 14th. The look-ahead is where a foreman looks you in the eye on Monday and says he'll have it done by Thursday. One is a contract milestone; the other is a promise between two people who both remember it was made.
Public commitments carry more weight than private ones
There's a reason the pull-planning and last-planner crowd insist commitments get made out loud, in the room, with the affected trades present. A promise made privately to the super is easy to walk back. A promise made in front of the electrician who's stacked right behind you, and the tile setter waiting on both of you, is a different animal. Nobody wants to be the reason three other trades sat on their hands.
So run your weekly planning meeting as the place commitments get spoken and recorded, not just where the super reads the schedule at people. Go trade by trade. Ask each foreman what he's committing to this week and what he needs from the crews around him to hit it. When the plumber says he needs the framing inspection signed off by Tuesday to start his rough, the carpenter in the room now owns that Tuesday date — and everybody watched him take it. That handoff, visible and verbal, is worth more than any dashboard.
Every constraint needs a name next to it
Half of missed commitments trace back to a constraint nobody owned. The material was on backorder. The RFI answer never came back. The prior trade wasn't finished. The permit inspection wasn't scheduled. These aren't mysteries — they're the same six or eight things every single week, and they're all knowable in advance if somebody's job is to look.
Good constraint management is boring and it works. For every task entering your look-ahead window, you screen it against the usual suspects: materials on site, information available (approved submittals, RFI closed), prior work complete, permits and inspections lined up, labor and equipment available, and access to the area. Anything that isn't green becomes a constraint with two things attached: an owner and a need-by date. Not "someone should chase the light fixtures." Marcus owns the fixture delivery, needed on site by the 9th.
The accountability here isn't about the crew that does the work — it's about the people clearing the path in front of them. The PM who owns getting the RFI answered. The super who owns calling the inspection. The sub's office who owns the material order. When a task blows up because a constraint didn't clear, the honest question is "who owned that constraint and what happened," not "why didn't the drywall crew perform." Most of the time the crew was ready and something upstream wasn't. Tracking constraints by owner is what surfaces that pattern instead of letting it hide behind the trade that got caught holding the bag.
Measure PPC, but use it to learn — not to punish
Percent Plan Complete is the cleanest accountability metric the industry has, and also the easiest one to ruin. PPC is simple: of the commitments made for this week, what percentage got fully done? Made twenty commitments, finished sixteen, that's 80%. It's binary — 90% done is not done. Half a wall of rock is a zero for that task.
A healthy job usually lands somewhere in the 65–85% range once the team is honestly measuring. If you're seeing 100% week after week, your crews aren't superheroes — they're sandbagging the plan, committing to less than they can do so the number looks good. That's the first way PPC gets ruined: the second everyone believes the number is a report card that gets them yelled at, they stop making real commitments. You'll get a beautiful 95% and a job that's behind, because the plan stopped being ambitious enough to matter.
The value of PPC isn't the number — it's the conversation about the misses. Every task that didn't complete gets a reason code: waiting on prior trade, material late, weather, rework, manpower short, scope change, bad estimate. Do that for a month and the reasons cluster. If a third of your misses every week are "waiting on prior trade," you don't have a lazy-crew problem, you have a sequencing problem, and no amount of leaning on foremen will fix it. That's the real payoff — variance analysis points you at the broken system instead of a scapegoat. A schedule tool like LookAheadWall earns its keep here by keeping the commitment history and the reason codes in one place, so the patterns are visible over weeks instead of evaporating after each meeting.
Subcontractor track records are institutional memory
Everybody "knows" which subs are reliable, but that knowledge usually lives in the super's head and walks off the job when he does. Documented commitment history turns gut feel into something you can actually use. When you can pull up that the framer has hit his weekly commitments 85% of the time and the fireproofing sub is running closer to 55%, you plan differently. You build more buffer around the shaky trade. You have a specific, factual conversation with the sub's PM instead of a general gripe — "here are the last six weeks, here's where we slipped and why."
It also protects the good performers. The trade that consistently delivers shouldn't be treated the same as the one that's always three days late, and a record keeps you honest about which is which when memories get selective. Come the next bid, that history is worth real money to know.
Leaders get held to the same standard — or none of it holds
Here's the part that separates accountability from finger-pointing: it has to run uphill too. If the trades are on the hook for their commitments but the GC's own obligations — clearing constraints, answering RFIs, getting areas turned over, providing hoisting and access — are never tracked, the crews figure that out in about a week and the whole thing loses its teeth.
So put the general contractor's promises on the same board. If you told the drywall foreman the elevator lobby would be ready for him Monday and it wasn't, that's a GC miss, and it should show up in the variance list with your name on it, not get quietly dropped. Nothing buys credibility with the field faster than a super who logs his own team's misses out loud. It signals the whole exercise is about finishing the job, not building a case against the subs.
Make it transparent, then keep it routine
Accountability dies in the dark. If the schedule lives in a file only the super opens, the commitments, the constraint owners, the PPC trend, and the reason codes are invisible to the people who need to act on them. Post it where the trades can see it — a shared look-ahead the foremen can pull up on a phone in the field beats a printout that's stale by Wednesday. When a crew leader can open the current week on his phone and see exactly what he committed to and what's blocking it, the plan stops being the super's document and becomes the team's.
The other half is rhythm. Accountability isn't an event you stage when things go sideways — it's the same short loop every week: make commitments Monday, work the plan, screen next week's constraints, measure what got done, talk through the misses, adjust. Run that loop consistently for a month or two and it stops feeling like anyone's being audited. It's just how the job is run. A missed commitment becomes a normal thing you diagnose and fix, not a confrontation. That's the whole game — get the follow-up boring enough that it happens every week whether or not anyone's in trouble.
The payoff
Accountability built this way doesn't come from squeezing people harder. It comes from being specific about who committed to what, honest about what got in the way, and even-handed about applying the standard to the field and the office alike. Do that, and the Monday meeting stops being theater. The plumber's Thursday commitment means Thursday, the constraint owner clears the path before it's a fire, and when something does slip you learn why fast enough to fix the next one. That's a schedule that holds — and a crew that trusts it.