How to Prepare a Strong Extension of Time Claim

An Extension of Time claim is not simply a request for more days. It is a structured demonstration that a compensable or excusable event affected the contractual completion obligation, that the event caused delay to completion or to a relevant sectional milestone, and that the claimant preserved its entitlement through notice, particulars, records and contractual procedure. Many project teams treat EOT claims as a planning exercise. In reality, a strong EOT claim is a contract, records, planning, causation and narrative exercise that must be developed together.

The core question is not whether the project was late. The core question is why the project was late, when the delaying event occurred, whether that event sat on the critical path, whether the contract allows time relief for that event, whether the claimant complied with notice and substantiation obligations, and whether the claimed period can be demonstrated by reliable evidence.

Weak EOT claims usually fail for predictable reasons. The event is described in general terms, but the mechanism of delay is not explained. The programme analysis shows movement in dates, but not contractual causation. The claim refers to correspondence, but not to a disciplined record trail. The contractor explains that progress was disrupted, but cannot separate employer risk events from contractor delay, procurement slippage, productivity issues, design coordination problems or self-inflicted resequencing.

Another common failure is the late reconstruction of events. A claim prepared months after the event may be technically possible, but it is rarely as persuasive as a claim built from contemporaneous records. Decision-makers generally prefer evidence generated at the time, by people managing the project, before the dispute crystallised. Daily reports, progress updates, inspection records, approved drawings, design review logs, access records, procurement trackers, manpower returns, correspondence, notices, meeting minutes, lookahead programmes and photographs all become part of the claim architecture.

The first step is always the contract. The team must identify the exact clauses that create entitlement to time relief, the notice conditions, the time limits, the form of notice, the required particulars, the update requirements and the decision-making procedure. Under international forms such as FIDIC, particular attention must be paid to the distinction between a claim notice, supporting particulars, fully detailed claim submissions, interim updates and subsequent determinations or agreements. Under bespoke EPC or construction contracts, the wording may be stricter, softer, ambiguous or heavily amended.

The claim must not assume that every delay event creates entitlement. Late information, variation instructions, exceptional weather, force majeure events, unforeseeable physical conditions, authority delays, employer access failures or suspension events may each be treated differently. Some events may grant time only. Some may grant time and cost. Some may grant relief only if a notice is served within a strict period. Some may require demonstration that the event delayed completion, not merely that it caused inconvenience.

A strong EOT claim explains causation in a disciplined chain:

• What happened?
• Which contractual obligation or risk allocation is engaged?
• When did the event start?
• When did it cease to affect the works?
• Which activities were affected?
• Were those activities critical or near-critical?
• How did the event affect planned logic, sequence, productivity, access, procurement, design, testing or commissioning?
• What mitigation was possible?
• What mitigation was actually implemented?
• What period of delay is claimed?

This chain must be written in plain technical language. It is not enough to say that a variation caused delay. The claim must explain whether the variation increased quantities, introduced new work, changed access constraints, disrupted trade sequence, required redesign, delayed procurement, affected commissioning, or consumed float. The stronger the event-to-impact explanation, the easier it becomes for the reviewer to understand the claim.

Programme evidence should support the factual narrative, not replace it. A delay analysis method must be appropriate to the contract, project records, available programme data and stage of the dispute. A prospective time-impact analysis may be suitable when assessing a delay event as it arises. A retrospective as-planned versus as-built analysis may help explain actual progress where reliable updates are limited. A windows analysis may be more persuasive where periodic updates exist and the critical path changed over time. Impacted as-planned analysis can be useful in limited circumstances but is vulnerable if it does not account for actual progress, mitigation, resequencing and concurrent delay.

The method should be explained in the claim. The baseline programme should be identified. Updates should be listed. Logic changes should be disclosed. Calendars, constraints, data dates, progress entries and critical path movement should be transparent. If the schedule is weak, the claim should acknowledge limitations and support the analysis with non-programme records. A polished chart cannot compensate for unreliable underlying data.

Concurrent delay arguments are often decisive. A claimant should not wait for the respondent to identify contractor delays. The claim team should test whether other delays were operating during the same period, whether they affected the same critical path, whether they were independent or related, and how the governing law or contract treats concurrency. Float should also be addressed carefully. If the event consumed available float but did not delay completion, the claimant may face difficulty depending on the contract and applicable principles. If float was shared, project-owned, contractor-owned or controlled by programme logic, that issue must be made clear.

The record base should be organised around entitlement, causation and quantum of time. Essential records include the contract, baseline programme, approved updates, progress reports, daily reports, manpower and plant records, correspondence, RFIs, drawing registers, submittal logs, variation instructions, site access records, photographs, meeting minutes, procurement records, inspection and test records, authority correspondence and commissioning records.

The best claims do not simply attach records. They interpret them. A record matrix should identify each document, date, author, relevance, event supported and claim paragraph. This prevents the claim from becoming a document dump.

Before submitting an EOT claim, ask:

• Has the claim identified the exact contractual basis for time relief?
• Were notices issued in time and in the correct form?
• Is the delay event described with dates, facts and affected activities?
• Does the claim distinguish entitlement from causation?
• Does the programme analysis reflect actual progress and project logic?
• Are concurrent delays addressed honestly?
• Are mitigation measures explained?
• Is the claimed period clearly calculated?
• Are records indexed and connected to the narrative?
• Would a reviewer unfamiliar with the project understand the claim?