Grace Design Studios · Module 7 of 12

The Pull-Plan Builder

Project Planning 2 — Companion Reference & Interactive Tool

The LBP frameworksBuild a pull planNeeds & providesBiweekly work plan

The five LBP frameworks

Logic-Based Planning runs in five frameworks, sequenced from the whole phase down to this week’s work. Each keeps the team aligned to the deliverables that matter.

Framework 1

Phase Milestone Planning

Set the phase schedule; define “done” per deliverable (Deliverable / QA checklist).

Framework 2

Intermediate Milestone / Pull Planning

Find 30/60/90% checkpoints; separate deliverables from information; reverse-sequence to the critical path.

Framework 3

Biweekly Work Planning

Each discipline plans its parallel work in a rolling two-week look-ahead.

Framework 4

Information Flow Management

Move the right information between disciplines on time, so no one stalls.

Framework 5

Work Plan Review

Revisit and adjust on a cadence — planning is a process, not an event.

The pull-plan builder

Pull Planning sequences work backward from a milestone. Each row is a handoff: a discipline needs something, then provides something in a stated duration. The rows are listed in pull order (milestone first). The tool sums the critical-path durations and tells you how early the chain must start. It’s seeded with the Oakhaven 30% DD example — edit it, or build your own.

DisciplineNeeds (from upstream)Provides (downstream)Days
Critical-path duration
0 days
Handoffs
0

Durations sum the critical-path design work. Add the client/owner review window (shown as the last handoff) to find the true start-by date. Reverse-sequencing exposes the decision that gates everything — while there’s still time to force it.

Needs & provides — 30% DD

At each intermediate milestone, every discipline declares two lists: what it needs from the team, and what it provides to the team. These are the raw material of the pull plan.

DisciplineNeeds from othersProvides to the team
ArchitectureEquipment for preliminary bidding; initial structural sizing/depth; initial MEP system sizing; initial code review.Initial code-compliance plan; initial floor plan; elevations; preliminary wall construction type.
StructuralLateral frame locations; non-standard opening locations; roof/floor-to-floor heights; locations & weights of mechanical loads.Initial column grid; bearing-wall locations; initial framing scheme; shear-wall locations.
MechanicalMechanical room locations identified; preliminary equipment locations.Main piping & duct routes/sizes; major equipment layout; exhaust/pump locations; initial heating/cooling system.

Intermediate milestones are not print deadlines — they are checkpoints where certain things must be determined for the team to reach the phase deliverable.

The biweekly work plan

The milestone plan holds only the shared, critical handoffs. Each discipline’s parallel work lives in its own biweekly plan — a rolling two-week look-ahead pulled back from its milestone commitments.

Look ahead 2 weeksStarting Monday, plan the tasks through the following Friday — pulled back from your milestone commitments.
Work the weekExecute the current week against the plan; protect the critical handoffs you owe the team.
Drop & addAt week’s end, drop the finished week, confirm next week, and add one new week to the end.
Stay alignedEvery group always has a two-week view, plans just one new week each week, and stays oriented to the milestone plan.

The biweekly plan becomes the source of truth for each discipline’s work between milestones — fast to maintain, decluttered, and visible to every other group without intermixing.