The modern playbook for EOT Claims.

Learn how top commercial managers move from reactive disputes to proactive, undeniable Extension of Time claims using forensic schedule analytics.

15 Min Read Comprehensive Guide

1. The Anatomy of a Winning Claim

In mega-projects, an Extension of Time (EOT) claim is rarely a simple request. It is a highly technical, forensic argument demonstrating that an excusable delay has directly impacted the project's critical path.

Traditionally, claims are built retroactively. Consultants spend thousands of hours digging through old Primavera P6 backups, searching for the exact moment the logic broke. This retroactive approach is expensive, slow, and highly susceptible to rejection by the Owner or Engineer.

The Industry Standard Shift

The most successful contractors have shifted from a "Forensic Delay Analysis" mindset to a "Predictive Delay Mitigation" mindset, capturing the data required for an EOT in real-time as the event occurs.

2. Baseline Validation

You cannot prove you were delayed if you cannot prove where you were supposed to be. A pristine, approved baseline is the bedrock of any EOT claim. Before submitting an initial baseline schedule, it must be rigorously audited.

  • Zero Open Ends: Every activity (except Start/Finish) must have at least one predecessor and one successor.
  • Restricted Constraints: Hard constraints (like "Must Finish By") artificially manipulate float and are easily attacked by claims consultants.
  • Realistic Float: Beware of excessively high float paths, which indicate missing logic links rather than actual schedule flexibility.

3. Demonstrating Critical Path Impact

A delay to a specific activity does not guarantee a delay to the project completion date. The core of your EOT argument relies on the Time Impact Analysis (TIA) method.

To successfully argue a TIA, you must take the accepted schedule update immediately prior to the delay event, insert the delay as a fragnet (fragmentary network of activities), and recalculate the schedule. The mathematical difference between the original finish date and the new finish date is your requested EOT.

4. The Complexity of Concurrent Delays

Concurrent delays occur when an Employer Risk Event and a Contractor Risk Event happen at the same time, both independently causing a delay to the critical path.

In most standard contracts (like FIDIC), a true concurrent delay grants the Contractor an Extension of Time (relief from liquidated damages) but does not grant Prolongation Costs (financial compensation for the extra time). Because of this financial nuance, Owners will fiercely search for Contractor-caused delays to run concurrently with their own.

5. Automating the Process

Manual Time Impact Analysis on a 50,000-activity schedule can take weeks. By the time the claim is drafted, the project has moved on.

This is where platforms like P6 Intelligence come in. By continuously ingesting P6 XER or XML files, the platform's AI engine automatically tracks logic changes, highlights critical path shifts, and generates automated EOT drafts the moment a client-driven delay occurs.

Master your next claim.

Download the full 40-page PDF guide, complete with sample TIA narratives and P6 layout configurations.