5 Mistakes Civil Contractors Make with Delay Documentation
Most civil contractors who lose delay claims don’t lose because they were wrong about the delay. They lose because their documentation wasn’t good enough to prove it.
After working with civil teams on daily documentation, these are the five most common mistakes we see — and each one is entirely preventable.
MISTAKE 1
Documenting After the Fact
The single biggest credibility killer in a delay claim is documentation that was clearly created after the events occurred. When daily logs are written days or weeks later, the evidence shows it: batched entries, inconsistent detail levels, dates that don’t match submission timestamps.
Claims consultants and opposing counsel look for this. If your “daily” logs were submitted in batches every Friday, they’re weekly recollections, not daily records. Their weight as evidence drops significantly.
The fix: Log daily, on-site, as events happen. Use voice input if typing is impractical. A 90-second voice note recorded while walking the site is more credible than a polished paragraph written three days later at a desk.
MISTAKE 2
No Weather Records
Weather delays are the most common type of excusable delay on civil projects. Yet many contractors don’t systematically document weather conditions in their daily logs. When the claim comes, they try to reconstruct weather history from NOAA data — which shows regional conditions, not site-specific conditions.
Did it rain at the airport weather station? Maybe. Did it rain enough at your site to prevent earthwork? Only your daily log can answer that.
The fix: Record temperature, rain (yes/no), wind, and site conditions in every daily log — even on clear days. A complete weather record across the whole project is far more powerful than cherry-picked bad weather days.
MISTAKE 3
Vague Descriptions Without Impact
A log entry that says “rain delay” or “waiting on materials” documents the existence of a problem but not its impact. In a delay claim, you need both.
The question isn’t just “did it rain?” — it’s “what work was prevented, what crews were affected, and what was the schedule consequence?”
Weak: “Rain delay. No work today.”
Strong: “Heavy rain starting 6am, 1.5 inches by noon. Section C excavation flooded, pumps running but water level rising. 8-person grading crew sent home at 7:30am. Foundation pour for Building 2 postponed — was scheduled for today per Rev 3 schedule. Site access road impassable for delivery trucks.”
The fix: For every delay event, document three things: (1) what happened, (2) what work was prevented, and (3) what the schedule impact is. Be specific about crews, equipment, and planned activities that were disrupted.
MISTAKE 4
No Photos or Visual Evidence
Text descriptions are debatable. Photos are not. Yet many contractors still submit daily logs with no photos, or with photos stored separately from the log entry (in a phone camera roll, a shared drive, or an email thread).
When a claims consultant asks “show me the site conditions on March 15th,” you need GPS-tagged, timestamped photos linked directly to that day’s report — not a camera roll with 3,000 unsorted images.
The fix: Attach photos directly to the daily log entry. Use a tool that GPS-tags and timestamps photos automatically. Take photos of site conditions, progress, and any issues — even when everything looks normal. Normal conditions on non-delay days strengthen the contrast with delay days.
MISTAKE 5
Using Editable Formats
Daily logs stored in Word documents, Excel spreadsheets, or email threads can be modified at any time. There’s no audit trail, no submission timestamp, no proof that the content wasn’t changed after the fact.
Opposing counsel knows this. “How do we know this spreadsheet wasn’t updated last month?” is a question that kills credibility — and it’s unanswerable if your records are in editable formats.
The fix: Use a system that locks records after submission. BuildLog makes report content immutable once submitted — no edits, no deletions. Each report includes a submission timestamp, GPS coordinates, and a SHA-256 hash that proves the content hasn’t been modified. This is evidence integrity, and it’s the difference between records that are trusted and records that are challenged.
Fix All Five with One Tool
BuildLog gives civil contractors daily voice logging (Mistake 1), built-in weather tracking (Mistake 2), structured reports (Mistake 3), GPS-tagged photos (Mistake 4), and tamper-evident evidence integrity (Mistake 5). Most reports take under 2 minutes.
Book a DemoConclusion
None of these mistakes are about being wrong. They’re about being unable to prove you’re right. The contractor who logs daily, with weather data, specific descriptions, photos, and immutable records, has the evidence to defend their position. The contractor who doesn’t is fighting the claim with one hand tied behind their back.
Fix these five mistakes and your delay documentation goes from a liability to a weapon.