Construction attorneys talk about daily logs the same way they talk about seatbelts: everyone knows they're important, but most contractors wait until after the accident to wish they had better ones. The daily log is the single most defensible document in a construction dispute — and most GC teams are producing logs that would fail the basic legal test of admissibility or credibility under pressure.
This article is about what makes a daily log legally defensible, what the common failure modes are, and how to fix them before you're in a dispute rather than during one.
What a Daily Log Is Actually For
The primary business purpose of a daily log is to document what happened on the project each day — who was on site, what work was performed, and what conditions affected production. Most GC teams understand this at a basic level.
The legal purpose of a daily log is to create a contemporaneous record: documentation created at the time events occurred, not reconstructed after the fact. This matters in three specific dispute scenarios that are common in commercial construction:
- Schedule delay claims. When an owner claims the GC is responsible for a delay and the GC needs to demonstrate that the delay was caused by an RFI response backlog, an owner-directed change, a weather event, or a subcontractor who didn't perform — the daily log is the primary evidence. If the log has gaps for the days in question, or if the logs were clearly written on Friday from memory rather than captured daily, the record is compromised.
- Extra work claims. When a GC submits a change order for additional work directed in the field and the owner disputes that the direction was ever given — daily logs documenting the direction, who gave it, and what work was done in response are often the difference between a paid claim and a dispute that goes to mediation.
- Damage claims from subcontractors. When a sub claims they were delayed or disrupted by the GC's schedule management and suffered productivity losses — the GC's daily logs showing actual site conditions, crew counts on each trade, and work-in-place by day are the baseline for evaluating whether the sub's claim is supported by the site record.
The Six Most Common Daily Log Failures
1. Logs submitted in batches (the Friday afternoon problem)
A daily log submitted 4 days after the events it describes is not a contemporaneous record. In a dispute, the other side will establish when the log was submitted — and if logs for Monday through Thursday all show a Friday submission timestamp, the reliability of every record from that project comes into question. The argument is simple: if the superintendent was filling in four days of logs from memory on Friday, what else was reconstructed after the fact?
Daily logs must be submitted each day, before the end of the shift, to have evidentiary value as contemporaneous records.
2. Generic work descriptions
"Concrete work on Level 3" is not a useful daily log entry. "Poured Level 3 slab, grid lines A through J, 80 CY placed, crew of 12, completed by 3 PM" is a useful entry. The specificity matters because it demonstrates the record reflects what actually happened that day — not a placeholder description that could have been written at any time.
3. Missing crew counts by trade
Crew count by trade is one of the most useful pieces of data in a schedule delay dispute. If you're claiming a subcontractor was undermanned and caused a delay, your daily logs need to document their crew count each day. "Mechanical sub on site" is insufficient. "Mechanical sub — 3 journeymen, 1 apprentice" is a record you can use.
4. Weather documented as a code rather than a description
Weather logs that use codes ("Rain — partial day stoppage") have less credibility than logs with specific descriptions ("Rain began at 10 AM, temperature 38°F, wind 18 mph; concrete placement suspended at 10:15 AM per spec section 033000 cold-weather requirements; crew demobilized at 11 AM"). If a weather-related delay claim goes to dispute, the NOAA historical weather data for that date will be pulled. Your description needs to be consistent with it and specific enough to show it was a real-time observation.
5. Delays documented without cause
"Work delayed today" without identifying the cause gives you no documentation to support a change order or time extension request. The log should identify the cause: "Level 5 mechanical rough-in delayed — RFI #47 on high-bay HVAC routing still open, awaiting EOR response. Mechanical crew redirected to Level 4 rough-in pending resolution."
6. No documentation of owner or architect direction given in the field
When the owner's rep or architect walks the site and gives direction verbally, that direction is typically worth a change order. If your daily log doesn't capture what was said, by whom, and when — and what work was done in response — you have no documentation for the extra work claim. "OAC representative on site, directed additional waterproofing at Level 2 mechanical room floor drain area, verbal direction from [architect name], 2 PM site walk" is a claim. "Architect visited site" is not.
What a Defensible Daily Log Contains
A daily log that will hold up in a dispute contains, at minimum:
- Submission date and time (must be same day as events described)
- Weather: temperature range, conditions, precipitation, any work stoppages caused
- Crew count by trade — GC direct labor and each sub on site, with crew composition where relevant
- Work performed: specific, with location references (floor, grid, area)
- Materials delivered: product, quantity, vendor
- RFIs submitted or received, by number and subject
- Owner, architect, or third-party site visits with name and any direction given
- Delays: cause documented, duration, crew affected, what work was done instead
- Equipment on site (any changes from prior day)
- Safety incidents (any)
The log doesn't need to be lengthy — a well-structured daily log for a typical productive day is 8–12 lines. What it needs is specificity and same-day submission.
The Superintendent's Resistance to Same-Day Submission
The practical barrier to good daily logs is usually behavioral, not technical. Superintendents are focused on running the site. Daily logs feel like administrative overhead, and in the heat of the day, they often get deprioritized until Friday.
The most effective change we've observed across GC teams that shifted from batch to daily submission: reduce the friction of submission to under 5 minutes. A structured form on a phone — where the fields prompt for crew count, work performed, weather, and delays — takes less time to complete in the field than to reconstruct from memory on Friday. Superintendents who use a structured mobile form consistently submit same-day. Superintendents who are expected to open a laptop and fill out a Word template on Friday are the source of the Friday batch problem.