Design-build (DB) is the right tool for a specific class of healthcare projects — not a universal default. This article is the decision guide: the conditions under which a single design-build entity outperforms the alternatives, the conditions under which it backfires, and the concrete trade-offs an owner accepts when consolidating design and construction under one contract.

Scope note: this Article covers the selection decision and its trade-offs. The DB variants (bridging, progressive DB), the contract and risk mechanics, the healthcare-specific control levers (user-group involvement, clinical validation), and the procurement/best-value process are each covered by their sibling Articles in this Part. Here we stay on "should we use DB, and what do we give up to get its benefits."

DB trades design control for single-point accountability and speed

Every delivery-model decision is a trade among four owner priorities: schedule, cost certainty, design control, and risk transfer. DB's core bargain is to maximize the first, second, and fourth at the expense of the third.

Under design-bid-build (DBB), the owner holds two separate contracts — one with the architect/engineer (A/E), one with the contractor — and sits in the gap between them. That gap is where the owner retains maximum design control but also absorbs the risk of design errors and omissions (the "spearin" implied-warranty exposure), coordination disputes, and change orders. Under DB, the owner signs one contract with a single entity that carries both design and construction. The designer now works for (or with) the builder, not the owner.

What the owner gains:

• Single-point accountability. One throat to choke for both design adequacy and construction quality. Finger-pointing between A/E and contractor is internalized inside the DB entity.
• Schedule compression through overlap. Design and construction phases overlap (fast-track / phased release). Foundations can be released for construction while interior fit-out is still being designed.
• Earlier price and schedule certainty. A committed price (often a GMP or lump sum) can be established earlier in the design process than in DBB, where pricing waits for ~100% construction documents.
• Constructability and cost feedback baked in. The builder is at the table during design, so means-and-methods, long-lead procurement, and value-engineering happen continuously rather than as a post-bid reconciliation.
• Risk transfer. Design-error and coordination risk shifts substantially to the DB entity. The owner is no longer the implied warrantor of the design's sufficiency.

What the owner gives up:

• Direct design control. The A/E's primary duty of loyalty runs to the DB entity, not the owner. Without deliberate contractual levers (owner's project requirements, bridging documents, design reviews, an owner's advisor/criteria architect), the owner can lose visibility into design decisions that affect clinical operations.
• Pricing transparency. Single-source procurement reduces the competitive-bid price discovery that DBB provides line-by-line.
• Late-change flexibility. DB's speed advantage erodes quickly when scope is still moving. Changes after the design is committed are expensive and disruptive, because the overlap that buys schedule also removes the buffer that absorbs indecision.

The decision, then, is not "is DB good" but "does this project's profile reward the trade DB offers."

DB fits schedule-driven, scope-definable, repeatable healthcare work

DB performs best when the owner can define what is needed clearly and early, and is willing to let the DB entity decide how to deliver it. The strongest-fit healthcare scenarios share these traits:

• Schedule is the dominant constraint. A health system needs beds, an ED, or an imaging suite open by a fixed date — to capture market share, satisfy a certificate-of-need commitment, relieve census pressure, or meet a lease/financing milestone. DB's overlap and early-GMP certainty are most valuable when every week of schedule has measurable financial or clinical cost.
• Scope is definable up front. The clinical program, room counts, and performance criteria can be specified before design is complete — typically because the owner has a strong programming/medical-planning foundation or a standard prototype.