Pull Planning Step-by-Step for Construction (Last Planner®️ Made Simple)

Pull Planning Step by Step: Last Planner Made Simple

Pull planning is one of the most powerful tools in the Last Planner System. When it is done right, it produces a sequence that trade partners helped build, a production plan they are committed to, and a set of constraints that are optimized before the first crew enters the first zone. When it is done wrong and it is done wrong on most projects it produces a large-batch exercise that wastes days, disconnects from the milestone it was supposed to hit, and generates a plan that nobody in the field actually uses. Here is how to do it right, step by step.

The Pain of Pull Planning the Wrong Way

Most pull planning happens in a large room, with sticky notes covering an entire wall, covering the whole building or the whole phase at once. Trades sit through a multi-day session, the facilitator tries to coordinate a hundred different activities across a massive area, and by the end of it, everyone is exhausted and the resulting plan is so unwieldy that it gets filed and forgotten within two weeks. The weekly work plans that follow are invented fresh each time because nobody can figure out how to filter from the pull plan they just did. Percent plan complete suffers. Trades lose faith in the process. And the team concludes that pull planning is too slow or too complex to be worth doing consistently.

That is not a pull planning failure. That is a facilitation method failure. The pull plan was done for the wrong unit the whole building instead of one zone and in the wrong format batching days into single activities instead of a sticky per day. The system was set up to fail the team before the meeting even started.

The Failure Is in How It Was Taught

Pull planning is widely taught as an in-person, large-batch, whole-phase exercise. That teaching comes from good intentions and a genuine commitment to collaboration, but it misses what the system actually needs to produce: a verified, zone-by-zone sequence with diagonal trade flow, confirmed by a forward and backward pass, that can be tiled across all zones in the phase and compared against the end milestone to verify that buffers have been gained. Doing that for the whole building at once is not collaborative it is overwhelming. Doing it one zone at a time, digitally, with a sticky per day, is the approach that produces a plan the team can actually execute.

The trades who struggled inside the old approach were not bad at pull planning. They were asked to plan in a format that was never designed for the outcome they needed. The system failed them.

What to Prepare Before the Session Begins

The pull plan does not start the day of the meeting. It starts with homework preparing the trades and the facilitator before anyone sits down together. The macro Takt plan needs to be current, with the end milestone for the phase, the base sequence, and the line of balance already established. The zone maps need to be ready. The team needs to have an idea of the preferred number of zones going into the discussion. And the trades should know their scope well enough to declare their activities on the spot without having to reconstruct their scope from memory in the room.

Additionally, before the session begins, the rules of the pull plan should be established with the group. Every facilitator has a slightly different method, and every group of trades comes in with different experiences. Setting the rules together at the start how stickies get declared, how needs get communicated, how disagreements get resolved, how the digital board gets managed keeps the session from descending into chaos and keeps everyone psychologically safe enough to contribute honestly.

Zone First, Then Sequence

The most critical thing to establish before the pull plan begins is the zone strategy. This conversation happens with trade partners collaboratively the facilitator comes prepared with an idea of the preferred zone count, and then opens a discussion using the Takt calculator to show what different zoning strategies produce in terms of phase duration. When trades can see that moving from five zones to eleven zones shortens the overall phase duration while giving them the same or more time in each zone, the conversation shifts from resistance to engagement. They are no longer being told what to do. They are seeing the math and choosing together.

Once the zone strategy is confirmed, the pull plan proceeds for a single zone. Not the whole phase. One zone. Everything else replicates from that one zone and gets adjusted at the zone-to-zone comparison stage. This is the principle that most pull planning misses, and it is the one that makes everything else in the system work.

The Forward Pass: Declaring Activities

The forward pass is where trades declare what the job needs. The facilitator asks each trade partner: what is the first activity in your scope for this zone, and how many days does it take? One sticky per day. Not five days batched into one sticky one sticky per day, with the activity name and duration on it. The format on every sticky is: duration, activity name, and when the backward pass happens, the needs that must be satisfied for this activity to execute.

This format matters because it is what allows the forward and backward passes to connect cleanly. When every sticky is a single day with a specific activity, the team can see at a glance whether the sequence is realistic, whether any day is overpacked, and where gaps exist. Batching multiple days into a single sticky obscures all of that. It creates an illusion of planning without the granularity that makes a plan executable.

The facilitator does not tell the trades how much time they have. They declare it. The role of the facilitator is to make sure the declarations are captured accurately, that the sequence is logical, and that the forward pass produces a complete picture of what is needed in the zone before moving to the backward pass.

The Backward Pass: Confirming Needs

Once the forward pass is complete for the zone, the backward pass begins. Starting from the last activity and working toward the first, the facilitator asks each trade: what do you need in order to execute this activity? At least two needs per activity, declared by the trade and typed onto the sticky. The facilitator then checks whether each declared need appears earlier in the pull plan sequence. If it does, it gets a checkmark or a small marker confirming it is covered. If it does not, it gets added to the plan.

This is the moment when missing activities are found. The backward pass is a systematic verification that every dependency is on the board and that the sequence accounts for every requirement before it expects a crew to execute. When the backward pass is complete and every need is confirmed as satisfied somewhere in the forward pass, the team does one final check against the drawings running through the scope to make sure nothing has been left off. This double-check, done at the end of the zone pull plan, is what produces a complete sequence rather than an optimistic one.

Zone to Zone Comparison and Diagonal Trade Flow

Here is where the system becomes something more than a collaborative scheduling exercise. Once the single zone pull plan is complete, the facilitator copies it and staggers it across the subsequent zones. The team then looks not just at how well the trades perform within a zone, but at how they flow from zone to zone. This is the diagonal trade flow that makes Takt planning work each trade moving at a consistent pace from one zone to the next, with a stagger that creates rhythm and prevents stacking.

The facilitator checks for two specific problems. Trade stacking too many trades in a single zone at the same time creates crowding and stops flow. Trade burdening one trade spread across too many zones simultaneously overloads the crew and destroys their productivity. Both problems are visible when the pull plan is laid out zone by zone in a diagonal. Both problems can be fixed at the pull plan stage, before anyone sets foot in the field.

When the zone-to-zone comparison confirms that diagonal trade flow is achievable and that no stacking or burdening exists, the facilitator compares the full phase against the end milestone. If the pull plan has been done well, the phase will have shortened the train of trades will reach the milestone earlier than the macro plan predicted, and buffers will have been gained in the process. The trades did not lose any time in their zones. The phase simply became more efficient because the sequencing was optimized.

What Happens After the Pull Plan

Every constraint that existed at the start of the pull plan should be optimized by the end of it. The varying speeds between trades should have been addressed in the zone sizing. The sequence gaps should have been filled in the backward pass. The zone count should be confirmed with the calculator. The milestone should be verified. Everything that follows the pull plan the look-ahead, the weekly work plan, the day plan is now filtering from a real production plan built collaboratively by the people who will execute it.

After the pull plan, the team’s focus shifts entirely to roadblocks. Constraints are system-design issues that belong in the pull plan. Roadblocks are temporary obstacles that appear ahead of the train of trades and must be removed before the crew arrives. Keeping these two categories clean means the system stays actionable all the way through to the end of the phase.

The book Pull Planning for Builders and the accompanying free templates and board formats cover this in full detail. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

A Challenge for Every Project Team

Before your next pull planning session, ask one question: are we planning the whole phase or one zone? If the answer is the whole phase, stop and redesign the session. Pick one zone, plan it in detail with a sticky per day, run the forward and backward pass, compare it zone to zone, verify the diagonal trade flow, and confirm the milestone. The session will be shorter, faster, and more useful than anything done the old way.

Taiichi Ohno said, “Where there is no standard, there can be no improvement.” The zone-by-zone pull plan, done digitally with a sticky per day, is the standard. Build it that way and the production plan will follow.

On we go.

Frequently Asked Questions

Why is digital pull planning better than in-person sticky notes on a wall?

Digital pull planning is faster, easier to replicate across zones, and produces a format that can be directly imported into the production plan. It also makes the diagonal trade flow comparison zone to zone far easier to visualize and adjust than a physical wall of sticky notes.

Why must pull planning be done by zone instead of by whole building or phase?

Because batching the whole phase into one pull plan produces a sequence that is too large to verify, too disconnected from zone-level reality, and too difficult to tile correctly across the train of trades. One zone planned correctly replicates accurately across the whole phase.

What is the difference between the forward pass and the backward pass?

The forward pass declares what the job needs each trade’s activities in sequence, one sticky per day. The backward pass confirms what each activity needs the dependencies that must be satisfied before that activity can execute. Together they produce a complete, verified sequence.

How does pull planning eliminate constraints?

By optimizing zone sizing, trade sequencing, stagger between zones, and Takt time during the session itself. By the time the pull plan is complete, the system-level constraints should be resolved or identified as the most limiting factor that has been optimized as much as possible.

What happens if the pull plan reveals that the milestone cannot be hit?

That is valuable information that belongs in the pull plan room, not on the field at the end of the phase. The team adjusts zone sizing, trade speed assumptions, or sequencing during the session until the milestone is achievable or brings that constraint back to the first planner team with data rather than hope.