Delays are an inevitable reality in major construction projects. However, for contractors operating under the standard FIDIC Red Book (Conditions of Contract for Construction), managing delays is not just a scheduling challenge—it is a strict contractual procedure. Securing an extension of time FIDIC Red Book (EOT) is essential to shield your project from costly liquidated damages (LDs) and to claim prolongation costs.

A single missed deadline, a poorly drafted notice, or an inadequate delay analysis can bar a contractor from any entitlement, leaving them fully liable for delays. To prevent this, commercial managers and contract administrators must follow a disciplined, step-by-step process.

This guide outlines the essential FIDIC EOT claim checklist that every contractor should implement on site. We also show how digital contract tools like LegisDex streamline these notice and risk management workflows to protect project margins.

The Contractor's FIDIC Red Book EOT Claim Checklist

1. Identify the Delay Event & Establish Entitlement

Before spending time preparing a submission, you must verify that the delay event qualifies for an extension under the contract. Under Clause 8.4 of the FIDIC Red Book 1999 (or Clause 8.5 of the 2017 Edition), a contractor is entitled to an EOT if completion is or will be delayed by any of the following causes:

A Variation (unless valued as a change to completion time under Clause 13).
A cause of delay giving entitlement to EOT under a specific clause of the Conditions (e.g., Clause 1.9 [Delayed Drawings], Clause 4.12 [Unforeseeable Physical Conditions], or Clause 4.7 [Setting Out Errors]).
Exceptionally adverse climatic conditions (supported by historical weather data).
Unforeseeable shortages in the availability of personnel or Goods caused by epidemic or governmental actions.
Any delay, impediment, or prevention caused by or attributable to the Employer, the Employer's Personnel, or the Employer's other contractors on site.

💡 How LegisDex simplifies this: Upload your contract documents to the secure LegisDex Contract Q&A workspace. You can ask the AI chat direct questions like, "What are the requirements for setting-out error claims under this contract?" or "Does adverse weather entitle us to cost under this agreement?" to confirm your contractual basis immediately without flipping through hundreds of PDF pages.

2. Issue the Notice of Claim within the 28-Day Time Bar

The notice requirement is the most critical hurdle under the FIDIC Red Book. Under Clause 20.1 (1999 Edition) / Clause 20.2.1 (2017 Edition), the Contractor must give notice to the Engineer of the event or circumstance giving rise to the claim.

⚠️ Warning: Notice must be given within 28 days after the Contractor became aware, or should have become aware, of the event or circumstance. If the Contractor fails to give notice within this 28-day period, the Time for Completion will not be extended, the Contractor will not be entitled to additional payment, and the Employer is discharged from all liability.

Keep your notice concise and formal. It must state that it is a notice under Clause 20, describe the delay event, and mention that a detailed submission will follow.

💡 How LegisDex simplifies this: Setting up automated Compliance Playbooks on LegisDex allows your commercial team to automatically screen site instructions and emails. The AI flags notice periods and alerts you when critical notice deadlines are approaching, ensuring you never miss a 28-day window.

3. Establish Contemporary Records on Site

Under FIDIC Clause 20.1 (1999 Edition) / Clause 20.2.3 (2017 Edition), you must keep contemporary records as may be necessary to substantiate any claim. Contemporary records are those generated at the actual time the delay is occurring. Retroactive records created months later carry very little weight in disputes.

Ensure your project team is diligently compiling:

Daily site logs indicating manpower levels, machinery usage, and specific activity locations.
Weather records (daily temperatures, rainfall, wind speeds) matched against historical averages.
Material delivery receipts and correspondence showing supply chain disruptions.
Progress photographs and videos showing delayed work areas.
Written instructions, emails, and minutes of site progress meetings.

💡 How LegisDex simplifies this: Instead of leaving records scattered across site diaries, personal laptops, or chat threads, you can upload them to LegisDex. Our Issue Tracker links these contemporary records directly to the contract clause and the specific claim, building a watertight, auditable evidence trail for the Engineer's review.

4. Demonstrate Critical Path Impact (Delay Analysis)

Entitlement is only half the battle; you must prove that the delay event actually delayed the completion date of the project. This requires showing that the event impacted the critical path of the Clause 8.3 Programme.

Contractors should employ recognized delay analysis methodologies, such as:

Time Impact Analysis (TIA): Ideal for ongoing delays. You insert the delay event (modeled as a delay subnet) into the latest updated schedule to see its prospective impact.
As-Planned vs. As-Built: A retrospective comparison of what was planned to happen against what actually occurred.
Collapsed As-Built (But-For Analysis): Removing delay events from the actual schedule to show when the project would have finished but for the Employer's delays.

Ensure your program baseline is regularly updated. If the Engineer has not formally approved schedule updates, compile contemporary evidence of the work sequence regardless.

5. Submit the Fully Detailed Claim within 42 Days

Within 42 days (or another period approved by the Engineer) after you became aware (or should have become aware) of the delay event, you must submit a fully detailed claim under Clause 20.1 / Clause 20.2.4.

The EOT claim submission should include:

Executive Summary: A high-level overview of the event, the EOT days requested, and additional costs claimed.
Factual Narrative: A chronological, cause-and-effect narrative of what happened.
Contractual Basis: Citing the specific FIDIC clauses that entitle the contractor to relief.
Delay Analysis: The technical program analysis proving critical path impact.
Substantiating Records: Appendix of daily diaries, weather data, photographs, and instructions.

💡 How LegisDex simplifies this: Need to draft the factual narrative or formal claim letters? You can use LegisDex to Generate Professional Drafts directly from your workspace. Ask the assistant: "Draft a formal claim submission cover letter under Clause 20.1 for the delay caused by Clause 4.12 unforeseeable ground conditions," and get a precise, contract-styled draft in seconds.

6. Track Determinations and Settle Disputes

After submission, the Engineer must proceed under Clause 3.5 (1999 Edition) / Clause 3.7 (2017 Edition) to consult and determine the claim. The Engineer has 42 days to respond with approval, disapproval, or requests for details. Keep a close eye on the calendar, as the Engineer's failure to determine a claim within the time limits can trigger a dispute under Clause 20.4 / Clause 21 (Dispute Avoidance/Adjudication Board).

💡 How LegisDex simplifies this: Use the LegisDex Risk Tracker to assign responsibilities to commercial managers, monitor response timelines, and ensure that contested determinations are flagged early for legal review before they escalate into arbitration.

FIDIC Red Book EOT Checklist Summary Table

Below is a quick reference table for managing extension of time claims under the FIDIC Red Book:

Identify Delay (Clause 8.4/8.5): Check for entitlement (Variations, weather, Employer prevention).
Notice of Claim (Clause 20.1/20.2): Submit to Engineer within 28 days of awareness (Strict time-bar!).
Contemporary Records (Clause 20.1/20.2): Keep daily logs, photos, weather records, supply issues.
Delay Analysis (Clause 8.3): Establish critical path impact using TIA or As-Planned vs As-Built.
Detailed Submission (Clause 20.1/20.2): Submit full particulars and narrative within 42 days of awareness.
Engineer's Determination (Clause 3.5/3.7): Engineer must agree or determine within 42 days of detailed claim.

Take Control of Your Contractual Notice Procedures

In construction contract management, discipline is more profitable than arguments. Implementing a clear FIDIC EOT claim checklist, combined with modern contract administration tools, ensures your site teams are protected from late notices and missing records.

With LegisDex, quantity surveyors, commercial directors, and project managers have a unified contract workspace that does the heavy lifting of clause tracking, compliance checks, and drafting claims.

👉 Start your free trial of LegisDex today and never lose an extension of time claim to a 28-day time bar again.

FIDIC Red Book EOT Claim Checklist for Contractors