
Practical Steps for Preparing a Successful Extension of Time (EOT) Claim Under FIDIC
Practical Steps for Preparing a Successful Extension of Time (EOT) Claim Under FIDIC
An Extension of Time (EOT) claim is a contractual mechanism designed to relieve the contractor of liability for Liquidated Damages and to extend the project completion period due to events beyond their control. To ensure the claim's success under FIDIC contracts, the contractor must submit a formal notice to the Engineer within 28 days of becoming aware of the delaying event. Subsequently, a detailed claim must be submitted, supported by a delay analysis demonstrating the event's impact on the project's critical path.
The Strategic Importance of EOT Claims
In the management of major engineering projects, an EOT is not merely about gaining extra time; it is a crucial tool for managing commercial risk. Securing an approved EOT protects the company from devastating liquidated damages and paves the legal way to claim financial compensation for "Prolongation Costs." A lack of clear methodology in preparing these claims often leads to their rejection, placing the contractor in a precarious financial and legal position.
Step-by-Step Process: How to Build an Irrefutable EOT Claim
To prepare a robust and coherent EOT claim that stands up to scrutiny by the Employer and the Engineer (or even arbitration panels), the following strict contractual steps must be followed:
Step One: Submitting the Notice of Claim
As soon as an impediment or delay occurs (or is even anticipated), FIDIC requires the contractor to submit a formal notice to the Engineer. Timing is critical here; The notice must be submitted within a maximum of 28 days from the date the Contractor became aware of the event. Failure to take this step may result in the total forfeiture of the Contractor's right to claim.
Step Two: Maintaining Contemporary Records
Successful claims rely not on memory or speculation, but on daily records. Once the notice has been submitted, the Contractor must begin meticulously documenting all aspects of the disruptive event, including idled resources, correspondence, and site photographs. The Engineer has the right to inspect these records at any time.
Step Three: Conducting a Delay Analysis
This constitutes the technical core of the claim. The Contractor must use the approved schedule (Baseline Programme) to demonstrate that the disruptive event has actually impacted the project's "Critical Path." Delays affecting activities that possess "float"—and which do not impact the final completion date—do not warrant an extension of time.
Step Four: Submitting the Fully Detailed Claim
The complete claim dossier must be submitted within 42 days of the Contractor becoming aware of the event (or within any other timeframe agreed upon by the Engineer). The dossier must include the legal narrative, supporting records, the technical delay analysis, and the precise duration of the requested extension. Expert Insight from PMA (Eng. Mohamed Ali Salam):
"In our assessment of hundreds of claims across the Middle East, we find that the primary reason for the rejection of Extension of Time (EOT) claims is not a weak technical position on the part of the contractor, but rather a 'procedural failure.' Ignoring the statutory deadline for submitting the 28-day notice is a fatal strategic error. We always advise companies to view notices as a tool for business alignment rather than as an adversarial measure against the Employer."
Checklist: Essential Documents for a Robust EOT Claim File
To ensure your claim file meets institutional and contractual standards, make sure to include the following documents:
Copy of the initial claim notice: To demonstrate compliance with the 28-day deadline.
Statement of Facts: A clear chronology of the events that led to the delay.
Contractual Basis: Identification of the specific FIDIC clause entitling the contractor to make the claim (e.g., Clause 8.4 of the 1999 FIDIC Red Book).
Baseline Schedule: The original schedule against which measurements are made.
Updated Schedule: Showing the project status at the time the delaying event occurred.
Delay Analysis Report: Detailing the analysis methodology used (e.g., Time Impact Analysis).
Supporting Records: Weather reports, daily progress reports, meeting minutes, and official correspondence.
Frequently Asked Questions (FAQ) about Extension of Time Claims
What happens if the contractor fails to submit the notice within the 28-day period? Under the express terms of the FIDIC contracts, if the Contractor fails to submit the notice within the specified timeframe, they forfeit their right to an Extension of Time (EOT) or any financial compensation, and the Employer is absolved of any liability regarding the delay.
**Does every Extension of Time (EOT) entitle the Contractor to financial compensation?**
No. An EOT protects the Contractor from delay penalties and provides the time needed to complete the work. Financial compensation (prolongation costs), however, depends on the nature of the event: if the delay is caused by the Employer (e.g., late issuance of drawings), the Contractor is entitled to claim payment. Conversely, if the delay results from *Force Majeure*—such as exceptional weather conditions—the Contractor typically receives the time extension but not financial compensation.
**Can the Engineer reject a detailed claim if the records are insufficient?**
Yes; the Engineer has the authority to reject the claim or evaluate it based solely on the contemporaneous records available to them. Therefore, meticulous documentation serves as the Contractor's first line of defense.
**Does your company require professional support in preparing or reviewing project claims?**
PMA understands the commercial risks inherent in engineering projects. We provide enterprise-grade consultancy services for claims management, delay analysis, and the protection of your contractual rights.
[Contact our claims management experts today] or invest in your engineering team's development through the [Construction Claims Management Course] at the PMA Academy.
