Anonymised worked example

Inspect the evidence trail before creating an account.

This illustrative extension-of-time record shows how sources, chronology, drafting, evidence gaps and review decisions fit together. It contains no real client or project information and makes no claim about a commercial outcome.

Sample controls

Use your browser's print dialog to inspect the layout or save this worked example as a PDF.

Draft for professional review

Extension of Time Claim Record

Late issue of coordinated design information

Not approved for issue
Project
Riverside Fit-Out Phase 2 (illustrative)
Event reference
EV-014
Contract
To be confirmed from executed terms
Prepared
Worked example, 17 Jul 2026
01

Executive summary

The available records indicate that coordinated M&E design information required for planned ceiling closure activities was not complete by the recorded information-required date of 6 May 2026. Revised information was issued on 14 May 2026 under instruction AI-014 [S-01, page 1; S-03, activities MEP-220 to MEP-250].

Meeting minutes, correspondence and site records indicate that the affected team raised the outstanding information, recorded the dependency and attempted resequencing [S-02, item 4.2; S-04, entries 118-125; S-05, messages 2, 5 and 8]. The current record supports further review of notice compliance and time effect; it does not yet establish the operative contractual clause or final extension sought.

02

Source register

Each source has a stable reference. Locators show where a reviewer can check the statement without searching the full file.

RefRecordDateLocatorUse in draft
S-01Architect instruction AI-01414 May 2026Page 1Confirms the revised coordination information and issue date.
S-02Design coordination meeting minutes12 May 2026Item 4.2, page 4Records that ceiling closures depended on coordinated M&E information.
S-03Accepted programme update 0530 Apr 2026Activities MEP-220 to MEP-250Shows the planned sequence requiring design release by 6 May 2026.
S-04Site diary and progress photographs15-24 May 2026Diary entries 118-125Records restricted progress and temporary resequencing measures.
S-05Email chain: design release follow-up5-13 May 2026Messages 2, 5 and 8Records requests, warnings and the date information remained outstanding.
03

Event chronology

Programme update 05 records the planned sequence and required design release.

S-03

The project team requests the outstanding coordinated information.

S-05, message 2

Recorded information-required date passes without complete coordinated details.

S-03; S-05

Coordination minutes record the dependency affecting ceiling closure activities.

S-02, item 4.2

Revised information is issued under instruction AI-014.

S-01, page 1

Diary entries record restricted progress and mitigation through resequencing.

S-04, entries 118-125
04

Causation and mitigation record

Current supported position

  • The accepted programme record identifies the affected activity sequence and a required design-release date [S-03].
  • Correspondence and meeting minutes record that the outstanding information was raised before issue [S-02; S-05].
  • Site records describe temporary resequencing and restricted progress after the instruction [S-04].

Reservation

These records support a factual sequence but do not alone prove critical-path delay, contractual entitlement or the final duration. Those matters require review against the executed contract and appropriate programme analysis.

05

Evidence gaps and next actions

Executed contract and amendments

Action required

The notice clause, time bar, recipient and service method cannot be confirmed from the sample sources.

Next: Upload the signed contract and verify the operative clause before issue.

Critical-path effect

Professional review

The records show disruption to planned activities but do not, by themselves, establish the final time impact.

Next: Review the accepted programme, updates and any suitable delay analysis.

Proof of notice service

Evidence missing

No issued notice, transmission record or recipient acknowledgement is included.

Next: Record the approved recipient, issue method, issue time and proof of receipt.

06

Review and approval checklist

  • Project facts and source locators checked against the original records
  • Executed contract, amendments, notice clause and service requirements verified
  • Chronology, causation, mitigation and programme position reviewed by the responsible professional
  • Assumptions, exclusions and unsupported statements resolved or retained as express reservations
  • Recipient, issue method, attachments and proof of service approved and recorded
Illustrative workflow sample only. This is not legal, contractual, quantity surveying, delay-analysis or expert advice and is not approved for issue.

Use your own project record

Create a private workspace when you are ready to organise real evidence.

Account creation does not make a project record public. Confirm the plan and billing choice after the workspace is created.

Create a private workspace