Part V — Running the Project

Communication and the Record

Here is an uncomfortable claim, and this part of the book will try to earn it:

Most construction failures are communication failures wearing a technical costume.

The steel arrived twenty-three days late on the Northgate job. That is a procurement failure, or a fabrication failure, or a scheduling failure — depending on who is telling the story. But trace it back far enough and it is none of those. A submittal sat on a desk for eleven days because it was underneath other paper, and nobody had built a system that would surface it. The engineer then took a full fourteen-day review because nobody had negotiated a shorter one for the item that gated a mill slot. Every hard consequence downstream — the acceleration, the $168,000, the trade stacking, the spike in near-misses in weeks 34 through 36 — descends from an information-handling failure in an office.

Part V is about the three systems that handle information on a construction project: the document control system, the meeting and reporting system, and the planning system that decides what work is actually ready to do.

The three chapters

Chapter 25 — Submittals, RFIs, and Document Control. The most under-taught, highest-leverage administrative skill in the industry. How a submittal log is built by back-scheduling from required delivery dates rather than by transcribing the specification's table of contents. How to write an RFI that gets a usable answer in one round instead of three. How to run drawing revisions so that no crew ever builds from a superseded sheet. And the threshold concept: the paper trail is the project's memory, and contemporaneous records are worth ten times reconstructed ones.

Chapter 26 — Meetings and Field Documentation. The meetings that actually run a job — the owner- architect-contractor meeting, the subcontractor coordination meeting, the pre-installation conference, the pull-planning session — and how to run each so it produces commitments with names and dates rather than a list of topics discussed. Then the daily report, which is the single most valuable document a project produces and the one most often filled out badly at 4:55 p.m. by someone who wants to go home.

Chapter 27 — Lean Construction and the Last Planner System. Why a CPM schedule tells you what should happen and a constraint log tells you what can. Pull planning, the six-week look-ahead, the weekly work plan, making work ready, percent plan complete, and the discipline of measuring your own reliability. Its threshold concept reframes everything in Part III: the schedule is a plan, and the constraint is what makes the work actually available.

The two failures this part exists to prevent

Failure one: the record that was never made. Eight weeks after the imaging-suite slab was poured under a verbal directive, Kestrel could substantiate $121,000 of the $186,400 it had actually spent. It settled for $142,750 and ate $43,650 — not because the work was not real, but because the record was not. The price of a change is set by what you can document, not by what it cost you.

Failure two: the plan that was never made ready. A schedule bar says drywall starts Monday. On Monday the crew arrives and the in-wall inspection has not been called, so they stand there. That is not a scheduling error. It is a constraint error, and no amount of CPM sophistication catches it, because CPM assumes that when a predecessor finishes, its successor is ready. On a real job, it very often is not.

A note on tone

These three chapters are about paperwork, meetings, and planning boards. They are, on the face of it, the least glamorous material in the book.

They are also where good project managers are separated from mediocre ones. Anyone can pour concrete in good weather. What distinguishes a manager is whether, four months from now, they can produce the document that shows they gave notice on the eleventh, that the answer came back on the twenty-eighth, that the crew was idled for six days, and exactly what that cost.

Everyone knows this. Almost nobody does it consistently. That gap is your opportunity.

Chapters in This Part