Most variation control on UAE projects is administration dressed as governance. The register records what has already been instructed, the monthly report totals it, and by the time anyone is alarmed the decision that caused it was taken months earlier by somebody on the owner's own side of the table.
Owners do. A peer-reviewed study of UAE construction firms ranks variations initiated by the owner as the single largest cause of disputes in this market — ahead of permit and approval delays, ahead of material changes during construction, ahead of owner slowness in decision-making. Owner-related causes ranked highest of all categories surveyed.
The study covered 150 firms with 54 responses, split between local and international contractors and consultants, scored on a weighted scale. Owner-initiated variations came top at 4.06. An earlier UAE study across 56 Dubai and Abu Dhabi firms reached the same place by a different route: change and variation orders were the leading cause of claims at 51.3%, and oral change orders by the owner ranked third at 48.8%.
The regional picture is consistent. A dispute-analytics series covering Middle East projects found change in scope affecting 57.3% of them against 33.3% globally, and late design information affecting 32.1% against a global 17.9%.
So this is not an article about resisting contractor claims. It is about not generating them. Everything that follows assumes the owner is the party with the most to fix.
No — and the belief that it does is among the most widely repeated errors in this market. The Civil Code requires the employer's assent to the change and an agreement covering it. It prescribes no particular form. The writing requirement that everyone cites comes from the contract, usually FIDIC Clause 13, not from statute.
The point is sharper than it looks. The old lump-sum provision required assent plus an agreement in force with the contractor concerning the modification. The neighbouring provision governing re-measurable contracts did impose a notice duty with an express forfeiture sanction — if the contractor failed to notify, its right lapsed. The legislator knew exactly how to write a strict procedural bar, and chose not to write one for lump-sum variations.
Under the Civil Transactions Law in force since June, the successor provision keeps the lump-sum bar: a contractor executing an agreed design for a lump sum cannot demand an increase, and is entitled to additional payment for a change in scope only by agreement of the parties. Two features matter to an owner. It applies unless otherwise agreed by the parties — it is a default rule, so if you want a writing requirement to bite, it has to be in your contract, because the Code will not supply it.
And it adds something new that cuts against owners: an entitlement to additional payment where the change is attributable to the employer's own fault. Defective employer-supplied information. Late instructions. Employer-caused disruption. That provision is aimed squarely at projects tendered before the design was frozen, and it does not require the owner to have agreed anything.
One note on sourcing. The official text of the new Code is not publicly retrievable in full — the published file truncates before the relevant chapter. The account above is drawn from consistent reporting by five named law firms, and this article does not quote the provision as statutory text.
Probably none with any consequence attached. The 1999 FIDIC editions that still dominate this market contain no advance-warning provision at all. The 2017 editions added one — a duty owed by both parties to advise in advance of known or probable events which may adversely affect the contractor's personnel or the performance of the works, increase the contract price, or delay execution.
It has no sanction. Two independent commentaries say so in terms: there is no sanction provided for failure to comply, and no time limit for giving a warning. The only leverage available is the general claims provision, which requires the owner to show that the failure prevented or prejudiced proper investigation of the claim — a much weaker instrument than it sounds.
Two things partly fill the gap.
The Civil Transactions Law now imposes its own duty: the contractor must immediately notify the employer of events or circumstances that may impede proper execution of the works, and on failure bears the consequences arising from them. Named firms read that as exposure to damages and to loss of entitlement to extension of time or additional payment. It sits underneath whatever the contract says, and one firm assesses that it shifts the balance in the owner's favour on time bars — a contractor arguing that enforcing a notice bar offends good faith is now arguing against the grain of the statute.
And NEC shows what a working mechanism looks like. Where the project manager decides the contractor failed to give an early warning that an experienced contractor would have given, the compensation event is assessed as if the warning had been given. Not forfeiture — counterfactual assessment, which strips out the premium created by lateness and leaves the contractor paid what timely warning would have cost. NEC pairs that with a standing register carrying two mandatory fields, the risk and the action to avoid or reduce it, produced within a week of start, with a contractually stated meeting interval and a reissued register within a week of each meeting.
| Mechanism | Who owes it | Trigger | Time limit | Sanction for failure |
|---|---|---|---|---|
| FIDIC 1999 | — | No advance-warning provision | — | None |
| FIDIC 2017 | Both parties | Known or probable events affecting personnel, performance, price or time | None stated | None; only the general prejudice provision |
| NEC | Both parties | Matters that could increase the price, delay completion or a key date, or impair performance in use | As soon as aware | Compensation event assessed as if the warning had been given |
| UAE Civil Transactions Law | Contractor | Events that may impede proper execution | Immediately | Contractor bears the consequences |
There is also a provision most owners already have and never monitor. Under the 2017 editions, if the contractor considers an instruction constitutes a variation it must give notice immediately and before starting the work, and the Engineer has seven days to confirm, reverse or vary the instruction. If the Engineer does not respond, the instruction is deemed revoked. For an owner that notice is a dated, formal declaration that somebody on their team has just changed the scope — and a seven-day clock running against their own consultant.
Because the notice is the cheap part. Published research comparing projects with and without early warning — 97 completed responses at a 32.3% response rate, from professionals with five years or more in key management roles — found highly significant effects on resolving issues at the lowest level, on speed of resolution and on mutual satisfaction, and significant effects on abandoning blame culture and on joint problem-solving. Quality improved with high significance and time with significance.
But the effect on cost was only marginal. And the effect on preventing the same problem recurring was not significant at all. Early warning surfaces and resolves. It does not fix the system that generated the problem.
At scale it degrades further. A study with a major infrastructure client found projects above £100m generating more than one early-warning notice per day, with contractors submitting around 82% of them. The mechanism was being used asymmetrically — as commercial self-protection rather than joint risk management — and administrative sanctions intended for risk management were being weaponised for commercial advantage.
So the argument is not "install early warning." It is that the value sits in what happens after the notice: triage, a governance forum with the authority to decide, and closing the loop back into design and approval management. A register that produces notices and no decisions is a claims file being assembled at your expense.
Four things that no published register carries. The lag between when a change originated and when it was instructed. A notice clock running on both parties. Attribution of where the change came from. And a link to the precursor — the request for information, the late approval, the unanswered submittal that preceded it.
Every register I have reviewed, from software vendors and professional bodies alike, logs changes after they have become changes. That makes them accounting records. An early-warning register has to capture the thing before it is a variation, or it is not doing early warning.
| Field | Why it is there |
|---|---|
| Reference number | Discrete registration for every change, agreed or not |
| Precursor | The request for information, late approval or unanswered submittal that preceded it |
| Date of origin | When the change actually arose |
| Date of instruction | The lag between origin and instruction is the leading indicator |
| Source | Owner, design, authority, site condition or contractor |
| Notice clock | Contractual deadline and days remaining, tracked for both parties |
| Cost impact | Estimated at origin, then agreed |
| Time impact | Estimated at origin, then agreed |
| Authority implication | Whether it triggers a resubmission, and the programme cost of that |
| Status | Agreed, pending consideration, more information requested, or rejected |
| Owner | The named competent reviewer accountable for the decision |
Around that sits the governance layer, and published guidance is clear about what it requires: a discrete registration number for every change; status tracked as agreed, pending consideration, more information requested or rejected; a single named competent reviewer with cost, time, safety and performance expertise; a change board on larger projects; and a monthly documentation pack covering the instruction, its contractual basis, build-ups, effects on preliminaries and insurances, and a revised programme.
The UAE-specific column is the authority implication. A change that triggers a resubmission to the municipality or a free-zone authority carries a programme cost that nobody prices at the moment it is instructed, and which surfaces six weeks later as a delay nobody attributed to the change.
There are also leading indicators worth logging alongside, drawn from a published indicator inventory: early depletion of contingency or allowances; change orders that omit time and impact-cost provisions; excessive or frivolous requests for information; a radical change in the tone of progress meetings; a claims consultant appearing at site meetings; and float eroding while the completion date stays unchanged. None of these is a variation. All of them precede one.
Classification, retrieval and flagging can be automated reliably. Prediction cannot. Software can read the document flow across correspondence, requests for information and submittals, and surface the mechanical facts an owner's team misses at volume — the request raised eighteen days ago and still unanswered, the notice with no reply, the drawing revision issued without a corresponding instruction. What it cannot do, on the published evidence, is tell you a claim is coming.
The honest statistic is worth stating. A 2026 scientometric review of text mining and natural language processing in construction research covered 153 peer-reviewed articles published over a decade. Thirty-eight of them address safety risk identification, where the models are mature and validated against large public accident datasets. Four address contract management and dispute resolution. The review's own stated limitations include scarce domain-specific labelled data, historical dependence, regional limitation, degraded performance outside the training domain, and inconsistent data standards preventing generalisation across projects.
Set against that, the commercial claims in this space are unvalidated — an eighty per cent reduction in review time supported by a single customer testimonial, forty per cent more compensation events identified with no methodology, sample or baseline disclosed.
So the formulation we use is not marketing language, it is a description of where the evidence stops: machines analyse the document flow; senior people exercise judgement. Automate the detection of lag and silence, because that is mechanical and machines are better at it than a project team reading three hundred emails a week. Keep the judgement about what a lag means with a named human who can be asked why they decided what they decided.
You lose the benefit of it. UAE law contains a principle that a party who seeks to set aside what he has conclusively performed shall be rejected — functionally an estoppel. Two Cassation decisions have applied it, including one barring an employer from claiming delay damages for delay it had itself caused.
An owner who has repeatedly paid for unwritten variations has performed conduct it may struggle to disavow when it later insists on the letter of the contract. Combined with the good-faith duty, that is a serious argument, and it is the most likely route for a contractor to defeat a defence built on the absence of a written order.
The counterweight is real, and recent. A 2023 DIFC Court of Appeal decision enforced the FIDIC 28-day notice as a condition precedent notwithstanding that the employer was responsible for the bulk of the delay, rejecting the prevention principle as an override and holding that the obligation of good faith neither requires nor permits rewriting agreed terms to circumvent a time bar. A January 2026 Privy Council decision on a lump-sum FIDIC contract went further: a contractor lost four categories of allegedly oral-instructed work for failing to give early warning, failing to seek a determination and failing to claim within the notice period — the court holding that the Engineer has no authority to waive contractual machinery, and that certainty, not flexibility, lies at the heart of sophisticated construction contracts.
That decision should be read honestly, because it cuts both ways. Roughly two million dollars of work that was actually performed went unpaid on process rather than merit. An owner relying on that severity is relying on a mechanism that will be applied to it with equal indifference.
Which is why the instruction is not "insist on writing." It is enforce consistently. Selective enforcement is what converts a defensible position into a losing one, and it is the single most common self-inflicted wound in this area.
One related point worth knowing: no UAE onshore judgment appears to hold that a consultant's certification binds the employer. Commentary suggests the engineer binds the employer as its agent absent bad faith, but also that where the contract requires the employer's consent for a document to issue, it cannot bind without it — and assessment of performance sits within the trial court's discretion in any event. Certification is neither a shield nor a settled liability.
Dubai's own government contracting law supplies a benchmark. A government entity may issue a variation order reducing a contract's value by any percentage whatsoever, but may increase it by no more than thirty per cent of the total contract value — and only where the approving authority matches the value and type of the change, and where funds are confirmed available in the budget before the order is made.
Private owners are not bound by any of this. It is still the clearest UAE statement of what a well-governed contract treats as the outer limit of change, and the two features beyond the headline number are the useful ones. The cap is asymmetric — unlimited omission, thirty per cent ceiling on addition. And the gate is a three-part test: authority threshold, funding confirmation, percentage ceiling. Any private owner can adopt that tomorrow.
On what change costs, published analysis with a stated derivation puts median direct rework at around five per cent of contract cost, and combined direct and indirect rework at 7.25 to 10.89 per cent with a median just above nine, alongside schedule growth near ten per cent — roughly 72 days on a two-year programme.
And one correction worth making openly. The design-stage cost curve that appears in every presentation on this subject has no published dataset behind it. The researcher who traced its history concluded it should be treated as a diagram rather than a statement of fact, and the underlying idea dates to a paper from 1976. The direction it describes is uncontroversial and matches everyone's experience. The multipliers attached to it are not evidenced, and this article does not repeat them.
Yes, and there is Gulf evidence for it rather than assertion. A peer-reviewed study measured ten completed projects where variation orders ran at 7.13% of contract value, then applied a three-stage variation management framework across thirty-two further projects. Additional budget impact fell from 11.79% to 3.2%. Deductions fell from 7.85% to 2.5%. And average variations per project fell from 10.3 to 3.3.
The root cause the authors identified is worth sitting with: the combined effect of the designer, the owner's technical committee, the designer's documentation and the owner's stakeholder committee. Which is the same finding as the UAE dispute study, arrived at from the opposite direction.
The decision this article asks an owner to make is therefore not about how to administer variations. It is about accepting that the input is theirs to control. Freeze the brief before tender. Close the design rather than issuing it in tranches. Resource the approvals so late authority responses stop generating instructions. And run one register that catches precursors rather than recording outcomes.
The contractor's claim is almost always downstream of a decision the owner made months earlier. The register's job is to make that decision visible while it is still a decision.
Under the FIDIC forms the 28-day notice operates as a condition precedent, and both a 2023 DIFC Court of Appeal decision and a January 2026 Privy Council decision enforced it strictly — the DIFC case even where the employer caused most of the delay. Good faith arguments were rejected as a route around it. The bar bites.
Usually not successfully, but do not rely on that. A January 2026 appellate decision denied four categories of allegedly oral-instructed work because the contractor had not sought a determination or claimed in time. The owner's real exposure is different: a pattern of paying for unwritten instructions may prevent you from later insisting on the written requirement.
Published guidance sets a five-tier hierarchy: contract rates for similar work; pro-rata adjustment with a fair allowance for changed character, conditions or quantity; fair valuation at actual cost plus overhead and profit; dayworks for minor or unmeasurable work; and a contractor quotation. Check for collateral effects on other work, and guard against double recovery between valuation and loss and expense.
It depends entirely on the form. Under FIDIC 2017 there is no sanction — the duty exists and nothing attaches to breaching it. Under NEC the compensation event is assessed as if the warning had been given, which removes the premium created by lateness. Under the UAE Civil Transactions Law the contractor bears the consequences of failing to notify impediments.
The contractor is exposed, and so are you. Its claim will likely fail on process. Your exposure is that the work exists, may be needed, and may be unpaid — which is not a stable position on a live project. The answer is to decide, in the forum, within a stated period, rather than letting the question sit unanswered.
Watch the precursors, not the variations. Early depletion of contingency. Requests for information rising in volume or falling in quality. Notices with no reply. A change in the tone of progress meetings. A claims consultant attending site. Float eroding while the completion date stays fixed. None of these is a claim. All of them come before one.
Bring the project. The first conversation is a working session, not a sales call.