Managing EOT Claims on GCC Projects: From Delay Event to Determination

Most contractors treat an EOT claim as a document to be produced once the delay has run its course. The claim becomes a writing exercise, started late and assembled from whatever the project happens to have kept. On GCC projects, where EOT claims meet amended FIDIC forms and strictly enforced time bars, that approach surrenders entitlement before the first page is drafted.

The EOT Claim Is a Lifecycle, Not a Document

A successful extension of time claim is the output of a process with distinct stages: identifying the delay event, preserving the right through notice, building the evidence while the delay runs, analysing cause and effect against the programme, quantifying the time and any cost, submitting within the contractual windows, and managing the determination that follows. Each stage has its own deadline, its own evidential standard, and its own way of failing.

Treating those stages as one task, performed at the end, is the most common structural mistake we see. A claim assembled as a reconstruction reads as one. A claim that grew alongside the delay reads as a record of fact, and tribunals treat the two very differently.

What Do EOT Claims in the GCC Actually Involve?

EOT claims in the GCC run on three layers at once. The contract, usually a FIDIC form amended by Particular Conditions the employer drafted. The procedure, notices and submissions under Clause 20 with time bars that tribunals across the region enforce. And the governing law, civil codes that shape how obligations, evidence, and good faith are read. A contractor managing a claim is managing all three at the same time.

The amendments matter more than the form. Employer-drafted Particular Conditions routinely shorten notice periods, add service formalities, and convert procedural steps into conditions precedent. A claims team that reads only the standard form is administering a contract that does not exist. The starting point of every claim is the contract as amended, not as printed.

From Event to Notice: The Window That Decides Everything

The lifecycle opens with recognition, not drafting. Someone on the project has to identify that an instruction, a late drawing, an access restriction, or a changed site condition is a delay event with contractual consequences, and fix the date of awareness in writing. Every deadline that follows runs from that date, whether anyone recorded it or not.

Notice is the stage that kills more claims than any analysis ever will. The 28-day rule exists to be enforced, and a notice that is late, informal, or served on the wrong address preserves nothing. Serve it in the contractual form within the window and the rest of the lifecycle stays open. Miss it and the finest delay analysis in the region has nothing to attach to.

Building the Claim While the Delay Runs

Entitlement is proved, not asserted. The contemporaneous records created while the delay runs are the claim's evidence base: site diaries, programme updates, dated photographs, correspondence, and resource returns that connect the event to its effect. The Society of Construction Law Delay and Disruption Protocol recommends precisely this, records agreed early and delay analysed from evidence made at the time.

Method matters as much as material. The delay analysis has to fit the records the project actually holds, the requirements of the contract, and the nature of the delay itself. A time impact analysis built on a programme nobody updated persuades no one. Choosing the methodology early, while the records that support it are still being created, is analysis. Choosing it in the final week is triage.

Submission, Determination, and What Comes After

Under the 2017 forms the fully detailed claim falls due 84 days from awareness, and the statement of contractual basis carries its own sanction. The submission is a legal argument, an engineering analysis, and a commercial account in one document, and it is read by an Engineer whose determination sets the negotiating baseline for everything that follows.

Determination is managed, not awaited. Respond to requests for particulars quickly, keep interim claims current where the effect of the event continues, and treat a rejection, actual or deemed, as the start of the escalation clock rather than the end of the claim. Contractors who recover time treat the dispute board and arbitration provisions as live procedure. Contractors who lose it treat them as decoration.

The Discipline That Separates Recovered Time From Lost Time

In CALIM's experience across dozens of GCC engagements, the difference between recovered and surrendered entitlement is rarely the quality of the argument. It is whether anyone ran the claim as a workstream: an owner for each stage, deadlines tracked from the date of awareness, records reviewed monthly, and quantum built alongside the delay rather than after it. The recurring failure points are set out in why so many EOT claims get rejected, and every one of them is a process failure before it is a legal one.

At CALIM, we run EOT claims as embedded claims management engagements: the lifecycle mapped at the first sign of delay, notices served to the contractual standard, records structured for the chosen methodology, and submissions built to be determined, not merely filed.

Frequently Asked Questions

How long do I have to submit an EOT claim under FIDIC?

Notice of the claim is due within 28 days of the date you became aware, or should have become aware, of the delay event. The fully detailed claim follows within 84 days of the same date under the 2017 forms. Employer amendments often shorten both periods, so the contract as amended governs.

What should my EOT claim actually contain?

Four things: the contractual basis of entitlement, the facts of the delay event evidenced by contemporaneous records, a cause-and-effect delay analysis against the programme, and the extension and any associated cost claimed. A submission that asserts delay without connecting event to effect through the programme is an opinion, not a claim.

Can I claim prolongation costs together with my EOT claim?

Usually, but they are separate entitlements with separate proofs. The EOT addresses time and relief from delay damages. Prolongation addresses the cost of staying on site for the extended period, proved through actual time-related costs incurred. Claim both where the contract allows, and evidence them separately.

What happens if the Engineer rejects or ignores my EOT claim?

A rejection, or a determination that never arrives, opens the next stage rather than ending the claim. Under FIDIC 2017 a claim the Engineer fails to agree or determine within the contractual period is deemed rejected, which releases it to the dispute board. Track the escalation deadlines as strictly as the original notice.

Do amended GCC contracts change the standard FIDIC claim procedure?

Almost always. Particular Conditions commonly shorten notice periods, prescribe the form and address for service, add conditions precedent, and adjust the Engineer's determination timeline. The printed FIDIC procedure is only the starting point. Run every deadline from the contract as amended, not from the standard form.

An EOT claim is not written at the end of a delay. It is run from the start of one.

Note: This article provides general information on managing extension of time claims and is not legal advice. Entitlement and procedure depend on the contract form, the Particular Conditions, and the governing law. Contractors should take advice on their own contract before relying on it.