PCC Research preview

This page is a working demonstration for NPA and Council leadership. Enter the preview phrase to continue.

That is not the phrase. Try again.
A publication of the National Parking Association -- Parking Consultants Council
NPA's 75th Year · 1951–2026  ·  How this connects to WeAreParking.org →
Parkonomics PCC Research
PCC Research / The PCC Book of Parking / Part IV · Making It Stand / Module 36
PART IV · MAKING IT STAND · MODULE 8 OF 8 MEMBER EDITION · PREVIEW

Project Delivery: Design-Bid-Build, CM, Design-Build, and IPD Compared

By Frank Lozano and Adam Cochran · Edited for the Book of Parking by Andrew Sachs, PTMP
Reviewed August 2026 · v0.1 draft · in Council author review · revision record begins at publication

The project delivery method is the owner's first structural decision, made before any concrete is specified: it allocates design responsibility, construction risk, and the right to make changes among the owner, the designer, and the builder, and it is often locked by procurement law before preference gets a vote. The four methods that deliver most American parking facilities (Design-Bid-Build, Construction Management in its variants, Design-Build, and Integrated Project Delivery) are really four different answers to the owner's questionnaire: What are the needs and the budget, and when must hard costs be known? What ranks first among aesthetics, cost, time, and quality? Who designs, who builds, who manages, who operates? Answer those honestly and the method largely picks itself.

Design-Bid-Build: the sequential baseline. DBB is the traditional method: three phases (design, bid, construction) run in strict sequence, none overlapping. The owner contracts separately with the prime design professional (for parking, typically a specialized parking consulting firm, often first engaged for the demand study or feasibility analysis that scoped the project) and, after the authority having jurisdiction completes plan review, releases 100-percent-complete documents for bids. Public owners frequently must take the low bid, which is why the two-stage RFQ-then-RFP process exists: qualify the shortlist first, then let only proven contractors price. The method's virtues are real (open owner-designer communication, a design vision unpressured by the builder's schedule, competitive bidding's lower first cost) and so are its defects, all descending from one fact: the contractor is absent during design. No means-and-methods input reaches the drawings, so bidding and construction generate RFIs, redesigns, and design-related change orders, and the sequential schedule is the longest of the four methods. The accelerated variant bids from 90-to-95-percent "Issue for Bid" documents while the permit set sits in AHJ review, buying schedule at the price of pricing on incomplete documents, with the AHJ's comments as the wildcard the bid did not carry.

Construction Management: buy the builder's brain early. The CM family puts a construction professional at the owner's side from before schematic design, providing cost estimating, constructability review, scheduling, structural-system recommendations, and market knowledge, and its three variants differ by how much risk the CM holds. CM as advisor consults without construction risk, holding no trade contracts. CM as agent additionally holds some design contracts on the owner's behalf, sharing design-side liability but not construction cost risk. CM at Risk (CMaR) converts at construction into the general contractor, holding the trade subcontracts and bearing the classic GC risks of escalation and delay, after serving as the owner's preconstruction consultant for a fee. The family's advantages compound where the owner uses them: earlier cost and scope decisions, more predictable phase budgets, designers with a builder to test constructability against, reduced owner management burden across multiple primes. The honest disadvantages: another consultant to manage, an advisor who can turn adversarial to the design team, and, in the advisor and agent forms, the risk that the CM's estimates are not as good as a CMaR's, whose own money enforces accuracy. The deciding variables are the owner's experience with the method and the depth of the CM's preconstruction operation.

design-bid-buildfull drawings, then the low bidprice known late, owner holds gapsCM at riskbuilder joins during designGMP earlier; two contracts to managedesign-buildone contract, one throat to chokespeed and certainty; owner sees lessP3 / concessionfinance + build + operate, one dealrisk transferred farthest, control toopick where the risk should sit, then pick the method that puts it there -- never the reverse
Figure 1.Delivery method is risk allocation with a schedule attached: each step from design-bid-build toward the concession moves risk off the owner and control with it.Source: delivery structures per Ch 14 as carried in this module.

Design-Build: one throat to choke. DB collapses design and construction into a single entity under one owner contract, typically a construction firm that subcontracts a specialized parking design firm. The owner's risk drops with the interface: designer and builder cannot blame each other across a contract line they share, unified recommendations replace adversarial ones, claims and litigation thin out, and the schedule compresses. The price is control: less owner influence over material quality and design detail, limited competitive bidding below the DB entity, and outcomes that depend heavily on how well the owner specified the project before handing it over. Public DB procurement runs the RFQ/RFP two-step, often around bridging documents, a 25-to-30-percent design set prepared by an independent firm that gives all bidders a common foundation (that firm sometimes staying on as the owner's third-party advisor through completion), with stipends compensating shortlisted bidders where the RFP demands design work. The variant gaining ground is Progressive Design-Build: the team is selected on qualifications without a price commitment, then works collaboratively with the owner through programming and preconstruction to establish the basis of design, budget, and schedule, with an owner's off-ramp at defined milestones. It trades the certainty of a bid-day price for early collaboration with a competitively selected team, and owners who value the off-ramp value it highly.

Integrated Project Delivery: shared risk, shared pool. IPD binds owner, designer, and builder (and on complex projects, the major engineers and trade contractors) into one multi-party contract built on lean practices and a deliberately collaborative culture. Its economic engine is the profit pool: each party's actual labor and material costs are paid monthly, while profit is withheld into a shared pool proportioned to each firm's scope; overruns shrink the pool, savings grow it, and distribution rides on total project outcome rather than individual firm performance, so every firm's profit depends on everyone's work. The method drives genuine innovation on complex, schedule-driven projects and demands what it advertises: complete trust, transparency, lean discipline, and ideally teams with history together. Its costs are structural: significant upfront investment, diminishing returns if design and permitting stretch, insufficient savings on simple projects to repay the setup, and no firm price cap at the start, which alone disqualifies it for owners whose financing requires one.

VERDICT

choose the method from the constraint that binds: DBB where procurement law or a low first cost governs and schedule can absorb the sequence; CMaR where the owner wants preconstruction intelligence with a builder whose estimates carry its own risk; DB (progressive where the off-ramp matters) where single-point responsibility and schedule outrank design control; IPD only for complex projects with committed, experienced partners and financing that tolerates an open price. And in every method, put the parking specialist in the room from the feasibility study forward, because no delivery structure repairs a program scoped without one.

Sources: PCC project delivery practice per the source chapter; CMAA characterization of DBB; Lean IPD framework as cited therein. Procurement law varies by jurisdiction and governs public owners' choices.

From the shelf

Source crosswalk -- where each section came from in the manuscript
Module section Source: Chapter 19, "Project Delivery Methods"
The owner's questionnaire "Introduction" (questions list, procurement law, four methods, BIM/sustainability context)
DBB "Design Bid Build" (sequence, RFQ/RFP two-step, advantages/disadvantages, Issue-for-Bid variant)
CM family "Construction Management (CM)" (scope, cautions); "CM as Advisor"; "CM as Agent"; "Construction Management at Risk"; advantages/disadvantages chart
Design-Build "Design Build" (single entity, procurement, bridging documents, stipends, pros/cons); "Progressive Design Build"
IPD "Integrated Project Delivery" (multi-party contract, lean, profit pool, pros/cons)
Not carried forward BIM/technology paragraph (context, absorbed into opening); contractual-relationship figures (figure audit items)