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 to provide both the project's design and its construction. The design–builder may be one firm or a team of designers and constructors organized as one owner-facing contracting entity. The decisive feature is the responsibility line: the owner looks to that entity for the combined design-and-construction undertaking, instead of separately contracting with a designer and then a builder.[1][2]
That arrangement can let designers and builders coordinate a buildable design and can permit construction work on approved portions while other design work continues. Those are possibilities created by the arrangement, not automatic outcomes. The owner still must define the project and may retain design-review, quality-assurance and acceptance duties; the actual contract and approvals determine their allocation.[1][3][4]
The pattern is therefore narrower than “people who design and build together.” An architect and contractor can collaborate intensely while holding separate contracts with the owner. Conversely, a design–builder can use several specialist firms and remain one contracting counterparty. Count the owner-facing design and construction contracts first; then ask how responsibility and review actually work inside that arrangement.[2][1]
Structural Signature¶
- Owner and project criteria. A public agency or private client states what is to be delivered, sets procurement and performance requirements, and holds the combined delivery contract. In the FHWA highway description, the owner supplies enough preliminary definition to procure the project without necessarily completing the whole design.[1]
- Single design–builder responsibility line. One entity contracts with the owner for both design and construction. It can be a firm, consortium or joint venture; the singularity is contractual responsibility to the owner, not the number of organizations doing the work.[1][2]
- Design and construction specialists. Architects, engineers, constructors and trades perform their respective work under the design–builder's delivery structure. Their coordination can expose construction constraints while design decisions are still revisable, but the internal team structure varies.[3][5][6]
- Specified scope and risk boundary. Project criteria, design submissions, review rights, quality duties, price terms and remedies determine what the design–builder owes and what remains with the owner. “One point of responsibility” does not erase owner obligations or make every risk transferable.[1][4] Optional operating choice: The design–builder may package design and construction so some work begins before all design is complete. Agency-specific approvals can still require a completed design for a particular component, and an early start can occur at the contractor's risk. This scheduling option is not a fifth constitutive role.[3][4]
Sig role-phrases: owner with project criteria; one owner-facing design–builder; design and construction specialists; scope and risk boundary.
What It Is Not¶
- Not design–bid–build. In that route the owner obtains a design and then separately procures construction. The builder and designer have different owner-facing contracts; the owner is the contractual bridge between them.[3]
- Not any integrated design process. Specialists can jointly revise a design under separate owner contracts. That may be Integrated Design, but it is not the one-contract delivery allocation here.
- Not guaranteed speed, savings or defect prevention. A combined contract opens coordination and scheduling options; it does not prove that a particular project used them well or beat a comparator.[3]
- Not the absence of independent review. The 2009 Transportation Design-Build Users Group compilation reports that LADOTD separately procured an independent design-review and quality-assurance consultant while using design–build, and kept decision authority over acceptance of completed design plans.[4]
- Not necessarily a fixed-price job or a single-firm team. DBIA offers owner–design-builder forms for both lump-sum and cost-plus-fee compensation, and FHWA describes single firms, consortia and joint ventures as possible design–builder entities. These variants leave the combined responsibility line intact.[7][1]
Scope of Application¶
The method appears in public infrastructure procurement, where a transportation agency specifies a bridge or roadway and selects a team responsible for both design and construction. The 2009 transportation-practices compilation describes the John James Audubon Bridge and its approach roads as a Louisiana design–build undertaking with a single lump-sum contract; the contractor's original announcement identifies the selected Audubon Bridge Constructors joint venture.[8][6]
It also appears in private buildings. DBIA identifies Google's 1212 Bordeaux office as a completed design–build project and lists Google as owner, Devcon Construction as design–build firm, Parabola as architect, and additional engineering and specialty contractors. That page does not reproduce the executed Google–Devcon contract; the one-contract interpretation follows from DBIA's project designation together with its stated definition of design–build.[5][2]
The scope can be expanded to maintenance or operation, creating design–build–maintain or design–build–operate–maintain arrangements. Those forms include the base design-and-construction responsibility and add later-life duties; maintenance is not required for a base design–build project.[1]
Clarity¶
Draw the owner's contract lines. If the owner hires an architect to design, waits for the drawings, and then signs a separate construction contract, the two lines meet at the owner: that is design–bid–build even if the professionals communicate constantly. If the owner signs one agreement with a design–builder that must supply both design and construction, the combined delivery responsibility sits with that entity. It may in turn hire an architect, engineer and trades.[3][2]
This test also clarifies claims about errors. The combined design–builder is the owner-facing party for its contracted design and construction duties, which can reduce the owner's exposure to a designer–builder blame dispute. It does not mean every design fault is automatically resolved, that every owner-supplied requirement is correct, or that the owner stops reviewing the work. Identify the alleged defect, the contract's scope and the applicable acceptance path before assigning responsibility.[8][1][4]
Manages Complexity¶
A conventional owner must manage separate designer and builder relationships and the handoff between them. A design–build owner has one combined delivery counterparty, so the contractor and designer can settle some constructability and redesign questions inside the team. The simplification is in the owner-facing coordination and responsibility path; it is not a disappearance of the underlying technical complexity.[8][3]
The complexity moves into the quality of the owner's requirements, the design–builder's internal coordination and the review regime. FHWA warns that a fully designed solicitation can leave little opportunity for the design–builder to improve methods, while one with basic scope questions unresolved is not ready for procurement. The owner therefore has to define enough to compare proposals and enforce performance without prescribing every design choice it expects the team to integrate.[1]
Abstract Reasoning¶
To classify a project, first identify the owner, then list each contract the owner uses to obtain design and construction. One combined owner-facing design–builder obligation is the identity test; a project with two separate owner contracts fails it regardless of shared meetings or overlapping calendars.[2][3]
Next trace a change: who revises the design, who decides how it will be constructed, and who answers the owner if the two conflict? Then locate the remaining gates: what project criteria were fixed, what design packages must be approved before construction, and who performs quality assurance? These questions reveal the actual distribution of authority and risk within a design–build contract rather than assuming that the label answers them.[1][4]
Finally distinguish capacity from result. The arrangement can permit earlier construction and reduce a separate procurement interval, but a schedule advantage must be shown for the actual project, not inferred from the method's name.[3]
Knowledge Transfer¶
The same one-contract pattern can be recognized in a public bridge and a private office even though their owners, team members and procurement rules differ. In the Audubon case, LADOTD is the owner and Audubon Bridge Constructors is the selected joint-venture design–builder. At 1212 Bordeaux, Google is the owner and DBIA names Devcon as design–build firm. Each case has design and construction specialists coordinated within the owner-facing design–builder role.[8][6][5]
The comparison does not transfer case-specific details. The transportation-practices compilation identifies a lump-sum bridge contract; the Google award page does not establish its compensation form. LADOTD's separately contracted quality-assurance practice shows independent oversight can coexist with design–build, but it does not establish the exact review contract for the Audubon Bridge or Google office. Carry the roles across cases, and check the terms anew.[8][4][5]
Examples¶
Canonical: John James Audubon Bridge¶
Louisiana's transportation department selected Audubon Bridge Constructors, a Flatiron-led joint venture with Granite Construction and Parsons Transportation Group, to design and construct a Mississippi River bridge and about twelve miles of approach roads. The transportation-practices compilation reports that LADOTD used a single lump-sum design–build contract for the project. That gives a public owner, one joint-venture design–builder, a multi-firm design/construction team, and a defined bridge-and-roadway scope. The source record describes the selected contract, not a final measured cost or time advantage.[8][6]
Mapped back: LADOTD fills the owner role; Audubon Bridge Constructors fills the single design–builder role; the named joint-venture members supply the specialist delivery structure; the bridge and approaches plus lump-sum undertaking mark the documented scope and payment boundary. The public sources do not specify the detailed allocation of every internal design task or this project's exact approval gates.
Applied / In Practice: Google at 1212 Bordeaux¶
DBIA's project record names Google as owner of a Sunnyvale office building, Devcon Construction as the design–build firm, Parabola as architect, and engineering and specialty contractors. The record calls it Google's first design–build project. It describes the team and the completed building, but the executed owner–design–builder contract is not available on that page; its one-contract structure is inferred from DBIA's project classification and definition.[5][2]
Mapped back: Google is the owner; Devcon is the named design–builder; Parabola, Nishkian Menninger/IMEG and ACCO illustrate specialist delivery; the office building is the project scope. The record does not make Parabola the owner-facing prime or document a specific project risk allocation.
Near miss: coordinated separate contracts¶
An owner separately hires an architect and a contractor, then puts both in weekly meetings and lets early site preparation overlap later design decisions. Coordination and overlap are present, but there is no single design–builder contracted to the owner for both services. To make this a design–build instance, the owner-facing design and construction obligations would have to be combined in one design–builder agreement.[2][3]
Mapped back: The owner and specialists exist, but the single responsibility line is absent. The example demonstrates why collaboration and fast tracking are insufficient identity tests.
Structural Tensions¶
T1: Defined requirements versus design–builder discretion. The owner needs criteria clear enough to procure and accept the project. Too much completed design can leave the design–builder little room to coordinate design and construction methods; too little definition can leave proposals incomparable and basic scope unresolved. The choice is where to fix outcomes, interfaces and approvals while leaving implementation decisions open. Diagnostic: Which requirements must be fixed to make performance verifiable, and which design choices can the design–builder still improve?[1]
T2: Earlier package release versus exposure to incomplete design. One combined team can plan construction preparation while design continues, but the practical start gate is project-specific. The Transportation Design-Build Users Group compilation reports NAVFAC allowing work on approved partial designs, sometimes at contractor risk, while WSDOT required a component's design to be complete before construction. Starting earlier trades more schedule opportunity for dependence on later design decisions and explicit risk allocation; holding for complete component design reduces that exposure but relinquishes some overlap. Diagnostic: For this component, what design is approved, who authorizes the start, and who carries an at-risk change?[3][4]
Structural–Framed Character¶
The pattern has a portable-looking skeleton: put two coupled responsibilities under one accountable counterparty and reduce handoff disputes. But each word that makes it useful here—owner, Design, Construction, Contract, procurement, acceptance—names a construction practice with enforceable obligations. Its evaluative weight depends on what the owner values: control, speed, innovation, cost certainty and quality can pull in different directions. The method does not itself certify any one of those outcomes.[1][3]
Its human-practice dependence is high. Owners set requirements; firms form design–builder entities; designers and builders exchange information; contracts allocate liability; and agencies or private owners review compliance. Its institutional origin is also concrete: public procurement and professional contracting rules shape what a design–builder may undertake and what the owner retains. No physical law forces a single contract. Design–build is chosen and governed.[1][4][7]
The vocabulary travels badly without that frame. Calling a software team “design–build” may suggest that design and implementation are integrated, but unless there is a construction owner and a design-and-construction delivery contract, this is an analogy. Importing the name can help discuss coordination; it does not reveal a new instance of the procurement method. Its character: a strongly framed, domain-specific responsibility arrangement, with a generic coordination motif inside it but a constitutive construction contract boundary.
Structural Core vs. Domain Accent¶
The skeletal move—combine coupled obligations in one accountable entity—can appear elsewhere. A single vendor might design and implement software, or one organization might plan and execute a campaign. Those similarities might support a broader abstraction about consolidated responsibility, but they do not preserve this entry's recognition test: one owner-facing undertaking for the design and construction of a built project, with project criteria and review duties allocated around it.[2][1]
The construction roles are therefore core, not decorative examples. Remove the design–builder's obligation to build and it is a design-services contract. Remove its design obligation and it is a construction-only contract. Split those obligations into separate contracts with the owner and the method becomes design–bid–build even if the same professionals collaborate. The domain accent is the specific procurement vocabulary and regulatory practice; the domain-bound core is the combined responsibility line itself. A cross-domain Prime would need a different, genuinely shared recognition test rather than a metaphorical “design and build” phrase.
Instantiates / Related Primes¶
This entry is part of Contract.
The live Contract Prime describes an enforceable bundle of obligations between parties. Design–build uses such a bundle to make one entity answerable to the owner for both design and construction. The construction method adds specific counterparties, deliverables and risk questions to that general contractual structure.[2]
The live Coordination Prime helps explain why bringing design and construction specialists into one delivery organization may reduce a handoff between separate contractors. Yet coordination by itself does not identify design–build: separately contracted designers and builders can coordinate, and an integrated contracting form can still coordinate poorly. Integrated Design is a nearby domain entry about jointly revising coupled technical choices. It can occur inside a design–build team, but neither implies the other's contractual arrangement.
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.Every literal design–build project has an owner and one design–builder bound by a combined design-and-construction agreement. The parties accept one bundle of duties for a defined project; performance criteria and review gates make fulfillment or breach assessable, while remedies and the governing regime give the agreement binding force. The owner must specify enough for procurement and acceptance without settling every later design choice, reflecting Contract's incompleteness tradeoff. Remove this combined agreement and the single owner-facing responsibility line disappears even if designers and builders collaborate. A contract can exist without any construction project, and the delivery arrangement includes project scope, specialists and reviews beyond the agreement itself. This is strict composition/part_of in the parent_in_child direction, not subsumption or external presupposition. Contract's Interface edge is conditional on a distinct modular exchange surface; this child does not universally assert that further Interface or Boundary ancestor.
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
Not to Be Confused With¶
Design–bid–build puts design and construction into separate owner-facing contracts; design–build combines them. Integrated design is a way of revising coupled design decisions across specialties, regardless of contract form. A design–build–operate–maintain contract adds later operation or maintenance obligations to a design–build core rather than disproving that core. None of these distinctions turns on whether a project calls itself collaborative, uses a joint venture, starts work early or reports a favorable outcome.[3][1]
References¶
[1] 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. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o ↩p
[2] 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. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j
[3] 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. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m
[4] 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. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i
[5] 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. registry ↩a ↩b ↩c ↩d ↩e
[6] 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. registry ↩a ↩b ↩c ↩d
[7] 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. registry ↩a ↩b
[8] 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. registry ↩a ↩b ↩c ↩d ↩e ↩f