Seven Records Every EOT Claim Needs

An extension-of-time claim is not proved by showing that an event occurred or that completion was late. The claimant generally needs to establish contractual entitlement and demonstrate how the event affected completion or a relevant milestone, supported by reliable contemporaneous evidence.

The exact requirements depend on the contract and governing law. However, across FIDIC-style and other major forms, the same record groups repeatedly determine whether an EOT claim can be understood, tested and fairly assessed.

1. The contract, tender and accepted baseline

Start with the obligation that was allegedly affected. Preserve the executed agreement, conditions, specifications, drawings, bills or schedules, tender clarifications, access dates, sectional milestones, calendars and the accepted baseline programme in native format.

These records establish the original bargain: scope, risk allocation, completion obligations, planned sequence and contractual procedure. Keep amendments and document-priority provisions with them. A claim should never quote a clause or planned date without making the controlling version identifiable.

Minimum links: contract clause, milestone, work package, baseline activity and relevant risk event.

2. Notices and contractual communications

Maintain the initial notice, acknowledgement, further particulars, interim updates and final claim, together with instructions, variation communications, requests and responses relevant to the event.

A notice register should record:

• event and clause relied upon;
• awareness or trigger date;
• contractual deadline;
• actual submission date and method;
• recipient and proof of delivery;
• continuing-effect updates;
• response, determination and status.

Do not rely on a progress meeting reference as a substitute unless the contract and governing law permit it. Notice wording and time bars are contract-specific.

3. Native programme versions and schedule narratives

Keep the tender programme where relevant, accepted baseline, every periodic update, proposed revisions, recovery or mitigation programmes, look-aheads, narratives and change logs. Preserve native scheduling files as well as approved or issued PDFs.

The record should explain actual starts and finishes, remaining durations, logic and calendar changes, constraints, critical and near-critical paths, progress data date and reasons for revisions. An unexplained schedule change can be mistaken for retrospective manipulation even when it arose from a legitimate planning decision.

AACE Recommended Practice 29R-03 is useful here: it treats forensic schedule analysis as a technical exercise in which method selection, data reliability and validation matter. No single delay method is automatically correct for every claim.

4. Contemporaneous progress and physical evidence

Programme data should be capable of verification against what happened on site and across design, procurement and approvals. Relevant records may include:

• daily diaries and daily reports;
• weekly and monthly progress reports;
• dated and located photographs or video;
• inspection and test records;
• measurement records;
• drawing, RFI and submittal logs;
• procurement, manufacturing and delivery records;
• meeting minutes; and
• weather or access records where relevant.

Useful records state facts, not merely conclusions. "Excavation delayed" is weak. "Excavation in Zone B stopped from 10:30 to 16:00 because instructed utility isolation had not been provided; Activity EXC-B-140; 18 workers and two excavators available" is testable.

5. Resource allocation and productivity records

Record planned and actual labour, staff, plant, equipment, materials and subcontractors by date and, where practicable, by activity, location or work area. Include hours worked, idle time, transfers, output and the reason for any loss of productivity.

The SCL Delay and Disruption Protocol notes that proving time and cost consequences becomes more difficult without records of planned and utilised resources. Generic payroll or plant lists show presence, not necessarily event impact. Allocation is what connects the resource to the affected work.

6. Event-linked cost records

Even when the immediate relief sought is time, cost records can test the event, resource response and mitigation. For time-related compensation, they are essential.

Preserve timesheets, payroll, plant records, invoices, purchase orders, subcontract accounts, site overhead ledgers, payment evidence and cost reports. Establish suitable cost codes early enough to separate:

• baseline and normal execution cost;
• event-related direct cost;
• time-related indirect cost;
• unrelated or concurrent cost;
• cost recovered elsewhere; and
• avoided or mitigated cost.

Reconcile claimed figures to the project accounts. A spreadsheet prepared for the claim is a calculation; it is not, by itself, proof that the underlying expenditure was incurred because of the relevant event.

7. The event, decision and mitigation trail

This seventh group connects the other six. Maintain an event record showing:

• what occurred and when;
• source documents supporting the fact;
• affected activities, locations and milestones;
• responsibility and contractual basis asserted by each party;
• options and mitigation considered;
• decisions, instructions and actions taken;
• forecast and actual effect;
• unresolved contradictions; and
• links to notice, programme, progress, resource and cost records.

This should not be a retrospective advocacy document disguised as a site record. Facts, party positions, analysis and assumptions should be clearly separated. When a matter remains uncertain, say so and identify what evidence is missing.

A record is valuable only if it can be trusted

The SCL Protocol recommends electronic records that are accessible, searchable, retrievable and, for programmes and formula-bearing spreadsheets, retained in native format. Record quality also depends on authorship, date, version, approval status and a reliable history of change.

For every material EOT record, ask:

• Is the source original or derived?
• Who created it, and when?
• Was it issued, accepted, rejected or superseded?
• Has the native file been preserved?
• Can it be linked to the relevant event and activity?
• Is there a contradictory record that must be considered?

Turn seven record groups into one evidence chain

An EOT claim becomes easier to assess when the reviewer can move from the event to the clause, notice, programme activity, site evidence, mitigation action and cost without manually reconciling separate folders and registers.

ContraClaim DMS is designed to help teams organise those relationships, retain source references and surface missing links for professional review. It does not replace a competent planner, contract professional, delay expert or lawyer. It gives them a more controlled evidence base on which to work.

See how ContraClaim DMS can support a source-linked EOT record from first notice through final assessment.

Sources and further reading

• Society of Construction Law — Delay and Disruption Protocol, 2nd edition
• AACE International — Recommended Practice 29R-03: Forensic Schedule Analysis
• FIDIC — Claims Procedures

This article provides general contract-administration information, not legal advice or a prescribed delay-analysis methodology. Apply the express contract terms, facts and governing law, with advice from appropriately qualified professionals.