How to Prove Delays Effectively in an EOT Claim?

In construction, delays are almost inevitable. But when they occur, proving their cause and impact is what decides whether your Extension of Time (EOT) claim succeeds or fails. A well-prepared delay proof not only protects your contractual rights but also strengthens your credibility as a contractor.

Below is a clear breakdown of how to prove delays effectively in an EOT claim.

1. Understand What Needs to Be Proven

To justify an EOT claim, you must prove three things:

• The cause of the delay (what happened and why)
• The effect of the delay (how it impacted the project schedule)
• The entitlement (whether the delay qualifies for time extension under the contract)

Without showing the direct link between these three, your claim is likely to face rejection.

2. Identify the Type of Delay

Before preparing the claim, identify the type of delay event:

• Excusable delay: Events beyond your control such as design changes, weather issues, or late approvals.
• Non-excusable delay: Caused by contractor inefficiency or poor planning.
• Compensable delay: When the client or consultant is responsible, allowing both time and cost entitlement.

Labeling delays correctly sets the foundation for a valid claim.

3. Maintain Strong Project Records

Good record-keeping is your best defense. Every EOT claim depends on factual evidence. Keep:

• Daily site reports
• Progress photos and videos
• Correspondence and meeting minutes
• Updated project schedules

These records should clearly show the sequence of events and the impact on progress. Without proper documentation, even a valid claim can be denied.

4. Use Recognised Delay Analysis Methods

An analytical approach makes your claim credible. Some proven methods include:

• As-Planned vs As-Built: Compares the planned schedule to the actual progress.
• Impacted As-Planned: Inserts delay events into the baseline to measure their effect.
• Time Impact Analysis (TIA): A dynamic method used for live projects to demonstrate the effect of each delay as it occurs.

Choose the method that aligns with your contract requirements and available data.

5. Link the Delay to the Critical Path

Not every delay justifies an EOT. You must prove that the event affected the critical path of the project schedule. If the delay occurred on a non-critical activity, it won’t impact the overall completion date.

Updating your schedule regularly helps identify whether the delay truly pushed the project timeline.

6. Provide Timely Notice

Most contracts (like FIDIC or JCT) require you to submit a notice of delay within a specific time. Late submission often leads to automatic rejection, even if your delay is genuine.

A clear, timely notice protects your rights and demonstrates good contract management.

7. Present the Claim Professionally

Organise your claim in a logical format:

• Introduction and background
• Description of delay event
• Supporting records and correspondence
• Delay analysis results
• Entitlement and conclusion

Keep the language factual, avoid emotional or defensive tones, and ensure all data is traceable.

Proving delays in an EOT claim is about clarity, evidence, and timing. A structured record system, accurate analysis, and professional presentation can turn a potential dispute into an approved claim.

When managed properly, EOT claims are not just about getting more time; they show that your project control and documentation are solid and dependable.