A variation clause exists for a simple reason: change is normal on complex projects, and someone needs a formal way to capture it — what changed, why, what it costs, what it does to the programme, and who agreed to all of it.
Used at the moment change happens, that mechanism does exactly what it was designed to do. It gives the Employer visibility into what’s being added to the contract and why. It gives the Contractor a documented right to time and cost. It converts an informal moment on site into a position both parties can rely on later.
Used after the fact — reconstructed weeks or months later, once the work is already done — the same clause stops protecting anyone. It becomes a negotiation about memory, not a record of fact.
THE MECHANISM DOESN’T CHANGE. THE TIMING DOES
Every FIDIC-based and most bespoke construction contracts contain broadly the same architecture: an instruction is given, its effect on scope is identified, it’s valued, and the valuation is agreed or determined. Nothing about that architecture is unusual or contentious.
What varies enormously, project to project, is whether that sequence happens close to the event or long after it. And that timing gap — not the contract wording — is usually what determines whether a variation ends up strengthening a project’s commercial position or quietly weakening it.
HOW A VARIATION SLIDES FROM CONTROL INTO EXPOSURE
The slide rarely happens through a single bad decision. It happens through a sequence of individually reasonable ones.
An instruction is given informally — verbally on site, or in an email that doesn’t reference the contract mechanism at all — because the work is urgent and everyone already understands what’s being asked. The Contractor proceeds, because stopping to formalise the instruction first would look uncooperative, and the relationship is good enough that formality feels unnecessary.
Valuation gets deferred. There’s a general sense that “we’ll sort out the numbers later,” because the immediate priority is keeping the work moving, not building a commercial position. Weeks pass. The event that triggered the variation starts to blur into the broader flow of the project — no longer a distinct, dated, causally clear instruction, but one of several things that happened “around that time.”
By the time anyone raises the variation formally, the conversation has already changed shape. It’s no longer “here’s what was instructed, valued, and needs to be agreed.” It’s “do you remember agreeing to this?” — a question answered by recollection and inference, not by a record created when the facts were still fresh.
THE SAME CLAUSE, TWO DIFFERENT FUNCTIONS
This is what makes variations structurally interesting compared to some other contract mechanisms: the clause itself is neutral. It doesn’t determine whether it will function as protection or as exposure. That’s determined entirely by how — and especially when — it’s actually used.
Raised at the time, a variation instruction creates a contemporaneous record: what was asked, by whom, under what authority, with what immediate understanding of scope. That record doesn’t need to resolve every question about value or programme impact on day one. It just needs to exist, clearly enough that later valuation and agreement have something solid to build on.
Raised late, the same instruction has to be reconstructed from whatever happens to survive — an email thread that doesn’t quite capture the full instruction, a site diary entry that mentions the work without explaining the direction behind it, the recollection of people who may or may not still be on the project. The variation mechanism is still technically available. What’s missing is the evidential foundation that makes it worth anything.
WHY “WE’LL FORMALISE IT LATER” IS THE MOMENT CONTROL STARTS SLIPPING
The phrase sounds harmless because, in the moment, it usually is reasonable — the work genuinely is urgent, the relationship genuinely doesn’t need friction introduced over a routine instruction, and everyone genuinely does understand what’s happening.
The problem isn’t the individual decision. It’s that “later” rarely arrives on its own. Formalising a variation after the fact requires someone to actively return to an event that’s no longer urgent, no longer top of mind, and increasingly inconvenient to raise the longer it’s left — because raising it late can itself start to look like an afterthought, or worse, an attempt to manufacture a claim.
Meanwhile, the underlying exposure doesn’t wait for anyone’s convenience. Cost is being incurred. Programme may be affected. And the contractual position that should be tracking all of that in real time is instead sitting in a queue of things to “sort out later” — a queue that tends to grow faster than it clears.
WHAT KEEPS A VARIATION FUNCTIONING AS CONTROL
None of this requires treating every instruction as a formal event requiring immediate written confirmation with full valuation attached. That level of rigidity creates its own problems — friction, delay, and a project culture where raising anything formally feels adversarial.
What it does require is a much smaller discipline: separating the instruction from the valuation. The instruction — what changed, when, under what authority — can and should be captured close to the event, even briefly. A short written confirmation, even after an informal verbal instruction, preserves the record without requiring the full commercial conversation to happen immediately.
The valuation, the programme impact, the final agreed value — all of that can legitimately follow later, once enough information exists to assess it properly. What can’t wait is the basic record that the event happened, what it was, and that both parties understood a variation was in play. That’s the piece that, once lost to time, is nearly impossible to reconstruct credibly.
THE PRINCIPLE
A variation clause is not, by itself, a source of contractual protection. It’s a mechanism that produces protection only when it’s actually operated close to the events it’s meant to capture.
The same clause, applied promptly, gives both parties a shared, reliable record of change. Applied retrospectively, it gives neither party much more than a dispute about what was probably meant, probably agreed, probably understood — reconstructed from whatever fragments happen to have survived.
The contract doesn’t change between those two outcomes. What changes is discipline — whether the mechanism is used as a live control during execution, or remembered only once someone needs to explain, after the fact, where the money went.
How ACC TRUST can support
ACC TRUST supports contractors, subcontractors and project owners in maintaining variation discipline throughout execution, including:
- reviewing current practice for identifying, instructing and recording variations as they occur;
- structuring variation registers that separate instruction, valuation and agreement, so nothing waits unnecessarily on the others;
- identifying live projects where variations have accumulated without formal instruction or valuation, while records can still be reconstructed;
- reviewing delegated authority for issuing and confirming instructions;
- supporting the preparation and negotiation of variations where the underlying record is already incomplete.
For independent support with contract administration, variation management or commercial risk:
Explore ACC TRUST services:
→ https://acctrust.ro/en/services
Discuss a specific project:
→ office@acctrust.ro
About ACC Trust Insights
ACC Trust Insights is the knowledge centre for Commercial & Contract Governance, Project Delivery and Risk Management in complex construction, infrastructure and energy projects.
Explore all articles:
→ https://insights.acctrust.ro
ACC TRUST
Commercial & Contract Governance Advisory
Property · Infrastructure · Energy