Pull Planning

Definition

Pull planning is a collaborative scheduling technique in which the parties who will do the work — trades, engineers, designers — plan a phase of work together by starting at a milestone and working backward, pulling each handoff and commitment from the party responsible. Instead of a schedule pushed out by the planner, the schedule emerges from a face-to-face session where each party makes explicit commitments to the others. Pull planning is a core practice of the Last Planner System and of Lean Construction more broadly.

Why It Works

A push schedule — planner writes, everyone else complies — carries hidden fragility: no one has personally committed. When reality diverges, no one owns the recovery. A pull-planned schedule carries commitment, because the person doing the work agreed the duration and the handoff. The commitment is the product; the wall of sticky notes is just the artefact.

How a Pull Planning Session Runs

• Choose the milestone — usually 6 to 12 weeks out (a phase or interim handover).
• Assemble the trades — foremen and superintendents, not just schedulers.
• Work backward from the milestone, one activity at a time.
• Each trade writes its own tickets — activity, duration, predecessor, successor, prerequisites.
• Handoffs are negotiated face-to-face — "I need the slab cured by Wednesday to start layout Thursday."
• Test the plan — walk it forward and check for gaps.
• Commit — every trade signs off.

Real-World Construction Example

A 320-bed hospital fit-out ran phase pull planning every six weeks. The 12-week fit-out phase covered MEP rough-in, drywall, ceiling grid, above-ceiling MEP, ceiling tiles, floor finishes, and final MEP. In the pre-Lean baseline, this phase had slipped an average of nine days on the previous three phases. After introducing pull planning — foremen physically in the room, sticky notes on a 12-foot wall, backwards from the phase milestone — the next three phases slipped an average of two days. The team attributed most of the gain to the fact that the MEP foreman personally committed to duct hanging by day 14, and the drywall foreman personally believed him. That belief did not exist in the push-planned baseline.

Real-World IT / Agile Analogue

The nearest agile analogue is backward-planning a release train or a PI planning event, where teams work backwards from a programme increment date, pulling dependencies and committing to features. Facilitators from the Scaled Agile Framework community describe the mechanism in identical terms: face-to-face, cross-team, commitment-based, artefact captured on a physical or digital wall. Different vocabulary, same discipline.

Best Practices

• Get the actual foremen and team leads into the room, not just the schedulers.
• Work backward from a milestone the whole team recognises.
• Use physical sticky notes — the tactility matters for engagement.
• Capture prerequisites explicitly on each ticket (materials, permits, previous trade finished, information).
• Walk the plan forward at the end to test coherence.

Common Mistakes

• Sending deputies instead of the actual work leaders; commitments made by deputies are not commitments.
• Planning too far out; 12-week phases are the sweet spot, 24-week plans become theoretical.
• Using pull planning as a one-off launch event rather than a rolling practice.
• Skipping the forward walk-through; hidden gaps survive into execution.
• Not tracking commitment reliability afterwards; the practice needs the feedback loop to mature.

Expert Tips

• Enforce the "one-hand-off-per-ticket" rule. A ticket that describes multiple handoffs conceals problems.
• Measure Percent Plan Complete (PPC). The percentage of promised tickets completed on time is the practice's health metric.
• Coach foremen who over-promise. Sustained low PPC often traces to a specific individual's optimism; conversation, not blame, is the fix.
• Refresh the wall every phase. Old tickets and stale commitments erode trust.
• Do not digitise too early. A physical wall in the first year builds the muscle memory; migration to software comes after.

Practical Lessons Learned

• Projects that hold pull planning sessions rigorously outperform projects with equally skilled schedulers who plan alone — by roughly 20% in schedule adherence.
• The single strongest predictor of pull planning's success is whether foremen (not managers) attend.
• The practice takes two or three sessions to click; the first session often feels chaotic. Persistence pays off.

Key Takeaways

• Pull planning generates commitment, not just a schedule.
• Work backwards from a milestone; the doers write their own tickets.
• Handoffs are negotiated face-to-face and physically visible on a wall.
• The practice belongs to the trades and teams doing the work, not to the planner.
• Percent Plan Complete measures the practice's health over time.

Related Encyclopedia Entries

• Last Planner System
• Takt Time Planning
• Gemba Walk
• Rolling Wave Planning

Related Research Articles, Case Studies & Tools

• Pull Planning Facilitator's Kit
• Project Controls Academy: Lean Construction
• Hospital fit-out pull planning case study
• PPC and schedule reliability