A Delay Does Not Automatically Give You EOT

Anyone who has worked on a delayed EPC project has seen some version of this calculation:

ROW unavailable from 01 January to 10 April = 100 days delay = 100 days EOT.

Or:

Utility not shifted for 73 days = 73 days EOT.

Or:

Drawing approval delayed by 45 days = 45 days EOT.

It looks logical. It is also where many EOT assessments start going wrong.

The first number establishes the duration of the event. The second requires you to establish the delay attributable to that event under the contract.

Those are not the same exercise.

For an EOT assessment, the real question is not simply:

How long did the hindrance exist?

It is:

What did this event delay, when was that work required to be executed, and what was its demonstrated effect on the applicable Project Milestone or Scheduled Completion Date?

That distinction changes the entire way an EOT should be prepared.

Start With the Contract, Not the Number of Days

Assume that a highway contractor could not access a particular work front for 100 days because the required ROW was unavailable.

The site records establish the dates beyond dispute.

So we know:

Hindrance period = 100 days.

What we do not yet know is:

EOT entitlement = 100 days.

Before arriving at the second number, the contract administration team has considerably more work to do.

At minimum, the assessment has to address:

Event → contractual entitlement → notice → affected activity → programme impact → causation → mitigation/concurrency → substantiation → determination.

The event register may tell you how long the problem existed.

It does not necessarily tell you how much it delayed completion.

1. Define the Delay Event Properly

“ROW not available” is not a sufficiently developed delay event for an EOT submission.

A useful event record should identify, as applicable:

• chainage/location;
• length or extent of unavailable work front;
• affected BOQ/activity/work package;
• planned date of access;
• actual date of access;
• activity planned during the affected period;
• contractual responsibility;
• notice reference;
• correspondence references;
• photographs/joint records;
• relevant programme activity; and
• date on which the effect ceased.

Consider two statements:

Statement A:

“ROW was not available for 100 days.”

Statement B:

“ROW between Ch. 24+600 and Ch. 25+150 was unavailable from 01 January to 10 April, preventing commencement of embankment and associated drainage works planned under Activities X and Y in the accepted programme.”

Statement B gives the delay analyst something to work with.

Statement A merely records a hindrance.

That distinction matters.

2. Establish the Contractual Basis for EOT

Once the event has been defined, identify the clause under which time relief is being sought.

This should happen before calculating the claimed EOT.

In highway EPC contracts, potential delay events may arise from matters such as:

• delayed ROW/site availability;
• Change of Scope;
• Authority instructions;
• delayed approvals;
• utility-related obstruction;
• Force Majeure;
• Authority-attributable prevention or impediment; or
• other events expressly addressed by the agreement.

But an event being outside the contractor's control does not, by itself, tell you the contractual consequence.

The agreement has to answer:

1. Is this a qualifying event?
2. Does it provide time relief?
3. Does it provide cost relief?
4. What notice is required?
5. What particulars must be submitted?
6. How is the resulting Time Extension to be assessed?

For the NHAI EPC form examined for this research, Clause 10.5 deals with Extension of Time and operates where completion of a Project Milestone “is or will be delayed” by specified qualifying circumstances.

The important expression is not merely the existence of the event.

It is the extent to which completion is or will be delayed.

That is where event duration and EOT duration begin to separate.

3. Check the Notice Before Building the Claim

This is basic contract administration, but it continues to damage otherwise valid claims.

A project team identifies a genuine Authority-side delay, records it for months, prepares an elaborate impact analysis and then discovers that the contractual notice requirement was not complied with.

Do not start by asking:

“Is this a 14-day notice or a 28-day notice?”

Start by opening the contract.

Notice provisions vary.

The NHAI EPC provision examined during this research uses a 15-business-day requirement for the relevant EOT notice mechanism, calculated from when the Contractor became aware or should reasonably have become aware of the event or circumstance.

Other contracts may prescribe something different.

The trigger also matters.

It may not simply be the date somebody entered the hindrance in a register.

For each delay event, the contract team should therefore capture:

• Event date
• Date of awareness
• Contractual notice period
• Notice due date
• Actual notice date
• Notice reference
• Continuing particulars required
• Final substantiation required

This is why a generic “28-day notice rule” should never be hard-coded into an EOT system.

The contract controls.

4. Now Open the Programme

This is where a hindrance becomes a delay-analysis issue.

Suppose an obstruction existed from Day 1 to Day 100.

The obvious temptation is:

Day 100 − Day 1 = 100 days EOT.

Instead, ask:

When was the affected activity actually scheduled to occur?

Assume the blocked work front was required only from Day 60.

The first 59 days of physical obstruction may have a very different programme consequence from Days 60–100.

Now assume that the activity had available float.

Again, the completion effect may differ.

Now assume that the contractor's predecessor activity was itself 30 days late.

Again, causation needs examination.

Or assume the contractor could execute an unaffected adjacent reach and resequence its resources.

Again, the effect needs to be assessed rather than presumed.

This is why a hindrance register alone cannot establish EOT quantum.

You need to connect:

Event → affected activity → programme status → milestone/completion effect.

5. Which Programme?

This question matters more than it first appears.

Projects often have several programme versions sitting in the record:

• tender programme;
• initial programme;
• baseline programme;
• accepted/approved programme;
• monthly updates;
• revised programmes;
• recovery programmes; and
• programmes prepared retrospectively during the claim.

They are not interchangeable.

A useful EOT assessment should establish which programme represents the contemporaneous execution plan at the relevant time and how actual progress had developed before the delay event occurred.

Otherwise, an apparently precise delay analysis can be built on a programme that no longer represented the project.

The analysis should therefore look at:

• planned start and finish;
• actual start and progress;
• predecessor status;
• successor relationship;
• available float where relevant;
• Project Milestone linkage;
• contemporaneous programme updates;
• progress immediately before the event; and
• progress after the event.

The question is not simply whether an activity was shown as “critical” somewhere in Primavera.

The question is whether the project records establish a credible causal link between the event and delayed contractual completion.

6. Critical Path Is Important — But Don't Turn It Into a Slogan

There is another oversimplification worth avoiding:

“No critical-path impact = no EOT.”

That may sound technically sophisticated, but as a universal statement it is too crude.

The correct analysis depends on the contract, programme, available records, milestone structure and circumstances of the event.

Professional delay analysis may involve Time Impact Analysis, windows analysis, As-Planned versus As-Built techniques or other CPM-based approaches.

The method should follow the question being investigated and the quality of the records available.

What matters for the project team is simpler:

Can you demonstrate how this event translated into delay to the relevant contractual completion obligation?

A coloured Primavera printout does not establish causation merely because an activity appears red.

The logic behind it has to survive scrutiny.

7. Test Causation, Not Just Chronology

Consider a utility obstruction at a proposed pier location.

The utility remained in place for 60 days.

Scenario A

The piling rig was mobilised.

Approved drawings were available.

Predecessor activities were complete.

The pier was scheduled for execution.

The utility physically prevented piling.

There is an apparent causal chain worth analysing.

Scenario B

The same utility remained in place for the same 60 days.

But:

• the piling rig had not been mobilised;
• the required drawing was not available;
• predecessor work was incomplete; or
• the contractor was independently delayed in reaching that location.

The utility still existed for 60 days.

But the question becomes:

What delay during those 60 days was actually caused by the utility?

This is the difference between chronology and causation.

Two events happening during the same period does not automatically mean one caused the other.

8. Don't Ignore the Unaffected Work Fronts

This is particularly relevant to linear infrastructure.

A highway package may have several fronts available simultaneously.

If 500 m of ROW is unavailable, the delay assessment should not stop at:

“500 m unavailable for 120 days.”

It should also examine:

• what activities were planned in that 500 m;
• whether those activities controlled a milestone;
• availability of adjoining reaches;
• availability of structures/service roads/drains/other fronts;
• resource deployment;
• whether resources could reasonably be resequenced;
• what work actually progressed elsewhere; and
• whether the obstruction ultimately affected completion.

This does not mean that the contractor is automatically responsible simply because another work front existed.

Nor does it mean unlimited resequencing is always reasonable.

It means that the actual effect of the obstruction has to be demonstrated.

That is a more defensible position than simply counting calendar days.

9. Contemporaneous Records Will Decide How Much You Can Actually Prove

An EOT prepared six months after the event is only as good as the records generated while the event was happening.

For a ROW event, I would expect to look for things such as:

• ROW handover/possession records;
• strip plan;
• chainage-wise availability;
• joint inspection records;
• photographs;
• notices;
• correspondence;
• monthly progress reports;
• programme updates;
• affected quantities; and
• resource deployment.

For drawing/approval delay:

• drawing submission register;
• submission date;
• contractual review period;
• comments;
• resubmission;
• approval date;
• planned execution date;
• programme activity; and
• resulting impact.

For utility shifting:

• utility location;
• identification date;
• shifting responsibility;
• correspondence with Authority/utility agency;
• joint records;
• shifting date;
• planned activity;
• resource readiness; and
• programme impact.

For a claimed idle-resource consequence:

• manpower deployment;
• equipment deployment;
• equipment logs;
• site diaries;
• progress records;
• diesel/operation records where relevant; and
• evidence showing why the resources could not reasonably be deployed elsewhere.

The objective is not to attach more documents.

The objective is to establish the causal chain.

10. Mitigation Must Be Part of the Record

Suppose a work front becomes unavailable.

What did the contractor do next?

Did it:

• shift resources?
• resequence activities?
• move to another available reach?
• raise the issue promptly?
• propose an alternative?
• revise its programme?
• increase resources once access became available?

These facts matter.

A later statement saying:

“The contractor took all possible mitigation measures”

has limited value if nothing in the contemporaneous record shows what those measures actually were.

Mitigation should therefore be documented as an event develops.

The same applies when mitigation was not practically possible.

Record why.

11. Concurrency: The Part Nobody Likes Discussing

Now assume the Authority delayed ROW handover.

At the same time, the contractor was behind in mobilisation.

This is uncomfortable for both sides.

The Authority may say:

“You were delayed anyway.”

The contractor may say:

“ROW was unavailable, so our own delay is irrelevant.”

Neither statement should simply be accepted.

The analysis needs to establish:

• timing of both delays;
• activities affected;
• whether both delays affected the same completion obligation;
• whether they were genuinely concurrent;
• their respective causal effects; and
• how the contract treats the situation.

Concurrency is not solved by deleting the contractor delay from the chronology.

A credible EOT submission should be able to explain adverse facts as well as favourable ones.

12. EOT and Prolongation Cost Are Not the Same Claim

Another common shortcut is:

Authority delay → EOT → prolongation cost.

Not necessarily.

Time entitlement and cost entitlement need separate contractual examination.

Depending on the event and agreement, an event may result in:

Time only

or

Time + Cost

or

Neither

or another contract-specific treatment.

An approved EOT therefore should not automatically be treated as proof of monetary entitlement.

For every major delay event, maintain two separate questions:

What is our contractual entitlement to time?

and

What is our contractual entitlement to money?

Do not merge them prematurely.

13. What Should Happen on Day 1 of a Delay Event?

The best EOT claim is not assembled at the end of the project.

It is built contemporaneously.

When a potentially significant delay event occurs, the project team should immediately establish an event file containing, as applicable:

01 — Event identification

What happened? Where? Which activity?

02 — Contract clause

What contractual provision potentially applies?

03 — Notice

When does the notice clock start? When is notice due?

04 — Programme linkage

Which programme activity and milestone may be affected?

05 — Evidence

What records prove the event?

06 — Resource status

Were labour, plant, material, drawings and predecessor activities ready?

07 — Mitigation

What alternatives were considered or implemented?

08 — Periodic update

How has the effect changed since the previous assessment?

09 — Closure

When did the event cease?

10 — Impact assessment

What delay to the contractual completion obligation is ultimately attributable to the event?

Do this while the event is live and the eventual EOT submission becomes substantially easier to prepare and defend.

Ignore it for six months and the claims team will spend weeks trying to reconstruct history from emails, WhatsApp messages, photographs and incomplete site records.

The 100-Day Test

The next time a delay statement says:

“ROW unavailable for 100 days. EOT claimed: 100 days.”

don't reject it.

But don't accept it either.

Ask for the bridge between the two numbers.

Show me the event.

Where was the ROW unavailable?

What activity did it prevent?

Show me the contract.

Which clause provides the relief?

Was the notice compliant?

Show me the programme.

When was the affected work actually required?

What was the contemporaneous status of predecessor and successor activities?

Show me the records.

Was the contractor ready to execute?

What happened on the unaffected fronts?

Show me the causation.

How did this event move the relevant Project Milestone or completion obligation?

Show me the overlap.

What other delays existed during the same period?

Then show me the EOT calculation.

That is an EOT assessment.

Everything before that is an event chronology.

CivilUncut EOT / Delay Event Analyser

The CivilUncut EOT / Delay Event Analyser is intended as an initial contract-administration screening tool.

It captures the basic event data required before a delay is treated as an EOT position:

• event period;
• notice status;
• contractual responsibility;
• affected activity;
• programme relevance;
• supporting evidence; and
• missing information.

It does not determine contractual entitlement and it does not replace a detailed delay analysis.

Its purpose is to expose gaps early—while they can still be corrected.

Free EOT Documentation Checklist

If you are currently dealing with ROW, utility, approval, drawing, Change of Scope or another live delay event, use the CivilUncut EOT Documentation Checklist to check whether the basic event records are being maintained.

Do it while the event is happening.

Not six months later when somebody asks the contracts team to “prepare the EOT.”

The Point

A genuine Authority-caused obstruction may exist for 100 days.

That matters.

But it answers only one question:

How long did the event exist?

An EOT assessment has to answer another:

What delay to the contractual completion obligation is attributable to that event under the contract?

Keep the two questions separate.

1. EVENT↓
2. CONTRACT↓
3. NOTICE↓
4. RECORDS↓
5. PROGRAMME↓
6. CAUSATION↓
7. MITIGATION / CONCURRENCY↓
8. SUBSTANTIATION↓
9. DETERMINATION

That chain is where an event becomes an EOT case.

Technical Note

CivilUncut provides technical education and contract-administration tools for infrastructure professionals. This article does not determine entitlement on any individual project. Contract wording, governing law, programme status and project facts must be reviewed for the specific case.

Technical References

1. National Highways Authority of India / MoRTH EPC agreement

   Provisions relevant to Extension of Time, programme, Project Milestones and notices. The applicable executed agreement and edition must be checked.

2. AACE International Recommended Practice 29R-03: Forensic Schedule Analysis

   Professional delay-analysis guidance; not a universally mandatory contractual methodology.

3. Atlanta Limited v. Union of India, Supreme Court of India, 2022

   Contextual reference only. It is not presented as establishing a universal Event → Critical Path → EOT legal test.