The drawings were complete. The contract was signed. The schedule was baselined. And the project still stalled in a conference room, because no one could say who was entitled to decide, what information had to exist before the decision was valid, or what record would authorize the field to act on it.
That failure is structural rather than technical. Delivery method, procurement method, contract form, management model, and production system are routinely discussed as though they were a single decision. They are five, and confusing them is the most common and most expensive error in capital delivery. The consequences surface later as unclear design liability, price certainty that arrives too late to matter, risk sitting with the party least able to carry it, changes priced before anyone classified them, and a closeout that stops rather than ends.
This twenty-chapter guide separates those layers and rebuilds them into a working model, from owner readiness through post-occupancy review. The treatment is procedural rather than theoretical: where a decision requires a document, the document is named; where a process depends on a response time, the response time is discussed. Read it straight through as a course in delivery, or open it at the chapter that matches the decision on your desk this week.
Inside this guide you will:
- Tell the five delivery choices apart and make each one deliberately, then match a method to the project through selection criteria, public-sector constraints, and a side-by-side comparison of the major delivery families.
- Test whether an owner organization is genuinely ready, using decision rights, risk appetite, budget architecture, and a readiness gate that precedes procurement.
- Run design-build with discipline: team organization, qualifications and best-value procurement, criteria packages and bridging documents, design-to-release gates, and construction-phase administration.
- Make integration real rather than nominal, through validation, risk pool and incentive structure, open-book cost, lean planning, and information and model governance.
- Convert contract documents into governed field action through submittals, requests for information, supplemental instructions, observation planned around irreversibility, testing, and defensible disposition of nonconforming work.
- Classify change before pricing it, test the build-up rather than the bottom line, evaluate time impact on cause and logic, and certify payment applications on evidence.
- Close projects on criteria rather than optimism: substantial completion, punch lists, commissioning, owner training, record documents, warranties, and final payment.
The apparatus is built for daily use: sixty analytical figures, worked scenarios from public institutional, healthcare, university and civic projects, chapter sources, a glossary of working terms, and three appendices giving a delivery method comparison matrix, a construction administration document register, and a grouped closeout checklist.
One caution belongs at the front. The book discusses standard contract families and industry practice in general terms. It is not legal advice and cannot describe the agreement you signed; your executed documents, your jurisdiction, and your counsel govern.
It is written for the people who carry delivery risk: owners and owner representatives who must select a method and live with it, architects and engineers administering construction contracts, design-build and construction management practitioners, project and program managers, public agency capital staff, and students and examination candidates who need the reasoning behind the terminology rather than the terminology alone.
Open this guide at the decision in front of you and start running project delivery as a system instead of inheriting one by default.
