The Last Planner System: How Lean Construction's Weekly Commitment Planning Cuts Rework and Schedule Slippage

The Last Planner System (LPS), developed by Glenn Ballard and Gregory Howell starting in the 1990s, is the core production planning methodology of lean construction. Instead of top-down CPM schedules that cascade down to trades who then try to meet the master schedule, LPS inverts the dynamic: the "last planners" — the foremen and trade leaders actually doing the work — plan commitments collaboratively and incrementally, based on what's actually ready and achievable.

LPS is used most extensively on large complex projects where traditional scheduling breaks down under the weight of interdependencies, change, and uncertainty. Contractors who implement LPS consistently report reduced schedule slippage, fewer interfering handoffs, less rework, and better trade coordination. But implementing LPS requires cultural changes — trade leaders need authority to commit their crews, superintendents need to shift from directive to facilitative leadership, and owners and design teams need to participate in planning sessions rather than just receive reports.

Four Planning Levels

LPS organizes planning into four interconnected levels:

Each level feeds the next. The master schedule establishes milestones; phase schedules detail how to hit them; make-ready plans remove constraints so work can be scheduled; weekly work plans are the actual production commitments. The system pushes planning authority down to those closest to the work — the "last planners" who know what their crews can actually deliver.

Pull Planning

Phase schedules in LPS are developed through pull planning — a collaborative session where trade leaders plan backward from a target milestone. The mechanics typically involve sticky notes on a wall representing activities:

Pull planning sessions typically last several hours. Participants include superintendents from each trade, project management, design team members who need to contribute, and sometimes owner representatives. The product — the pull plan — becomes the working schedule for the phase.

Make-Ready Planning

The make-ready plan (sometimes called lookahead planning) identifies work that's scheduled for the coming 4-6 weeks and actively manages the constraints that could prevent it from happening:

Each constraint is assigned an owner and a target removal date. The make-ready meeting tracks constraint removal progress and escalates stuck constraints. Work can't move to the weekly work plan until its constraints are removed — meaning the work is actually ready to perform.

This is where LPS differs fundamentally from traditional CPM-driven scheduling. In CPM scheduling, activities are scheduled when the CPM says they should happen. In LPS, activities are scheduled when they're actually ready to happen. This prevents the common failure mode where crews arrive to start work on schedule only to find that prerequisites aren't done or information isn't available.

Weekly Work Planning

The weekly work plan is the actual production commitment. Each week, the trade leaders commit to specific tasks they'll complete that week — tasks they've verified are ready (constraints removed) and that they have the resources to execute.

Characteristics of good weekly work plan commitments:

The commitment is from the trade leader who will execute — not from project management imposing it. This distinction matters. A foreman who commits to a task they believe they can deliver has personal stake in delivering. A foreman who's told "do this by Friday" with no input has less stake and less ability to plan effectively.

Percent Plan Complete (PPC)

LPS tracks weekly work plan performance with Percent Plan Complete (PPC) — the percentage of committed tasks actually completed on time:

PPC is a measure of planning reliability, not just productivity. A team with high productivity but poor planning would have high output but low PPC (they did work, but not the work they committed to). A team with low PPC often has deeper issues — unstable inputs, unclear work definition, or consistent over-commitment.

Typical ranges: new LPS implementations often start at 40-50% PPC and improve to 70-85% with practice. Projects with 85%+ PPC are well-functioning; under 50% suggests significant planning breakdown requiring attention.

Variance Analysis

When commitments aren't met, LPS asks why. Variance analysis identifies root causes so the team can prevent similar misses:

Variance data accumulates into patterns. If 40% of misses this month were from missing materials, the team knows to improve material management. If 30% were from design information gaps, the design team and RFI process need attention. Variance analysis turns individual commitment failures into system improvement signals.

Daily Huddles

Many LPS implementations include daily huddles — brief (15-minute) stand-up meetings where trade leaders review the day's work, identify immediate issues, and confirm handoffs. Daily huddles catch problems while they're small and maintain the tempo of commitments and completions.

Effective daily huddles share characteristics:

Cultural Requirements

LPS isn't just a set of techniques — it requires cultural shifts that many organizations find difficult:

Organizations with command-and-control culture often struggle with LPS because the system requires decentralized decision-making. Organizations where "failure" is punished rather than analyzed often struggle because honest variance reporting is essential. Implementations that skip the cultural work and just impose the techniques typically produce half-hearted adoption with limited benefits.

Tools Supporting LPS

LPS started as an analog practice — sticky notes on walls, whiteboards, paper tracking. Digital tools have emerged that support LPS practices:

Digital tools support LPS but don't create LPS. Projects have successfully implemented LPS entirely analog; others have poor implementations despite sophisticated software. The cultural and practical discipline of LPS matters more than the specific tooling.

Interaction with CPM Scheduling

LPS typically coexists with traditional CPM scheduling rather than replacing it. Many contracts require CPM schedules for progress reporting, payment applications, and delay claims. LPS provides the working-level planning that makes the CPM schedule actually achievable:

The master CPM schedule becomes a target and reporting framework; LPS becomes the production planning engine. Both have roles, and they reinforce rather than conflict when properly integrated.

Bottom Line

The Last Planner System is the core production planning methodology of lean construction — pull planning for phase schedules, make-ready planning to remove constraints, weekly work planning driven by trade leaders, percent plan complete tracking, and variance analysis for continuous improvement. Contractors who implement LPS consistently report improved schedule reliability, less rework, better trade coordination, and higher team engagement. But LPS requires cultural shifts — decentralized decision authority, facilitative leadership, openness about misses — that many organizations find difficult. Half-hearted LPS implementations that adopt the techniques without the culture produce limited benefits. Full implementations where trade leaders, project management, designers, and owners all participate in the system produce the schedule and cost improvements that have made LPS the dominant methodology in lean construction circles. For contractors considering LPS adoption, starting with a single project champion, visible leadership support, and willingness to learn from early misses tends to produce better outcomes than attempts to roll out LPS across an organization at scale.