How to Document Construction Delay Reasons for Winning EOT Claims: India Contract Guide + Free Log Template

Seventy percent of Extension of Time claims die in Indian arbitration—not because the delay didn't happen, but because your site engineer's WhatsApp message won't stand up in a Delhi High Court hearing. If you're running PWD, CPWD, or private EPC projects, your delay paperwork determines whether you recover costs or watch liquidated damages eat your margin.

This isn't about listing why projects get delayed. You already know the reasons. This is about building a paper trail that arbitrators accept under CPWD Clause 2.5 and FIDIC Sub-Clause 8.4, with documentation that links directly to your RA bills.

The 28-Day Trap: Notice Requirements Under CPWD and FIDIC

Indian construction contracts—whether CPWD 2014 (Clause 2.5), State PWD agreements, or FIDIC-adapted EPC contracts (Sub-Clause 20.1)—impose strict notice requirements that contractors routinely miss until it's too late.

The rule is absolute: You have 28 days from the date you became aware of the delay event to notify the Engineer-in-Charge. Not 28 days from when the delay finishes. Not 28 days from when you calculate the impact. Day 1 is when the event occurs or becomes known, and the clock ticks whether you're ready or not.

Miss this window, and Bombay High Court precedent (following FIDIC strict interpretation) typically time-bars the claim. The employer can reject it outright, and you'll struggle to argue waiver or estoppel unless you have exceptional evidence that the employer knew and suffered no prejudice.

What counts as notice: Registered post with acknowledgment due (RPAD) or email with read receipts. WhatsApp and verbal site instructions do not satisfy contractual notice requirements under most Indian arbitration precedents, though courts may accept them as supplementary evidence of awareness.

Valid notice must include: - Specific contract clause invoked (CPWD 2.5, FIDIC 20.1, etc.) - Factual description with exact dates and locations - Affected schedule activities or BOQ items - Expected impact on completion date - Clear statement that you intend to claim EOT and/or costs

7 Categories of Documentable Delay Reasons

Not every delay earns an extension. Focus your documentation effort where liability is clear and Indian arbitration precedent supports compensation.

1. Employer Delays (Highest Success Rate)

These are your strongest claims. The liability is unambiguous. - Delayed site handover: Log the contracted handover date vs. actual possession. Keep the possession certificate and any correspondence acknowledging delay. - Late design approvals: Maintain a submission register showing when drawings were submitted vs. approved. Screenshot approval workflows with timestamps. - Suspension of works: Preserve the formal suspension order and the restart instruction. Calculate the standby costs for the idle period. - Delayed payments (beyond 30 days): Link RA bill submission dates to bank credit dates. Under CPWD and most State PWD contracts, payment delays beyond the stipulated period (usually 30 days) can trigger EOT and financing cost claims. - Scope changes (Variations): Document Variation Orders (VOs) and their impact on the critical path, not just the quantity changes.

2. Engineer/Authority Delays

• Delayed drawing approvals: Track submission dates and chasing emails. If the engineer takes 15 days to approve drawings specified for 7-day turnaround, that's 8 days claimable.
• Delayed inspections: Log inspection requests, site readiness confirmations, and actual inspection dates. Photograph work ready for inspection with GPS timestamps.
• Late testing/commissioning: Maintain equipment availability logs showing machinery sat idle awaiting testing.

3. Force Majeure

Under FIDIC Sub-Clause 19.1 and CPWD Clause 12, events like floods, earthquakes, epidemic lockdowns (COVID-19 precedent now established), and changes in law affecting site operations qualify for EOT (usually without cost compensation, depending on contract).

Critical documentation: Daily site logs showing work stoppage, actual labour counts vs. planned, equipment idle time, and safety measures implemented. Don't just write "rain stopped work." Record "85mm rainfall on 15-Mar-2024 prevented external plastering at Block A; work resumed 18-Mar-2024 after site drying period."

4. Third-Party Delays

• Utility diversion delays: Keep coordination meeting minutes and utility authority letters promising clearance dates.
• Adjacent contractor interference: Document interface meeting notes and safety incidents caused by others working in your area.
• Government permissions: Log application dates vs. approval dates for forest clearances, environmental clearances, etc.

5. Unforeseeable Physical Conditions

FIDIC Sub-Clause 4.12 allows claims for adverse conditions an experienced contractor couldn't reasonably foresee—like encountering rock where soil surveys indicated clay, unexploded ordnance, or contaminated soil requiring remediation.

Documentation: Geotechnical reports, pre-tender site investigation data, photos of the condition, and expert assessments proving the unforeseeability.

6. Material and Procurement Delays

• Client-specified material unavailability: High claim eligibility if the client mandated the supplier or specification. Keep material indent dates, PO delays, and correspondence.
• Import delays: If import licenses or client-supplied materials are delayed, document shipping documents and customs clearance records.
• Contractor-procured materials: Generally your risk, unless market shortages were unforeseeable and extraordinary (rarely successful in arbitration).

7. Concurrent Delays

When your own delays overlap with employer delays, documentation determines apportionment. Maintain separate registers for excusable (employer-caused) vs. non-excusable (contractor-caused) delays. Your schedule analysis must isolate the critical path impact of each concurrent event—otherwise the tribunal will apportion 50/50 or reject the claim entirely.

The Hindrance-to-Delay Mapping: Converting Daily Issues into EOT Evidence

Your site diary says: "Cement not available." Your arbitrator needs: "Material shortage delayed slab concreting of Block A (Activity CS-04) from 15-22 March 2024, consuming 3 days float and delaying successor activities by 2 days on the critical path."

The disconnect between site records and claims documentation explains why valid claims fail. Every hindrance entry must be translated into contractual evidence through five specific data points:

1. Precise Work Identification: Specific BOQ item or schedule activity ID (not "plastering" but "External plastering Block A Level 2")
2. Exact Duration: Calendar dates with start/end timestamps, not "last week"
3. Contractual Basis: Specific clause invoked (CPWD 2.5, FIDIC 8.4, etc.)
4. Notice Compliance: Date of 28-day notice with reference number
5. Critical Path Impact: Float consumption analysis showing effect on completion date

Superwise's Construction Hindrance Delay Log enforces this mapping at the source. When your site engineer records a hindrance in the mobile app, the system timestamps the entry, requires activity linkage, and flags it for claims review if it meets configured delay thresholds.

Link to Schedule: Your hindrance register and CPM schedule must integrate. For each event, identify the affected baseline activity, calculate impact using Time Impact Analysis (TIA) or Impacted As-Planned methods, and document the critical path effect—not just the activity delay.

Delay Log Fields That Arbitrators Look For

Tribunals evaluating EOT claims examine your delay register for completeness, contemporaneity, and consistency. Your log must contain:

The Contemporaneous Record Standard: Arbitrators weight documents created at the time of events far heavier than reconstructed month-end registers. Your delay log entries should be timestamped when the delay occurs—not compiled later from memory. Digital systems with immutable records (write-protected after supervisor review) satisfy this standard better than paper diaries that can be backdated.

Linking Delay Events to RA Bill Impacts: Cost Quantification

EOT claims succeed when they prove actual cost impacts, not just theoretical schedule slippage. Your Running Account Bills become evidence of delay costs when properly annotated.

Typical Cost Impacts to Document: - Extended site establishment: Additional security wages, site office rent, hoarding maintenance—code these separately in your accounts - Idle labour: Wages for workers present but non-productive—tag labour challans with delay codes - Idle equipment: Hire charges and operator wages for equipment standing by—log non-utilization hours in equipment registers - Material price escalation: Increased procurement costs due to delayed purchase—keep PO revisions showing price variations - Inflated overheads: Extended preliminaries and head office costs

RA Bill Reconciliation: Maintain measurement sheets with date-range annotations showing quantities executed during delay periods. When your delay log links directly to RA Bill line items, you create an auditable chain: Hindrance Event → Schedule Impact → Cost Quantification.

Email Templates for Delay Notifications

Adapt these to your contract clauses. Send via email with read receipt, and follow with registered post for critical claims.

Template 1: Initial Delay Notice (Within 28 Days)

Subject: Delay Event Notice - [Project Name] - Event Ref: [XXX]

Dear [Engineer-in-Charge],

As per Clause [2.5/20.1] of the Agreement dated [Date], we formally notify you of a delay event occurring on [Date]:

Event: [Factual description - e.g., "Delayed approval of revised GFC drawings for Block A electrical works submitted on [Date]"] Affected Works: [Specific BOQ items/Activities] Expected Impact: [X] days delay to the critical path

This notice is issued within the contractual 28-day period. We will submit detailed particulars of extension and cost impact within the time stipulated in the contract.

Please acknowledge receipt.

Regards,
[Authorized Signatory]
[Contractor Name]

Template 2: Detailed Claim Submission

Subject: Detailed EOT Claim - [Event Ref] - [X] Days Extension Sought

Dear [Engineer-in-Charge],

Pursuant to our notice dated [Date] (Ref: [XXX]), we submit detailed particulars:

Event Chronology: [Dates and facts]
Contract Basis: Clauses [X], [Y]
Schedule Analysis: [Critical path impact - attach TIA]
Cost Impact: Rs. [Amount] (detailed calculation attached)
Mitigation: [Steps taken to minimize delay]

Attachments: Delay log extract, photographs, correspondence, schedule analysis.

We request your determination within [XX] days as per Clause [Z].

Regards,
[Authorized Signatory]

Template 3: Follow-up/Chasing

Subject: Reminder: Pending Determination of EOT Claim [Ref: XXX]

Dear [Engineer-in-Charge],

We refer to our EOT claim submitted on [Date] (Ref: [XXX]). As [X] days have elapsed without determination, we request urgent review to avoid further project disruption and cost escalation.

Please confirm receipt and expected determination date.

Regards,
[Authorized Signatory]

Common Documentation Mistakes That Invalidate Claims

Mistake 1: Retrospective Record Creation
Creating delay logs at month-end destroys credibility. Arbitrators compare your register with contemporaneous emails and third-party weather data. Discrepancies kill claims.
Fix: Enforce daily DPR submission with hindrance logging before work closes.

Mistake 2: Generic Descriptions
"Rain stopped work" fails. "Heavy rainfall 85mm on 15-Mar-2024 prevented external plastering at Block A per IMD records; work resumed 18-Mar-2024" succeeds.
Fix: Mandate specific activity linkage and weather data in site diaries.

Mistake 3: Missing Notice Links
Every delay log entry must cross-reference the 28-day notice sent. Without this, tribunals assume notice was not given.
Fix: Use a reference numbering system linking notices to log entries.

Mistake 4: Ignoring Concurrent Delays
Claiming 30 days EOT when 15 days were your own fault invites apportionment or rejection.
Fix: Maintain separate registers with clear causation attribution.

Mistake 5: Photo Evidence Without Metadata
Photos help only with timestamps proving contemporaneity. Screenshots and undated photos carry minimal weight.
Fix: Use mobile apps with automatic GPS coordinates and timestamp embedding.

Digital vs. Paper: Audit Trails for Arbitration

Indian arbitration increasingly accepts digital records under the Indian Evidence Act, provided they meet authenticity and integrity standards.

Requirements for Arbitration-Ready Digital Records: - Authenticity: User authentication logs showing who created the record - Integrity: Immutable storage preventing post-hoc edits (write-protection after review) - Timestamp: Server timestamps, not device time which can be changed - Accessibility: Export capability in standard formats (PDF/A, CSV) for tribunal disclosure - Chain of Custody: Audit logs showing creation, review, and approval actions

Building the Archive: Export monthly PDF archives of delay logs with all attachments. Preserve system audit trails showing record creation history. For high-dispute projects, maintain offline backups separate from cloud systems.

Superwise's document management system maintains these audit trails automatically, with user action logs and tamper-evident storage satisfying Section 65B of the Indian Evidence Act for electronic records.

How Structured Documentation Powers Claims Analysis

When your delay data is structured from Day 1, you can leverage automated analysis for complex claims: - Opportunity identification: Flag delay events exceeding thresholds that haven't been claimed - Notice drafting: Generate first-cut notices from structured log entries - Impact calculation: Extract schedule and cost data for quantum preparation - Defensibility review: Cross-reference claims against contemporaneous records to identify evidentiary gaps before submission

The contractors best positioned for arbitration success are those whose documentation systems generate machine-readable, auditable records from the first day of the project.

FAQ: Construction Delay Documentation for EOT Claims

What if I miss the 28-day notice deadline? Can I still claim?
Under strict FIDIC and CPWD interpretations, missing the deadline typically time-bars the claim. However, Indian courts have occasionally allowed late notices where the employer had actual knowledge and suffered no prejudice (doctrine of waiver/estoppel). Document the delay anyway—you may argue these equitable grounds if the engineer continued processing other claims without objection.

How do I handle concurrent delays where both parties are at fault?
Maintain separate registers for employer-caused and contractor-caused delays. Apply the dominant cause test or apportionment based on time impact. Your schedule analysis must isolate the critical path effect of each concurrent delay—tribunals will apportion liability if you don't.

Can WhatsApp messages serve as delay notices?
While Indian courts increasingly accept WhatsApp as evidence of communication, most construction contracts require formal notice "in writing" (email or physical letter). Use WhatsApp for immediate awareness, but always follow with formal notice within 28 days. Save both as evidence of timely communication.

How detailed should my delay log descriptions be?
Sufficient for a third-party arbitrator to understand exactly what happened, when, where, and why it mattered to the critical path. Include: specific location coordinates, affected BOQ items, weather data if relevant, labour/equipment present, and immediate mitigation actions taken.

Do I need a separate delay log if I already maintain a site diary?
Yes. Site diaries are narrative and chronological. Delay logs are analytical and claim-focused, extracting hindrance events and structuring them for contractual analysis. Superwise's hindrance delay log bridges both—capturing narrative detail with structured claim fields.

How do I prove delay costs when my RA Bills don't itemize by period?
Use measurement sheets with date-range annotations. Tag labour challans and equipment logs with delay period codes. Maintain separate expense vouchers for extended site establishment costs, coded to specific delay events.

What schedule analysis method do arbitrators prefer?
Time Impact Analysis (TIA) or Impacted As-Planned are most commonly accepted in Indian arbitration. The key is demonstrating the effect on the critical path, not just activity delays. Maintain your baseline schedule and update it monthly to show progression and impact.

Can I claim EOT for delays caused by my subcontractors?
Only if the subcontractor delay was caused by an employer risk event (e.g., delayed drawings for subcontract works). Pure subcontractor performance issues are contractor risk under most contracts. Document the causation chain carefully to prove the employer's delay filtered down.

How long should I preserve delay documentation?
Minimum 12 years from project completion under Indian limitation law for construction contracts. For arbitration-prone projects, preserve indefinitely. Export archives monthly to independent storage.

Does Superwise integrate with Primavera or MS Project for schedule analysis?
Superwise handles baseline management and progress updates. For complex TIA, export progress data to your preferred scheduling tool and re-import analysis results. The hindrance log maintains the live link between delay events and schedule activities.

Download: Construction Delay Log Template

Get the ready-to-use Construction Delay Log template pre-formatted for CPWD and FIDIC notice requirements. The template includes event tracking fields mapped to contractual clauses, 28-day notice deadline calculator, schedule impact documentation columns, cost linkage sections for RA Bill reconciliation, photo evidence metadata fields, and concurrent delay apportionment framework.

Download the ready-to-use files for this article:

Arbitration-ready delay log pre-formatted for Indian construction contracts (CPWD Clause 2.5, FIDIC Sub-Clause 20.1). Includes 28-day notice deadline calculator, contract clause mapping, cost linkage fields for RA Bill reconciliation, and concurrent delay apportionment tracking. Best format: Excel, because this asset is meant to be edited and reused on-site. - Download Excel template

Access the digital version: Use Superwise's Construction Hindrance Delay Log for automated field capture, timestamping, and claims-ready export. Link directly to your Daily Progress Reports, Schedule, and RA Bills for complete project documentation that wins arbitration.