Preparing an Evidence-Based Extension of Time Submission

The situation

A civil engineering contractor faces design information changes, access restrictions and revised interfaces with specialist subcontractors. The project team needs to present a structured extension-of-time submission rather than a bundle of disconnected programme screenshots and correspondence.

The challenge

The claim must distinguish contractual entitlement from factual causation and the extent of critical delay. Notice requirements, relevant contract amendments and the available project records need careful consideration. A programme model alone cannot decide entitlement.

A practical approach

1. Review contractual framework

   Identify the governing contract, amendments, relevant notice provisions and the specific alleged delay events; obtain qualified contractual input where necessary.

2. Build the contemporaneous record

   Organise instructions, notices, progress reports, correspondence, site diaries, drawings and programme revisions into a chronological evidence index.

3. Demonstrate time effect

   Select and explain an appropriate scheduling method, identifying the relevant critical paths, mitigation and potential concurrency.

4. Prepare a coherent submission

   Connect each asserted event to records, time analysis and the requested determination, noting assumptions and unresolved points.

Illustrative deliverables

• Event-by-event claim register
• Documented chronology and evidence index
• Programme analysis appendices
• Structured EOT narrative and submission checklist

Key insight: The quality of an EOT submission rests on traceability between contract, event, evidence and time impact—not the volume of documents provided.

Key lessons

• Check the actual contract before treating any notice period as universal.
• Keep factual records and expert inferences distinct.
• Explain material assumptions and alternative interpretations.