Pull Planning

The Team That Debated MEP Coordination for Three Weeks Instead of Pull Planning It in One Day

There is a project with complex MEP rough-in on twelve floors. The superintendent knows coordination is critical. So he schedules meetings. Mechanical shows up with their plan. Plumbing has a different sequence. Electrical wants access first. Fire protection needs specific areas clear. And for three weeks they debate. Who goes first? Who follows whom? What are the handoffs? Nobody commits to anything because nobody trusts anyone else’s timeline. So work stalls. Trades sit idle. The schedule slips. And after three weeks of meetings that produce nothing, the superintendent finally makes unilateral decisions and pushes everyone into the space. Chaos follows. Mechanical blocks plumbing. Electrical cannot access what they need. Fire protection gets delayed. And rework piles up because nobody coordinated handoffs. Meanwhile another project faced the same challenge. But instead of debating, they ran a one-day pull planning session. Every trade showed up. They worked backward from the milestone. They identified handoffs. They committed to durations. And they left with a coordinated sequence everyone agreed to. That project started MEP rough-in immediately while the first project was still debating. Same problem. Different approach. One team used pull planning. The other drowned in meetings. And the gap was not resources or complexity. It was understanding when and how to use the right planning technique.

Here is what happens when teams confuse planning techniques. A superintendent hears about pull planning and thinks it is the same as phase planning. So he schedules a pull planning session for standard repetitive work that everyone already knows how to sequence. Carpenters show up confused. We have been framing walls for twenty years. Why are we putting stickies on a board? Electricians are frustrated. This is wasting time. We know what to do. And the session becomes theater. People go through the motions. They put up stickies. But nobody commits because the work did not need pull planning. It needed simple coordination. Three hours wasted. Trust damaged. And the team leaves thinking pull planning is bureaucratic nonsense. The superintendent wonders why lean techniques do not work. The answer is simple. He used the wrong tool for the job. Pull planning is brilliant for complex coordination where handoffs are unclear. It is wasteful for standardized work everyone already understands. And teams that do not know the difference burn credibility trying techniques that do not fit the problem.

The real pain is the lost coordination. Pull planning done correctly forces trades to identify handoffs explicitly. Mechanical commits: we need structural complete, sprinkler drops installed, and electrical conduit roughed in before we can hang duct. Plumbing commits: we need walls framed and mechanical overhead complete before we can run drain lines. Electrical commits: we need structural open and mechanical coordination complete before we can pull wire. Every handoff gets documented. Every constraint gets addressed. And when someone says they need something, the responsible party either commits to providing it or flags that they cannot. This creates clarity. Everyone knows what they are giving and what they are receiving. And when work starts, it flows because handoffs were negotiated up front instead of discovered mid-execution.

The failure pattern is predictable. A team hears about pull planning at a conference. It sounds great. Collaboration. Commitment. Visual management. So they schedule a session. But they skip preparation. Nobody does homework. Nobody understands the rules. And when people show up, the facilitator tries to explain pull planning while simultaneously running the session. Chaos follows. People do not understand the backward pass. They put up activities in random order. Nobody identifies constraints. Handoffs get missed. And after four hours, the team has a wall full of stickies that mean nothing because nobody committed to anything. The facilitator wonders why pull planning failed. It did not fail. The preparation failed. Pull planning requires homework, facilitation, and trust. Without those elements, it is just expensive theater that wastes time and burns credibility.

I learned pull planning at the cancer center with Last Planner System. Then at DPR on the Bioscience Research Laboratory. And I have done it backwards from milestones, forward, on physical boards, in Excel, in vPlanner, in Smartsheet, with stickies, dry erase, slats, cards, and laminated cards. I have run sessions in person and virtually during COVID. And here is what I know. Pull planning works brilliantly when you need it. And it wastes time when you do not. The key is knowing when each planning technique fits. Master schedules with milestones work best as Takt plans because Takt manages flow and staggers. Phase planning between milestones can use pull planning when coordination is complex and handoffs are unclear. Weekly work plans and daily plans use make-ready and constraint removal. And you choose the technique that fits the problem. Not the technique that sounds impressive.

This matters because construction cannot afford to waste time on planning theater. Projects need real coordination. Real commitments. Real handoffs. And pull planning delivers that when used correctly. But when teams confuse techniques or skip preparation, they get theater instead of coordination. Trades sitting in rooms putting stickies on walls without understanding why. Leaders facilitating sessions without preparation. And projects that leave with pretty boards but no actual commitments. This destroys credibility for lean methods. Because when pull planning fails due to poor execution, teams conclude that lean does not work. When the truth is simpler. The tool was either wrong for the job or implemented poorly. And both problems are fixable. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

What Pull Planning Actually Is

Pull planning is a technique for phase planning where trades work backward from a milestone identifying handoffs and committing to durations. It is not the same as phase planning. Phase planning is what you do. Planning phases of work up to milestones. Pull planning is how you do it when coordination is complex. You can phase plan with flow using Takt. You can phase plan with pull planning when handoffs are unclear. You can phase plan with traditional methods. The technique changes based on the problem. But the goal remains constant: plan the phase between milestones so work flows without delays.

The key to pull planning is working backward. Start with the milestone on the right. What is the last activity before we reach this milestone? Mechanical says: final connections and testing. What do you need before you can do that? We need all equipment installed, all duct hung, all controls wired. Who provides that? Our crew handles equipment and duct. Electrical handles controls. So electrical puts up a sticky: wire mechanical controls. What do you need before you can do that? We need mechanical equipment locations finalized and conduit roughed in. Who provides that? Mechanical provides locations. We rough our own conduit. And the backward pass continues. Each activity identifies what it needs. Each need becomes a predecessor activity. And the chain builds backward until you reach the phase start.

David Amstot and Dan Fauchier explain in Lean Project Delivery: “It is far better to discover the issues in planning than during work execution.” That is the power of the backward pass. When mechanical says we need sprinkler drops installed before we can hang duct, and fire protection says we cannot install drops until structure is complete, and structure says we will not be complete for three more weeks, you discover the problem now. On stickies. Where fixing it costs nothing. Instead of discovering it in the field when mechanical shows up ready to hang duct and realizes sprinkler drops are missing. Now the problem costs money and schedule. Pull planning shifts problem discovery left into planning where solutions are cheap.

How to Run Pull Planning Correctly

Preparation is everything. Before the session, every participant must do homework. Use a pull planning worksheet that asks: What are your major activities for this phase? What is the approximate duration of each activity? What do you need before each activity can start? Who provides what you need? Participants fill this out before the session. They think through their workflow. They identify constraints. And they show up ready to negotiate instead of discovering their needs live during the session. This cuts session time in half and doubles quality because people have already thought through their sequences.

Setup requires clear rules. Choose your medium: physical board with stickies, Bluebeam session, Concept Board, or vPlanner. Create swim lanes. Common options include geographical lanes showing different floors or areas, discipline lanes showing each trade, or package lanes showing design or procurement packages. Assign colors to each discipline. Mechanical gets blue. Plumbing gets green. Electrical gets yellow. Fire protection gets red. And create a milestone card on the right side of the board showing the phase end date and conditions of satisfaction. Everything works backward from this milestone.

The backward pass follows specific steps. Start with the milestone. Ask: what is the last activity before we reach this milestone? The responsible party creates a sticky with: activity name, crew size, duration in days, and ID number. Then ask: what do you need before this activity can start? List constraints on the sticky. Then ask: who provides what you need? That party creates predecessor stickies. Continue backward until the phase start. Every sticky must have: organization doing the work, activity description, duration, ID number linking to downstream activities it enables, and constraints that must be resolved before work starts. Activities longer than ten days get broken into smaller subtasks. This creates accountability and enables flow.

After the backward pass comes the forward pass. Work left to right verifying logical sequence. Check for opportunities to compress schedule by reallocating resources to critical path activities. Verify handoffs are clear and achievable. And confirm everyone commits to their durations assuming they receive what they need. This is where trust matters. People must believe others will deliver what they promise. Without trust, commitments are hollow. So if trust is low, take time to build it before running pull planning. Because pull planning without trust produces pretty boards but no actual coordination.

Signs You Need Pull Planning vs Other Techniques

Use pull planning when coordination is complex and handoffs between multiple disciplines are unclear:

• Major MEP rough-in on complex buildings where mechanical, plumbing, electrical, and fire protection must coordinate sequences tightly
• Design phases where architects, engineers, and consultants must hand off deliverables in specific sequences to meet milestones
• Site logistics on tight urban sites where multiple trades share limited laydown and access requiring precise sequencing
• Complex architectural finishes where multiple specialty trades must coordinate in specific sequences to avoid rework
• MRI or clean room installations where sequencing and contamination control require extremely tight coordination between trades
• Any work where asking “what do you need before you can start” produces answers that require negotiation between multiple parties

Do not use pull planning for standardized repetitive work where everyone already knows the sequence and handoffs are clear. Framing standard floors does not need pull planning. The sequence is known. Use simple coordination instead.

Common Pull Planning Mistakes That Kill Results

Watch for these patterns that turn pull planning into wasteful theater instead of productive coordination:

• Skipping homework so participants show up unprepared and discover their workflow live during the session wasting hours
• Facilitating sessions without clear rules so people put activities in random order instead of working backward systematically
• Using pull planning for simple work that does not need it and burning credibility when people see it as bureaucracy
• Creating beautiful boards but never using them afterward so commitments evaporate and coordination fails anyway
• Running sessions without trust so commitments are hollow and people do not actually believe others will deliver
• Confusing pull planning with phase planning and thinking they are the same thing instead of understanding pull planning is one technique for phase planning

These mistakes are fixable. Send homework templates before sessions. Train facilitators on the backward pass. Use pull planning only when coordination complexity justifies it. Hold teams accountable to use the plans they create. Build trust before running sessions. And understand that pull planning is a tool in the toolbox, not the only way to plan.

The Virtual Pull Planning Method

Virtual pull planning works when setup is correct. Create a shared digital workspace: Bluebeam session, Concept Board, or vPlanner. Send pull planning worksheets before the session asking participants to list activities, durations, and needs. Set up swim lanes showing disciplines, areas, or packages. Create a color legend. And establish ground rules: work backward from the milestone, identify constraints explicitly, commit to durations assuming needs are met, and negotiate handoffs until everyone agrees.

During the session, start with the milestone. Have the final trade create their last activity. Ask what they need. Have responsible parties create predecessor activities. Continue backward systematically. Use ID numbers linking activities so you can track which predecessors enable which downstream work. And after the backward pass, run the forward pass left to right checking logic and identifying schedule compression opportunities. Then export the plan into your scheduling tool or use it directly for make-ready planning.

The advantage of virtual pull planning is documentation. Physical boards with stickies disappear. Virtual boards persist. You can update them. Share them. And reference them during execution. The disadvantage is engagement. People zone out on video calls. So facilitate actively. Call on people. Ask questions. Keep energy high. And limit sessions to three hours maximum. Brains cannot handle longer virtual coordination sessions productively.

When to Flow, Pull, or Push

The hierarchy is simple: flow where you can, pull when you cannot, and push when you must. Flow is best. Takt planning creates predetermined sequences and staggers that manage supply chains and enable continuous workflow. Use flow for standardized repetitive work where the sequence is known and stable. Pull is second best. Use pull planning for complex coordination where handoffs are unclear and need negotiation. Pull creates commitments that enable flow once sequences are established. Push is last resort. CPM schedules that push work based on predetermined dates without regard for downstream readiness create chaos. Use push only when flow and pull are impossible.

Most projects need all three. Master schedules work best as Takt plans managing flow and milestones. Phase planning between milestones uses pull planning when coordination is complex. Weekly work plans use make-ready and constraint removal. Daily plans use huddles and real-time coordination. And you choose the right tool for each level. Not the tool that sounds impressive. The tool that fits the problem. That is how championship teams plan. They know when each technique works. And they use techniques appropriately instead of forcing every problem into one solution.

The Challenge

Walk into your next coordination challenge and ask: does this need pull planning? If handoffs are complex and unclear, schedule a session. Send homework worksheets asking participants to identify activities, durations, and needs. Set up the board with swim lanes and color coding. Facilitate the backward pass systematically working from milestone to phase start. Run the forward pass checking logic. And then use the plan. Hold people accountable to commitments. Update it when conditions change. And reference it during execution. Because pull planning only works if you actually use what you create.

As Amstot and Fauchier said, “It is far better to discover the issues in planning than during work execution.” So discover them. Run pull planning when you need it. Skip it when you do not. And remember the hierarchy: flow where you can, pull when you cannot, and push when you must. Because construction rewards teams that choose the right tool for the job. Not teams that force every problem into one technique regardless of fit. Know your tools. Use them appropriately. And build projects that flow instead of fighting. On we go.

Frequently Asked Questions

What is the difference between pull planning and phase planning?

Phase planning is planning work between milestones. Pull planning is one technique for doing phase planning when coordination is complex and handoffs need negotiation between multiple parties.

When should you use pull planning vs Takt planning?

Use Takt for standardized repetitive work where sequences are known and stable. Use pull planning for complex coordination where handoffs are unclear and need negotiation.

How does the backward pass work in pull planning?

Start with the milestone, identify the last activity, ask what it needs, have responsible parties create predecessor activities, and continue backward systematically until reaching the phase start.

What information goes on each pull planning sticky or tag?

Organization doing the work, activity description, crew size, duration in days, ID number linking to downstream activities, and constraints that must be resolved before starting.

Why do pull planning sessions fail?

Most failures come from skipping homework preparation, facilitating without clear rules, using pull planning for work that does not need it, or creating plans that never get used afterward.