Comparison · 7 min read

Red Book vs Yellow Book, compared.

The single sharpest structural difference in the FIDIC Rainbow Suite is where design responsibility sits. Here is how that one difference cascades through everything else.

The FIDIC Red Book and Yellow Book are both used on substantial construction projects. They share a lot of structural DNA — the notice discipline, the Engineer role, the claims workflow. But they answer one foundational question differently: who designs the works?

Get that answer right and the rest of the contract follows naturally. Get it wrong and the contract fights you at every step.

Design responsibility — the whole game

Under the Red Book, the Employer takes design responsibility. The Contractor is generally entitled to rely on the design as issued.

Under the Yellow Book, the Contractor takes design responsibility. The Employer defines outcomes through the Employer's Requirements; the Contractor produces a Proposal and delivers to it.

That difference shapes everything downstream: risk allocation, price basis, notice discipline, and the shape of any future claims.

Side by side

DimensionRed BookYellow Book
Full nameConditions of Contract for ConstructionConditions of Contract for Plant and Design-Build
Design responsibilityEmployerContractor
Design liability standardEmployer (subject to consultant appointments)Contractor, typically fitness for purpose
Payment basisTypically re-measured against Bill of QuantitiesTypically lump sum
Anchor documentEmployer's design (drawings, specifications)Employer's Requirements + Contractor's Proposal
Engineer roleFull contract administratorFull contract administrator
Risk allocationShared, moderate on ContractorWeighted more heavily toward Contractor
Typical projectsRoads, bridges, water networks, Employer-designed civilsProcess plant, MEP, data centres, industrial buildings
Ground conditionsShared risk (edition-specific mechanism)Shared risk, with tighter Contractor allocation
Best use caseEmployer wants control over designEmployer wants outcome; Contractor wants design freedom

How the design line changes claims

On a Red Book contract, a common Contractor claim category is late Employer information — drawings, RFIs, design decisions that arrive later than needed on the critical path. Because design responsibility sits with the Employer, that late information is often a contractual event.

On a Yellow Book contract, the equivalent categories are different. Design approval delays, changes to the Employer's Requirements, and interface issues with Employer-supplied packages come up more often than pure late-drawing claims. The Contractor is responsible for its own design; it cannot claim for its own design delay.

How the payment basis changes the schedule

Re-measurement on the Red Book means the BOQ drives the value of each measured item; the schedule is used for progress tracking and cash-flow forecasting. Under a Yellow Book lump-sum contract, the schedule doubles as the value baseline — typically through a schedule of values or activity-loaded schedule — and progress reporting drives payment applications directly.

Choosing between them

Two questions matter most in the choice:

  1. Does the Employer want to own the design? If yes, Red. If no, Yellow.
  2. Is the risk profile better priced by the Employer or the Contractor? If the Employer, Red. If the Contractor is genuinely better placed to price and manage the risk, Yellow.

See also: Red Book explained, Yellow Book explained, and the full four-way comparison on our course page: Red vs Yellow vs Silver vs Green.

A common procurement mistake

Contracting a Design-Build outcome under a Red Book, or contracting a construction-only scope under a Yellow Book, is one of the most common and expensive procurement mistakes in FIDIC. The design-responsibility line is not a technicality — it changes the whole risk shape of the contract.

Related GSTPM course
Both Books, side by side in practice.

The GSTPM FIDIC Contract Management course covers all four Books and how to choose between them for real projects.