Design-Build (DB) Delivery Method

Design-Build (DB) Delivery Method · Project Management

Language: 中文 English Español 日本語 한국어 Tiếng Việt ไทย Русский Français العربية

📖 Detailed Explanation

Design-Build (DB) is a project delivery method in which a single contractor is responsible for both design and construction under one contract with the owner. This integrated approach contrasts with traditional Design-Bid-Build, reducing coordination interfaces, shortening schedules, and lowering change order and claims risks. The DB contractor often engages specialist designers, construction managers, and suppliers early to optimize constructability and cost. DB is widely used in international building, industrial, and infrastructure projects where schedule certainty, single-point responsibility, and risk transfer are priorities. Success depends on clear Employer's Requirements, strong design management, and balanced risk allocation between owner and contractor.

💡 Practical Example

In an industrial park project in Southeast Asia, the owner adopted the Design-Build delivery method and awarded both design and construction to one international contractor, completing the plant three months ahead of schedule.

🔍 In-Depth Analysis

In-Depth Analysis of the DB Design-Build Model

I. Definition and Background

1.1 Precise Definition

The DB (Design-Build) model refers to a procurement and contracting approach in which the owner commissions both the design and construction of a project to a single general contractor (or consortium), who is responsible for the entire process of design, procurement, construction, and commissioning, ultimately delivering to the owner an engineered product that meets functional requirements.

Its core characteristic is a single point of responsibility: the designer and the constructor are no longer in an employer-contractor relationship as under the traditional DBB model, but rather operate as collaborating parties within the same contractual entity. The owner signs only one contract and faces only one responsible party, thereby avoiding the classic predicament of finger-pointing between design defects and construction errors.

1.2 Background of Formation

The rise of the DB model stems from three major pain points of the traditional DBB (Design-Bid-Build) model in large, complex projects:

Against this backdrop, the DB model achieves parallel operations and Fast-Track delivery through integrated design and construction, and has been widely adopted in international markets. FIDIC (the International Federation of Consulting Engineers) issued the *Conditions of Contract for Design-Build and Turnkey* (commonly known as the "Orange Book") in 1995, later updated in 2017 as the *Conditions of Contract for Plant and Design-Build* (Yellow Book), which has become the mainstream contract template for international DB projects. Since 2016, China has vigorously promoted engineering procurement construction (EPC/DB), with the Ministry of Housing and Urban-Rural Development successively issuing policy documents such as the *Several Opinions on Further Promoting Engineering Procurement Construction*, providing institutional support for central state-owned enterprises "going global" to undertake DB projects.

1.3 Scope of Application

The DB model is not a panacea; its applicability depends on project characteristics:

Suitable CircumstancesUnsuitable Circumstances
Owner has clear functional requirements but does not prescribe the means of deliveryOwner has strong desire to control design and requires drawing-by-drawing approval
Tight schedule requiring fast-trackHighly uncertain technical solutions requiring repeated deliberation
Single point of responsibility facilitates managementOwner possesses strong in-house design and construction management teams
Industrial/infrastructure projects with high standardizationHighly customized buildings with strong artistic requirements
Owner wishes to lock in a lump sum and transfer riskExtreme geological/policy risks making accurate pricing difficult

In overseas engineering practice, the DB model is commonly found in power, water, highways, buildings, and industrial parks, and is particularly suited for central state-owned general contractors to leverage their "design + construction + supply chain" integration advantages.

II. Detailed Core Content

2.1 Single Point of Responsibility and Contract Structure

The contract structure of the DB model is essentially a binary owner–general contractor relationship. Internally, the general contractor integrates design institutes, construction teams, and equipment suppliers through subcontracting, consortium agreements, and other means.

Key Points Checklist:

Risk Allocation Comparison:

Risk ItemDBB ModelDB Model
Design errorsOwner bears (design contract)DB contractor bears
Design-construction interfaceOwner coordinatesDB contractor coordinates internally
Schedule delaysProne to disputesSingle point of responsibility
Geological conditionsTypically owner bearsPer contract, often contractor bears
2.2 Parallel Design and Construction with Fast-Track

The greatest value of the DB model lies in Fast-Track: construction can commence on completed portions while design is still ongoing, achieving deep overlap between design and construction.

Implementation Points:

Typical Parallel Process:

```

Conceptual Design → Basic Design → Detailed Design A → Detailed Design B → Construction Drawings

↓ ↓ ↓

Construction Prep Construction Section A Construction Section B

```

2.3 Lump-Sum Contracts and Risk Pricing

DB projects mostly adopt Lump Sum Turnkey or Guaranteed Maximum Price (GMP) contracts. The contractor must estimate the full cost of design, procurement, and construction at the bid stage, bearing the risk itself.

Key Risks the Contractor Must Assess:

Response Tools:

2.4 Performance Indicators and Acceptance Criteria

DB contracts typically use Performance Guarantees as the core basis for acceptance, rather than a simple bill of quantities.

Common Performance Indicators:

Project TypeTypical Performance Indicators
Power PlantOutput, heat rate, emissions, availability
Water Treatment PlantWater production, water quality, energy consumption
HighwayTraffic capacity, smoothness, durability
BuildingsFloor area, storey height, energy efficiency rating, comfort

Acceptance Process:

1. Mechanical Completion;

2. Commissioning;

3. Performance Test;

4. Taking Over;

5. Defects Liability Period;

6. Final Acceptance.

2.5 Change Management and Claims Control

Under the DB model, when the owner requests functional changes, the contractor has the right to adjust the contract price and schedule; however, changes caused by the contractor's own design errors are borne by the contractor.

Change Management Points:

III. Comparison with Other Standards

Comparison DimensionChinese National Standards/EPC MeasuresInternational Standards (FIDIC Yellow Book)Host Country Local Standards
Contract Template*Model Text for EPC Contracts of Construction Projects*FIDIC Yellow Book/Orange BookCountry-specific, e.g., Saudi Arabia and UAE have local templates
Design ResponsibilityContractor responsible for design fitness for purposeContractor responsible for design fitness for purposeDepends on local law; some countries require local design institute stamp
Risk AllocationTends toward owner bearing unforeseen geologyClearly delineated, contractor bears moreVaries greatly; requires country-by-country due diligence
Acceptance StandardsNational standards + contract provisionsContract + international codesMandatory local codes, often coexisting with international standards
Dispute ResolutionDomestic arbitration/litigationInternational arbitration (ICC/CIETAC)Local courts or international arbitration

Practical Tip: Overseas DB projects often face a "triple standard overlay" — the contract specifies FIDIC, the design references Chinese national standards, and construction must satisfy local mandatory codes. Contractors must clarify standard priority at the bid stage to avoid acceptance disputes.

IV. Typical Application Scenarios

4.1 A Coal-Fired Power Plant Project in Pakistan

Public reports indicate that multiple coal-fired power plant projects under the China-Pakistan Economic Corridor framework adopted the EPC/DB model, with Chinese central state-owned general contractors responsible for design, procurement, construction, and commissioning. Such projects have tight schedules and strict performance indicators; the DB model effectively integrated design institutes and construction teams to achieve fast-track delivery. For specific project names and amounts, please refer to official public reports.

4.2 A Highway Project in Southeast Asia

Along the "Belt and Road," some highway projects have adopted the DB model, with contractors responsible for route design, subgrade and pavement construction, and traffic facility installation. Such projects involve complex geological conditions, and DB contractors reduce construction difficulty and cost through design optimization (e.g., adjusting alignment, optimizing slopes). Public reports can be found on relevant central state-owned enterprise websites and the Department of Outward Investment and Economic Cooperation of the Ministry of Commerce.

4.3 An Industrial Park Project in the Middle East

Industrial park projects in the Middle East often adopt the DB model, with the owner providing master planning and functional requirements, and the contractor responsible for detailed design, construction, and partial equipment installation. Such projects must satisfy local civil defense, environmental, and fire protection mandatory codes, and DB contractors must integrate local design consultants with international standards. For specific cases, please refer to public reports.

V. Frequently Asked Questions (FAQ)

Q1: What is the difference between DB and EPC?

DB and EPC are highly similar in contract structure, both being integrated design-construction models. The difference lies in: EPC places greater emphasis on "turnkey," with the contractor bearing a broader scope of procurement and commissioning responsibility; DB sometimes covers only design and construction, with procurement handled by the owner. In international practice, the two are often used interchangeably, with the key being the contract Scope of Work.

Q2: Under the DB model, how does the owner control design quality?

The owner specifies performance indicators through the Employer's Requirements and participates in key design confirmation through design review milestones, but should not excessively intervene in design details, as doing so may transfer corresponding liability. It is recommended to include a clause stating that "design review does not relieve the contractor of responsibility."

Q3: How should a DB contractor handle its relationship with local design institutes?

Common approaches: form a consortium with local design institutes, or engage them as design subcontractors. Local design institutes handle local code compliance, permitting, and approvals; international/Chinese design institutes handle overall solutions and core technology. Division of labor, responsibilities, and intellectual property must be clearly defined in the consortium agreement.

Q4: At the bid stage of a DB project, what level of design depth is required?

Typically Basic Design or Conceptual Design+ depth is required, sufficient to estimate quantities and costs. Too much design depth at bid increases costs; too little results in inadequate risk estimation. It is recommended to determine based on the owner's tender document requirements.

Q5: Under the DB model, who bears the risk of unforeseen geological conditions?

It depends on the contract provisions. Under the FIDIC Yellow Book, the contractor typically bears geological risk, but if the owner-provided survey data contains significant discrepancies, the contractor may claim a price adjustment. It is recommended to conduct independent surveys before bidding and to specify a Geotechnical Baseline in the contract.

VI. Practical Recommendations

1. Conduct thorough due diligence before bidding: Verify host country laws, taxation, foreign exchange, labor, environmental protection, and code systems item by item to avoid "winning the bid means losing money."

2. Clearly define functional requirement boundaries: Convert the owner's Employer's Requirements into verifiable performance indicators one by one, and seek written clarification on ambiguities.

3. Integrate design and construction early: Immediately form a joint design team after winning the bid, with the constructor engaging early to conduct constructability reviews.

4. Establish change control mechanisms: Document all changes in writing, set up a CCB, clarify cost and schedule impacts, and prevent "boiling frog" style changes.

5. Lock in key standard priorities: Specify in the contract the order of application as "local mandatory codes > contract-specified international standards > Chinese national standards" to avoid acceptance disputes.

6. Leave margin in performance guarantees: Reserve reasonable margins when pricing performance indicators to avoid triggering high liquidated damages due to failure to meet targets.

7. Make good use of insurance and guarantees: Procure professional indemnity and all-risk insurance, require subcontractors to provide performance bonds, and transfer some risks.

8. Emphasize defects liability period management: Prepare defect remediation plans in advance, retain sufficient warranty funds and personnel, and avoid delays in final acceptance.

9. Front-load dispute resolution clauses: Prioritize international arbitration (e.g., ICC, SIAC), and specify the seat of arbitration, language, and governing law.

10. Balance localization and compliance: Hire local consultants, lawyers, and accountants to ensure permitting, tax, and labor compliance, reducing local risks.

---

*This article is compiled based on public information and industry practice. For specific project data and standard numbers, please refer to official documents and contract provisions.*