Variation vs Contractor Risk Under FIDIC: How a Senior QS Makes the Call
The Fiber Optic Cable Nobody Knew Was There
During excavation for a major box culvert on a FIDIC Red Book highway project, our site team hit an uncharted, active fiber optic cable. It was positioned directly beneath where the box culvert foundation was supposed to go.
The Engineer issued an immediate instruction: stop excavation, safely expose the cable, and wait for the telecommunications company to relocate it.
The idle machinery costs were accumulating by the hour. The critical path was being affected. And the commercial question that needed answering immediately was: who pays for this?
Is this a Variation? Or is this the Contractor's Risk?
That question, in various forms, is one of the most commercially significant judgments a Quantity Surveyor makes on a construction project. Getting it right protects millions of dollars of entitlement. Getting it wrong means doing work for free, or submitting claims that will be rejected, or missing deadlines that destroy legal entitlement entirely.
This article shares the professional framework for making that judgment, the most common and costly mistakes QS professionals make, and the honest truth about how AI can help and where it will get you into serious trouble.
📚 Related Articles You May Find Useful:
The Three Tests - A Professional Framework
When an Engineer's instruction arrives or a site event occurs, I apply three sequential tests to determine whether the situation constitutes a genuine Variation or falls within the Contractor's contractual risk.
Test 1 - The Scope Test
Compare the Engineer's instruction against the original contract documents: the Bill of Quantities, Drawings, and Specification. The core question is whether the instruction adds, omits, or modifies the physical works beyond what the contract originally required.
If the Engineer is simply telling the Contractor to comply with obligations already accepted under the contract, that is not a Variation. That is the Contractor doing what they agreed to do.
If the instruction requires something genuinely additional to or different from the original contracted scope, that is the first indicator of a potential Variation.
Test 2 - The "What vs How" Rule
This is the golden rule of contracting and one of the most practically useful tools in FIDIC commercial management.
- The Employer and Engineer decide WHAT to build - "Build a box culvert to these dimensions at this location."
- The Contractor decides HOW to build it - "I will use this equipment, this sequence, this method."
If the Engineer steps in and dictates HOW the Contractor must execute their work, requiring a specific method, sequence, or resource that the Contractor had not planned and that adds cost, that is a Variation. The Engineer has crossed from specifying the end product into controlling the means of production.
If the Engineer stays within their lane and only directs WHAT the final product must be, the method remains the Contractor's risk.
Test 3 - The "Who Caused This?" Test
Trace the root cause of the event back to its origin.
- If a pipe is missing because the Employer's designer forgot to include it in the drawings, the Employer pays. That is a Variation.
- If a pipe is missing because the Contractor's site team ran over it with an excavator, the Contractor pays. That is their risk.
The causation question is often the most difficult to answer honestly, because site situations are rarely clean. But the professional discipline of tracing the root cause to its origin, rather than simply identifying who is suffering the financial consequence, is what separates a professionally defensible position from a speculative claim.
The Fiber Optic Cable - Three Tests Applied
💼 Real Situation — FIDIC Red Book Highway Project:
Scope Test: Did the contract drawings show this fiber optic cable? No. Was it reasonable for the Contractor to know it was there? No. Local utility records and available documentation did not show its existence. The Contractor had no reasonable basis to anticipate this obstacle.
What vs How Test: The Engineer was not simply telling the Contractor how to dig safely within their planned method. The Engineer was altering the sequence of work entirely and forcing a halt to a critical path activity because of a site constraint that the Employer's design process had failed to identify and disclose.
Causation Test: The delay was not caused by poor planning or a Contractor mistake. The root cause was an inaccurate design baseline that was missing critical utility data. The Employer provides the site. The Employer's designers are responsible for the accuracy of the design information. An unmapped active utility beneath the foundation location is a site deficiency that belongs to the Employer.
The Decision: This was not a Contractor Risk. Under the FIDIC Red Book, this situation engaged Sub-Clause 4.12 (Unforeseeable Physical Conditions) because an experienced contractor could not reasonably have foreseen this obstacle. Additionally, because the Engineer explicitly instructed a stop to works and a change to the construction sequence, it also engaged Clause 13 (Variations and Adjustments).
The claim was prepared on the basis of both unforeseeable physical conditions and Engineer's instruction, with contemporaneous records of idle plant, daily site diary entries, and the written Engineer's instruction as the core documentary evidence.
The 5 Most Costly Mistakes QS Professionals Make
Mistake 1 - The "Do It Now, Sort It Out Later" Trap
This is the single most common and commercially damaging mistake on construction projects. The Engineer gives a verbal instruction during a site walkthrough, promising to issue a formal Variation Order later. The Contractor executes the work.
Months later, the Engineer denies ever giving the instruction, or claims it was simply a "clarification" of existing work rather than a new instruction.
Under FIDIC Clause 3.3, if the Engineer gives an oral instruction, the Contractor has two working days to send a written confirmation. If the Engineer does not respond with a written rejection within two working days of receiving that confirmation, the confirmation constitutes the written instruction of the Engineer.
If the Contractor fails to send that written confirmation within two working days, the protection is lost. The work may have been completed. The cost may have been incurred. The entitlement is gone.
The rule: never execute work based on a verbal instruction without immediately issuing a written confirmation under Clause 3.3.
Mistake 2 - Confusing "Harder Than Expected" With a Variation
Contractors frequently assume that because a job becomes more difficult or more expensive than originally estimated, the additional cost must constitute a Variation. This misunderstands the fundamental allocation of risk in construction contracts.
Under Yellow Book and Silver Book contracts, the Contractor owns the design risk and the site investigation risk. Encountering hard rock during excavation is not automatically a Variation. A spike in steel prices is not a Variation. These are execution risks that the Contractor priced and accepted at tender.
The threshold for an unforeseeable physical condition claim under Sub-Clause 4.12 is specifically: conditions that an experienced contractor could not reasonably have foreseen. A harder job than estimated does not meet this threshold. An uncharted active utility not shown in any available records may.
Mistake 3 - Missing the 28 Day FIDIC Notice Deadline
FIDIC Sub-Clause 20.1 gives the Contractor 28 days from becoming aware of the event to issue a formal claim notice. Miss this deadline by one day and the contractual entitlement is completely waived. The Employer pays zero, regardless of how genuine the underlying claim may be.
The mistake is waiting. Waiting until the end of the month. Waiting until the scope of the claim is fully understood. Waiting until the cost has been quantified. The notice does not need to contain the full quantum. It needs to describe the event and be issued within 28 days.
Issue the notice first. Quantify the claim second. In that order. Always.
Mistake 4 - Relying on the BOQ Instead of the Drawings
QS professionals from a traditional measurement background sometimes treat the Bill of Quantities as the definitive scope document. If an item is not in the BOQ, they assume it must be a Variation.
Under design-build contracts (Yellow Book), the BOQ is primarily a pricing mechanism, not a scope definition document. Even under a Red Book, if a requirement is clearly shown on the contract drawings and specification but the estimator failed to include it in the BOQ description, the Contractor is generally expected to have priced it within their rates.
The contract drawings and specification define the scope. The BOQ prices it. Where there is conflict, the contract conditions and drawings typically take precedence.
Mistake 5 - Writing Emotional Letters Instead of Contractual Ones
When a variation is rejected or a claim is disputed, contractors sometimes allow frustration to drive their correspondence. Letters that say "this is unfair" or "the Engineer is causing unreasonable delays" achieve nothing commercially and undermine professional credibility.
An Engineer or arbitrator does not respond to emotional arguments. They respond to contractual ones. A professional letter must say: "Pursuant to Sub-Clause 13.1, this instruction constitutes a change to the Employer's Requirements, and notice is hereby given under Sub-Clause 20.1 of the Contractor's entitlement to additional time and cost."
Without the right clause references and the right professional tone, correspondence is commercially useless in any formal dispute.
How AI Actually Helps - The Practical Applications
I do not use AI to make the final variation versus risk decision. I use it to speed up the preparatory work and cross-reference data efficiently.
1. Instant Document Cross-Checking
When an Engineer issues an instruction about a specific item, I can upload the relevant specification section, BOQ, and Employer's Requirements into a secure AI tool and ask: does this specific item appear anywhere in the contract documents, or is this a completely new requirement? AI can scan thousands of pages in seconds and return exact clause or page references. What would take hours of manual document review takes minutes.
2. Drafting Tight Contractual Notices
AI is excellent at translating site frustration into cold, professional contractual language. If a project manager tells me the Engineer is forcing an expensive change to the pipe route, I can ask AI to draft a formal Notice of Variation under FIDIC Red Book Sub-Clause 13.1, with the exact formal tone required for contract correspondence. The factual content comes from me. The professional structure comes from AI.
3. Playing Devil's Advocate
Before submitting a claim to the Engineer, I feed my argument to AI and ask: act as a budget-conscious Engineer representing the Employer and find every weakness in my argument to reject this variation. This approach helps identify gaps in the claim logic before the real Engineer does. It is one of the most practically useful AI applications in commercial QS practice.
The Honest Warnings - Where AI Will Get You Into Serious Trouble
⚠️ Read This Before Using AI for Variation Assessment:
Warning 1: AI Hallucinates Clauses:
AI models are built to predict text, not to understand the legal weight of a contract clause. If you ask an AI to find a clause supporting your variation claim, it will sometimes invent a sub-clause that sounds completely real, complete with professional legal phrasing, but does not actually exist in your specific FIDIC edition. If you copy that invented clause reference into a formal letter to an experienced Engineer, your professional credibility is destroyed immediately. Always verify every clause reference against the actual contract document before professional use.
Warning 2: AI Cannot See Site Reality:
A variation claim is rarely won on contract text alone. It is won on contemporaneous records: daily site logs, weather reports, signed meeting minutes, time-stamped photographs. AI does not know that the concrete pour was delayed because the subcontractor's pump broke down (Contractor Risk), even if the drawings were revised the same day (potential Variation). Only a human who has spoken to the site team and reviewed the actual records can map out the real causation.
Warning 3: Garbage In, Garbage Out:
If you ask AI "the Engineer changed the design, is it a variation?" the AI will say yes. Because you gave it biased information. AI does not know how to cross-examine your account of events. It does not know that three weeks ago your team built the wall in the wrong location and the Engineer's instruction was simply a correction of a Contractor error. One-sided input produces one-sided output. Feed AI a complete and honest picture, or the answer is commercially useless.
Warning 4: Data Confidentiality:
Uploading your project's contract documents, commercial correspondence, and dispute details into public AI platforms is a serious breach of confidentiality obligations in most major construction contracts. If your Employer discovers sensitive project data has been uploaded to a public AI model, you could face legal consequences or immediate termination. Use enterprise AI platforms with appropriate data protection agreements for sensitive commercial work.
The Golden Rule for the Modern QS
Use AI to draft. Never to decide.
Treat AI as a calculator for text. Use it to organize your thoughts, write your letters, and search your documents. But never sign off on a variation assessment or a risk decision unless you have personally opened the physical contract, verified the clause, and confirmed the actual facts on the ground with your site team.
Conclusion
The fiber optic cable was not in the drawings. The Contractor could not reasonably have known it was there. The Engineer's instruction changed the construction sequence. Three tests applied. Three tests confirmed: this was a Variation, not a Contractor Risk.
That judgment call, made correctly and documented properly, protected a significant financial entitlement for the project.
AI assisted in drafting the formal correspondence and cross-referencing the specification documents. The judgment itself required direct site knowledge, professional contract expertise, and the discipline to trace the root cause honestly rather than conveniently.
Apply the three tests. Issue the notice within 28 days. Write contractual letters not emotional ones. Use AI to draft faster. Use professional judgment to decide correctly.
On a FIDIC project, the difference between a Variation and a Contractor Risk is often the difference between a recovered cost and an unrecoverable loss. Get that judgment right.
💬 Found This Useful?
If this article helped you, please consider:
- ⭐ Sharing on LinkedIn, every QS professional working under FIDIC needs this framework
- 💬 Leaving a comment below, have you ever had a variation claim rejected because it was actually Contractor Risk? Share your experience!
- 📖 Reading our related articles, links below
What is the most difficult variation vs contractor risk judgment you have faced? Share it in the comments!
About The Author
A practicing Quantity Surveyor with extensive experience in large scale infrastructure projects under FIDIC conditions.
Qualifications:
- BSc (Hons) Quantity Surveying
- MRICS, Royal Institution of Chartered Surveyors
- MCIOB, Chartered Institute of Building
- MQSi, Quantity Surveyors International
This blog shares real professional experience from live construction projects, not theoretical content.
📚 Related Articles You May Find Useful:
Frequently Asked Questions
What is the difference between a Variation and a Contractor Risk under FIDIC?
A Variation is a change to the original contracted scope instructed by the Engineer or arising from an Employer risk event, entitling the Contractor to additional time and payment. A Contractor Risk is an event or cost that the Contractor accepted as part of their contractual obligations when they tendered, for which no additional entitlement arises. The three tests for distinguishing between them are the Scope Test, the What vs How Rule, and the Causation Test.
What is the "What vs How" rule in FIDIC contracts?
The What vs How rule holds that the Employer and Engineer decide what to build, while the Contractor decides how to build it. If the Engineer steps in and dictates the Contractor's construction method, sequence, or resources in a way that adds cost beyond the original plan, they have created a Variation. If they only specify the end product and leave the method to the Contractor, any difficulty in execution is the Contractor's risk.
What is FIDIC Sub-Clause 4.12 and when does it apply?
Sub-Clause 4.12 covers Unforeseeable Physical Conditions, meaning physical conditions encountered during execution that an experienced contractor could not reasonably have foreseen based on available information at the time of tendering. The threshold is specific: conditions must be genuinely unforeseeable to an experienced contractor, not merely more difficult or expensive than anticipated.
Can AI determine whether something is a Variation or Contractor Risk?
No. AI can assist with document cross-checking, notice drafting, and correspondence structuring. The variation versus risk judgment requires direct site knowledge, professional contract expertise, and honest causation analysis that AI cannot perform. The golden rule: use AI to draft, never to decide.
What happens if AI invents a FIDIC clause that does not exist?
If an AI-generated clause reference is included in formal correspondence to an Engineer without verification, your professional credibility is immediately undermined. Experienced Engineers know FIDIC clause numbering precisely. An invented clause reference signals either professional incompetence or AI-generated content that was not checked. Always verify every clause reference against the actual contract document before professional use.
Why is the 28 day notice so important for variation claims?
Under FIDIC Sub-Clause 20.1, missing the 28 day notice deadline results in complete loss of entitlement to additional time and payment, regardless of how genuine the underlying claim may be. The notice does not need to contain the full quantum at this stage. It needs to describe the event and be issued on time. Issue the notice first. Quantify the claim second.
Take Your QS Workflow to the Next Level
Choose the free tool that fits your current task:
Comments
Post a Comment