Instructor Guide

Teaching Construction Management: Building the Built World

This guide accompanies a 42-chapter textbook that is free, openly licensed, and designed to be adapted. Take what works, cut what does not, and change the sequence if your program's structure demands it. Everything here is a starting point, not a prescription.

What is in the instructor companion

The book's pedagogical design, and what it asks of you

It is built around one project

The book follows the Northgate Outpatient Pavilion — a $47.5 million, 132,000 SF medical office building on a CM at Risk contract with a $47,500,000 guaranteed maximum price and 565 calendar days — from conceptual estimate to lessons learned. Three secondary projects run alongside it: a hard-bid public school, a state DOT bridge replacement on a unit-price contract, and a 34-lot residential subdivision.

Why this matters for teaching: students will encounter the same numbers repeatedly, in different contexts, across a whole term. The $10,650-per-calendar-day figure introduced in Chapter 1 recurs in Chapters 14, 22, 29, 30, and 33. The 23-day steel delay is a procurement story in Chapter 16, a scheduling story in Chapter 14, a control story in Chapter 29, a productivity story in Chapter 20, and a claim in Chapter 33.

This is deliberate interleaving, and it is the single most useful thing about the book's structure. Lean into it. When a number reappears, ask the class where they saw it last and what it meant there. Students who can do that have actually integrated the material; students who cannot have been reading chapters as isolated units.

It uses evidence-based learning design, and the parts that feel redundant are the parts that work

The book deliberately includes several things that look like padding to an inexperienced reader:

• Retrieval prompts (🔄 Check your understanding) with hidden answers, roughly every 1,500 words.
• Spaced review sections at the end of most chapters, actively revisiting earlier material.
• Productive struggle problems (🧩) that pose a problem before the solution is taught.
• Interleaved practice — Part M of every exercise set explicitly mixes the current chapter with named earlier ones.
• Metacognitive check-ins (🪞) every three chapters.

Students will want to skip all of these. The retrieval prompts feel like a quiz they did not sign up for, the spaced reviews feel like repetition, and the productive-struggle problems feel like being asked to fail on purpose. Tell them, explicitly and early, that these are the parts that make the material stick, and that the smoothness of just reading forward is the feeling of learning nothing. Chapter 1's "How to Use This Book" makes this argument; reinforce it in week one.

Practically: assign the spaced reviews. Grade the Part M exercises. Use the productive-struggle problems as in-class opening activities rather than reading.

It teaches fifteen threshold concepts

Fifteen chapters carry a marked 🚪 threshold concept — an idea that, once understood, changes how a student sees everything downstream. They are listed in the front matter's Learning Paths file.

These are your assessment targets. A student who can explain, in their own words and with an example, why "a guaranteed maximum price guarantees the contractor's exposure, not the owner's cost" has understood something that will still be useful in fifteen years. A student who can recite the definition of a GMP has not.

The threshold concepts also make excellent exam questions, discussion openers, and — because they are genuinely counterintuitive — excellent diagnostics for the "I read it and it seemed obvious" failure mode.

It runs a progressive project

Every chapter ends with a Project Checkpoint adding one deliverable to the Willow Street Community Center project notebook — a $6.8 million, 24,000 SF municipal building on a 425-calendar-day design-bid-build contract. The complete package is Appendix K.

Forty-two chapters, forty-two deliverables, one complete project record: charter, risk register, document control setup, estimate, schedule, bid package, buyout log, field plans, submittal and RFI logs, daily reports, cost reports, earned value report, change orders, pay application, delay analysis, closeout package, and lessons learned.

This is the spine of any course built on this book. It is where the learning actually happens, it produces a portfolio artifact students can show an employer, and it solves the assessment problem — you are not grading whether they read, you are grading whether they can do the work.

Rubrics are in additional-assessments/rubrics.md.

Choosing your course shape

A one-semester course cannot cover 42 chapters. Do not try. The 15-week syllabus covers 27 of them and treats the rest as reference. Students who want the whole book have it.

What students find hardest, in order

Detailed treatment is in common-struggles.md, but the top five are worth knowing before week one:

1. The forward and backward pass (Chapter 14). Students can follow a worked example and then cannot do one. The fix is repetition by hand, with feedback, on progressively less structured problems. Appendix B exists for exactly this — twenty worked problems.
2. Markup versus margin (Chapters 12 and 13). A ten percent markup is a 9.09 percent margin. This is arithmetic students believe they understand until an exam. Test it early and test it twice.
3. Cost-to-complete versus cost-to-date (Chapter 28). The threshold concept that separates accounting from management. Students consistently forecast by extrapolating spend rate.
4. Float ownership (Chapter 14). Students grasp float as a calculation and miss it as a contested asset. The question "who owns the float?" reliably produces confusion, which is the point.
5. That a change order's cost is not the cost of the work (Chapter 31). Impact and disruption are invisible to students who have never watched a crew get moved off a task and back onto it.

Teaching the ethics content

Ethics is threaded rather than siloed in this book. There is no ethics chapter. Instead, bid shopping appears in Chapters 15 and 16, unbalanced bidding and front-loading in 13 and 32, safety versus schedule pressure in 24 and 29, change-order padding in 31 and 33, quality shortcuts in 23, cost-report honesty in 28 and 34, wage and classification issues in 20, and professional integrity in 41 and 42.

This is a deliberate design choice, and it has a teaching consequence: you have to raise it repeatedly, in context, or students will not notice it. A single ethics lecture in week 13 will not do what a five-minute conversation in each of eight chapters does.

The book's position throughout is that the ethical line and the profitable line are usually — not always, but usually — the same line, viewed over a long enough horizon. Curtis Boone, the recurring cautionary character, exists to make this concrete without moralizing: he is skilled, likable, and wrong about the model, and his project is followed to its end so students can see the mechanism rather than being told a lesson.

Resist the urge to make Curtis a villain in class. The version of him students should leave with is the uncomfortable one: he is good at parts of this job, and most of us have some of him in us.

Teaching safety

safety-teaching-guide.md covers this in full, but the core instruction is short:

The book's position is that safety is a property of the production system, not a rulebook. The recurring scaffold near-miss has three findings, and the third — a crew running behind after an acceleration, under an unwritten pressure to make it up — is the one that would have prevented the next incident and the one nobody wanted to write down.

If your class leaves believing that safety is a compliance topic handled by the safety department, the book has failed regardless of how well they did on the OSHA questions. Every schedule decision in this course should be examined for its safety consequence. When a class recommends acceleration in the Chapter 29 exercise, ask them who is going to be on a scaffold in three weeks.

Prerequisites and student background

The book assumes basic algebra, general awareness of what a construction site looks like, and nothing else. It does not assume a business course, an accounting course, or a structures course. Every acronym is defined on first use in each chapter, and all math is worked step by step.

This means the book works for a genuinely mixed cohort — traditional CM undergraduates, career changers, craft professionals moving into management, and architecture or engineering students taking it as an elective. That mix is an asset in discussion. The craft students will know things the CM students do not, and structuring discussion so that surfaces is worth doing deliberately.

A note on the numbers in this book

Every cost, productivity rate, wage, lead time, and rental rate is illustrative and the book says so repeatedly. They are internally consistent so the arithmetic teaches something real; they are not a price book.

Please reinforce this. A student who leaves this course believing they know what concrete costs has learned something false. What they should leave knowing is where real numbers come from: their own company's historical cost data first, current market quotes second, and published data adjusted for time, location, and size third. That is Chapter 11's material and Chapter 28's purpose.

Adapting the book

It is CC BY-SA 4.0. You may edit it, reorder it, translate it, print it, and distribute it, including commercially, as long as you attribute it and license your version the same way.

Things instructors commonly change, and how to do it cleanly:

• Substituting a local project for Willow Street. Entirely reasonable and often better. The chapter Project Checkpoints describe the deliverable, not the building, so they transfer. Appendix K is the only file you must replace.
• Adding a regional legal module. Chapter 5 hedges every jurisdictional statement on purpose. A two-week module on your state's lien law, licensing, and prompt-payment statute slots in after Chapter 5 and improves the course substantially.
• Reordering Part II. If your program has a construction materials and methods course, drop Chapters 8–10 to reading and reclaim three weeks.
• Software. The book teaches CPM by hand deliberately, then names P6 and Microsoft Project without teaching their interfaces. If your program teaches scheduling software, Chapter 14 is the conceptual prerequisite, not a competitor.

Where to start

1. Read the front matter — the preface, "How to Use This Book," and "Learning Paths."
2. Read Chapter 1 and Chapter 14. Chapter 1 sets the voice and the anchor project; Chapter 14 is the most demanding chapter in the book and will tell you what you are dealing with.
3. Pick a syllabus.
4. Read common-struggles.md before week one.
5. Decide, before the term starts, whether you are running the Willow Street project. If yes, build the deliverable schedule into the syllabus from day one — it does not work as a late addition.