Esc

↑↓ move↵ openIndex · Pagefind

Extension-of-time preparation: build the evidence trail as the event develops

Organize event records, notices, schedule versions and mitigation evidence for a project-specific extension-of-time review.

Charley Forey2 min readSchedulingSchedule forensics
On this page
  1. Start an event record
  2. Explain the chain from event to milestone
  3. Maintain a living chronology
  4. Make the request reviewable

An extension-of-time request needs a traceable explanation of the event, its effect and the applicable contractual process. Waiting until project closeout makes that work harder: people leave, records become scattered and the original forecast assumptions become difficult to reconstruct.

This is an evidence-preparation workflow, not a determination of entitlement or a notice deadline. Read the incorporated terms, amendments and relevant communications with the people responsible for administering the contract. Do not borrow a deadline from another project.

Start an event record

Give the event an identifier and record the first known occurrence, discovery date, affected work, people involved and immediate actions. Preserve the actual documents rather than relying only on a later summary.

Record group What to collect
Contract process Applicable provision, notice route, recipients and required information
Event Instruction, RFI response, access record, delivery record or other direct evidence
Schedule Relevant baseline and updates, data dates, settings and narrative
Field effect Daily reports, locations, crew records, photographs and progress evidence
Response Mitigation options, decisions, approvals and implementation records
Submission history Notices, transmittals, responses and receipt evidence

The SCL Delay and Disruption Protocol discusses records and delay procedures. Use it as a further reference while establishing what your own contract requires.

Explain the chain from event to milestone

In a fictional project, a revised equipment requirement affects fabrication. Identify the instruction, the affected procurement activity, the manufacturer’s revised commitment and the installation/testing sequence. Then examine whether that sequence drives the relevant milestone during the period.

The event’s duration is not automatically the extension requested. Available float, overlapping work, other controlling paths and actual mitigation can change the effect. State the analysis method and the evidence supporting the connection.

Maintain a living chronology

Use one row per material development: date, event, source reference, affected activity, action and unresolved question. Keep factual observations separate from the team’s interpretation. If two records conflict, preserve both and identify the issue rather than silently choosing the convenient one.

Track notice and submission obligations independently from the schedule analysis. A strong model does not demonstrate that a communication reached the right recipient at the right time.

Make the request reviewable

Prepare an index linking each material assertion to its record. Explain the requested milestone adjustment, the calculation units, the method, assumptions and remaining uncertainty. Keep time and money analyses distinguishable; they may require different evidence and contractual treatment.

Before submission, have the responsible project and contract reviewers check completeness and consistency. Continue with time impact analysis, concurrent delay and the Schedule Forensics resource library.

Share this article

Written by

Charley Forey

Founder of os.construction. We're building the operating system for construction. Project Financials follows job money, and company Accounting covers the books and controls. AI agents remain planned. We write about how money and data actually move on a job, and we build in public.

Apply to the founding program →Start a free trial →
Open file