Contract Administration in GCC Construction: Managing FIDIC Obligations Before They Manage You

How many FIDIC notices did your project send last month — and how many were sent on time?

Most GCC contractors know the contract exists. Very few actively administer it. The difference shows up at final account: one contractor walks away with substantiated claims and full variation value; the other is arguing from memory with no contemporaneous records to stand on.

What Contract Administration Actually Means Day-to-Day

Signing the contract is not contract administration. Contract administration is the daily practice of tracking what the contract requires, doing it on time, and building the record that proves you did.

On a FIDIC Red Book project, that means issuing formal notices within contractual timeframes, submitting monthly statements that capture everything you are owed, documenting instructions and constraints as they happen — not when the dispute starts — and tracking subcontract obligations that mirror your main contract duties.

Every week you do not actively administer the contract, you are giving away entitlement. The question is how much, and whether you will find out before or after the final account is closed.

The Six FIDIC Obligations GCC Contractors Consistently Miss

1. Clause 20.2.1 — The 28-Day Notice

Any delay event entitling you to an EOT or additional cost requires a formal notice within 28 days of when you first became aware. Not 28 days after the impact became clear. Not 28 days after the instruction. Twenty-eight days from awareness.

Most contractors miss this because there is no system tracking when awareness occurred. The event gets noted in a site diary, the PM intends to raise it, and by the time the commercial team reviews it, the window has closed. A SAR 300M Eastern Province contractor lost SAR 4.2M in EOT entitlement for exactly this reason — seven documented delay events, all sent after the 28-day window had expired.

2. Clause 8.3 — Programme Updates

After an EOT event, a revised programme must be submitted showing the impact. Failure to update the programme weakens your entitlement — clients argue the delay was absorbed into the existing float. The programme update is not optional paperwork; it is a condition of the entitlement in most GCC contract forms.

3. Clause 14.3 — Monthly Statements

Clause 14.3 requires a statement of what you are owed, submitted monthly. This includes variations that are instructed but not yet formally approved. Contractors who do not submit monthly statements miss the opportunity to put instructed variations into the interim certification cycle — and miss the ZATCA tax point clock on Saudi contracts.

4. Clause 13.1 — Written Variation Instructions

Work directed verbally or by email does not automatically create a formal variation. FIDIC Clause 13 requires a written instruction. Contractors who execute variation work without a formal written instruction often find that work excluded from the final account with no recourse.

5. Clause 2.1 — Late Site Access

When the client fails to give access on time, there is an entitlement. But only if documented with dates, areas, and measurable impact. Late site access is one of the most common GCC delay causes and one of the least well-recorded. The event is known; the record does not exist.

6. Clause 4.24 — Fossils and Antiquities

Specific to GCC projects: when excavation hits archaeological material — not uncommon in the Arabian Peninsula — there is a contract procedure and a time obligation to comply with. Teams who do not know the clause exists lose the right to additional cost and time before the first call is made to the heritage authority.

Notice Management: Why the Calendar Matters More Than the Contract

A FIDIC obligation is not a concept. It is an action, a deadline, and a document trail.

For a SAR 200M project running 24 months, you will typically generate 40 to 80 potential notice events — weather delays, late access, unforeseen ground conditions, design changes, late approvals. Each one has a 28-day window.

Without a dedicated notice register that tracks the event, the date of first awareness, the 28-day expiry, the notice status, and the formal FIDIC correspondence reference, you are managing these deadlines by memory. That is how you lose SAR 3 to 8 million of legitimate entitlement on a mid-size project.

The notice register does not need to be complex. A log with six fields — event description, awareness date, expiry date, responsible party, status, reference number — reviewed weekly by the QS and project director closes the gap.

Monthly Statements as Cash Flow Protection

Clause 14.3 monthly statements are not just accounting. They are a commercial discipline that most GCC contractors underuse.

Every variation you have been instructed but not yet formally approved should appear in the monthly statement with its estimated value. This does two things: it puts the variation into the payment cycle, and it establishes a submission date that protects you commercially and under ZATCA Phase 2 for Saudi projects.

Contractors who wait until variations are approved before invoicing can wait three to six months on a complex design change. Contractors who submit monthly statements with instructed-but-unapproved variations start the clock earlier and create a contemporaneous commercial record that is very difficult to dispute later.

On a SAR 30 to 40 million monthly billing project, compressing the variation submission cycle by one month is worth SAR 200,000 to 400,000 in financing cost savings annually.

Back-to-Back Subcontract Obligations

Most GCC main contracts are FIDIC-based. Most subcontracts are back-to-back with the main contract. That means your Clause 20 notice obligations flow down: if a subcontractor delay event gives you a main contract notice entitlement, you need the subcontractor to notify you in time for you to notify the client.

In practice, subcontractors are rarely trained on FIDIC notice requirements. They call the site manager. The site manager notes it. The 28-day clock runs.

A working back-to-back administration process captures subcontractor events at the point they occur, maps them to the corresponding main contract notice deadline, and issues both sets of notices within the window. The three-layer chain — event to sub notification to main contract notice — is the difference between a recoverable delay and an unrecoverable one.

For GCC GCs managing 15 to 30 active subcontracts on a major programme, this chain needs to be systematic, not relationship-dependent.

Building a Contract Obligation Register

The minimum viable contract administration tool is a register that tracks:

• Obligation type — notice, programme update, monthly statement, instruction response, approval deadline
• Trigger — the event or clause that activates it
• Due date — calculated from the trigger date
• Responsible party — PM, QS, project director, or subcontract manager
• Status — open, issued, or overdue
• Reference — the document number when issued

Weekly review cadence: 15 minutes. Every open obligation with a due date in the next 14 days goes onto the week's action list. Every overdue obligation gets escalated immediately — overdue FIDIC notices are not recoverable after the fact.

For GCC projects with Vision 2030 clients, this register also serves as prequalification evidence. Aramco, NEOM, and ROSHN now evaluate contractors on commercial process maturity — not just HSE and technical capacity. A contractor who can produce a FIDIC correspondence register with all notices issued on time is a materially different commercial proposition from one who cannot.

Five Practical Starting Steps

• Audit your last three claim events. Were notices sent within 28 days of awareness? If not, identify exactly where the process broke down — PM awareness, commercial team lag, or no tracking system at all.
• Set up a notice deadline calendar. For every delay event currently live on your project, enter the 28-day expiry date in a shared calendar with a 7-day advance alert assigned to the QS.
• Review your last three monthly statements. Did they include all instructed but unapproved variations? If not, add a one-hour commercial review step before each statement is submitted.
• Document your subcontract notice obligations. Check whether your subcontracts include a notice provision mirroring Clause 20. Add it to the next subcontract template. Notify current subcontract managers of the requirement in writing.
• Create a FIDIC correspondence register today. Every formal letter, notice, and instruction needs a reference number, a date, and a status. The document trail you need at final account is built one notice at a time — not reconstructed under pressure six months before it closes.

Contract administration is not something you do when a dispute starts. By then, you are reconstructing — and reconstruction is expensive, uncertain, and often unsuccessful. The contractors who recover full entitlement on GCC projects are the ones who built the record as they went.