Delay Claim Documentation Example for Contractors

A delay can cost a contractor money before anyone calls it a claim. Crews lose productive hours, equipment sits, sequence changes, and the field team starts working around a problem it did not create. A solid delay claim documentation example shows what happened, when it happened, who was affected, and what the contractor did to reduce the impact.

That record needs to be built while the event is active. A daily report written two weeks later from memory will not carry the same weight with an owner, architect, general contractor, or attorney. The goal is not to write a dramatic narrative. The goal is to create a factual, dated record that connects the delay event to real project consequences.

What a Delay Claim Record Must Prove

A schedule claim is rarely won by proving that something went wrong. Construction projects always have issues. The stronger question is whether the record proves that a specific event delayed or disrupted a specific scope of work, and whether the affected party gave proper notice under the contract.

Good documentation establishes four things: the event, the impact, the cause, and the response. The event could be late structural steel, an owner-directed design revision, an access restriction, a failed inspection, or weather that meets the contract definition of an excusable delay. The impact is the work that could not proceed as planned. The cause identifies who controlled the issue. The response shows mitigation rather than passive waiting.

A report that says, “Unable to work due to delays,” is weak. It does not identify the condition, affected location, labor hours, schedule activity, or action taken. It leaves too much room for the other side to argue that the contractor could have worked elsewhere.

Delay Claim Documentation Example: Late Precast Panels

The following example shows the level of detail a superintendent or project manager should capture in a daily delay report. It is not a substitute for the formal notice requirements in your subcontract or prime contract. Notice periods, delivery requirements, and recovery rights depend on the contract documents.

Project delay report

| Record field | Example entry | |—|—| | Project | Riverside Medical Office Building | | Report date | May 14, 2026 | | Reporting party | Apex Drywall, Superintendent J. Martinez | | Delay event | Precast exterior panels for Grid Lines C through F were not delivered as scheduled. | | Planned activity | Frame exterior wall backing and begin Level 3 interior framing in the east wing. | | Scheduled start | May 14, 2026, 7:00 a.m. | | Actual condition | At 6:45 a.m., delivery area was empty. Supplier representative confirmed panels remained at the fabrication yard due to incomplete embeds. General contractor was notified at 7:10 a.m. | | Affected resources | 12 carpenters, 2 laborers, 1 telehandler, and 2 scissor lifts assigned to east wing work. | | Impacted duration | 6.5 productive hours lost for 14 employees. Total: 91 labor hours. Equipment remained on site and available but could not support planned exterior backing work. | | Schedule effect | Activity 3E-145, “East Wing Exterior Backing,” could not start. Follow-on interior framing sequence was restricted because material staging and layout access were unavailable. | | Mitigation | Crew moved to Level 2 punch work from 8:00 a.m. to 10:30 a.m. Remaining available work supported 6 employees only. Eight employees had no comparable productive work available after 10:30 a.m. | | Notice and communication | Written notice issued to general contractor at 11:20 a.m. Referenced subcontract Section 8.3. Requested direction and revised delivery date. | | Supporting records | Delivery schedule dated May 8, supplier email, photographs of empty delivery zone, daily manpower report, equipment log, and two-week look-ahead. |

This record does not claim a dollar amount on day one. That is often the right approach. The field report preserves facts, while the project manager later applies labor rates, equipment costs, productivity analysis, extended general conditions, and schedule analysis as required.

The report also avoids a common mistake: claiming every assigned worker was fully idle. In this example, the crew found limited alternate work for part of the day. Recording that effort strengthens credibility. A contractor that documents mitigation is in a better position to recover the unavoidable portion of the loss.

Write the Narrative Like a Field Record, Not an Argument

The narrative section should answer practical questions a reviewer will ask months later. What was supposed to happen? What condition prevented it? Who observed it? What work could not proceed? What did the team do next?

Use times, locations, quantities, and names. If the general contractor instructed the crew to stand by, record the instruction and the person who gave it. If a drawing revision prevented layout, identify the drawing number, revision date, and affected area. If weather caused the problem, capture the actual site conditions and compare them with the contract standard before labeling the event compensable or excusable.

Avoid loaded statements such as “GC completely failed” or “owner caused major damages.” Those conclusions belong in formal correspondence and claim analysis, if the facts support them. The daily report should be accurate enough that it still reads well when reviewed by someone who was not on the project.

A practical narrative for the precast example might read:

> At 6:45 a.m., the east wing precast panel delivery zone was empty. The planned delivery window was 6:30 a.m. to 7:00 a.m. Per supplier representative Mark Lee at 6:55 a.m., panels for Grid Lines C-F remained at the fabrication yard because required embeds were incomplete. This prevented installation support, exterior wall backing, and planned Level 3 east wing framing sequence. The crew was reassigned to Level 2 punch work where available. Six employees performed alternate work until 10:30 a.m.; eight employees had no available productive work for the remainder of the shift. General contractor superintendent R. Davis was notified at 7:10 a.m. Photos, manpower records, and supplier email are attached to this report.

That is short, factual, and useful. It identifies the planned work, the cause reported at the time, the exact impact, mitigation effort, and supporting evidence.

Attach Records That Corroborate the Delay

A delay report is stronger when its key facts appear in more than one project record. The daily report should not sit alone in a folder. It should match the manpower log, equipment log, schedule update, delivery record, meeting minutes, and project correspondence.

For most delay events, the field team should preserve at least these four categories of support:

• Dated photos and videos showing the actual condition, including blocked access, incomplete predecessor work, missing material, or weather conditions.
• Manpower and equipment logs showing who was assigned, who was reassigned, and what resources remained idle or underused.
• Schedule records, such as the current look-ahead, baseline activity references, recovery plans, and updated schedule narratives.
• Emails, texts, meeting notes, directives, inspection records, delivery tickets, and formal notices tied to the event.

Photos deserve special attention. A wide photo can establish the overall site condition, while close photos can capture missing embeds, standing water, incomplete work, or an occupied work area. Label the location and direction if the app does not capture it automatically. A photo without context can become just another image in a dispute file.

Document Every Day the Impact Continues

One report for the first day of a delay is not enough if the impact lasts a week. A continuing delay needs a continuing record. Each day, identify whether the condition remained, whether work was still affected, whether the crew found alternate work, and whether any new direction or recovery action was issued.

Do not copy yesterday’s narrative without updating it. Repeated language can make it appear that no one checked the actual conditions. If the impact changed from full stoppage to reduced productivity, say so. If a material delivery arrived but was incomplete or damaged, record that distinction. The claim may turn on the details.

There is also a trade-off between speed and completeness. A superintendent should not spend an hour writing a claim memo at the end of a long shift. But a two-minute report with accurate times, headcounts, photos, and a clear event description is far more valuable than a polished report created after the fact. Mobile field reporting helps standardize that work without pulling the superintendent away from the job.

Construction Reporting Apps is built around that field reality: records have to be fast enough to complete today and strong enough to support the project months later.

Keep Notice Separate From the Daily Report

A daily report documents the jobsite condition. Contractual notice protects rights. Those are related, but they are not always the same document.

If the contract requires notice within 24, 48, or 72 hours, send it on time even if the full cost and schedule impact are not known. Reference the delay event, reserve rights as appropriate, request direction, and state that the contractor is evaluating time and cost effects. Then continue building the field record as the event develops.

Waiting for a complete analysis can be risky. By the time the costs are known, the notice deadline may have passed. On the other hand, overstating the impact before the facts are developed can damage credibility. Timely notice plus factual daily reporting is the practical middle ground.

A defensible delay file starts with the first missed delivery, denied access condition, failed inspection, or owner directive. Capture it before the crew disperses and before the project team starts relying on memory. When the record is built in real time, the facts have a better chance of speaking for themselves.