There are two camps that both get the Last Planner System wrong. One says it's academic overhead that only makes sense on a hospital or a stadium — too much meeting time for a strip-mall tenant improvement. The other says a small crew doing a kitchen remodel is "too simple" to need any of it. I've run jobs at both ends, and both camps are wrong for the same reason: they're confusing the principles of Last Planner with the paperwork of Last Planner. The principles don't scale. They're the same on a four-week bathroom gut as they are on a 40-story tower. What scales is how much structure you wrap around them.
Let me walk through what actually stays constant, what actually changes, and how to run this on whatever job is in front of you right now.
The four things that never change, no matter the size
Strip Last Planner down to the studs and you're left with a handful of ideas that are true on every job I've ever been on.
First, only commit to work you can actually finish. This is the whole game. The master schedule tells you what should happen. The weekly work plan is what a foreman promises will happen — and a promise only counts if he had a real say in making it and a real ability to keep it. On a two-man remodel that's a thirty-second conversation. On a tower it's a room full of supers. Same idea.
Second, make work ready before you release it. An activity isn't schedulable just because its predecessor finished. It's ready when the constraints are cleared: the material's on site, the RFI is answered, the area's accessible, the prior inspection passed, the layout's approved. Screening for those constraints is the single highest-value thing the look-ahead does, and it matters more on small jobs, not less, because small jobs rarely have a full-time person chasing submittals.
Third, measure whether you kept your word. Percent Plan Complete — the number of commitments completed divided by the number made — is dead simple and brutally honest. If you planned twelve tasks and finished nine, that's 75%. The number itself matters less than the conversation about the three you missed and why.
Fourth, learn from the misses. Every incomplete task has a reason, and the reasons repeat. "Material didn't show." "Inspector was a day out." "The other trade wasn't done." Track those five-cent reasons for a month and you'll see your real bottleneck, and it's almost never the thing you were yelling about.
That's it. Reliable promises, ready work, honest measurement, continuous learning. Every version of Last Planner from a whiteboard to an enterprise platform is just those four ideas dressed for the occasion.
Small jobs: where the discipline pays back fastest
Here's the counterintuitive part. The smaller and tighter the job, the more a blown day hurts. A two-week schedule has no float to absorb a missed inspection. If your tile guy shows up Monday and the waterproofing wasn't done Friday because nobody checked that the material landed, you just lost 10% of your entire schedule to a constraint you could have cleared with a phone call.
You don't need software or a formal pull-planning session for a job like this. You need the habits. Here's a realistic small-project version:
- A weekly plan you actually write down. Even five lines on a legal pad. The act of committing it to paper forces you to ask "can this really happen?"
- A rolling three-week look-ahead in your head or on a whiteboard. What's coming, and what has to be true before it can start. This is where you catch the long-lead item — the shower glass, the specialty appliance, the permit — three weeks out instead of the morning of.
- A thirty-second constraint check. For every task next week: material here? area ready? inspection passed? sub confirmed? If all four aren't yes, it's not next week's work yet.
- A Friday two-minute honesty check. What did we say we'd do, what did we actually do, why the gap. You don't need to write it down formally, but you do need to say it out loud.
The mistake on small jobs isn't over-planning — nobody over-plans a remodel — it's skipping planning entirely because "it's just a small job." That's exactly the job where one dropped constraint eats your margin.
Medium jobs: the standard playbook, run for real
A mid-size commercial job — a tenant build-out, a small multi-family, a light industrial shell — is where the textbook version earns its keep. You've got eight to fifteen trades, a schedule long enough that patterns emerge, and enough money on the table that a week of slippage shows up on someone's P&L.
This is where you run the full four-tier structure without apology:
- Master / phase schedule — the milestones, built with the trades in a pull-planning session so the handoffs are theirs, not yours.
- A four-to-six-week look-ahead — updated weekly, with constraints logged and an owner and a due date on each one. This is the make-ready engine.
- A weekly work plan — the foremen's committed work for the coming week, made in a short weekly coordination meeting.
- PPC and a reasons-for-variance log — tracked every week and reviewed as a trend, not a one-off.
The weekly meeting is the heartbeat. Keep it to thirty minutes, keep it standing if you can, and keep it about commitments and constraints — not war stories. The fastest way to kill Last Planner on a medium job is to let that meeting turn into a two-hour gripe session. Trades stop showing up, and then you're just a super with a spreadsheet nobody believes.
This is also the size where good look-ahead scheduling software stops being a nice-to-have. When you've got a dozen foremen who each need to see their slice, when constraints have owners and due dates, when you want to actually chart your PPC trend instead of guessing — that's the job a tool like LookAheadWall is built for. A visual, location-based weekly plan the subs can see on their phones beats a printout that's stale by Tuesday. But the tool is the amplifier. The habit is the signal.
Large jobs: same principles, more structure to carry them
On a large, multi-phase job the principles don't get more sophisticated — the organization around them does. You can't run one weekly work plan for 400 workers across six floors and three buildings. So you break it up.
Large-project structure usually means:
- Planning by zone or area. Each floor, wing, or building runs its own look-ahead and weekly plan, often with its own area super, all rolling up to a master.
- Someone whose actual job is make-ready. On a job this size, constraint-clearing is a full-time role, not something the super squeezes in between fire drills. Submittals, long-leads, inspections, and inter-area handoffs need a dedicated owner.
- Formal handoff coordination between areas and trades. The trade-flow sequence — how a crew moves from one location to the next, and how the following trade shadows them — has to be explicit, because with this many bodies, an unclear handoff is a collision.
- Analytics that actually drive decisions. PPC by trade, by area, by week. Reasons-for-variance rolled up so you can see that Building B keeps stalling on inspections while Building C stalls on material. That's not vanity data; that's where you send your attention.
The failure mode at scale is different from the small-job failure mode. Small jobs die from skipping the process. Large jobs die from the process becoming a paperwork ritual disconnected from the field — beautiful pull plans on the wall, gorgeous PPC charts, and crews out in the field doing whatever they can find to do because nobody made their work ready. If the guys swinging hammers can't tell you what they committed to this week and why it's ready, all the structure above them is theater.
The one adjustment that actually matters: project type
Size gets all the attention, but project type changes the implementation more than size does.
- Renovation and occupied-space work lives on uncertainty — you don't know what's behind the wall until you open it. Your look-ahead needs more slack and your weekly plan needs a plan B, because "found conditions" will blow up a rigid schedule every time.
- Healthcare and lab work layers on infection-control barriers, ICRA permits, and above-ceiling inspections that gate everything downstream. Half your constraints are administrative, and they take longer than the physical work.
- Repetitive residential and multi-family is the dream for this method. Once you dial in the trade-flow sequence on floor two, you're running takt — a rhythm — and the look-ahead becomes about protecting the beat, not reinventing it.
- Industrial and mission-critical work demands tighter constraint detail because the tolerances and the commissioning sequence leave no room to improvise.
The principles hold across all of them. What you tune is how far out you look, how much buffer you carry, and which constraints you obsess over.
How to start, whatever's on your desk right now
Don't wait for the "right size" project to adopt this. Start on Monday, on whatever you've got:
- Write down next week's work as commitments, not wishes.
- For each one, ask the four make-ready questions — material, access, prior work, inspection — and don't schedule anything that fails.
- Friday, count what you finished against what you promised. That's your PPC.
- Write one line next to each miss explaining why.
- Next week, do it again — and watch the reasons repeat until they show you your real problem.
Start on a whiteboard. Move to a purpose-built look-ahead tool when the job gets big enough that the whiteboard can't keep up — when you need subs to see it remotely, when constraints need owners and dates, when you want the PPC trend charted for you. But understand the order: the discipline comes first, the software makes the discipline scale.
Last Planner works on any size project for the same reason a level works on any size wall. The tool doesn't care how big the job is. It just tells you the truth about whether things are where they're supposed to be — and gives you the chance to fix it before the concrete sets.