Preface

There is a moment on every project that I have never seen described in a textbook.

It is the moment you realize that the building in the drawings and the building on the site are two different things, and that closing the distance between them is your job, personally, and that nobody is coming to help.

Mine came in my second year. I was a project engineer on a school addition — not a big job, not a hard one — and I had a stack of submittals on my desk that I was working through in the order they arrived, which felt organized and responsible. One of them was for the gymnasium's laminated wood beams. It sat in my stack for nine days because it was on the bottom, and then it went to the architect, who took his three weeks, and then it came back marked "revise and resubmit" because the connection detail didn't match the structural drawings.

By the time those beams were approved for fabrication, the mill had moved on. We got a slot eleven weeks later.

The superintendent, a man about sixty who had been building schools since before I was born, did not yell at me. He took me to the gym slab, which was poured and cured and empty, and stood there with me for a while, and then said: "The whole rest of this job is standing behind those beams. What else is on the bottom of your stack?"

That is the question this book is about.

What this book is trying to do

Construction management is not a difficult subject in the way that quantum mechanics is difficult. Almost nothing in it is conceptually hard. What makes it hard is that it is wide — you have to know enough about soil, concrete, steel, ductwork, contracts, insurance, labor law, accounting, and human beings to make decisions in all of those domains, usually before lunch, usually with incomplete information, and usually with a real number attached to being wrong.

Most people learn it the way I did: badly, expensively, and out of order, by being handed responsibility slightly before they were ready and finding out afterward what they should have known. That method works. It produces excellent project managers. It just costs their employers a fortune and costs the person themselves several years of feeling stupid.

This book is an attempt to compress that. Not to replace the job site — nothing replaces the job site — but to give you the map before you are lost, so that when you do make the expensive mistake, you at least recognize it while it is happening.

Who I wrote it for

I wrote it for the field engineer in her first month, holding a set of drawings she does not fully understand, trying not to let anybody see it.

For the superintendent with twenty-five years in the field who is being asked to run the whole project now and has never built a cost report in his life.

For the estimator who is very good at numbers and has never been asked to explain why the schedule and the budget are the same conversation.

For the student who is going to graduate into this industry and would like to arrive knowing what a submittal log is for.

For the architect who wonders why the contractor keeps asking questions that seem obvious, and the owner's representative who wants to know whether the change order in front of her is fair.

And for the person who is about to build or renovate something with their own money and would like, very much, not to get taken. Appendix E is written directly for you, and you should feel free to start there and work backward.

What is different about it

It follows one project all the way through. Almost every construction management textbook teaches in topic order: here is estimating, here is scheduling, here is quality control. That is a reasonable way to organize a reference and a terrible way to learn a job, because on a real project none of those things happen separately. So this book follows the Northgate Outpatient Pavilion — a $47.5 million medical building — from the first conceptual estimate to the last warranty callback, and every topic arrives when the project needs it. Three other projects run alongside it: a hard-bid public school, a highway bridge, and a residential subdivision, so you can see the same principle behave differently when the contract and the market change.

It is honest about money. Every decision in this book has a number attached. When the steel is twenty-three days late, you will know that it costs $10,650 per calendar day and you will watch the team decide whether $168,000 of acceleration is worth it. When a change order gets built before it is priced, you will see the difference between the $186,400 it cost and the $142,750 that could be proven. Vagueness about money is the single most common failure in construction education, and it produces managers who cannot make the argument they need to make in the room where it matters.

It takes safety seriously in an unusual way. There is a chapter on safety management, and there are safety alerts throughout, but the book's actual position is stated in Chapter 24 and repeated everywhere: safety is a property of the production system, not a rulebook. The scaffold near-miss that runs through this book had three findings, and the third one — a crew running behind after an acceleration, under an unwritten pressure to make it up — is the one nobody wanted to write down. It is also the only one that would have prevented the next incident. If you take one thing from this book, I would like it to be that a schedule decision is a safety decision.

It says "it depends" and then tells you what it depends on. Construction law and practice vary by state, by country, by owner, and by market. You will see a lot of hedging in these pages about lien deadlines and pay-if-paid enforceability and retention limits, and that hedging is not evasion — it is the actual state of the world, and a book that gave you a confident national answer would be lying to you. What the book does instead is tell you which question to ask and who to ask it.

It has no code in it. Construction management runs on spreadsheets, scheduling software, estimating tools, and paper. Every calculation in this book is worked by hand, in a table, so that you understand what the software is doing when you let it do it for you. You will run a forward and backward pass on a CPM network with a pencil. That is on purpose.

What it will not do

It will not make you a structural engineer, and it does not try. Part II teaches enough about how buildings go together to manage the work — not enough to design it, and the difference matters.

It will not give you legal advice. It will tell you what a no-damage-for-delay clause does, and then it will tell you to call your attorney before you rely on that.

It will not promise you that if you do everything in it, your projects will go well. Some projects go badly for reasons no manager could have controlled. What good management buys you is that when the job goes sideways, you saw it coming, you wrote it down, you had a plan, and you can prove it.

A note about the people in this book

Everyone in these pages is invented. Ray Alvarez, whose voice narrates the book, is a composite of several project managers I have worked for and one I wish I had been earlier. Margo Deacon, the superintendent, is a composite of the field leaders who taught me most of what I actually use. Dani Okonkwo, the field engineer we follow from a first day to an assistant project manager's desk, is mostly me, and probably somewhat you.

Curtis Boone — the project manager who buys work low, shops his subcontractors, documents nothing, and manages on force of personality — is a composite too, and I want to say something about him directly. He is good at this job in several real ways. He is likable, he is fast, he wins work, and people follow him. He is not a villain and this book does not treat him as one. He is simply wrong about the model, and the book follows his job to the end so you can see exactly where and when being wrong about the model gets expensive. Most of us have a little Curtis in us. The chapters where he appears are not there to let you feel superior to him.

How to use it

Read Chapter 1, then read the "How to Use This Book" section that follows this preface, and pick your path. If you are working right now on a project and something specific is on fire, use the index and go straight to it — the chapters are written to stand alone well enough for that.

If you can, do the Willow Street project. It runs through all forty-two chapters, one deliverable per chapter, and at the end you will have a complete project notebook: an estimate, a schedule, a logistics plan, a buyout log, submittal and RFI logs, cost reports, pay applications, change orders, a delay analysis, and a closeout binder. It is a lot of work. It is also the closest thing to two years of experience that can be delivered in a book, and it is the thing you will put in front of a hiring manager.

The industry you are joining puts up roughly a trillion and a half dollars of construction a year in the United States alone, employs millions of people, and builds every space in which the rest of the economy happens. It is also, by most measures, one of the least productive, most adversarial, and most dangerous sectors we have. Those two facts are related, and they are related through management.

That is not a burden I am trying to put on you. It is the reason the job is worth doing well.

Now go find out what's on the bottom of your stack.

— Ray Alvarez