How is LPS different from CPM?

CPM is a calculation method that produces a network-logic schedule from durations and dependencies. LPS is a production-planning system that decides who commits to what each week. They are complementary: CPM gives the strategic frame; LPS runs the weekly production.

What PPC should we aim for?

Teams new to LPS often start at 40–55%. A mature team runs 75–85%. Anything consistently above 90% suggests under-promising; below 50% suggests promises aren't being protected. The trend matters more than the number.

Do we need software to run LPS?

No — LPS started on paper and sticky notes and still runs that way on many projects. Software (LeanProject, Touchplan, vPlanner) helps with distributed teams and analytics, but the core practice is human conversation. Tool first, culture second is the wrong order.

Who runs the pull-plan session?

A neutral facilitator — often a lean construction consultant on early projects, then an internal trained facilitator. The project manager and master scheduler attend to listen and capture, not to drive.

How often should pull planning happen?

Once per phase, then refreshed every 6–8 weeks or when a major event changes the plan. Look-ahead and weekly work plans happen continuously between pull-plans.

How does LPS interact with the contractual schedule?

The contractual CPM remains the basis for time-related claims and EOT analysis. LPS lives inside that frame as the production-planning layer. Done well, LPS reduces claims because the production reality stays closer to the plan.

Can LPS work in design phases?

Yes — Last Planner has been adapted to design management. The 'tasks' become design deliverables, the 'last planner' is the discipline lead, and constraint screening focuses on information dependencies. It is harder than construction LPS because design hand-offs are more ambiguous, but the discipline transfers.

What's the single biggest predictor of LPS success?

Whether foremen are allowed to say 'no, I can't commit to that.' Every other LPS practice falls apart if promises can be coerced. Protect that one rule and the rest follows.

Which calculators on PMMilestone.org apply to Last Planner System?

For Last Planner System, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.

What is a common misconception about Last Planner System?

That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.

Which related encyclopedia entries should I read alongside Last Planner System?

Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.

How does Dr. Hassan Eliwa's research treat Last Planner System?

Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Last Planner System is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.

How is Last Planner System defined on PMMilestone Research & Insights?

A collaborative lean construction planning method where the people who will perform the work commit to what they can actually do, replacing top-down schedules with promises and weekly learning. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

Lean · Letter L

Last Planner System

A collaborative lean construction planning method where the people who will perform the work commit to what they can actually do, replacing top-down schedules with promises and weekly learning.

By Dr. Hassan Eliwa, PhD · Founder of PMMilestone.org and PMMilestone.com · Updated 2026-06-23

Definition

The Last Planner System (LPS) is a lean construction planning method developed by Glenn Ballard and Greg Howell in the 1990s and now standard practice on most well-run lean projects worldwide. The "last planner" is the foreman or supervisor who actually directs work to the crew — not the master scheduler in the trailer. LPS argues that schedules are commitments only when the last planner makes them, and so it builds the production plan around a series of structured collaborative conversations rather than a top-down Gantt chart.

The Four Levels of Planning

Master Schedule: milestone-level, strategic. Owned by the project team.
Phase / Pull Plan: for each phase, the trades work backwards from the milestone to identify hand-offs and constraints. Done collaboratively in a "pull planning" session.
Look-Ahead Plan (6 weeks): activities are screened for constraints — design, materials, labour, equipment, predecessors. Only constraint-free activities advance.
Weekly Work Plan (WWP): the last planners commit to specific tasks for the next week. Only tasks they are confident they can complete are admitted.

The Key Discipline: PPC

At the end of each week, the team measures Percent Plan Complete (PPC) — the percentage of tasks promised in the WWP that were actually completed as promised. PPC is the system's heartbeat. A team starting LPS often runs 40–55%; a mature team runs 80%+. More importantly, every incomplete task is analysed for the reason for non-completion (materials, design, prerequisite work, labour, weather, change). The pattern of reasons becomes the team's improvement agenda.

Real-World Construction Example

A 60-storey residential tower in Toronto adopted LPS in earnest after a slow first year. Within four months PPC climbed from 47% to 78%; in the same period the labour productivity index rose by 19% and RFI volume dropped by a third. The biggest cultural shift was foremen openly saying "I can't promise that" — replacing the toxic earlier pattern of agreeing to everything and quietly delivering less. The schedule stopped lying, and the project started catching up.

Real-World IT / Agile Example

LPS shares deep DNA with Scrum and Kanban. The pull plan is the agile programme increment plan; the WWP is the sprint commitment; PPC is sprint completion rate; the reasons for non-completion are the retrospective material. On a complex software programme, we ran a fortnightly pull-plan session between platform, mobile, and data squads, then translated the result into each squad's normal sprint planning. The dependency conversations that LPS forced were exactly what SAFe PI planning tries — sometimes successfully, sometimes not — to do.

Project Controls Perspective

Controls teams supplement traditional CPM with LPS metrics: PPC trend, constraint-removal lead time, reasons-for-non-completion mix. These reveal production reliability that CPM and earned value cannot. A project with great CPI/SPI and bad PPC is on borrowed time; a project with weak CPI but rising PPC is usually about to turn the corner.

Common Mistakes

Treating LPS as a software tool. The tool is the easy part; the cultural shift is the work.
Master scheduler runs the pull plan. The whole point is that the foremen run it. The scheduler captures, doesn't dictate.
PPC theatre. Foremen learn to promise only what they're certain of; PPC hits 95% but actual production stays flat. Cap promises at what's actually achievable, then measure honestly.
Ignoring constraints. Look-ahead screening done sloppily means the WWP is full of work that can't actually start.
No reasons analysis. PPC without reasons-for-non-completion is a vanity metric.
Adopting LPS without leadership buy-in. If senior management still cares only about the CPM Gantt, foremen disengage.

Expert Tips

Start with one phase. Pilot LPS on a contained phase (e.g. MEP rough-in) before rolling out programme-wide.
Make the planning visible. Wall-sized pull-plan boards beat software tools for engagement.
Protect the planner's promise. If a foreman says "I can't commit," that has to be respected, not negotiated away.
Publish PPC openly. Hide it and people game it; publish it and people own it.
Invest in facilitation. Good pull-plan sessions are facilitated; bad ones are chaired.

Key Takeaways

LPS shifts planning authority from the schedule trailer to the foreman.
Four levels: master, pull plan, look-ahead (constraint screening), weekly work plan.
PPC and reasons-for-non-completion are the central metrics — production reliability, not schedule status.
The technique works in software too, where it overlaps deeply with Scrum and SAFe.
The hard part isn't the boards or the software — it's the culture of honest promises.

Related Encyclopedia Entries

Look-Ahead Schedule — companion entry on a directly related concept.
Just-in-Time Delivery — companion entry on a directly related concept.
Takt Time Planning — companion entry on a directly related concept.
Gemba Walk — companion entry on a directly related concept.
Agile Project Management — companion entry on a directly related concept.
WIP Limits — companion entry on a directly related concept.

Frequently Asked Questions

How is LPS different from CPM?
CPM is a calculation method that produces a network-logic schedule from durations and dependencies. LPS is a production-planning system that decides who commits to what each week. They are complementary: CPM gives the strategic frame; LPS runs the weekly production.
What PPC should we aim for?
Teams new to LPS often start at 40–55%. A mature team runs 75–85%. Anything consistently above 90% suggests under-promising; below 50% suggests promises aren't being protected. The trend matters more than the number.
Do we need software to run LPS?
No — LPS started on paper and sticky notes and still runs that way on many projects. Software (LeanProject, Touchplan, vPlanner) helps with distributed teams and analytics, but the core practice is human conversation. Tool first, culture second is the wrong order.
Who runs the pull-plan session?
A neutral facilitator — often a lean construction consultant on early projects, then an internal trained facilitator. The project manager and master scheduler attend to listen and capture, not to drive.
How often should pull planning happen?
Once per phase, then refreshed every 6–8 weeks or when a major event changes the plan. Look-ahead and weekly work plans happen continuously between pull-plans.
How does LPS interact with the contractual schedule?
The contractual CPM remains the basis for time-related claims and EOT analysis. LPS lives inside that frame as the production-planning layer. Done well, LPS reduces claims because the production reality stays closer to the plan.
Can LPS work in design phases?
Yes — Last Planner has been adapted to design management. The 'tasks' become design deliverables, the 'last planner' is the discipline lead, and constraint screening focuses on information dependencies. It is harder than construction LPS because design hand-offs are more ambiguous, but the discipline transfers.
What's the single biggest predictor of LPS success?
Whether foremen are allowed to say 'no, I can't commit to that.' Every other LPS practice falls apart if promises can be coerced. Protect that one rule and the rest follows.
Which calculators on PMMilestone.org apply to Last Planner System?
For Last Planner System, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.
What is a common misconception about Last Planner System?
That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.
Which related encyclopedia entries should I read alongside Last Planner System?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.
How does Dr. Hassan Eliwa's research treat Last Planner System?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Last Planner System is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.
How is Last Planner System defined on PMMilestone Research & Insights?
A collaborative lean construction planning method where the people who will perform the work commit to what they can actually do, replacing top-down schedules with promises and weekly learning. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

View the full FAQ page for Last Planner System →