FIDIC Claims Notice Deadlines, What Every Saudi Contractor Must Know

Saudi Arabia's construction market is now dominated by FIDIC and FIDIC-derived contracts. Vision 2030 giga-projects, mega infrastructure programmes, and most large private developments all reference FIDIC's Red, Yellow or Silver books. Yet contractors continue to lose hundreds of millions of riyals every year not because their claims lack merit, but because they miss a single procedural step: the notice.

What is a FIDIC notice?

A FIDIC notice is the formal written communication that activates a contractor's right to additional time or money. It is the legal trigger that converts an event on site into an enforceable entitlement under the contract. Without it, the right does not crystallise, even if the underlying delay or cost was entirely the Employer's fault.

Under Sub-Clause 20.1 of the 1999 Red Book and Sub-Clause 20.2.1 of the 2017 Red Book, the contractor must serve notice on the Engineer within 28 days of the event giving rise to the claim, or 28 days of when it should reasonably have been aware of it.

Clause 20 explained

FIDIC Clause 20 (now Clause 20 / 21 in the 2017 editions, depending on the book) sets out a two-stage process:

1. Notice of Claim (28 days), short, dated, identifies the event. This is the condition precedent.
2. Fully Detailed Claim (84 days), full contractual basis, supporting records, quantum and time impact. Can be updated as the event continues.

The 2017 editions tightened the regime considerably. Sub-Clause 20.2.4 expressly requires the contractor to maintain "contemporary records" sufficient to support the claim, and the Engineer can reject the claim outright if the records are inadequate. Saudi tribunals and DABs increasingly enforce this.

Common deadline mistakes

From auditing dozens of Saudi contractor claim files at Nahl ALMaha, five mistakes appear again and again:

• Treating site instructions as informal. A verbal instruction from the Engineer's representative still triggers the 28-day clock.
• Sending the notice to the wrong party. Notice must go to the Engineer (or Employer's Representative under the Silver Book), not the Project Manager or Consultant's site staff.
• Using email without the contractual notice format. If the Particular Conditions specify hard copy or a portal, email alone may not satisfy Sub-Clause 1.3.
• Missing the trigger date. The clock starts on awareness of the event, not on the date the cost or delay materialises.
• Letting the notice lapse on continuing events. A continuing event (e.g. ongoing access restriction) requires periodic updates under Sub-Clause 20.2.5.

Case study, SAR 47 million lost on a Riyadh project

A tier-1 Saudi contractor delivering a mixed-use scheme in northern Riyadh suffered an 11-month delay caused entirely by late Employer-supplied design information. The contractor's commercial team raised internal cost claims monthly but issued only one Clause 20 notice, at month seven, when the Project Director escalated the matter.

At final account, the Engineer rejected SAR 47 million of prolongation and disruption costs on the basis that the 28-day notice was issued out of time for events that had occurred between months one and six. The technical entitlement was never disputed. The procedural failure cost the contractor the entire project margin.

How N&M prevents losses

Our Commercial & Contractual Management team embeds within contractor commercial functions to:

• Run a daily "notice register" that auto-flags events triggering the 28-day clock.
• Train site engineers and QSs to recognise notifiable events at the point they occur.
• Draft compliant notices in the exact format required by the Particular Conditions.
• Maintain contemporary records mapped to each open notice.
• Audit the claim chain quarterly so nothing falls between cost, planning and contracts.

On every project we have run this discipline, the notice rejection rate has fallen to under 5%, protecting tens of millions in entitlement that would otherwise be discharged.