Daily Reports for Delay Claims: How to Document So Your Records Hold Up

For general background, see what a construction daily report is.

Why daily reports matter so much in disputes

Claims are often decided months or years after the work. Memories fade and people leave. The records made at the time, especially daily reports, photos, schedules, RFIs and meeting minutes, become the story. Commentators in construction law, including the American Bar Association's construction litigation committee, have noted that routine records like daily reports often become central in litigation. Source: https://www.americanbar.org/groups/litigation/resources/newsletters/construction/spot-litigation-issues-in-reporting-construction-records/

Under the U.S. Federal Rules of Evidence, records of regularly conducted activity made at or near the time can be admitted as an exception to hearsay if conditions are met (Rule 803(6), https://www.law.cornell.edu/rules/fre/rule_803). That is one reason "same day, every day" matters.

What to record for a potential delay

Record the delay every day it continues

This is the most common gap. A delay noted on day one and never again looks like a short event. Use a running count:

"RFI 112, day 6. C4 bay steel still on hold. Ironclad working D-line; D-line work runs out Thursday. If unanswered by Thursday, Ironclad crew will be idle or demobilize."

Record good days and the baseline

Claims reviewers look for selectivity. If you only record weather on rainy days, or manpower only when it is short, the record looks built for a claim. Record weather, manpower and work performed every day.

Planned vs. actual

Delays show up as the gap between plan and actual. Writing "Installed 120 LF of 180 LF planned due to duct conflict at corridor, third day of condition" ties lost productivity to a cause, which is the hard part of any loss of productivity claim.

Notice: daily reports support, they do not replace

Most contracts require written notice of delay or claim within a set number of days. Your daily report should record that notice was given, how, and to whom, but the notice itself must follow the contract. Check the notice clause before you need it.

Write facts and leave out arguments

Argumentative language invites cross-examination and can make the whole report look biased.

Do not edit old reports

Once submitted, a report should not be rewritten. If a correction is needed, issue a dated revision explaining the change and keep the original. A report changed after the fact can damage the credibility of every other report.

Tie the records together

A strong delay record connects:

• Daily reports with running counts
• Dated, located photos (see photo documentation)
• RFI and submittal logs
• Schedule updates showing the affected activities
• Meeting minutes
• Formal notices
• Weather records (see weather delay documentation)

Checklist

• Report written the same day
• Cause, affected work, crews and times recorded
• Running day count for ongoing delays
• Notice recorded with date and method
• Planned vs. actual noted
• Photos attached
• Factual language only
• No edits after submission without a revision

What reviewers look for in daily reports

People who review daily reports in a dispute, such as scheduling consultants, attorneys and arbitrators, tend to ask the same questions:

• Were reports done every day? Gaps raise questions.
• Do they match other records? Manpower in the report should line up with payroll, T&M tags and sign-in sheets.
• Do they show the delay as it happened? Running counts and same-day notes show the delay was real at the time.
• Is the cause clear? "Waiting on RFI 112" is a cause; "slow day" is not.
• Were they changed later? Revision history matters.

Building reports with these questions in mind costs nothing extra on a normal day and saves a lot on the rare day you need them.

A complete, timestamped record without extra work

Cascade is SMS-first field intelligence for general contractors and subcontractors: superintendents and foremen text in their day, along with their subs, and Cascade builds a sealed daily report from those timestamped messages and photos. Ask "show me every day RFI 112 was mentioned" and get a plain-English answer. Product scope: Daily reports, manpower and hours by sub, photos, toolbox talks, pre-task plans (JHA), safety incidents and corrective actions, project + schedule planning, automatic sub reminders, analytics and plain-English answers.

Subcontractor access is free, and general contractors see 95%+ sub daily report compliance, so the record has fewer gaps. See why Cascade. Free onboarding and integration, a one-month pilot on the general contractor plan with no contract lock-in, and a price below Raken, Procore and ACC, guaranteed.

Request Access