Variation Claims Under FIDIC: Clauses 13.1 & 20.1 Explained
This guide unpacks how Variations work under FIDIC Clause 13, the interaction with Clause 20.1 notices, and the two paths a Variation claim typically travels. If your project has ongoing changes — and most do — understanding this structure is the difference between an orderly final account and a bruising dispute.
What Is a Variation Under FIDIC?
A Variation, under Clause 13 of the FIDIC 1999 Red Book, is any change to the Works instructed by the Engineer. It can add work, omit work, or modify how work is done. Variations can also change the sequence, timing, or method of any element of the Works.
When the Engineer instructs a Variation, two things happen contractually. First, the Works scope changes. Second, the Contract Price and (where relevant) the Time for Completion are adjusted to reflect the change. Both adjustments must be fair, and both usually require supporting information from the Contractor.
Not every site change is a Variation. A legitimate clarification of existing drawings, for example, is not. A correction of a drawing error may or may not be, depending on the contract wording. Proper identification matters because it determines which contractual process applies.
Key Takeaway: A Variation is a change to the Works instructed under Clause 13. It adjusts price and sometimes time. Not every change qualifies — identification matters, because Variations follow a different process from claims.
Instructed vs Constructive Variations
Variations come in two flavours, and contractors who do not recognise the second one end up leaving money behind.
- Instructed Variations — the Engineer issues a formal instruction explicitly labelled as a Variation. These are straightforward: the instruction is the trigger, and the valuation follows.
- Constructive Variations — the Employer or Engineer does something that effectively requires the Contractor to perform work differently, without ever calling it a Variation. Classic examples include unusual approval delays, unreasonable re-sequencing demands, restricted site access that changes the method, or unofficial instructions given in meetings.
Constructive Variations are the Trojan horse of FIDIC claims. They arrive disguised as "normal contract administration," cause real programme and cost impact, and only later reveal themselves as chargeable changes. The Contractor's job is to recognise them in real time — not in the final account.
If you suspect a constructive Variation, the safest route is a prompt Clause 20.1 notice describing the situation and requesting confirmation from the Engineer. The notice preserves the right; the Engineer's response either formalises the Variation or clarifies the position.
Key Takeaway: Instructed Variations are explicit; constructive Variations are hidden. Recognising the hidden ones in real time — and notifying under Clause 20.1 — is where the money hides.
The Two Notice Paths (13.1 + 20.1)
A Variation usually travels two parallel paths through the contract:
- The Clause 13 path — the Variation instruction itself is issued (or confirmed), the Contractor submits supporting information, and the Engineer values the change and adjusts the Contract Price and Time for Completion where applicable.
- The Clause 20.1 path — where the Variation causes consequential impact beyond the direct valuation (delay to other activities, disruption, acceleration costs), the Contractor notifies under Clause 20.1 within 28 days of awareness.
The two paths are not mutually exclusive — most significant Variations travel both. The Clause 13 valuation handles the direct work; the Clause 20.1 notice handles the knock-on effect. Skipping the Clause 20.1 notice because "it is already a Variation" is how contractors leave consequential costs on the table.
The timing matters. The Clause 13 submission has its own timeframe driven by the Engineer's request. The Clause 20.1 notice still runs on the 28-day rule from the awareness of the consequential impact. These are not the same date.
Key Takeaway: A Variation follows Clause 13 for valuation of the direct change and Clause 20.1 for consequential impact. Use both paths, and watch the separate deadlines — they do not overlap cleanly.
How Valuation Disputes Arise
Variation valuation sounds mechanical — rates from the Bill of Quantities, or fair new rates where none apply. In practice, it is the single most common source of final account disputes on FIDIC projects.
The standard causes:
- Rate analysis disagreement — the Engineer applies BoQ rates; the Contractor argues they are inapplicable because the conditions or quantities have changed. Both positions can have merit, and negotiation is the norm.
- Omission valuations — when the Engineer omits work, the Contractor often resists the BoQ rate applied to the omission because it loses contribution to fixed overheads. This is one of the hardest valuation fights to win.
- Star rates for new work — where BoQ rates do not apply, the Engineer must derive new "star" rates based on contract pricing principles. These negotiations can drag for months.
- Disruption and acceleration — the valuation of loss of productivity or acceleration costs arising from a Variation almost always needs separate notice and substantiation.
The Contractor's job is to participate actively in the valuation process, submit supporting records in time, and escalate disagreements through the contract's dispute mechanism when stuck. Going silent during valuation and then disputing the outcome at final account is a recipe for a weak case.
Key Takeaway: Valuation disputes are common and slow. Engage actively, submit timely records, challenge the Engineer's rates with substance (not just disagreement), and escalate properly when agreement is impossible.
When You Must Notify Separately
Not every Variation needs a Clause 20.1 notice. The direct value of a straightforward work change may be fully handled through Clause 13 valuation alone. But a Clause 20.1 notice becomes essential when:
- The Variation causes delay to other activities on the critical path
- The Variation disrupts productivity on unchanged work
- The Variation requires acceleration to maintain the completion date
- The Variation's cumulative impact with other changes exceeds what any individual valuation captures
- The situation is a constructive Variation the Engineer has not formally instructed
In each case, the Clause 13 valuation handles the direct work; the Clause 20.1 notice reserves the right to recover the knock-on impact. Without the notice, consequential costs are often lost when the Employer later argues that the valuation already covered everything.
Key Takeaway: Separate Clause 20.1 notice is needed whenever the Variation affects other work, disrupts productivity, requires acceleration, or builds cumulative impact. The direct valuation alone will not capture these.
How to Draft the Notice
A Clause 20.1 notice linked to a Variation should:
- Reference both Clauses 13 and 20.1 explicitly
- Identify the Variation by reference number and date
- Describe the consequential impact — specifically the effects beyond the direct work
- State the awareness date for the consequential impact (often different from the Variation instruction date)
- Reserve time and/or cost as appropriate
- Confirm that 42-day particulars will follow
The distinction between the Variation instruction and the consequential impact is critical. The Engineer can easily accept that the Variation happened while disputing that it caused the impact claimed. Your notice should make clear that the awareness of the impact — not the awareness of the Variation itself — is what triggered the 28-day clock.
Key Takeaway: Reference both Clauses 13 and 20.1, identify the Variation, and focus on the consequential impact — not the Variation itself. Awareness of the impact triggers the clock, and the Engineer will look closely at that date.
Common Mistakes With Variation Claims
- Assuming the Variation covers everything. A Clause 13 instruction values the direct change. Consequential impact needs its own Clause 20.1 notice.
- Missing constructive Variations entirely. Treating informal instructions, approval delays, or re-sequencing demands as "normal project life" instead of contractual events.
- Accepting the Engineer's valuation without substantiation. Once a rate is agreed, it is very hard to revisit. Push back in real time or not at all.
- Letting interim payments become the valuation. Interim certificates are provisional. Do not treat them as final agreement.
- Cumulative impact claims at final account. Waiting until the end of the project to claim cumulative disruption is usually too late. Notify events as they happen, and correlate the cumulative impact in supporting submissions.
- Mixing multiple Variations into one notice. Each Variation impact should be separately identified, even if bundled administratively. Mixing them creates confusion and gives the Engineer ammunition.
Key Takeaway: The recurring errors are assuming Variations cover consequential impact, missing constructive Variations, accepting valuations without substantiation, and claiming cumulative disruption at final account. Each of these is avoidable with disciplined real-time notification.
Frequently Asked Questions
What is a Variation under FIDIC?
A Variation is any change to the Works instructed by the Engineer under Clause 13. It can add, omit, or modify work, and adjusts the Contract Price and (where relevant) the Time for Completion. Variations must be properly valued and often trigger notice requirements for cost or time impact.
What is a "constructive variation"?
A constructive variation is a change in the Works caused by the Employer's conduct or instructions that, although not labelled as a Variation, effectively functions as one. Examples include re-sequencing demands, restricted access patterns, or unusual approval delays. These require prompt notice under Clause 20.1 to preserve the entitlement.
Do I need a separate notice for the cost or time impact of a Variation?
Usually yes, particularly where the consequential impact extends beyond the direct valuation of the Variation itself. The Variation instruction covers the added or omitted work; a Clause 20.1 notice covers the knock-on effects on programme and other activities.
Can the Contractor refuse to execute a Variation?
Only in limited circumstances — typically where the Variation is outside the scope of the Contract, requires specialist work the Contractor cannot reasonably perform, or otherwise falls outside the Engineer's powers. In most cases, the Contractor must proceed and then secure fair valuation and any notice-based claims for impact.
What if the Engineer and Contractor cannot agree on the valuation?
The Engineer is entitled to make a fair determination under the Contract. If the Contractor disagrees, the dispute can be escalated through the contract's dispute mechanism — typically the DAAB, then arbitration. Proper notice and substantiation throughout the process are essential for any later challenge.