Overcoming Project Delays: Extension of Time (EOT) Best Practices

Construction delays are almost inevitable in large-scale infrastructure projects. Whether caused by unprecedented weather, scope changes, delayed drawings from the consultant, or unforeseen ground conditions, how a contractor handles these delays determines the project's financial success.

The Extension of Time (EOT) claim is a critical contractual mechanism designed to protect contractors from unfair Liquidated Damages (LDs) when they are delayed by events beyond their control. However, proving entitlement to an EOT is one of the most complex tasks in construction management.

Core Principles of a Successful EOT Claim

To prepare a robust EOT claim, project planners and contract administrators must establish a clear, undeniable cause-and-effect relationship between the delay event and the project's critical path.

• Timely Notices (Condition Precedent): Always submit delay notices within the timeframe stipulated in the contract (usually 14 to 28 days under FIDIC). Failing to submit a notice on time can completely invalidate your right to claim, regardless of how unfair the delay was.
• Critical Path Impact: The delay must actually affect the longest path in the schedule. If an event delays a non-critical activity by 5 days, but that activity had 20 days of total float, the project completion date is unaffected, and no EOT is warranted.
• Concurrent Delays: Carefully analyze overlapping delays caused by both the employer and the contractor. How concurrent delays are apportioned depends heavily on the specific contract wording and local jurisdiction.

Recommended Delay Analysis Methodologies

You cannot simply write a letter asking for more time; you must mathematically prove the delay using the approved baseline schedule. Choosing the right methodology is crucial for proving your claim:

1. Time Impact Analysis (TIA): The preferred method for forward-looking analysis during the project. It involves taking the most recent updated schedule, inserting a "fragnet" (fragmentary network) representing the delay event, and recalculating the schedule to show the immediate impact.
2. As-Planned vs. As-Built: A retrospective, global method comparing the original baseline schedule to the actual progress. While easier to perform, it is often criticized for failing to isolate specific causes of delay.
3. Collapsed As-Built (But-For): A highly analytical retrospective method. It involves taking the final, as-built schedule and systematically extracting employer-caused delays to prove what date the contractor *would have* finished on "but for" those delays.

The Role of Meticulous Record Keeping

An EOT claim is only as strong as the contemporaneous evidence supporting it. The best delay analysis in the world will fail if you cannot prove the event actually occurred.

• Daily Site Reports: Must be detailed, noting weather conditions, manpower, equipment on site, and idle time.
• Visual Evidence: Dated photographs and drone footage showing lack of access or unforeseen conditions.
• Correspondence Logs: Meticulously maintained RFI (Request for Information) logs proving the consultant delayed issuing critical construction drawings.

Master the art of claims drafting, delay analysis methodologies, and contract administration in our comprehensive Project Delay Analysis & EOT Claims program.