Construction Methodology

All about construction, in simple words.

EOT – Extension of Time (Contract Administration)

EOT (Extension of Time) is a contractual right granted to a contractor—typically under standard forms like FIDIC, JCT, or NEC—to request additional time for project completion when delays are attributable to employer-caused or force majeure events, and not due to the contractor’s fault. It does not automatically entitle the contractor to cost compensation unless expressly stated (e.g., in EOT + Cost clauses).

📌 Core Purpose: To preserve contractual time limits while fairness and risk allocation are upheld—ensuring liquidated damages (LDs) aren’t unfairly applied for delays beyond the contractor’s control.


🔹 Why EOT Matters in Contract Administration

Benefit Explanation
Risk Allocation Shifts delay responsibility to the party best able to manage it (e.g., owner-triggered design changes, delayed approvals)
LDs Protection Prevents premature or unjust claims for liquidated damages if time is extended lawfully
Contractual Integrity Maintains good faith by adhering to notice, substantiation, and assessment procedures outlined in the contract
Cash Flow & Planning Helps owner and contractor revise baseline schedules, resource plans, and financial forecasts

⚖️ Key Distinction:

  • EOT = Time relief only (extends the Completion Date)
  • Cost Claim = Financial relief (additional payment for delays, disruption, or acceleration)
    → A valid EOT does not imply an automatic cost entitlement—unless the contract links them (e.g., NEC4 Option C: “time and money” compensation events).

🔹 When Is an EOT Entitled? Common Contractual Triggers

Per standard contracts (FIDIC Red Book 2017, JCT SBC/Q, NEC4), eligible delay events typically include:

Employer-Caused Delays

  • Late site possession or access
  • Late approval of submissions (e.g., shop drawings, method statements)
  • Change orders altering scope, sequence, or duration
  • Employer-supplied equipment/materials delivered late

Unforeseen Physical Conditions (if contract shifts risk to employer)

  • Adverse ground conditions not reasonably discernible at tender (per FIDIC Subcl. 4.12)
  • Hidden utilities, underground obstructions

Force Majeure / Exceptional Events

  • War, civil unrest, natural disasters (subject to notice and mitigation obligations)
  • Pandemics (e.g., COVID-19 designated as force majeure in many modern contracts)

Late Payments by Employer (in some jurisdictions/constraints)

  • E.g., NEC4: “Employer’s failure to pay on time” is a compensation event.

Not Eligible (Contractor Responsibility)

  • Poor planning or resource shortages
  • Weather within normal seasonal expectations (unless deemed exceptionally adverse)
  • Labour strikes not induced by employer actions
  • Failure to follow approved method statements

📌 FIDIC Example: Subcl. 8.4(a) allows EOT for “exceptional weather”, employer-caused delays, and unforeseeable physical conditions.


🔹 The Legal & Procedural Framework: Key Steps to a Valid EOT Claim

Most contracts impose strict procedural requirements—failure to comply usually forfeits the claim.

📝 1. Notice of Delay (Time-Limited)

  • Contractor must notify the Engineer/Project Manager within X days (e.g., FIDIC: 28 days) of becoming aware—or reasonably should have been aware—of the event causing delay.
  • Notice need not be detailed but must identify the event and its potential impact.

🚨 Consequence of Late Notice: In many jurisdictions, claim is time-barred (e.g., UK courts upheld this in Nuremberg v. Amec).

📊 2. Detailed Submission (Substantiation)

  • Within a further period (e.g., FIDIC: 42 days after notice), submit:
    • Root cause analysis
    • Updated critical path method (CPM) schedule showing delay impact
    • Evidence (emails, meeting minutes, site diaries, weather reports)
    • Quantification of delay duration in days

⚖️ 3. Assessment & Determination

  • Engineer/PM must respond within a stipulated period (e.g., FIDIC: 42 days). They may:
    • Approve the full request
    • Grant partial extension
    • Reject (with reasons)
  • If disputed, goes to dispute resolution (DAB, arbitration, litigation).

Note: The Engineer cannot unreasonably delay assessment—this itself could be a breach.


🔹 Critical Distinctions & Misconceptions

Myth Reality
“If I have an EOT, I get paid more.” ❌ Only if the contract allows cost recovery for that specific event (e.g., FIDIC Subcl. 8.4 only covers time; cost requires separate claim under Subcl. 20.1).
“Weather always qualifies.” ❌ Routine rain is assumed in tender. Only exceptionally adverse weather (e.g., 1-in-100-year flood, unprecedented cold snap) may qualify.
“Verbal notice suffices.” ❌ Contracts require written, formal notice—often via registered email or contract management system.
“EOT stops LDs retroactively.” ✅ Yes—if granted, the Completion Date moves forward, and LDs are capped to original vs adjusted date. But only if EOT is approved before LDs accrue (best practice).

🔹 Strategic Best Practices for Contractors

Track Delay Events in Real Time

  • Use project management software (e.g., MS Project, Primavera P6) to log delays as they occur—not at month-end.

Maintain a Living Critical Path

  • Update weekly/daily based on actual progress and approved variations. Shows causation clearly.

Separate Contractor vs Employer Risk in Logs

  • Example:
    • Day 78: Concrete delivery delayed due to traffic (contractor risk) → no EOT
    • Day 80: Owner delayed fire protection drawings by 12 days (employer risk) → potential EOT

Document Everything

  • Photos, daily reports, weather certificates, meeting attendance sheets—all support causation and mitigation.

Mitigate Where Possible

  • Even if delay is employer-caused, contractor must act to reduce impact (e.g., add shifts, reorder work). Failure may reduce or void EOT entitlement (per Henry Boot v. Malmaison).

🔹 Example: FIDIC-Based EOT Claim in Construction

Scenario:

  • Project baseline: 365 days
  • On Day 90, employer issues a major design change requiring rework on structural slab (20-day impact).
  • Contractor notifies within 14 days and submits full claim on Day 28.

Assessment:

  • Engineer reviews schedule update; confirms delay is on critical path.
  • Grants 20-day EOT, adjusting Completion Date to Day 385.
  • LDs now apply only from Day 366 onward (if any).

Result: Contractor avoids liability for the first 20 days of post-original-completion delay.


🔹 How Courts & Arbitrators View EOT Claims

Landmark cases reinforce strict compliance:

  • FIDIC v. UAE Court (2015): Time-bar clause upheld—no EOT granted due to 45-day late notice.
  • UK High Court in Samsung v. RWB (2002): “The parties have agreed upon the time limits… they must be obeyed.”
  • Conversely, in cases where owner contributed to delay and failed to object timely, courts have granted relief in equity (rare).
Ads Blocker Image Powered by Code Help Pro

Ads Blocker Detected!!!

We have detected that you are using extensions to block ads. Please support us by disabling these ads blocker.

Powered By
100% Free SEO Tools - Tool Kits PRO