Risk & contracts

How to document construction delays before they become disputes

Document a construction delay by recording the event, affected work, timing, instructions and mitigation. Preserve the current schedule and resource evidence, then check the executed contract for notice requirements. A delayed activity does not by itself prove a critical-path delay or a right to additional payment.

Start with the blocked work, not a legal conclusion

A foreman’s “we are held up” text is an alert, not a complete delay record. Ask which activity and area are blocked, what was expected to happen, the observed cause, the first affected time and whether other work is available. Preserve the original message and identify who supplied each fact.

For a GC, missing access, design information or a predecessor trade may affect several work fronts. For a subcontractor, the immediate issue may be a crew on standby or a promised area that is not ready. Separate observations from the later determination of responsibility.

Connect the event to the schedule

A three-day obstruction does not automatically mean three days of project extension. Critical-path effect, concurrent delay, float and mitigation need review. Do not turn an estimated impact in a text into an approved schedule change.

  • Identify the activity ID, location and current schedule revision.
  • Preserve the relevant lookahead, planned dates and dependencies.
  • Record actual progress, available alternative work and instructions.
  • Record when the obstruction clears and work resumes.

Check notice before waiting for the final cost

Read the executed agreement and amendments for the trigger, recipient, delivery method and required content. Notice may be required before the full cost is known. A crew text to a project assistant is not necessarily contractual notice to the required party.

FAR 52.242-14 addresses qualifying suspensions and delays when incorporated into a federal contract. Its conditions, exclusions and notice requirements are not a template for every private subcontract. Have the responsible contract reviewer confirm the applicable procedure.

Keep mitigation and resource records distinct

Record alternative work considered, directions received, actions taken and results. Track labor allocated to productive work separately from idle time. Record equipment operating and standby hours, locations and reasons without assuming that all idle cost is recoverable.

Link timesheets, tickets, agreed rates, invoices, photos and dated communications to the event. Cost records support review; they do not establish entitlement without contract and causation analysis.

What a useful follow-up looks like

ILLUSTRATIVE EXAMPLE
Downtown Office Tower, Level 6
Foreman: “Can’t start ceiling rough-in. Inspection still outstanding.”
Follow-up: Which inspection, work area and schedule activity? When was access expected? How many workers are affected, and what can they move to?
Record: Result unconfirmed. Link the current lookahead and resource update.
Review: PM checks impact and the contract notice process before external delivery.

Capture the facts while the event is happening

Magra is positioned to cross-check updates against supplied project documents, flag missing facts and organize records and drafts. Keep schedule versions, contacts and notice procedures current. The team verifies the event and determines its contractual effect.

The example above is illustrative, not a customer claim. The objective is an earlier, better-supported decision about mitigation, direction and notice, not a guarantee of claim avoidance or recovery.

Common questions

How do I prove a construction delay?

Preserve event records and schedule versions, connect the event to affected activities, and document actual impact and mitigation. Contract terms, causation and concurrent delay require review; a daily log alone does not establish entitlement.

What should a subcontractor record when another trade holds up its crew?

Record the area, activity, obstruction, timing, direction requested, resource use, alternative work and resumption. Follow the executed subcontract’s notice process.

Can AI warn me about a schedule delay?

It can help flag a reported gap against the supplied schedule and request missing facts. It cannot independently observe the site or replace a critical-path analysis.

Sources & editorial note

By Magra editorial. Examples are illustrative, not customer results. Not legal advice; executed documents, amendments and applicable law govern. Product availability can change.

Put the record to work.

Magra is the AI project manager for contractors, on your phone.

Explore Magra’s schedule and risk checks · Text Magra

Keep reading