Grace Design Studios · Module 5 of 12 · Part B

Quick Reference · The Pull-Plan Builder

Planning Process · Part B · Companion Reference Guide

The LBP frameworksA worked pull planNeeds & providesBiweekly work plan
1

Steps 5 to 7

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. The five frameworks are how you Control Advancement across a phase, and they carry Steps 5 through 7 of the seven step plan.

Framework 1

Phase Milestone Planning

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

Framework 2

Intermediate Milestone / Pull Planning

Find the intermediate checkpoints inside the phase. 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 continuing process.

Planning Studio · Frameworks 2 to 5, run live

Planning Studio 2 runs this stack on Oakhaven DD: milestones planted first, the phase pull plan built backward from them, and the labor demand your biweekly work plans will have to honor. The hours committed in the Part A Studio supply the people. Open Planning Studio 2 →

2

A worked example

A worked pull plan

Pull Planning sequences Grace’s own work backward from a milestone. Architecture’s tasks are planned in detail. Structural and Mechanical are outside consultants on Oakhaven: Grace tracks the commitment, what they owe the team and by when, not how they plan their own work internally. Below is the Oakhaven 50 percent progress set, read exactly as you will read your own.

Grace does not plan the work of outside consultants. Rows tagged Consultant track what they owe the team and when, a commitment, not a task Grace schedules for them.

Milestone · 50% DD Progress Set

Direction of planning
DisciplineNeeds (from upstream)Provides (downstream)Days
MilestoneMilestoneThe 50% progress set must be reachable—0
Pull 1Structural ConsultantInitial floor plan (Arch)Shear-wall locations3
Pull 2ArchitectureEquip sizes, clearances & room req’ts (Mech)Initial floor plan3
Pull 3Mechanical ConsultantMechanical system selection (Owner)Equipment sizes & room req’ts2
Pull 4OwnerThree system options (PM)System selection10
Pull 5Project ManagerInitiates the chainThree system options to owner0
Direction of work
Critical-path duration
8 days
Handoffs
5
Critical-path design work totals 8 working days, behind a 10-day client/owner review. The chain must start about 18 working days before the milestone, and that start date is the PM’s to protect.

Durations sum the critical-path work: Grace’s own tasks plus the consultant commitment windows. The client/owner review window (Pull 4) is added separately to find the true start-by date. Reverse-sequencing exposes the decision that governs everything, while there is still time to force it. Build your own chain in Planning Studio 2.

Planning Studio · This builder, with a checker

The Pull pass of Step 5 is this pull-plan builder with prerequisite intelligence: deadlines derive from your milestones, QAQC weeks are reserved before you place a single bar, and every violation is named in plain language. The checker reports what starts before its input exists, what finishes inside a review week, and what breaks the milestone. Try it yourself before letting it pull-plan for you. Then lock it and watch the Post pass sort your network into the Gantt. Build the pull plan →

3

The raw material

Needs & provides · the 50% progress set

At each intermediate milestone, Grace’s own disciplines and its outside consultants each declare two lists: what they need from the team, and what they provide to it. For Grace’s own work, these lists drive detailed task planning. For consultants, they are commitments Grace tracks, not tasks Grace plans.

Grace does not plan the work of outside consultants. Rows tagged Consultant track what they owe the team and when, a commitment, not a task Grace schedules for them.

DisciplineNeeds from othersProvides to the team
Architecture GraceEquipment 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.
Structural ConsultantLateral 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.
Mechanical ConsultantMechanical room locations identified, preliminary equipment locations.Main piping & duct routes/sizes, major equipment layout, exhaust/pump locations, initial heating/cooling system.

Intermediate milestones are checkpoints rather than print deadlines. At each one, certain things must be determined for the team to reach the phase deliverable. Grace plans its own rows in detail. Consultant rows are commitments to track, not schedules to build.

Planning Studio · Handoffs have a date and a format

The Studio flags every same-week handoff in your network amber, applying exactly this section’s discipline: legal but tight, so name the day and the format. Needs-and-provides turns those handoffs into commitments the team can plan against.

4

Between milestones

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, uncluttered, and visible to every other group without intermixing.

Planning Studio · From plan to people

The Studio’s labor demand table is the bridge from this page to the roster: every role’s committed hours, spread the way planned value lands, week by week, with hot weeks flagged wherever demand exceeds one full-time person. A one-click, cost-parity fix is available when it does. Write your first biweekly work plan against that table. See the labor demand →

5

What is left

Steps 6 and 7 · From role demand to the line

The frameworks above deliver Step 5, a sequenced schedule. Two steps remain, and both belong to Part B. Work them in Planning Studio 2.

StepThe question it answersWhat you doThe artifact
Step 6
Hard resource the plan
Which named people, in which weeks?Put names against the roles, week by week, and check that nobody is asked for more than one person can give. Flag every week over 40 hours and fix it before the phase starts.Labor demand table
Step 7
Draw the Earned Value Plan
How does the fee get earned?Weight each work package by its share of the fee, spread it across the sequenced weeks, and read the cumulative curve. That curve is the line you measure every week against.Earned Value Plan and S-curve

Soft resourcing (Step 3) asked what kind of person does the work. Hard resourcing asks whether the plan is physically staffable by the people Grace actually has. A budget that balances and a roster that cannot deliver it is still a plan that fails.