Extension of Time (EOT) & Delay Analysis Software: Linking Contemporaneous Site Diaries to Primavera P6 Fragnets

For an EPC Project Director, Head of Planning & Delay Forensics, or Claims Manager executing complex infrastructure, metro, refinery, or high-rise building contracts, Time for Completion is governed by severe financial asymmetry. A single day of unexcused delay beyond a sectional milestone or final completion date triggers Delay Damages / Liquidated Damages (LD) typically set at $0.05\%$ to $0.10\%$ of the Contract Price per day (capped at $5\%$ to $10\%$ of total contract value), while simultaneously freezing upward price escalation indices and exposing the contractor to millions of rupees per week in unrecovered site overhead prolongation costs.

Yet across most construction sites, the two teams responsible for defending schedule entitlement operate in complete isolation: - Site Engineers record daily events (heavy rainfall, utility shifting holds, local villager agitation, late client inspection, tower crane breakdown) in paper site diaries or unstructured WhatsApp messages, and occasionally enter a line in a physical CPWD Hindrance Register without specifying the exact WBS activity ID or chainage blocked. - Planning Engineers update the Primavera P6 or MS Project programme once a month by overwriting actual start/finish dates, often adjusting logic links or constraints without maintaining a frozen archive of monthly contemporaneous updates or inserting structured Delay Fragnets.

When a dispute reaches the Independent Engineer, Dispute Avoidance/Adjudication Board (DAAB), or arbitral tribunal, this disconnect causes four fatal failures:

1. Contractual Time-Bar Forfeiture Under FIDIC Sub-Clause 20.2.1: Under FIDIC 1999 (Sub-Clause 20.1) and 2017 (Sub-Clause 20.2.1), the Contractor must give a formal Notice of Claim describing the delay event or circumstance as soon as practicable, and no later than 28 days after the Contractor became aware (or should have become aware) of the event. If a site hindrance sits in a field diary for 45 days before reaching the contracts team, the entire EOT and prolongation claim for that event is legally time-barred.
2. Rejection of "Global Gross Hindrance Sums" Over Overlapping Calendar Windows: In traditional public-sector disputes, contractors often sum up every hindrance entry in the Hindrance Register (e.g., 45 days of rain + 60 days of late drawing + 50 days of utility obstruction = 155 days EOT claim) even though these events occurred in the same calendar months or affected non-critical sideline activities with 40 days of Total Float ($TF > 0$). Independent Engineers immediately reject gross additive hindrance totals.
3. Inability to Prove Critical-Path Causation via Time Impact Analysis (TIA): Both the SCL Protocol (Core Principle 4 & 11) and AACE 29R-03 establish that EOT entitlement must be demonstrated by inserting the Employer Risk Event as a Fragnet into the contemporaneous programme update prevailing immediately prior to the delay event, re-running the Critical Path Method (CPM) calculation, and measuring the net axial push on the Terminal Milestone.
4. Commingling Compensable Delay with Concurrent Contractor Delay: When an arbitrator sees that the contractor's own batching plant breakdown or form-work shortage ran concurrently with the client's late GFC foundation drawing release, and the contractor's claim does not cleanly separate Excusable & Compensable (EC) days from Excusable & Non-Compensable Concurrent (EN-C) days, the tribunal disallows the entire prolongation cost claim.

The strategic decision for EPC leaders is to deploy an ERP-Integrated Site Diary, Hindrance Clock, and P6 Fragnet Forensics Engine that converts every field hindrance into a time-stamped contractual notice clock and links it directly to a Primavera P6 activity and Fragnet impact calculation.

1. Time Impact Analysis (TIA) and Fragnet Insertion

Under the Society of Construction Law (SCL) Delay and Disruption Protocol (2nd Edition), when an EOT application is assessed during the currency of the project (or forensically using contemporaneous windows), the preferred method is Time Impact Analysis: 1. Identify the Contemporaneous Programme Update immediately preceding the onset of the Delay Event (establishing the pre-impact Scheduled Completion Date $T_{\text{pre}}$ and existing Total Float $TF_i$ of affected activities). 2. Model the Delay Event as a discrete Fragnet (e.g., Activity FRAG-014: Client Hold on Pier P-18 Pile Cap GFC Revision due to Underground 66kV Cable Conflict, duration $d_{\text{frag}}$ days) and link it logically (Start-to-Start or Finish-to-Start) to the constrained baseline activity (ACT-2040: Pier P-18 Pile Cap Rebar & Pour). 3. Re-compute the CPM network to determine the post-impact Scheduled Completion Date $T_{\text{post}}$. 4. The net critical-path Extension of Time entitlement ($\Delta EOT$) attributable to the event is: $$\Delta EOT = \max\left(0,\; d_{\text{frag}} - TF_{\text{pre}}\right) = T_{\text{post}} - T_{\text{pre}}$$

2. The Four-Quadrant Delay Classification Matrix

Every calendar day of critical-path delay in an EPC window analysis must be classified into one of four legal categories:

Consider a ₹400 Crore River Bridge & Approach Viaduct EPC Project with a contractual completion date of 30-Jun-2026. During Window-04 (Quarter 4: 01-Oct-2025 to 31-Dec-2025, 92 calendar days), three distinct delay events occur. Let us trace how the ERP Delay Forensics Engine computes net EOT entitlement and separates compensable prolongation costs.

Step 1: Pre-Window Programme State (as of 01-Oct-2025)

• Pre-Window Forecast Completion Date ($T_{\text{pre}}$): 30-Jun-2026 (on schedule, $0$ days project delay).
• Primary Critical Path ($TF = 0\text{ days}$): River Main Span Pier P-12 Pile Cap $\rightarrow$ Pier Shaft $\rightarrow$ Cantilever Segment Launching.
• Near-Critical Parallel Path ($TF = +8\text{ days}$): Approach Viaduct Pier A-04 to A-08 Foundation $\rightarrow$ Precast Girder Erection.

Step 2: Contemporaneous Delay Events Logged in Window-04

1. Event E-1 (Employer Risk — Late GFC Drawing & Utility Hold on Main Pier `P-12`):

• *Window:* 05-Oct-2025 to 18-Nov-2025 (45 calendar days).
• *Cause:* Client discovered an unmapped municipal trunk water main intersecting P-12 pile cap and placed a formal Stop-Work Order while redesigning the pile cap geometry.
• *Path Affected:* Primary Critical Path (TF = 0).

1. Event E-2 (Contractor Risk — Batching Plant Twin-Shaft Mixer Gearbox Failure Affecting `P-12` & `A-04`):

• *Window:* 04-Nov-2025 to 18-Nov-2025 (15 calendar days).
• *Cause:* Contractor failed to maintain spare planetary gearbox seals; structural concrete production halted for 15 days.
• *Path Affected:* Overlaps directly with the last 15 days of Event E-1 (04-Nov-2025 to 18-Nov-2025) on the Primary Critical Path.

1. Event E-3 (Employer Risk — Delayed Land Acquisition / RoW Handover at Approach Pier `A-06`):

• *Window:* 10-Nov-2025 to 15-Dec-2025 (36 calendar days).
• *Cause:* State Revenue Department delayed handing over encumbrance-free possession of Approach Pier A-06 plot.
• *Path Affected:* Near-Critical Parallel Path (which initially had $TF = +8\text{ days}$).

Step 3: Fragnet CPM Computation & Overlapping Window Slicing

A naive contractor submission simply adds $45 + 36 = 81\text{ days}$ of Employer hindrance. Instead, the ERP Fragnet Engine models the exact axial critical-path push across the calendar timeline:

• Sub-Period 1 (`05-Oct-2025` to `03-Nov-2025` = 30 calendar days):
• Only Event E-1 (Employer Utility Hold on `P-12`) is active on the Critical Path ($TF = 0$).
• Classification: 30 days Excusable & Compensable (EC). Completion date pushes from 30-Jun-2026 to 30-Jul-2026.
• Sub-Period 2 (`04-Nov-2025` to `18-Nov-2025` = 15 calendar days):
• Event E-1 (Employer Hold on `P-12`) and Event E-2 (Contractor Batching Plant Breakdown) run simultaneously on the critical path. Even if the client had released the P-12 GFC drawing on 04-Nov-2025, the contractor could not have poured the P-12 pile cap until 18-Nov-2025.
• Simultaneously, on 10-Nov-2025, Event E-3 (Approach `A-06` RoW Hold) starts consuming its $+8\text{ days}$ of Total Float (10-Nov to 17-Nov).
• Classification: 15 days Excusable & Non-Compensable Concurrent Delay (EN-C). Completion date pushes by another 15 days to 14-Aug-2026. The contractor receives 15 days of EOT (protecting against LD), but zero prolongation cost for these 15 concurrent days.
• Sub-Period 3 (`19-Nov-2025` to `15-Dec-2025` = 27 calendar days):
• On 19-Nov-2025, Pier P-12 resumes work (having suffered $30 + 15 = 45\text{ days}$ total delay).
• What about Approach Pier A-06 (Event E-3)? Event E-3 ran for 36 calendar days (10-Nov to 15-Dec). After absorbing its initial $+8\text{ days}$ of Total Float, Event E-3 would push the Approach path by $36 - 8 = 28\text{ days}$ beyond the original baseline (30-Jun-2026).
• However, because the Main Span P-12 path has already pushed the overall project completion by 45 days (14-Aug-2026), and $45\text{ days} > 28\text{ days}$, the Approach path remains sub-critical by $45 - 28 = +17\text{ days}$ of relative float!
• Classification: Event E-3 causes 0 additional days of terminal completion delay beyond the 45 days already driven by P-12.

Step 4: Financial Quantification (LD Avoidance + Prolongation Cost Claim)

• Contractual Liquidated Damages Rate: $0.05\%$ of ₹400 Crore per day = ₹20,00,000 (₹20.00 Lakhs) per day of unexcused delay.
• Audited Daily Site Overhead & Dedicated Plant Prolongation Rate ($C_{\text{prolong}}$):
• Project Management, QA/QC, HSE & Camp Running Staff: ₹1,85,000 / day
• River Marine Barges, Gantry Launcher & Dedicated Tower Cranes (Time-Related Standby Cost): ₹2,65,000 / day
• Total Audited Daily Prolongation Rate: ₹4,50,000 (₹4.50 Lakhs) per day.

By proactively carving out the 15-day batching plant concurrency window and proving the 45-day critical push via Fragnet TIA, the contractor secures immediate Independent Engineer certification of 45 days EOT (saving ₹9.00 Crore in LD) and ₹1.35 Crore in compensable prolongation costs.

1. Mobile Geo-Tagged Hindrance Logging & WBS Binding

• Owner: Section In-Charge / Site Execution Engineer.
• Workflow: Whenever work on a front is obstructed (e.g., unshifted HT overhead line, missing GFC drawing revision, client stop-work instruction, or rainfall exceeding threshold mm/day), the Site Engineer logs a Contemporaneous Hindrance Record in the mobile ERP app before the end of the shift. The system requires selecting the exact Primavera P6 Activity ID, chainage/pier number, geo-tagged photos of the obstructed front, and a list of stranded labour and plant asset IDs idling at that location.

2. Automated 14/28-Day Contractual Notice Clock

• Owner: Project Planning Engineer & Site Contracts Manager.
• Workflow: Creating a Hindrance Record immediately starts a Contractual Time-Bar Countdown:
• Day 1–3: Planning Engineer links the hindrance to its baseline P6 activity and classifies the contractual clause (e.g., FIDIC Sub-Clause 1.9 *Delayed Drawings or Instructions* or Sub-Clause 2.1 *Right of Access to the Site*).
• Day 7: System auto-generates a draft Notice of Claim (FIDIC Sub-Clause 20.2.1) pre-populated with event particulars, affected P6 activity IDs, and contemporaneous photo logs.
• Day 14 (Internal Hard Gate): Escalates to Project Director if the formal Notice of Claim letter number has not been transmitted to the Engineer, guaranteeing zero forfeitures under the 28-day statutory time-bar.

3. Monthly Contemporaneous Fragnet TIA & Interim Particulars

• Owner: Lead Forensic Planner.
• Workflow: At the end of every month, before updating actual progress for the next month, the Lead Planner freezes the Monthly P6 Baseline Snapshot (`.XER` archive) in the ERP, inserts the active hindrance Fragnets (FRAG-xxx), runs the CPM schedule impact, and issues the 28-day Interim Claim Particulars required for continuing delay events under FIDIC Sub-Clause 20.2.6.

4. Exceptions & Recovery Playbook

• Exception A: Employer Alleges "Pacing Delay" Is Actually Contractor Incompetence
• *Scenario:* Knowing that the client's turbine hall foundation drawing is delayed by 60 days, the contractor deliberately slows down structural steel fabrication in the shop (reducing overtime and shift count) so fabricated trusses do not sit rusting in the yard. Later, the Employer claims the shop fabrication slowdown was a Concurrent Contractor Delay that forfeits prolongation costs.
• *Recovery:* Under the SCL Protocol and AACE 29R-03 (Pacing Delay Doctrine), a contractor is entitled to pace non-critical or parallel activities to match a known Employer critical delay, provided the pacing decision is contemporaneously notified. The ERP includes a "Contemporaneous Pacing Notice" template that records the parent Employer delay (FRAG-014) and formally notifies the Engineer that secondary activity production is being paced to mitigate storage damage—preventing the client from reclassifying pacing as concurrent fault.
• Exception B: Constructive Acceleration When Engineer Refuses Timely EOT
• *Scenario:* Despite 45 days of documented Employer RoW delay, the Engineer refuses to grant an interim EOT before the monsoon and instructs the contractor to achieve the original 30-Jun-2026 completion date by mobilizing a second piling rig and working 24-hour double shifts.
• *Recovery:* The ERP logs a Notice of Reservation & Constructive Acceleration, tagging all incremental night-shift overtime, extra piling rig mobilization charges, and additional formwork sets to a dedicated Acceleration Cost Collector WBS so the contractor can recover acceleration costs alongside the disputed EOT.

1. Eliminate Unlinked Hindrance Registers: Configure your site ERP so no hindrance entry can be saved without selecting at least one Primavera P6 / MS Project Activity ID and attaching contemporaneous photographic or official weather/correspondence evidence.
2. Enforce an Automated Day-14 Escalation Gate on 28-Day FIDIC Notice Clocks: Never allow a site delay event to cross 14 calendar days without issuing a formal contractual Notice of Claim referencing the exact sub-clause of entitlement.
3. Archive Monthly Immutable `.XER` Schedule Snapshots with Inserted Fragnets: Prohibit planning engineers from overwriting historical P6 schedules in place; store a locked monthly .XER snapshot before and after Fragnet insertion so every monthly RA bill period has an auditable Time Impact Analysis.
4. Separate `EC`, `EN-N`, and `EN-C` Days in Every EOT Submission: Always present a transparent Concurrency Matrix that voluntarily deducts overlapping contractor-fault days from the prolongation cost multiplier while preserving full EOT entitlement against Liquidated Damages.

How should EPC planning engineers link contemporaneous daily site-diary hindrance logs (rain, RoW hold, late client GFC drawings) to baseline schedule fragnets to substantiate Extension of Time (EOT) claims?

Teams should govern construction delay analysis by linking every transaction to its source evidence, timestamp, and assigned owner before permitting downstream posting. Distinct from EPC-012 (lookahead weekly scheduling); EPC-115 governs contemporaneous delay-event notice clocks (e.g., 14/28-day contractual time-bar alerts) and separating excusable-compensable client delays from contractor concurrent delays. Rather than relying on informal spreadsheet overrides, the workflow enforces a documented verification gate and preserves the original observation whenever a correction is recorded.

How does primavera p6 integration handle exceptions and mismatches?

When a discrepancy occurs during primavera p6 integration, the system routes the blocked record into an owned exception queue rather than silently dropping or auto-adjusting the balance. Assigned operational, quality, and finance owners must review and approve exceptions before posting. Each exception retains the original quantity, date, and counterparty reference until the designated reviewer resolves the variance with supporting evidence.

What should teams test before automating construction claim management?

Before scaling construction claim management, run a bounded pilot using historical records that include partial receipts, late updates, duplicate messages, and rejected lines. Verify that the integration preserves idempotency, maintains a clear segregation of duties between operational entry and financial approval, and produces an auditable trail for every state transition.

A reliable control loop lets project managers, site engineers, and commercial reviewers trace every transaction back to its approved drawing, inspection lot, and measurement sheet.

1. Freeze the baseline scope, revision code, and unit-of-measure rules for one work package before capturing site events.
2. Verify physical measurements, test certificates, and counterparty sign-offs at the designated hold point.
3. Route any out-of-tolerance variance into an explicit exception queue with a named owner and target resolution date.
4. Post only certified quantities and reconciled costs into the project ERP and WBS progress ledger.