Extension of Time Claims in GCC Construction: How to Build a FIDIC-Compliant Record

Most Delay Claims Fail on Documentation, Not Merit

The delay happened. The contractor was entitled. But three months after the event, the project records are a mix of WhatsApp screenshots, unsigned daily reports, and emails nobody replied to. When the formal claim is submitted, the engineer disputes the dates, the subcontractor forgets the conversation, and the notice was never sent.

This is how GCC contractors lose EOT claims they deserved to win. Not through weak entitlement — through weak record-keeping. Building a FIDIC-compliant claim is a continuous process that starts on day one of the project, not on the day you instruct a claims consultant.

FIDIC Clause 20.2: The 28-Day Clock Most Contractors Miss

Under FIDIC 2017, Clause 20.2.1 requires the contractor to give notice of a claim within 28 days of when the contractor became aware — or should have become aware — of the event giving rise to the claim. Miss the window and you lose entitlement, regardless of the merits.

Three things make this harder than it sounds:

• "Became aware" is interpreted broadly. Engineers and arbitral tribunals apply an objective test: when should a competent contractor have known? If you were aware of a late drawing but did not connect it to a critical path impact for 60 days, the clock may have started at day one.
• On a 400-person GCC construction site, the event and the notification process involve different people. The site engineer sees the problem; the contract manager writes the notice. The handoff often does not happen.
• Verbal acknowledgement of delay by the engineer or client does not satisfy the notice requirement. FIDIC Clause 1.3 requires notices in writing, with specific references.

The fix is not a legal one — it is a process one. The project team needs a system that captures delay events at the field level in real time, triggers a contract manager review within 24-48 hours, and generates a formal notice before the 28-day clock expires.

The Four Delay Types That Determine Your Entitlement

Not all delays carry the same recovery rights. Under FIDIC, the classification of the delay event determines whether you recover time, cost, or both:

• Employer-risk events — late drawings, late access, late instructions, nominated subcontractor failure, variation orders: time and cost under Clauses 8.5 and 13.
• Exceptional events (force majeure) — conflict, natural disasters, pandemic-related restrictions: time only under Clause 19.
• Concurrent delays — where both parties contributed to the same delay period: typically time only, no cost recovery for the concurrent period.
• Contractor-risk events — own resource shortfalls, subcontractor failures, procurement mismanagement: no entitlement; liquidated damages exposure under Clause 8.8.

Misclassifying a delay — treating a late instruction as a force majeure event, or failing to document that a delay was employer-caused — creates a claim that collapses under scrutiny. The classification needs to happen at the time of the event, not during claim preparation six months later when memories have faded and the project team has moved on.

Five Contemporaneous Records That Make or Break a Delay Claim

Contemporaneous means captured at the time. Anything assembled retrospectively will be challenged, and tribunals treat reconstructed evidence as significantly weaker than records created during the delay itself.

1. Daily Construction Reports

Structured DCRs with mandatory constraint fields — not free-text comment boxes. The DCR for the day a delay event starts should record: the constraint category (Late Employer Instruction, Late Material Delivery, Access Restriction), the work package affected, the number of resources on standby, and the first occurrence date. DCRs signed off within 24 hours by the PM and formally submitted to the engineer are near-irrefutable. DCRs reconstructed from memory and signed retroactively are routinely dismissed.

2. Resource Records by Trade and Package

Total headcount is not enough. What the arbitrator needs is resource records at the trade and subcontract package level. If you have 140 rebar fixers stood down for nine days because employer-issued structural drawings were late, that is 1,260 man-days of unrecovered resource cost — but only if the records were captured daily, broken down by package, not reconstructed from aggregate payroll runs.

3. RFI and Transmittal Logs with Response Dates

Every request for information and every document submission must be time-stamped in a register, with submission date, contractual response period, actual response date, and WBS activity affected. If the engineer took 52 days to respond to an RFI about a critical structural interface — against a 14-day contractual period — that log is direct evidence of a 38-day delay cause. Without the log, it is a disputed assertion.

4. Procurement Records Linked to Activity Dates

Late-delivery materials that held up critical activities need an unbroken paper trail: original PO delivery commitment, vendor promised dates at order and at follow-up, GRN actual date, and the WBS activity start date that was dependent on the delivery. A one-week material delay on a critical path activity supports a one-week EOT — but only if the link between the GRN date and the activity start is documented, not assumed.

5. FIDIC Correspondence Register

Formal letters, notices, and engineer instructions must be tracked in a dedicated register — reference number, issue date, subject, FIDIC clause invoked, response due date, and response received date. Not emails. Not WhatsApp. FIDIC Clause 1.3 is explicit: notices must be in writing, delivered to the specified address. If a contractor gives verbal notice of a delay event, the engineer can argue — and often does — that the contractual clock never started.

Quantifying the Claim: From "We Were Delayed" to a Defensible Number

Having the records establishes causation. You still need to connect the delay event to a measurable extension of the contract completion date. The two most widely accepted approaches in GCC and FIDIC arbitration are:

Time Impact Analysis (TIA): Take the accepted as-planned programme at the point of the delay event. Insert the delay as a new activity with its actual duration. Run a forward pass to determine the revised completion date. The difference is the impacted period attributable to that event.

As-planned vs as-built per delay event: For each claimed event, document the planned start and finish of affected activities, the actual start and finish, and the causal link between the delay event and the activity start. This method is easier to explain to non-technical reviewers and works well when delay events are discrete rather than overlapping.

Both approaches require one precondition: a baseline programme that was formally accepted by the engineer, with all revisions tracked and accepted rather than silently overwritten. A programme that has been amended 18 times with no formal revision history has lost its baseline integrity — and with it, the foundation of any TIA.

On a SAR 300M infrastructure package in the Eastern Province, a contractor presented a claim covering seven delay events over 14 months. Five events were supported by contemporaneous DCRs, resource logs, and RFI response records. Two were reconstructed from payroll data and email searches. The tribunal awarded recovery on the five supported events. The two reconstructed claims were dismissed — not because the delays did not occur, but because the evidence did not survive adversarial cross-examination.

How a Unified Project System Builds the Claims File Passively

The gap between knowing you have an entitlement and being able to prove it is a data problem. By the time a claim is formally submitted — typically 6-18 months after the events — paper-based and email-based systems have lost the thread. People have left the project. Files have been archived. The timeline has to be reconstructed from fragments.

A platform that connects daily reports, RFI logs, transmittal records, procurement timelines, and resource allocations means the claims file is being assembled continuously as the project runs. Three integrations matter most:

• DCR to delay event register: Every constraint entry in a daily report auto-populates a delay log with first occurrence date, cumulative duration, and affected work package.
• RFI register to schedule activities: RFIs linked to specific WBS activities so the response lag directly connects to measurable schedule impact rather than requiring a separate analytical exercise.
• Procurement records to activity start dependencies: PO delivery dates linked to the activity start dates they feed, so a late GRN creates an automatic delay event record with the procurement trail already attached.

The secondary benefit is deterrence. When the project team, subcontractors, and the engineer know that every delay event is being logged in real time — with first occurrence dates, constraint categories, and resource counts — disputed events become less frequent and claims settle faster.

Actionable Takeaways

• Set up a 28-day notice tracker. Every delay event gets logged on the day it occurs, with a 14-day internal trigger to prepare and submit a formal notice before the FIDIC window closes.
• Define a constraint taxonomy in your DCR system. Six to eight standard categories — Late Drawing, Late Instruction, Access Restriction, Late Material, Force Majeure, Client Variation, Weather, Concurrent — capture 90% of real-world delay events.
• Record resources at the trade and package level, not just total headcount. Idle resources disaggregated by subcontract package is what quantification requires.
• Register every RFI and transmittal in a single log with response dates. Export it monthly during the project, not only at dispute stage.
• Lock and formally accept your baseline programme. All revisions should be submitted to and accepted by the engineer in writing. Never overwrite a baseline.
• Build the claims file as you go. Twelve months of clean contemporaneous records settles faster and costs less to prepare than six months of retrospective reconstruction — and it changes the negotiating dynamic before you reach arbitration.