Design-build (DB) is a project delivery model in which the owner holds one contract with a single design-build entity that takes responsibility for both the design and the construction of the facility. That single contract — and the single point of accountability it creates — is the defining feature that distinguishes DB from design-bid-build (DBB), where the owner holds two separate contracts (designer and contractor) and sits in the gap between them. This article defines the model, explains how it actually works mechanically, and maps the principal variants used on US healthcare projects: design-build done direct, bridging (design criteria) design-build, and progressive design-build (PDB).
In DB, the owner runs a single procurement and signs a single agreement. Behind that agreement, the design-build entity organizes the designers and constructors however it sees fit. Three common organizational forms exist:
Regardless of internal form, the owner's experience is the same: one entity is accountable for delivering a facility that meets the contract criteria. If a building element doesn't perform, the owner does not have to adjudicate whether the cause was a design defect or a construction defect — that allocation is the design-builder's problem, not the owner's. This collapse of the "design vs. means-and-methods" finger-pointing seam is the central value proposition of DB.
In DBB, the owner sits at the apex of two contracts and inherits the gap between them. When a wall assembly fails an acoustic or infection-control performance target, the designer says the contractor built it wrong and the contractor says the design was deficient — and the owner, who has a contract with each, often ends up absorbing the cost and schedule consequences of resolving it. DB removes that seam:
The trade-off — covered in depth in the sibling Articles — is that the owner cedes a degree of direct control over the design. The A/E's primary contractual loyalty runs to the design-builder, not to the owner, which is a meaningful shift in healthcare where clinical users, infection control, and facilities engineering expect deep, iterative design influence. Bridging and progressive DB (below) are largely responses to that concern.
Because one entity controls both phases, DB permits overlapping (concurrent) design and construction — often called fast-tracking. Foundations and structure can be released for construction while interior fit-out, MEP, and specialty clinical spaces are still being designed. This is the primary reason owners on schedule-driven healthcare projects choose DB.
Practical mechanics: