What Is Extension of Time in Construction? EOT Claims Explained

<div class="ge-article-wrapper"><nav class="ge-toc" aria-label="Table of contents"><p class="ge-toc-label">In this article</p><ul class="ge-toc-list"><li><a href="#the-core-mechanism">The Core Mechanism</a></li><li><a href="#eot-timeline-how-the-process-works">EOT Timeline: How the Process Works</a></li><li><a href="#how-sv-t-data-supports-eot-claims">How SV(t) Data Supports EOT Claims</a></li><li><a href="#worked-example-20m-project-6-week-delay">Worked Example: £20M Project, 6-Week Delay</a></li><li><a href="#nec4-eot-doesnt-exist-as-a-concept">NEC4: EOT Doesn't Exist as a Concept</a></li><li><a href="#the-connection-between-spi-trends-and-eot-entitlement">The Connection Between SPI Trends and EOT Entitlement</a></li><li><a href="#common-mistakes">Common Mistakes</a></li><li><a href="#frequently-asked-questions">Frequently Asked Questions</a></li></ul></nav><article class="ge-article-body"><p>An extension of time (EOT) is a contractual adjustment to the completion date when qualifying delay events prevent the contractor from finishing on time. It doesn't give you more money. It doesn't excuse poor performance. What it does is move the contractual completion date forward, which protects you from liquidated damages for the period of the qualifying delay. In practical terms, an EOT is the difference between a legitimate programme overrun and a contractor paying penalties for something that wasn't their fault.</p><p>This definition is part of the <a href="/en/earned-value/definitions">earned value definitions glossary</a> because <a href="/en/earned-value/cost-schedule-variance">schedule variance</a> data provides powerful evidence for EOT claims. For the broader EVM framework, see the <a href="/en/earned-value">earned value management guide</a>.</p><h2 id="the-core-mechanism">The Core Mechanism</h2><p>Under most standard form contracts (JCT, NEC, FIDIC), the contractor can claim an extension of time when a "relevant event" or "compensation event" delays the completion date. The process follows a predictable pattern:</p><ol><li>A qualifying delay event occurs</li><li>The contractor notifies the client within the contractual time limit</li><li>The contractor demonstrates that the event actually delayed the critical path</li><li>The client (or contract administrator) assesses the entitlement</li><li>The completion date is adjusted</li></ol><p>Sounds straightforward. It isn't. Step 3 is where most EOT claims live or die, because demonstrating causation between an event and a delay to the critical path requires programme analysis and contemporaneous records.</p><h2 id="eot-timeline-how-the-process-works">EOT Timeline: How the Process Works</h2><pre class="ge-ascii-diagram ge-anim"> EXTENSION OF TIME PROCESS =========================== Original Programme: |========================================| Start Completion 1 Mar 2025 30 Sep 2025 Delay Event (unforeseen ground conditions): |XXXXX| 15 May 15 Jun (4 weeks lost on critical path) Client-caused design change: |XXX| 1 Jul 15 Jul (2 weeks on critical path) EOT Claim: |========================================|======|====| Start Original +4wk +2wk 1 Mar 2025 30 Sep 28 Oct 11 Nov 2025 2025 2025 Adjusted Completion Date: 11 November 2025 ^^^^^^^^^^^^^^ 6 weeks EOT (No LDs for this period) Without EOT: LDs at £15,000/week x 6 weeks = £90,000 EXPOSURE </pre><p>That £90,000 is real money. And on larger projects, LDs can run at £50,000 to £100,000 per week. A properly evidenced EOT claim isn't just good contract administration. It's financial survival.</p><h2 id="how-sv-t-data-supports-eot-claims">How SV(t) Data Supports EOT Claims</h2><p>Here's where earned value connects to extensions of time, and it's a connection that most QS teams miss entirely.</p><p><a href="/en/earned-value/definitions/schedule-performance-index">Schedule Performance Index</a> (SPI) and Schedule Variance tell you whether the project is ahead of or behind programme. But the time-based variant, SV(t), measured in time units rather than cost, provides direct evidence of delay magnitude.</p><p>If SPI drops from 1.02 to 0.78 in the same month that unforeseen ground conditions are encountered, you've got contemporaneous earned value data showing exactly when the programme was impacted and by how much. That's evidence a delay analyst can use.</p><p>On one highways project I worked on, the contractor's EOT claim relied entirely on the programme analysis. The client's delay expert challenged it. But the earned value data showed SPI dropping from 0.98 to 0.71 during the exact period of the alleged delay, recovering to 0.94 once the issue was resolved. The SPI trend independently corroborated the programme analysis. The claim was accepted.</p><p>I'm not saying earned value data replaces proper delay analysis. It doesn't. But it provides independent, contemporaneous evidence that's very difficult to dispute.</p><h2 id="worked-example-20m-project-6-week-delay">Worked Example: £20M Project, 6-Week Delay</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> A £20M NEC4 Option C road improvement scheme. The programme shows a planned completion date of 14 November 2025. At week 16, the contractor encounters unforeseen ground conditions (contaminated fill material) on a section of earthworks that sits on the critical path.</p><p><strong>The delay:</strong></p><ul><li>Contamination discovered: 7 July 2025</li><li>Remediation design approved: 21 July 2025 (2 weeks waiting for client instruction)</li><li>Remediation completed: 18 August 2025 (4 weeks of additional work)</li><li>Total delay to critical path: 6 weeks</li></ul><p><strong>The earned value evidence:</strong></p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Month</th><th>PV</th><th>EV</th><th>SPI</th><th>SPI Trend</th></tr></thead><tbody><tr><td>May 2025</td><td>£3.2M</td><td>£3.15M</td><td>0.98</td><td>Stable</td></tr><tr><td>Jun 2025</td><td>£4.8M</td><td>£4.70M</td><td>0.98</td><td>Stable</td></tr><tr><td>Jul 2025</td><td>£6.4M</td><td>£5.12M</td><td>0.80</td><td>Sharp drop</td></tr><tr><td>Aug 2025</td><td>£8.0M</td><td>£6.24M</td><td>0.78</td><td>Still depressed</td></tr><tr><td>Sep 2025</td><td>£9.6M</td><td>£8.93M</td><td>0.93</td><td>Recovering</td></tr><tr><td>Oct 2025</td><td>£11.2M</td><td>£10.75M</td><td>0.96</td><td>Near recovery</td></tr></tbody></table></div><p>SPI dropped from 0.98 to 0.80 in July (the month of the delay event) and stayed depressed through August. By October, it had recovered to 0.96. The 6-week SPI depression maps directly to the 6-week delay period.</p><p><strong>Under NEC4, this isn't technically an "extension of time."</strong> NEC4 doesn't use that term. It's handled through compensation events. The unforeseen ground conditions are a compensation event under clause 60.1(12). The Project Manager assesses the delay to the Accepted Programme and the Completion Date moves by 6 weeks.</p><p><strong>The financial impact:</strong></p><ul><li>LDs avoided: 6 weeks at £25,000/week = £150,000</li><li>Additional Defined Cost (remediation works): £380,000</li><li>Prolongation: 6 weeks of time-related prelims at £45,000/week = £270,000</li><li><strong>Total compensation event value: £800,000</strong></li></ul><p>Without the EOT (or rather, without the compensation event adjusting the Completion Date), the contractor would face £150,000 in delay damages AND still have to absorb the £650,000 in additional cost. That's an £800,000 swing.</p></div><h2 id="nec4-eot-doesnt-exist-as-a-concept">NEC4: EOT Doesn't Exist as a Concept</h2><p>This catches a lot of people out, especially those coming from JCT or FIDIC backgrounds.</p><p>NEC4 doesn't have a mechanism called "extension of time." The concept exists, but the contract handles it differently. Under NEC4, delays caused by compensation events automatically adjust the Completion Date as part of the compensation event assessment. There's no separate EOT application. The delay assessment is embedded in the CE quotation process.</p><p>Under clause 63.5, the delay to the Completion Date is assessed by reference to the Accepted Programme. The Project Manager (capitalised, always) looks at the impact on planned Completion and adjusts accordingly.</p><p>This is actually cleaner than JCT's approach. You don't need a separate EOT mechanism because the compensation event system handles both the time and cost impacts together. But it means you must notify compensation events properly and on time. Miss the 8-week time bar under clause 61.3, and you lose both the cost recovery and the time entitlement.</p><h2 id="the-connection-between-spi-trends-and-eot-entitlement">The Connection Between SPI Trends and EOT Entitlement</h2><p>Here's a practical point that ties the <a href="/en/earned-value">earned value</a> framework directly to delay claims.</p><p>If you're tracking <a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> monthly and you see a sudden, sustained drop that coincides with a qualifying delay event, you have powerful corroborating evidence. The SPI data shows:</p><ul><li><strong>When</strong> the programme was impacted (the month SPI drops)</li><li><strong>How severely</strong> (the magnitude of the SPI decline)</li><li><strong>How long</strong> the impact lasted (how many months SPI stays depressed)</li><li><strong>Whether recovery occurred</strong> (SPI returning to pre-event levels)</li></ul><p>This doesn't replace a proper delay analysis (time impact analysis or windows analysis). But it provides an independent data set that's very hard to challenge, because it's generated from progress and cost data captured at the time, not reconstructed after the fact.</p><h2 id="common-mistakes">Common Mistakes</h2><p><strong>Failing to notify on time.</strong> Every standard form contract has a notification deadline. Under NEC4, it's 8 weeks from the date the Contractor became aware of the event (clause 61.3). Under JCT, the contractor must give notice "forthwith." Miss the deadline and your entitlement evaporates, regardless of how genuine the delay was.</p><p><strong>Not demonstrating critical path impact.</strong> A delay that affects a non-critical activity doesn't entitle you to an EOT. You must show that the event delayed the critical path, which means you need a properly maintained programme with logic links. If your programme is a bar chart with no linked logic, proving critical path impact is nearly impossible.</p><p><strong>Waiting until the end of the project.</strong> Retrospective EOT claims are harder to prove and easier to challenge. The best practice is to assess delay entitlement contemporaneously, as events occur, using the current programme.</p><p><strong>Ignoring concurrent delay.</strong> If the contractor's own delay is running alongside the qualifying event, the EOT entitlement may be reduced or eliminated depending on the contract and jurisdiction. This is one of the most contested areas in construction law and there's no clean answer that applies universally.</p><div class="ge-product-note ge-anim"><p><strong>How Gather helps.</strong> Gather's AI reads your site diaries daily and maps progress against your cost-loaded programme, giving you accurate earned value data without manual spreadsheet updates. <a href="https://gatherinsights.com/contact">Book a demo</a> to see it working on a live NEC4 project.</p></div><h2 id="frequently-asked-questions">Frequently Asked Questions</h2><h3>What qualifies as a "relevant event" for an EOT claim?</h3><p>It depends on the contract. Under JCT, relevant events include variations, force majeure, exceptionally adverse weather, and various client-caused delays. Under NEC4, the equivalent is the list of compensation events in clause 60.1, which includes 19 categories of client-risk events. The key principle across all contracts: the delay must be caused by something that isn't the contractor's fault or risk.</p><h3>Can you get an EOT without additional money?</h3><p>Yes. An EOT adjusts the completion date but doesn't automatically include additional cost. Under JCT, loss and expense is a separate claim from EOT. Under NEC4, compensation events usually include both time and cost, but the cost element depends on whether the contractor incurred additional Defined Cost. A weather delay might give you time but not money if you didn't incur additional costs during the delay period.</p><h3>How does earned value data help with EOT claims?</h3><p><a href="/en/earned-value/cost-schedule-variance">Schedule variance</a> and <a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> trends provide independent, contemporaneous evidence of when and how severely the programme was impacted. This corroborates the formal delay analysis and is particularly useful in disputes where the programme analysis is challenged. SPI data captured at the time is harder to dispute than a delay analysis prepared months later.</p><h3>What's the difference between EOT and prolongation?</h3><p>EOT is the time adjustment itself: the completion date moves. Prolongation is the cost consequence: the additional time-related costs (prelims, site management, plant hire) incurred during the extended period. You can have EOT without prolongation costs (if no additional costs were incurred) but you can't have prolongation without EOT (because without the time entitlement, the additional costs aren't recoverable).</p></article></div>