Self-Paced Independent Study

For readers working through the book alone

No cohort, no instructor, no deadlines. This path is milestone-based rather than calendar-based, because a self-studying reader's real constraint is life, not weeks — and a schedule you miss twice becomes a schedule you abandon.

How long it takes. At one chapter a week, roughly ten months. At two a week, five. Most people who finish do about a chapter a week with breaks, and take somewhere between eight months and a year.

First: decide honestly what you are here for

The book supports four genuinely different goals, and they call for different paths. Pick one before you start, because the wrong path is the main reason self-studiers quit.

The rest of this document assumes the Standard path. Adapt freely.

The four milestones

Forget weeks. Work toward these.

Milestone 1 — "I can read the documents and the deal" (Chapters 1–7)

You are done when you can: open an unfamiliar contract and find the order of precedence, the notice period, the LD amount, and the changes clause in under ten minutes; explain why the same building costs different amounts under different delivery methods; and hunt a drawing set for conflicts systematically rather than by luck.

Self-check: Take the Chapter 3, 4, and 7 quizzes cold, a week after reading them. If you score below 70% on any, reread that chapter's key-takeaways.md and retake it.

Project deliverables: charter, stakeholder analysis, delivery memo, contract risk map, legal checklist, risk register, document control setup.

Milestone 2 — "I can produce a number and a date" (Chapters 8–17)

You are done when you can: perform a documented takeoff; build a unit cost from a crew, a production rate, and a burdened labor rate without looking it up; run a forward and backward pass by hand and get the right answer; and write a scope sheet that closes the gap between two trades.

This is the hardest milestone and where most people stall. Two specific pieces of advice:

• Chapter 14 requires repetition, not rereading. Work Appendix B problems 1–10 by hand. Do not look at a solution until you have an answer. Getting it wrong and finding out why is the entire mechanism.
• Markup versus margin will trip you. A 10% markup is a 9.09% margin. Work it in both directions until it is automatic.

Project deliverables: systems narratives, conceptual estimate and VE log, quantity takeoff, detailed estimate, CPM schedule, bid package, buyout log, preconstruction plan.

Milestone 3 — "I can run the job" (Chapters 18–27)

You are done when you can: build a submittal log by back-scheduling from required-on-site dates; write an RFI that would get a usable answer in one round; write a daily report with a real impact statement; explain why a schedule decision is a safety decision; and screen a look-ahead into ready and not-ready work using a constraint log.

Self-check: Write an RFI on a genuine ambiguity — from a real drawing set if you can get one, from Appendix K if you cannot. Then read Chapter 25's model RFI and mark your own against it.

Project deliverables: site logistics, subcontractor and labor plans, equipment and temporary-structures plans, quality plan, safety plan with JHAs, submittal log and RFIs, daily reports, look-ahead and constraint log.

Milestone 4 — "I can tell whether we are winning" (Chapters 28–42)

You are done when you can: produce a cost report with a defensible cost-to-complete forecast; update a schedule and identify float erosion; compute the earned value indices and say what they do not tell you; price a change order including impact and time; build a schedule of values and a pay application; and perform a delay analysis addressing entitlement, causation, and concurrency.

Project deliverables: cost report, schedule update and recovery plan, earned value report, change orders, SOV and pay application, delay analysis, WIP entry, BIM and sustainability plans, closeout plan, leadership plan, and the assembled notebook.

How to study this book so it sticks

The book is built on evidence about how people actually learn, and the parts that feel like a waste of time are the parts that work. Specifically:

Do the 🔄 Check your understanding prompts before looking. Retrieving something from memory is what moves it into long-term storage. Reading the answer produces a warm feeling of understanding that is almost entirely false.

Do the 📋 Try it drills with a pencil. Every one of them. Reading a worked calculation and doing one are different activities with different outcomes, and only one of them is learning.

Do not skip the ## Spaced Review sections. They feel redundant. That is the point — they are placed to catch material just as you are about to forget it, which is exactly when reviewing it does the most good.

Attempt the 🧩 Productive struggle problems before reading the solution. Spend three to five minutes failing. You will understand the solution far better afterward.

Pay extra attention to the fifteen 🚪 threshold concepts. They are listed in the front matter's Learning Paths file. If you can explain all fifteen to somebody else in your own words with an example, you have got what this book is for.

Doing the project alone

The Willow Street Community Center project is the difference between having read a book and being able to do the job. Appendix K is the full package.

Two adaptations for a solo reader:

1. Do not try to make each deliverable perfect. A rough takeoff you actually finished beats a beautiful one you abandoned in week nine. You can always improve it later; the arithmetic in the later chapters only needs it to exist.
2. If you work in construction, substitute your own project. It is more work and vastly more valuable, and your deliverables become things you can show an employer and use at work tomorrow.

Keep everything in one folder from day one, with a table of contents. Chapter 42 asks you to assemble it, and assembling forty-two scattered files at the end is a miserable evening.

Getting feedback without a class

The genuine weakness of self-study is that nobody tells you when you are wrong. Four partial fixes:

• The answers are in the book. Appendix J has worked solutions to the calculation exercises, and every quiz answer is behind a <details> block. Use them after attempting, not during.
• Find one person in the industry who will look at three things. Not everything — three. Your estimate, your schedule, and your delay analysis. Most experienced project managers will do this for someone who is clearly putting in the work.
• Join an association. AGC, ABC, CMAA, DBIA, and NAWIC all have local chapters with meetings that cost very little and are full of people who do this for a living. This matters more in construction than in most industries, because it is a relationship business.
• Explain a threshold concept to somebody. If you cannot make a friend understand why a guaranteed maximum price does not guarantee the owner's cost, you do not understand it yet.

If you stall

Almost everyone stalls, usually at Chapter 14 or somewhere in Part VI. Three things that help:

1. Drop to the Fast Track temporarily. Read the next four chapters' key-takeaways.md files only, then come back. Momentum matters more than completeness.
2. Skip ahead to a chapter you actually want. The book is written to be read in order, but the chapters stand alone reasonably well. Chapter 41 or 42 will remind you why you started.
3. Do a deliverable instead of a reading. Producing something is more motivating than consuming something, and it is where the learning is anyway.

The failure mode is not slowness. It is a month of not opening the book, followed by feeling too far behind to start. There is no behind. Open it.

What this book will not give you

Judgment. That comes from a job site and from being told, specifically and kindly, what you just did wrong.

What this gives you is the map, the vocabulary, the arithmetic, and a portfolio — so that when you get onto that job site, you are learning judgment instead of learning what a submittal is.