Module 5 · Live Session Recap

A recap of the August 20 call, for anyone who could not attend.

Module 5 Live Discussion · What the Cohort Covered

A recap of the fifth live discussion, built around one live demonstration: what happens once a project’s hours connect to its actual tasks. This summary carries the substance of the full hour.

Meeting RecordingFull August 20 discussion · 1h 33m
August 20, 2026~6 minute readLive Discussion · Module 5
← Back to Module 5

Where the Room Started

The cohort already runs a planning process

The session opened with one question: what tool works for you today, beyond the Grace process in the videos? The room answered with three real habits already in use.

A sheet list, staffed by discipline

List every sheet a project needs, and assign hours to each one. Plans and elevations go to one person. Sections and details go to another. No two people work the same sheet.

An internal kickoff, before the client one

Run an internal kickoff early, with a group wider than the core team. It catches tasks that do not look traditional, like custom wall graphics on a school project, before they get missed.

A weekly connect, shared with QC up front

Run a weekly team connect, and send the schedule to the QC reviewer before QC starts. Architecture and interiors plan together, as one team, not two.

One exception to roles over names came up. Plan the spec writer and the QC reviewer by name, early. There are only so many of them on staff. Know who they will be before you need them, and share the schedule the moment you know it.

The Gap the Room Named

A role carries a rate. A person carries availability. Nothing ties them together yet.

Some PMs track tasks in Microsoft Teams. Others use Planner. Both tools sit apart from the project’s budget and hours. One question pushed further: once a role turns into a real person, does the plan still know what that person costs, and whether they are even free?

The Scheduling HalfBST has a resource heat map

Its limit is clear: the heat map only earns its value once enough PMs enter real project data. Until then, checking whether someone is free is still a one to one conversation.

The Judgment HalfA named plan breaks the moment someone leaves

This question had no clean answer. A person on the plan can move to another project, or go out for personal reasons, at any time. No fix emerged beyond building in a buffer.

The work drives who you need. Not the other way around.

The standing rule, demonstrated moments later: staff a project because a piece of work is ready for someone, not because a person needs something to do.

A related risk came up. A heat map can find an available PA1. It cannot tell you if anyone has worked with them before. There is no silver bullet for that, only extra teaching and review time budgeted for someone new to the team.

The Demonstration

Two missing pieces, shown on one Oakhaven phase

A working mock planning board was built live, for Oakhaven’s 13 week DD phase, to show what happens once a phase’s hours connect to its actual tasks. Two steps do not exist in any current Grace tool. Everything else, the room already had.

Work packages, not just hours
A schedule, in critical path order
A heat map, driven by the schedule

Elevations and sections became one work package: three weeks, the named roles, and a cost of $20,165. One line from the room summed up why this matters: “you can eat the elephant.” Track what is done, and what has been spent, at the halfway point.

Floor plans before interiors. Interiors before QC. The room named the result before it was labeled: critical path. Convert that order to a Gantt chart, and staffing demand for every week appears on its own. Nobody has to guess it.

The room caught the real problem live, before it was pointed out. Week 3 sat on Thanksgiving. Weeks 7 and 8 sat on Christmas. The plan overloaded two holiday weeks by accident, not by anyone’s choice.

Moving work did not clean the plan up. It moved the pressure.

The hours were redistributed on screen. The best case still left the team at 52, 52, and 43 hours across three straight weeks. That number stayed on screen on purpose: a good plan does not guarantee an easy one, it lets a PM see the problem in week one, not the week before Thanksgiving.

One line on rework landed hardest: staff running ahead of decisions, on tasks that are not really ready, is the number one cause of rework on a project. The answer for the room: break the phase into work packages, then schedule when each one finishes. Grace’s existing tools already carry the rest.

Take It With You

Project Planning on One Page

Everything Module 5 covered, on a single sheet: Grace’s process from a signed fee to a live plan in BST11, the seven step method with what to watch for at each step, and the four traps that break a plan before it starts.

The one sheet

Read it here, or keep the PDF

The browser version opens the full sheet and scales to your window. The PDF prints at 17 × 11 inches and holds its type at that size, which is the one to pin up next to your desk.

What is on it

  • Grace’s process — signed fee to a live plan in BST11, in four steps.
  • The seven step method — Part A sets what, which role, and how much. Part B sets when, and who.
  • Soft resource vs hard resource — one prices the work, the other confirms the roster can deliver it.
  • The three plans — financial, task, and resource, with the constraint that binds each one.
  • Four traps — and the fix for each, plus the standard to plan against.

The Honest Answer on Tools

The board is a teaching tool. The gap it points to is still real.

One pointed challenge came from the room: what was demonstrated does not exist as a tool the cohort can use today. That is true, without hedging. The project budget spreadsheet, the phase roadmaps, and BST’s scheduling and heat map already exist. The one missing step, turning a task list into a schedule, is manual PM judgment. That is not expected to change, whatever software the firm buys next.

The floor closed on the room’s real advantage: no tool has been mandated yet. Whatever works, whatever a PM builds or finds, still counts, as long as BST gets what it needs to run the firm responsibly.
  • 1
    No new module content tomorrowModule 6, Communication Planning, opens Friday as scheduled, with a lighter load. Modules 4 and 5, the two heaviest, are behind the cohort now.
  • 2
    Ask before you copy the planning boardIt is a teaching tool, not an operational one. Ask for help if you want to build your own version, as a test case on a real project.
  • 3
    Keep entering real project data in BSTThe resource heat map, like any tool built on aggregated data, only gets useful once a critical mass of PMs are using it on real projects at the same time.
  • 4
    Next live session, next ThursdaySame time, same call. Module 6 opens the content the day before it.