Design–Build Project Delivery¶
A construction owner contracts with one design–builder for both design and construction, assigning their coordination to one responsible entity.
Core Idea¶
In design–build project delivery, a construction owner contracts with one design–builder for both design and construction of a specified project. The design–builder may be one firm or a joint team, but the owner has one combined responsibility line. The method is defined by that owner-facing undertaking, not by a guaranteed price, schedule advantage or absence of owner review.[ref-65c32d024548][ref-c7b11f0aaf9c]
Scope of Application¶
The sourced cases here span public transportation infrastructure and a private commercial building; they do not establish every possible habitat.
- Public bridge and approaches: Louisiana's transportation department contracted with Audubon Bridge Constructors for the John James Audubon Bridge and approaches.[ref-c83285e57cfa][ref-5aab57321740]
- Private office building: DBIA lists Google's 1212 Bordeaux office with Devcon as design–builder and Parabola as architect.[^ref-b74073f53b9b]
Clarity¶
Count the owner's design and construction contracts: separate contracts remain design–bid–build even if teams collaborate, whereas one design–builder may hire many specialists under its own obligation.[ref-e7f943716708][ref-c7b11f0aaf9c] DBIA's Google page names the team but omits the executed contract, so its one-contract instance follows DBIA's classification and field definition.[ref-b74073f53b9b][ref-c7b11f0aaf9c] Design–build can retain owner quality assurance and approvals without guaranteeing risk transfer or better outcomes.[ref-c83285e57cfa-2][ref-65c32d024548]
Manages Complexity¶
The combined contract can move design/construction handoff and responsibility for their conflicts inside the design–builder's team. The owner still defines the project; proposal comparisons, design-package approvals and acceptance checks follow the procurement and contract. Too much prescribed design can limit the team's discretion; too little project definition can leave basic scope unsettled. Design–build contracts can use lump-sum or cost-plus-fee forms, so a fixed price is not part of the identity.[ref-65c32d024548][ref-e7f943716708][^ref-7b8eaf7e9d8c]
Abstract Reasoning¶
Identify the owner, the owner-facing design–builder and the design and construction obligations. Then trace a disputed change: who revises the design, who selects the construction method, who answers the owner, and which approvals remain with the owner? Ask what design is approved before a component starts. Some agencies permit work on approved partial designs at contractor risk; others require complete component design before construction. These are contract and approval choices, not universal effects of the delivery method.[ref-c7b11f0aaf9c][ref-c83285e57cfa-2][^ref-e7f943716708]
Knowledge Transfer¶
The bridge and office cases share the same four roles: owner, one owner-facing design–builder, design/construction specialists, and defined project scope. Their compensation, review rules and measured outcomes cannot simply be transferred from one project to the other. The live Contract Prime is an internal constituent: one enforceable bundle carries both design and construction duties. Integrated Design may improve cross-specialty decisions inside that arrangement, but it can also occur under separate contracts. The Contract Prime's Interface relation is conditional; design–build does not automatically inherit hidden internals or independent evolution.[ref-c83285e57cfa][ref-b74073f53b9b][ref-c7b11f0aaf9c][ref-65c32d024548]
Relationships to Other Abstractions¶
Current abstraction Design–Build Project Delivery Domain-specific
Parents (1) — more general patterns this builds on
-
Design–Build Project Delivery is part of Contract Prime
One enforceable owner-facing contract bundles a design–builder's design and construction duties as an internal constituent of this delivery arrangement.
Hierarchy path (1) — routes to 1 parentless root
Neighborhood in Abstraction Space¶
Design–Build Project Delivery sits in a sparse region of the domain-specific corpus (100th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Unclustered & Miscellaneous (2721 abstractions)
Nearest neighbors
- Construction — 0.74
- Cleanroom software engineering — 0.74
- Latent defect — 0.73
- Intergenerational public procurement — 0.72
- Design for logistics — 0.72
Computed from structural-signature embeddings · 2026-10-17
References¶
[^ref-65c32d024548]: Federal Highway Administration. “Design Build.” Center for Innovative Finance Support, Alternative Project Delivery, sections “Design Build,” “Responsibilities,” “Project Definition,” and “Design Build and Maintenance Contracting.” https://www.fhwa.dot.gov/ipd/alternative_project_delivery/defined/new_build_facilities/design_build.aspx. Authoritative agency guidance; the fixed-fee statement describes this FHWA form, not all possible design–build compensation. [^ref-e7f943716708]: Federal Highway Administration. “EDC-2: Design-Build.” Everyday Counts, section “Design-Build,” including the conventional design–bid–build contrast and the paragraph beginning “By awarding one contract.” https://www.fhwa.dot.gov/innovation/everydaycounts/edc-2/designbuild.cfm. Authoritative agency account of potential coordination and schedule mechanisms. [^ref-c83285e57cfa]: Transportation Design-Build Users Group. “Current Design-Build Practices for Transportation Projects,” June 2009, chapter 2, “Background,” §§2.1–2.2, especially “LADOTD (May 2009)” and “FHWA (Jan 2002).” https://www.fhwa.dot.gov/construction/contracts/pubs/dbpractice/02.cfm. FHWA-hosted informational compilation of agency experiences; its cover disclaims official FHWA/DOT policy and it is not a controlled outcome comparison. [^ref-c83285e57cfa-2]: Transportation Design-Build Users Group. “Current Design-Build Practices for Transportation Projects,” June 2009, chapter 6, “Project Management,” §§6.2–6.3, especially LADOTD, NAVFAC and WSDOT design-review/approval accounts and LADOTD quality assurance. https://www.fhwa.dot.gov/construction/contracts/pubs/dbpractice/06.cfm. A different chapter of the same FHWA-hosted Users Group work, reporting agency practices rather than official FHWA/DOT policy. [^ref-c7b11f0aaf9c]: Design-Build Institute of America. “Owners FAQ,” “What Is Unique About Design-Build?” https://dbia.org/owners/owners-faq/. Field association definition of the one owner-facing design–builder contract. [^ref-b74073f53b9b]: Design-Build Institute of America. “Google at 1212 Bordeaux,” 2019 project record, “Design-Build Team Summary” and “Design-Build Team.” https://dbia.org/project/google-at-1212-bordeaux/. Original association project description; executed Google–Devcon contract and independently measured project outcomes were not inspected. [^ref-5aab57321740]: Royal BAM Group / Flatiron Constructors. “Flatiron Wins $348M Contract to Design and Build New Mississippi River Cable Bridge,” body dateline 9 May 2006, webpage header 10 May 2006. https://www.bam.com/en/press/press-releases/2006/5/flatiron-wins-348m-contract-to-design-and-build-new-mississippi-river. Original contractor announcement identifying LADOTD, Audubon Bridge Constructors, its joint-venture members and the bridge/approach scope. [^ref-7b8eaf7e9d8c]: Design-Build Institute of America. “DBIA’s Updated Contracts Reflect Industry’s Recent Changes,” 15 September 2022, list items 525 and 530. https://dbia.org/blog/dbias-updated-contracts-reflect-industrys-recent-changes/. Original association list of lump-sum and cost-plus-fee owner–design-builder forms; establishes availability, not prevalence.