Back

Construction Delay and Extension of Time Record Reference Sheet

Key information to capture when documenting construction delays and extension of time events.

Gillian Laging
COO
Scopey Onsite

Delays rarely start as formal claims or programme issues. They begin on site, often as small interruptions to planned work that seem manageable at the time. When those interruptions are not recorded clearly as they occur, teams are left trying to reconstruct events later, which weakens the ability to support entitlement when the delay is assessed.

This reference sheet sets out the key details that should be captured when work is delayed, along with practical guidance on when and how to record them under live site conditions. It provides a consistent standard for capturing delay events early, so records can be relied on when entitlement is reviewed. A shared standard for recording delay events early, will mean project and commercial teams have a reliable record to work from as the project progresses.

Field When and how to record it Why this matters
Date and time delay first observed Record as soon as work is stopped, slowed, or disrupted. Establishes when the delay began and supports notice timing.
Activity or work affected Record the specific task, work front, or activity impacted. Links the delay to actual work rather than the project generally.
Location or area affected Use the same area names used in programmes and reports. Creates a clear record of where the delay occurred.
What happened Describe the event in plain language while details are fresh. Creates a factual record that can be relied on later.
Link to programme activity Reference the relevant programme activity if known. Connects the delay event to planned works.
Triggering event or instruction Record the instruction, event, or constraint that caused the delay. Helps explain why progress was affected.
Work stopped, slowed, or resequenced Record how planned progress was affected. Demonstrates the nature of the disruption.
Trades or resources affected Record the crews, subcontractors, or plant impacted. Supports assessment of broader project impacts.
Duration observed Record the duration or note that the delay is ongoing. Provides a basis for tracking delay impact.
Photos or supporting evidence Capture photos, emails, screenshots, or other records. Supports facts with contemporaneous evidence.
Follow-up required Record any notices, updates, or actions required. Ensures the delay is managed as well as recorded.
How the delay was communicated Record when and how the issue was raised. Demonstrates timely communication and escalation.
Record status Mark the record as initial, updated, or closed. Shows how the event developed over time.

Capturing this information consistently on a live site is difficult.

Scopey Onsite is built to help site teams capture these records as work happens, using simple messages, photos, and voice notes, without changing how they already operate. The result is a consistent, time-stamped record of site events that can be relied on to support entitlement.

If you would like to see whether Scopey could work for your team, you can book a short demo to walk through how it is used on site.