What Separates Contractors Who Recover Variation Costs From Those Who Don't

Jun 3 2026

What Separates Contractors Who Recover Variation Costs From Those Who Don’t

Same Change Event. Two Different Outcomes.

Two sub-contractors on the same project type. Both receive late design information from the consultant. Both carry out additional coordination work. Both absorb additional cost.

One recovers it. One doesn’t.

The design change was identical. The entitlement, in both cases, was probably real. The outcome was different — not because of legal sophistication, not because of contract type, and not because one had a more aggressive commercial team.

Because one was set up for it before the project started. The other wasn’t.

What the Contractors Who Recover Have in Common

After watching variation claims succeed and fail on UAE and Saudi projects, the pattern on the successful side is consistent across three areas.

They defined scope with a boundary, not just a description.

A scope of works that says “provide MEP coordination to LOD 350 in accordance with the BEP” is a performance obligation. It has no ceiling. It gives you no baseline from which to argue that something additional was instructed.

A scope that defines coordination cycles, identifies a design freeze milestone, and specifies what triggers an additional cycle has a boundary. When the consultant revises the design after that freeze point, you have a defined baseline to argue from. Without it, every revision is arguably “part of scope.”

The contractors who recover variations consistently are the ones who drew that boundary before the project started — not after the change event occurred.

They served notice when the event happened — not weeks later.

Under FIDIC Sub-Clause 20.1 (1999) and Sub-Clause 20.2 (2017), the notice requirement is 28 days from the date the contractor became aware of the event giving rise to a claim. In UAE courts and arbitration, late notice is routinely used as the first line of defence against variation claims. It does not always extinguish entitlement — but it significantly weakens the recovery position.

On fast-track projects, 28 days closes faster than most teams realise. The contractors who recover variations have a process: when a change event occurs, a notice goes out within days. Not at month-end, not with the next interim application. When the event happens.

They had contemporaneous records from day one.

A variation claim is only as strong as its evidence base. For BIM and coordination-related variations, that evidence is hours logged against specific cause, cross-referenced to the instruction or drawing revision that triggered the additional work.

These records need to be built in real time — weekly, event by event, from the start of coordination. A claim reconstructed at month five from email threads and memory is a starting position for a negotiation, not a substantiated claim. A claim built on weekly contemporaneous logs is a documented entitlement.

What the Contractors Who Don’t Recover Are Missing

The contractors who absorb variation costs are not less entitled. They are less prepared.

The scope had no ceiling, so every change is “still in scope.” The notice was served at month four, giving the other side a legitimate procedural defence. The records don’t exist in a format that supports a claim, so the quantum cannot be substantiated.

The variation argument then becomes a commercial negotiation starting from a weak position — where the contractor is asking for something rather than demonstrating an entitlement. Those negotiations settle at a fraction of the actual cost, or not at all.

This is not bad luck. It is the predictable outcome of a setup that didn’t account for variation risk before the project started.

The Setup That Changes the Outcome

Three things need to be in place before mobilisation — not after the first change event.

A scope ceiling. Whatever form the BIM and coordination obligation takes in the sub-contract, it needs at least one defined limit — a coordination cycle count, a design freeze reference, a resubmission cap. Something that creates a boundary from which additional scope can be argued.

A notice process. Someone on the project — the BIM manager, the project manager, or the commercial manager — needs to be explicitly responsible for identifying potential claim events and issuing written notice within the required timeframe. This is not the default behaviour of a BIM team. It is a commercial instruction that needs to be given at the start of the project.

A weekly log format. One page. Completed every week by the BIM team. What was worked on, how many hours, against which instruction or drawing revision, and what was the cause of any additional effort. Ten minutes per week during delivery. The foundation of a recoverable claim if a variation event occurs.

None of this requires a new contract. It requires treating variation risk as a setup task — before the project starts — rather than a recovery task after the cost has already been absorbed.

Vee7 works with sub-contractors and specialist contractors across UAE and Saudi Arabia on BIM delivery that is structured to protect commercial position — not just meet submission requirements. If your BIM setup has no variation risk process behind it, that is the right conversation to have before your next package.