Part I — Foundations

The Industry, Its Contracts, and Its Rules

There is a temptation, when you start learning construction management, to go straight to the interesting part. Concrete. Cranes. The schedule. The thing you can point at.

Resist it for seven chapters.

Here is why. Almost every expensive problem on a construction project has already been decided before anyone shows up with a shovel. The delivery method decided whether the contractor was in the room during design. The contract decided who pays when the soil is not what the report said. The general conditions decided how many days of notice you get before your claim evaporates. The drawings and specifications decided what "complete" means, and whether those two documents agree with each other.

By the time a problem reaches the field, it is usually not a field problem. It is a paper problem that has been waiting patiently for its moment.

Part I is about that paper.

What is in this part

Chapter 1 answers the basic question — what does a construction manager actually do all day — and introduces the project that runs through the whole book: the Northgate Outpatient Pavilion, a $47.5 million medical building, and the team that is about to build it. It also introduces the number that should live in your head permanently: $10,650 per calendar day, which is what one day of delay costs on that job.

Chapter 2 is the business context. Why margins in this industry are so thin that a single bad week can erase a good quarter. Why everyone subcontracts. Why money moves so slowly. Why contractors chase revenue, and why growth kills more of them than recession does.

Chapters 3 and 4 are the two halves of one decision: who owns which risk, and what does that cost? Design-bid-build, design-build, CM at risk, and integrated project delivery are not four ways to organize a project — they are four different answers to that question. Lump sum, guaranteed maximum price, cost-plus, and unit price are four more. Together they set the price before the first estimate is written.

Chapter 5 is the legal framework: liens, bonds, insurance, notice provisions, and how disputes actually get resolved. It is the chapter that will save you the most money and the one most readers want to skip. It repeats, more times than you will enjoy, that this varies by jurisdiction and that you must check yours. That repetition is not padding. It is the actual state of the world.

Chapter 6 takes the theme running under all five of those chapters and turns it into a method: a risk register, expected value, and an honest treatment of contingency as a priced, owned, drawn-down reserve for named risks rather than a comfortable cushion of fat.

Chapter 7 teaches you to read a set. Four hundred and eighty sheets of drawings and nineteen hundred pages of specifications, and the discipline of finding the eleven places where they disagree before somebody builds one of them.

The thread

Every chapter in Part I is a different view of the same question:

Who owns this risk, what does it cost, and where is that written down?

If you can answer those three parts for any situation on a construction project, you are most of the way to being good at this job. Part I is where you learn to ask them.

What you should be able to do at the end of Part I

  • Explain what a construction manager does, and where the role sits under each delivery method.
  • Read a project's delivery method and contract type and predict, before you see a single drawing, which risks are yours.
  • Translate a general-conditions clause into plain English and name the dollar consequence.
  • Find the notice requirements in a contract and put them on a calendar.
  • Build a risk register with named owners, expected values, and a defensible contingency.
  • Open a set of construction documents, find the order-of-precedence clause, and systematically hunt for conflicts between the drawings and the specifications.

That is not a small list. It is also entirely paper. The dirt starts in Part II.

Chapters in This Part