---
title: 'Construction delay claims: preserve the schedule and cost evidence'
url: 'https://piper-ai.com/resources/construction-delay-claim-evidence-register'
description: 'Build a delay-evidence register linking events, notices, schedule effects and cost records. Separate contemporaneous facts from assumptions about entitlement.'
contentTypes: [guide]
publishedAt: '2026-11-17T16:56:15.412Z'
updatedAt: '2026-11-17T16:56:15.428Z'
author: 'Ido Gedanken, CEO'
readingTime: 2
---

# Construction delay claims: preserve the schedule and cost evidence

A construction delay claim is a request for contractual relief associated with an alleged delay, such as additional time, money or both. An event record is the starting evidence, not proof of entitlement. Preserve what happened, the notice delivered, the contemporaneous schedule and the costs separately so the project team can test each link.

The actual contract determines notice, relief and proof requirements. As one federal example, [FAR 52.249-10](https://www.acquisition.gov/far/52.249-10) addresses specified excusable delays and written notice when incorporated. Its deadlines and remedies are not universal. Counsel should assess the governing terms, causation, concurrency and any defenses.

## Record the event while it is happening

Capture the planned access date and source, actual access date, location, affected activities, communications, photographs and daily reports. Save the native schedule and dated updates used at the time, including status dates, logic, calendars and revisions. Preserve the unaltered originals and identify who created each record. A later narrative should point back to these records rather than replacing them.

Separate three questions: Does the contract provide relief for this event? Did it affect a completion-driving path, considering other delays and available float? What additional cost is supported and recoverable under the contract? A late activity can consume float without extending completion, and an extension does not by itself establish compensation.

## Work an owner-access event

Assume an illustrative plant project gives the GC access to a room on April 1, but the owner releases it April 8. A substation installation and commissioning sequence cannot start as planned. The scheduler finds that the current update showed three working days of float before the event. Different calendars and other events may alter the result; seven calendar days of restricted access is not automatically seven days of project delay.

| Record | Evidence to retain | Decision still open |
| --- | --- | --- |
| Access | Contract access plan, dated correspondence and actual release | Was access an owner obligation and did the contract provide relief? |
| Notice | Required notice, recipient, delivery proof and response | Was the contractual process satisfied? |
| Schedule | Baseline and updates before and after the event, logic and calendars | What portion affected the controlling path, including concurrent events? |
| Mitigation | Resequencing proposal, authorization and actual outcome | Was the response reasonable and approved where required? |
| Cost | Dated labor, equipment, subcontractor and support records | Which incremental costs are substantiated and recoverable? |

If the team adds a second shift, retain the decision, timesheets and invoices separately from ordinary planned work. Avoid counting the same cost in a subcontractor request and the GC's own cost report. Record a possible impact range as an estimate until the schedule and contract review is complete.

## Hand off the open record

Name an owner for the notice deadline, another for schedule analysis and a reviewer for cost support. [Track schedule and cost risks](https://piper-ai.com/resources/estimating-is-risk-management-not-cost-calculation) against bid assumptions, and [trace clarifications into scope](https://piper-ai.com/resources/construction-rfi-prebid-scope-review) when an unresolved owner decision becomes an actual constraint. Update the register with responses and preserve the original submissions.
