Design-Build vs Design-Bid-Build
A working guide for U.S. general contractors. How the two delivery methods actually differ in scope, risk, contract structure, pricing, and bid response, and how to read which one a solicitation is calling for before pricing the work.
Last updated
The two delivery models, in operational terms
Design-bid-build and design-build are the two dominant project delivery methods in U.S. construction. Both produce buildings, infrastructure, and the rest of the built environment. They differ in who holds the design contract, when the contractor is brought into the project, and how risk is allocated across the parties.
Design-bid-build is the traditional model. The owner contracts with an architect or engineer to develop a complete design through the document phases that culminate in a bid set, sometimes called a 100% construction document set. The owner then advertises the construction work for competitive bid based on the finished design. General contractors price the work against a known scope, the lowest responsive and responsible bidder typically wins, and the contractor builds the project according to the documents the design firm produced. Design and construction are sequential, and the owner sits between the two parties.
Design-build collapses the two contracts into one. The owner contracts with a single design-build entity that takes responsibility for both the design and the construction. The design-build entity is most often led by a general contractor with one or more design firms on the team, though architect-led design-build is a recognized model in some markets. Once the contract is in place, design and construction proceed under the same entity, often with portions of the work starting before the design is fully complete.
The choice between the two is not just procedural. It changes what the contractor is bidding (a finished design vs. a design responsibility plus construction), what the contractor is risking (execution against fixed documents vs. design and execution against an outcome standard), and what the contractor’s bid response has to demonstrate (capability to build vs. capability to design and build).
Why owners choose one over the other
The delivery method choice is the owner’s, made at the start of the procurement process and rarely revisited mid-project. Understanding the owner’s reasoning helps the contractor read the procurement correctly and price the work to the right standard.
When owners choose design-bid-build
Owners choose design-bid-build when the design is already well-defined and stable, when the owner wants direct control over design quality through a separate A-E contract, when the project is small enough that the documentation overhead of design-build is not justified, or when the owner’s procurement statutes require competitive low-bid selection on construction. Public agencies in jurisdictions where design-bid-build is the statutory default use it for most work; private institutional owners with strong in-house design-management capability often prefer it for the design control it provides.
When owners choose design-build
Owners choose design-build when schedule compression matters (the phases can overlap), when a single point of accountability simplifies the owner’s administration, when the project benefits from contractor input during design (constructability, value engineering, market knowledge), or when the project type lends itself to performance-based specifications rather than detailed design specifications. Federal infrastructure procurement has shifted substantially toward design-build over the past two decades, partly for schedule reasons and partly for risk-allocation reasons.
Hybrid considerations
Some owners use design-build for projects with relatively standardized scopes (warehouses, parking structures, certain repetitive building types) and design-bid-build for projects with high design complexity (signature buildings, projects with significant historic preservation requirements, projects with extensive owner-specific operational requirements). The hybrid approach reflects that the right delivery method depends on what the project is, not on a single best practice across all projects.
Statutory authority and public-sector adoption
On public work, the owner’s choice is sometimes constrained by statute. Many states authorize design-build for some agency procurement and not others. Federal design-build authority is governed by 41 U.S.C. § 3309 and implemented in FAR Part 36.3, with two-step procedures specified for design-build solicitation. State DOTs have specific design-build authority under 23 U.S.C. § 112 and state-level enabling statutes. The contractor reads the solicitation against the statutory framework that governs the procurement, not against generic delivery-method preferences.
The right delivery method depends on what the project is, not on a single best practice across all projects.
What the contractor is actually bidding
The single largest operational difference between the two delivery methods is what the contractor sees in the bid documents and what the contractor is committing to deliver.
Design-bid-build: the documents are the scope
On design-bid-build, the bid documents include a complete set of drawings and specifications that define the scope of work to a high level of detail. The contractor performs quantity takeoffs against the documents, prices each scope element, builds the bid number, and commits to construct the work as documented. The risk the contractor accepts at bid is execution risk: the contractor will build what the documents describe at the price submitted. Design risk sits with the owner and the design firm under their separate contract.
Design-build: the program is the scope
On design-build, the bid documents typically include an owner’s program, a basis-of-design document, performance specifications, and reference standards. Detailed design drawings are not part of the bid; the contractor and the design partners produce them as part of the contract performance. The contractor is bidding the design responsibility plus the construction, with the work defined by performance and outcome standards rather than detailed prescriptive specifications.
Design risk allocation
The shift in scope shifts the risk. Design-build consolidates design and construction responsibility under the design-build entity, which simplifies the owner’s position (one party to coordinate with, one party to hold accountable) and shifts more risk to the contractor in exchange for the contractor’s control over the design process. Design errors, design coordination issues, and design completeness issues that would have been the owner’s problem on design-bid-build become the design-build entity’s problem.
Pricing implications
Design-bid-build pricing is straightforward in theory: price the documented scope, win the bid, build the work. The complexity comes from change orders when the documents turn out to be incomplete or when conditions in the field differ from documented assumptions. Design-build pricing is more complex: the contractor prices a scope that has not been fully designed, with allowances and contingencies for the design work that has not happened yet, plus the construction. The pricing model is closer to a partially-defined commitment than to a fixed construction bid.
The contract documents that govern each
Both delivery methods use standardized contract documents on a substantial share of U.S. work. The standard forms have been refined over decades and are familiar to most parties; departures from the standards are usually project-specific modifications rather than wholesale rewrites.
Design-bid-build standards
The American Institute of Architects (AIA) publishes the most widely used design-bid-build contract documents. The A101 (owner-contractor agreement) and A201 (general conditions) are the foundational pair on most private design-bid-build work. The B101 governs the owner-architect agreement, executed separately. AGC ConsensusDocs publishes a parallel set (the 200 series) with similar coverage. Federal design-bid-build construction uses FAR-based contract clauses incorporated into agency-specific contract forms.
Design-build standards
Design-build has its own standardized contract documents. AIA publishes the A141 (owner/design-builder agreement) and A142 (design-builder/contractor agreement) as the design-build pair, with the B series including B141 for the owner-architect side of the design-build relationship. AGC ConsensusDocs publishes the 400 series for design-build. The Design-Build Institute of America (DBIA) publishes an independent set of design-build contract documents that are widely used on both public and private design-build work and that some practitioners prefer for the way they handle specific risk-allocation issues.
Federal design-build
Federal design-build procurement uses agency-specific contract forms with clauses derived from FAR Part 36.3. The two-step procurement procedure (Phase One qualifications evaluation, Phase Two technical and price proposals from a shortlisted group) is standard on most federal design-build above stated thresholds. Each agency layers its own supplemental clauses; USACE design-build, NAVFAC design-build, and GSA design-build solicitations look meaningfully different in their detailed contract structure even though the FAR foundation is shared.
Why the contract choice matters
The contract choice affects how risk is allocated, how disputes are handled, how design changes are processed, and how the parties relate during execution. A contractor moving between owners or between contract families should not assume the contractual mechanics will be the same; reading the actual contract documents during bid preparation is the only path that catches the differences before they become disputes.
Team composition and how it’s built
Design-bid-build bids come from a contractor with a planned subcontractor list. Design-build bids come from a contractor leading a team that includes architects, engineers, and (in some structures) specialty designers and consultants alongside the construction-side subcontractors. The team has to be assembled and committed before the bid is submitted.
Teaming agreements
Design-build teams are typically governed by teaming agreements that bind the design firms to the contractor for the duration of the procurement. The teaming agreement prevents the design firm from joining a competing team, defines the parties’ obligations during the bid period, and sets the framework for the post-award subconsultant agreement if the team wins. A loosely committed team can lose a key design partner to a competitor in the middle of the bid period, which forces a scramble to find a replacement and erodes the response quality.
Lead partner choice
Most design-build teams in U.S. building construction are contractor-led, with the design firms as subconsultants to the contractor. Architect-led design-build exists, particularly in markets where design firms have strong client relationships and the contractor brings construction execution to the team rather than client leadership. The choice of lead affects the contractual structure, the risk allocation between the lead and the subconsultants, and the way the team presents to the owner.
Sub-team development on multi-prime arrangements
Some federal design-build procurement, particularly large infrastructure projects, uses a Design-Build prime with separately-procured smaller construction packages or with public-private partnership structures that layer additional parties. The team-development work on these procurements extends beyond a simple GC-plus-A-E pair, and contractors pursuing this work often spend months on team development before any solicitation lands.
Early-stage team selection
On design-bid-build, the contractor’s subcontractor team is typically not finalized until after award; bid solicitation to subs happens during the prime bid window, and the prime selects the subs based on the bids received. On design-build, key team members (the lead architect, structural engineer, MEP engineer, and other major design partners) are committed before the bid because their qualifications are part of the prime’s response to the owner.
On design-build, key team members are committed before the bid because their qualifications are part of the prime’s response to the owner.
Pricing structures across the two methods
Design-bid-build pricing
Design-bid-build pricing is typically a lump-sum bid against the owner’s bid form. The contractor submits a single number based on the documented scope, and the contract is awarded at that number. Some design-bid-build work uses unit-price bidding (typical on heavy and civil work where the quantities are defined in the bid documents but the actual execution may vary), but lump sum is the dominant pattern on building construction.
Design-build pricing variants
Design-build pricing varies more than design-bid-build pricing. The standard structures include lump sum, guaranteed maximum price (GMP), cost-plus with a fixed fee, target price with shared savings, and progressive design-build (where pricing is established at a defined design milestone rather than at procurement). The solicitation specifies the structure, and the contractor responds in the form the owner has called for.
Lump sum design-build
Lump-sum design-build commits the contractor to a fixed price for the design and construction. The price has to account for the design work that has not happened yet, the design risk the contractor is absorbing, and the construction. Lump-sum design-build works on relatively standardized projects where the design risk is bounded; it gets harder to price defensibly on projects with significant design uncertainty.
GMP design-build
Guaranteed maximum price design-build sets a ceiling on the contractor’s cost, with a target cost below the ceiling and shared savings if the actual cost lands below target. The structure is more flexible than lump sum and supports projects where the design is partly defined at procurement but will continue to evolve through performance. The owner gets price certainty at the GMP level; the contractor gets some upside on cost control performance.
Two-step pricing on federal procurement
Federal design-build under FAR Part 36.3 typically uses a two-step procurement. Phase One evaluates qualifications and shortlists a small group of design-build teams. Phase Two collects detailed technical proposals and price proposals from the shortlisted teams. The owner evaluates technical and price together (best-value source selection on most federal design-build) and makes the award. The pricing in Phase Two reflects the contractor’s detailed analysis of the project after the team has invested significant Phase Two design effort.
Schedule overlap and how the phases relate
The schedule difference between the two methods is one of the practical reasons owners choose design-build for time-sensitive projects.
Design-bid-build: sequential phases
On design-bid-build, the phases run sequentially. The owner hires the design firm and works through schematic design, design development, and construction documents over a period that can run from a few months to multiple years depending on project complexity. The construction bid period happens after design completion, typically four to eight weeks. Construction begins after award and contract execution. The total schedule is the sum of design plus bid plus construction.
Design-build: overlapping phases
On design-build, design and construction can overlap. The design-build team begins detailed design after contract execution and can release construction packages (foundation, structure, MEP rough-in) for execution before later design packages are complete. The total schedule compresses by the overlap. On large projects, the schedule compression is substantial: a project that would take 36 months as design-bid-build can sometimes complete in 24 to 28 months as design-build, depending on how aggressively the team is willing to overlap and how much design risk the team accepts in pursuing the early construction packages.
The early-release tradeoff
The schedule advantage of design-build is real but not free. Releasing foundation work before structural design is complete, or starting structural work before MEP design is complete, exposes the team to coordination problems that can produce rework. The teams that compress schedule successfully on design-build invest in design coordination protocols that catch coordination issues before they become rework, and they price the rework risk into the bid as a contingency. The teams that compress schedule without those protocols sometimes find the schedule advantage eaten by rework cost.
Owner schedule expectations
Owners who choose design-build for schedule reasons usually have a schedule expectation that drives the procurement. The contractor should understand the owner’s schedule logic and price the bid to a schedule that the owner will accept; a design-build proposal with a schedule longer than the owner’s expectation is a strong signal of misalignment that often loses on the technical evaluation regardless of the price.
Risk allocation in detail
Design risk on design-bid-build
On design-bid-build, design risk sits primarily with the owner and the design firm. The contractor builds what the documents describe; if the documents are incomplete, contradictory, or contain errors, the contractor has the right to a change order for the additional cost of resolving the issue. The Spearin doctrine (from the 1918 Supreme Court case U.S. v. Spearin) establishes that the owner impliedly warrants the adequacy of the plans and specifications provided to the contractor on a design-bid-build project.
Design risk on design-build
On design-build, the design-build entity holds the design risk. Documents the design-build team produces, errors in those documents, and coordination issues across the documents are the team’s problem to resolve at the team’s cost. Spearin does not apply in the same way; the contractor cannot disclaim responsibility for the design the team itself produced. The shift is one of the structural reasons design-build commands different pricing than design-bid-build for similar physical scope.
Performance specification risk
On design-build, performance specifications shift performance risk to the contractor. An owner who specifies “the building shall achieve LEED Silver certification” has assigned the contractor the obligation to achieve the certification; if the as-built work does not, the contractor bears the cost of remediation. Performance specifications work well on design-build because the contractor controls the design path that produces the performance; they work poorly on design-bid-build because the contractor cannot control the design.
Differing site conditions and unforeseen conditions
Both methods address differing site conditions through standard contract clauses (FAR 52.236-2 on federal work, standard AIA clauses on private). Subsurface conditions different from those documented at bid time generally support a change order on either method. The contractor’s allocation of geotechnical investigation responsibility differs slightly between the methods (design-build teams sometimes accept more geotechnical risk in exchange for design-build pricing flexibility), but the core differing-conditions framework is similar.
Insurance considerations
Design-build entities typically carry both contractor general liability insurance and design professional liability insurance, either through the design partners’ existing coverage or through project-specific design-build insurance products. The insurance structure is meaningfully more complex than on design-bid-build where the design firm carries professional liability separately. Contractors building design-build practices invest in the insurance side as a structural part of the practice, not as an afterthought.
How the bid responses differ in volume and substance
The bid response on a design-build procurement is a substantively different document from a design-bid-build bid response. The volume difference is meaningful, but the substantive difference is more important for the contractor’s pricing strategy.
Design-bid-build response
A design-bid-build response on a typical building-construction project might run 50 to 200 pages plus the drawing set the contractor is bidding to. The proposal narrative is usually short and focused on responsibility statements, the contractor’s qualifications for the work, and bid form completion. The pricing exhibit, the bid bond, and the supporting documentation are mechanical to assemble. The contractor’s effort is concentrated on the takeoff, the sub solicitation, and the pricing strategy.
Design-build response
A design-build response on a comparable project commonly runs several hundred pages, sometimes more than a thousand on large federal procurements. The response includes a full technical narrative addressing the team’s design approach, key personnel, schedule logic, technical solutions, and management plan. Preliminary design documents (concept drawings, key plan layouts, structural and MEP schematics) are often required as part of the submission. The qualifications of the team members (the design firms, the major subcontractors, key personnel) are documented in detail.
Evaluation factor mapping
The design-build response is structured around the owner’s evaluation factors. Federal design-build under FAR Part 15 uses best-value source selection with stated evaluation factors and weights; the contractor’s response addresses each factor explicitly, and the technical narrative is organized to make the evaluator’s scoring as straightforward as possible. A design-build response that is not organized around the evaluation factors is harder to score and tends to score lower than its substance would justify.
Bid effort cost
The bid effort on design-build is meaningfully larger than on design-bid-build. The design firms on the team commit billable hours to the procurement before any contract is in place. The contractor’s preconstruction team commits substantial proposal-writing, technical-coordination, and scheduling effort. The total bid cost on a major design-build pursuit can run hundreds of thousands of dollars between the contractor’s hard costs and the design partners’ opportunity cost. Treating design-build as a higher-effort, lower-frequency pursuit pattern (rather than as routine bidding) is what most contractors with successful design-build practices have settled on.
Reading the procurement and pricing to the right standard
The most common error contractors make on the delivery-method question is treating both methods with the same approach. A design-bid-build template applied to a design-build procurement produces a thin response that loses the technical evaluation. A design-build effort applied to a design-bid-build solicitation is overinvested in narrative content that the owner is not weighting heavily, with the bid effort better spent on takeoff and pricing.
Reading the actual evaluation criteria and the actual contract documents during bid preparation is what distinguishes which approach to take. The labels (“design-build,” “design-bid-build,” “design-assist,” “CMAR,” “progressive design-build”) are sometimes used loosely; the substance of the procurement is in the evaluation factors, the contract structure, and the scope definition. A solicitation labeled design-build but with a 100% complete design attached and lump-sum pricing against the documents is functionally a design-bid-build procurement. A solicitation labeled design-build with a basis-of-design document and best-value evaluation is a real design-build procurement that needs the full design-build response approach.
The bid documentation discipline applies on both methods, with the substance differing. On design-bid-build, the compliance matrix tracks the documented requirements, the proposal narrative is short, the pricing math is the centerpiece. On design-build, the compliance matrix tracks the evaluation factors and the program requirements, the proposal narrative is the centerpiece, the pricing math sits inside a more complex framework that has to account for the design work and the design risk.
The ScalaBid Submission Packageis built to the actual delivery method in the solicitation, which means a design-bid-build package and a design-build package come back as substantively different deliverables even on similar project types. A design-bid-build package leans on a tight compliance matrix, a clean drawing index of the owner’s bid documents, and a focused proposal narrative. A design-build package contains a full technical and management narrative organized around the owner’s evaluation factors, with sections that address the design approach, key personnel, schedule logic, and management plan at the depth design-build evaluations expect. The compliance matrix and the action checklist reconcile across both methods the same way they do on every package, and the contractor’s team gets a response shaped to the procurement rather than a generic template adapted after the fact.
Contractors building durable practices in either method invest in the practice deliberately. Design-build practice requires team development between bids, design-firm relationships, insurance structures, and proposal-writing capability that design-bid-build practice does not need at the same depth. Design-bid-build practice requires takeoff and pricing infrastructure, sub-solicitation discipline, and bid-bond capacity that design-build practice uses differently. Most contractors above a certain size end up doing both, but the underlying disciplines are distinct enough that treating them as the same activity is a structural mistake.
Related field notes
- CMAR (Construction Manager at Risk) · The third path that sits alongside design-build and design-bid-build.
- Design-build proposal narrative structure · How the technical narrative on a design-build response is actually built.
- Progressive design-build · A variant gaining traction on public infrastructure.
- Design-build vs design-bid-build (glossary) · Definitional companion to this pillar.
- SF-330 (Architect-Engineer Qualifications) · The form federal design-build teams use for the design-side qualifications.