Most construction claims fail on process, not merit. The outcome is usually settled months before anyone realises there is going to be an argument.
The most expensive twenty-eight days in construction
There is a particular kind of meeting that happens on troubled projects, usually about eight months in. Someone has finally totted up what the delays have cost, the number is worse than anyone privately feared, and the question on the table is who absorbs it. The contractor believes the answer is obvious. So does the employer. Both of them are, in a sense, right, and neither position is what will decide the outcome.
What decides it is a set of dates from months earlier that nobody was thinking about at the time.
Under the FIDIC forms that govern most major projects in the Gulf, a contractor who wants to claim additional time or money has to give notice within twenty-eight days of becoming aware of the event that caused it. Miss that window and the entitlement can be lost outright, regardless of how well-founded it was. The 2017 editions went further than their predecessors in making this explicit, and the drafting is deliberately unforgiving.
This is the uncomfortable heart of construction claims: a great many of them are lost not because the claim was weak, but because the paperwork that would have proved it was never created. The merits were fine. The process wasn’t.
What FIDIC actually is, and why the colour matters
FIDIC — the International Federation of Consulting Engineers — publishes a suite of standard contract forms that have become the default language of international construction. In the Gulf they are near-ubiquitous, though almost always amended.
The forms are usually referred to by the colour of their covers, and the distinction between them is not cosmetic. It is a decision about who carries risk.
The Red Book is for works designed by the employer. The employer owns the design, so the employer generally owns design risk, and the contractor is paid by measurement against what is actually built.
The Yellow Book covers plant and design-build. The contractor takes on the design, and with it the risk that the design does not perform, usually against a lump sum.
The Silver Book is the EPC/turnkey form, and it shifts risk furthest toward the contractor. The contractor is expected to have satisfied itself about site conditions, and the employer’s grounds for exposure narrow considerably. It is used where certainty of price and date matters more than flexibility — which describes a great many Gulf projects.
Choosing between them is not an administrative preference. It determines, before a single foundation is poured, who pays when the ground turns out to be different from the survey. Kairos, a Dubai-based project management consultancy, has a useful breakdown of how the FIDIC families differ for anyone who wants the detail.
The complication in practice is that almost nobody uses the standard form unamended. Particular Conditions routinely rewrite the risk allocation, and the amendments are where the real contract lives. A project team that has read the standard form and assumed it applies is working from the wrong document.
Why the Gulf raises the stakes
Everything above is true anywhere. The Gulf sharpens it for four reasons.
Scale. The region is running some of the largest construction and infrastructure programmes in the world. On a project of that size, a percentage point of leakage is a very large number.
Compression. Giga-projects are frequently built against fixed, publicly announced deadlines. Compressed programmes generate more concurrent activity, more interfaces, and more of exactly the events that give rise to claims.
Multi-party complexity. A single package might involve a European designer, an Asian contractor, regional subcontractors and an international project management consultant, operating across several legal traditions and working languages. Contemporaneous records — the ordinary daily evidence that claims are built from — get harder to maintain the more parties there are.
Heavy amendment. Gulf employers tend to amend the standard forms substantially. Notice periods get shortened. Conditions precedent get added. Dispute mechanisms get modified. Assumptions carried over from a textbook understanding of FIDIC are frequently wrong.
Put together, this is an environment where the gap between adequate and excellent contract administration is measured in nine figures rather than percentages.
Where claims are actually lost
In practice, failed claims tend to fail for the same handful of reasons, and almost none of them are about the underlying entitlement.
- The notice was late, or wasn’t a notice. An email to the engineer mentioning a problem is not necessarily notice under the contract. Many forms specify the addressee, the format, and what the notice must state. An informal heads-up that everyone acknowledged at the time can count for nothing.
- The records don’t exist. Delay analysis needs a baseline programme, regular updates, and site records showing what actually happened when. If the programme was never properly updated, reconstructing causation after the fact is expensive and unconvincing.
- Variations were handled informally. Someone senior said to proceed, work was done, and nobody papered it. Months later there is a genuine disagreement about scope with no contemporaneous record to resolve it.
- Concurrency was never analysed. Where employer delay and contractor delay overlap, entitlement depends on analysis that has to be built from data captured at the time.
- Nobody owned it. Contract administration sat with a project manager already fully occupied delivering the works, and it slipped.
The pattern is consistent: the claim was decided long before anyone thought of it as a claim.
What good contract administration looks like
The remedy is unglamorous and mostly a matter of discipline.
It means a contract register that records every notice, instruction, variation and claim with its dates and deadlines — so nothing depends on someone remembering. It means the programme being genuinely maintained rather than reissued unchanged. It means correspondence that is written with the knowledge it may be read in a dispute two years later. It means someone whose actual job is the commercial record, rather than someone doing it in the gaps.
Most importantly, it means running from day one rather than from the day a dispute starts. By the time a claim is contested, the evidence that would have won it was supposed to have been gathered months earlier. This is the whole argument for treating contract management as a discipline rather than an administrative afterthought: it only works if it is in place before it is needed.
The same logic applies to the forecasting side. Project controls — cost, schedule and risk run as live disciplines rather than monthly reporting — are what tell you in week six that the trajectory lands two months late, while there is still time to do something about it. Firms that treat project controls as an early-warning system rather than a reporting obligation get to make decisions early, when they are cheap. The alternative is a beautifully maintained dashboard that nobody steers by.
The economics
The reason this is chronically underfunded is that its successes are invisible. There is no line item for the dispute that never happened, the variation that was documented properly, the three months not lost. The costs of weak administration are equally invisible until they arrive all at once, by which point they have already been incurred.
Set against that, the cost of doing it properly is small and knowable. A contracts manager for the duration of a project is a rounding error against a single contested delay claim. The asymmetry is stark, and it runs the opposite way to most people’s instincts under budget pressure.
The clause that decides who pays is rarely the one anyone argues about at the time. It is the notice provision, buried in Clause 20, that determined the outcome months before anybody realised there was going to be an argument.