PR MEPS Map

MEP Contractor ISO 9001:2015


And ISO 14001:2015

PR MEP SERVICES

← Back to Academy

PR MEP Academy • Training Day 18

Delay Forensics & EOT Claims

Mastering Time Impact Analysis (TIA), modeling delay Fragnets, isolating concurrent risk parameters, and structuring legally defensible contractual claims.

1. Theoretical Lecture: Delay Classifications & Forensic Frameworks

The Contractual Taxonomy of Project Delays

Under international standard contracts (e.g., FIDIC), disruptions are evaluated and bucketed into three legal classifications that dictate commercial entitlement:

  • Excusable & Compensable: Delays caused directly by the Owner or Consultant (e.g., late drawing release, delayed site access handovers, late engineering submittal approvals). The Contractor is legally entitled to both a calendar Extension of Time (EOT) and financial compensation for prolonged site overhead costs.
  • Excusable & Non-Compensable: Delays driven by neutral, unpredictable forces (e.g., extreme acts of God, unexpected natural monsoons, sudden nationwide trade strikes). The Contractor gets extra time to clear Liquidated Damages (LDs) but receives no financial recovery.
  • Non-Excusable: Delays caused entirely by the Contractor or their specialized subcontractors (e.g., slow mobilization, technical re-work due to poor quality, tool labor shortages). The Contractor gets no extra time and faces immediate Liquidated Damages.

The Time Impact Analysis (TIA) Workflow

This is the industry-standard forensic method used to prove delay impacts dynamically. The process involves inserting a modeled chain of delay activities—called a Fragnet (Delay Fragment Network)—into the last approved schedule update database immediately *prior* to the delay event. Running the calculation engine (F9) then models the precise shift caused on the primary critical path.

2. Core Concepts: Fragnet Engineering & Strict Notice Constraints

Enforcing absolute administrative discipline to preserve legal claim validity:

  • The 28-Day Contractual Timeframe: Under standard construction clauses (e.g., FIDIC Clause 20.1), a contractor cannot claim an EOT months after an event has passed. They must issue a formal **written Notice of Delay within 28 days** of the event first occurring. Failure to hit this administrative deadline results in an automatic forfeiture of all legal time and cost entitlement.
  • Fragnet Structural Integrity: A delay fragment must be logically bound by real-world parameters. It must feature a hard predecessor anchor (e.g., date of submittal submission) and a hard successor anchor driving a specific physical site activity (e.g., the exact installation task blocked by that submittal).

3. Practical Activity: Building a Fragnet & Running a Forensic TIA

Field Task Scenario: Model a Fragnet for a prolonged consultant engineering review cycle, link it logically to a chilled water pipe insulation package, and calculate the exact net extension entitlement.

The trainee forensic submittal entry must structure calculation variables exactly inside the code box below:

[Trainee Name: XYZ] — [Day 18: Time Impact Analysis & Forensic Delay Report] 1. Delay Event Metadata & Fragnet Specification: - Event Title: Late Approval of Chilled Water Pipe Insulation Submittal - Delay Owner: Consultant / Client - Impacted Activity: [ACT-MECH-040] "Apply Thermal Pipe Insulation" (Original ES = 15-Nov-2026) - Fragnet Component Model: * Activity ID: FRAG-ELV-01 | Description: "Consultant Extended Material Review Window" * Planned Submittal Duration allowed by contract = 14 Days * Actual Review Time consumed by Consultant = 39 Days * Fragnet Net Delay Duration (39 - 14) = 25 Calendar Days Added to Network Loop 2. Network Logic Integration Trace: [Submittal Filed: 01-Oct] ──> [FRAG-ELV-01: 25-Day Net Delay] ──> FS ──> [ACT-MECH-040: Insulation Work] 3. Forensic TIA Schedule Engine Output Results: ┌───────────────────────────────────┬────────────────────────┬────────────────────────┐ │ SCHEDULE ENGINE CHECK RUN │ UNIMPACTED SCHEDULE │ IMPACTED SCHEDULE (TIA)│ ├───────────────────────────────────┼────────────────────────┼────────────────────────┤ │ Target Activity Early Start │ 15-Nov-2026 │ 10-Dec-2026 │ │ Project Completion Milestone Date │ 24-Dec-2026 │ 08-Jan-2027 │ │ Total Path Float │ 0 Days (Critical) │ -15 Days (Negative) │ └───────────────────────────────────┴────────────────────────┴────────────────────────┘ *Forensic Impact Conclusion:* The 25-day delay in submittal approval consumed the 10 days of available path float and pushed the final project completion date out by exactly 15 calendar days. 4. Legally Enforced EOT Claim Recommendation: - Based on this formal TIA model, the contractor has a contractually defensible claim for an Extension of Time (EOT) of exactly 15 calendar days. The delay sits directly on the primary critical path.

4. Assessment & Knowledge Wrap-up

Question 1: The client delays the physical site handover of an electrical switchgear room layout by 30 days. However, during that exact same 30-day window, your site installation crew has zero electricians on-site due to an internal subcontract labor dispute. How does this concurrency affect your EOT claim?

Click to view Model Answer

Model Answer: This is a classic **Concurrent Delay** scenario where separate delays caused by both the owner and the contractor occur on parallel critical paths within the same time window. Under standard international tracking protocols (e.g., the SCL Delay and Disruption Protocol), the contractor is legally entitled to an **Extension of Time (EOT)** to protect themselves from facing Liquidated Damages, because the owner's failure to hand over the room would have blocked progress regardless. However, the contractor is **not entitled to monetary compensation** or prolongation costs, because their own labor shortage would have frozen progress anyway during that exact same window.

Question 2: Why will a forensic Time Impact Analysis (TIA) show zero entitlement to an EOT if the activity impacted by an owner delay displays 45 days of Total Float inside the approved baseline schedule?

Click to view Model Answer

Model Answer: A TIA measures entitlement by evaluating if an owner delay pushes out the final contract completion date. If an activity carries 45 days of Total Float, it sits on a non-critical sequence with a large safety buffer. If an owner delay impacts that task for 20 days, the activity simply consumes 20 days of its available float, leaving it with 25 days of remaining buffer. Because the delay did not exceed the float boundary, it never hits the critical path and does not cause a shift in the final project end date, meaning no contractual EOT is granted.

Professional & Specialized MEP Contractor in Gurgaon, Delhi NCR

Contact us