A construction daily log is the day-by-day record of what happened on a jobsite — who was there, what they did, the weather, deliveries, and any delays or problems — and it's the single most valuable document you have when a project ends up in a dispute. The thing that makes a daily log hold up isn't a fancy template; it's that it was written that day, captures the right facts, and records delays as concrete events rather than a vague note. This guide covers what a dispute-grade daily log actually needs.
Why the daily log is worth more than it looks
Most of the documents on a job exist to move work forward — RFIs get answers, submittals get approvals, change orders get signed. The daily log is different: it mostly sits there, day after day, until the moment something goes wrong. Then it becomes the most important paper on the project.
When there's an argument months later — who caused a delay, whether a site condition was as represented, whether a sub was even on site when they said they were, how long an owner-caused interference actually lasted — the contemporaneous daily log is the evidence everyone reaches for. Courts and arbitrators give real weight to records made at the time, in the ordinary course of business. A log written that day, consistently, is credible. A log reconstructed after the dispute starts is worth a fraction of it, and an absent log can leave you with no record of your side of the story at all.
For a small contractor, that's the whole value proposition: a few minutes a day of disciplined logging is cheap insurance against a delay claim or a payment dispute that can cost a job's entire margin.
What to capture every day
A daily log doesn't need to be long, but it needs to be complete on the facts that matter. At a minimum, capture:
- The basics — project name, date, and who prepared the log.
- Weather — general conditions, temperature, and precipitation. Weather is the most common documented cause of delay, and a contemporaneous weather note is hard to argue with later.
- Manpower on site — which crews and subcontractors were present and roughly how many workers and hours. This is your proof of who was (and wasn't) working.
- Work performed — what was actually accomplished, by area or by trade. Specific beats vague: "set forms and poured footings, grid lines A–D" is evidence; "concrete work" is not.
- Equipment — major equipment on site and in use.
- Deliveries — what materials arrived (and what didn't show up that was supposed to).
- Visitors and inspections — the building official, the owner's rep, the architect, an OSHA compliance officer, a third-party inspector.
- Delays, interferences, and problems — and this is the part that wins disputes.
The part that wins disputes: logging delays
A generic daily report treats a delay as a one-line note — "rain, lost half a day." A dispute-grade log treats each delay as a structured event you can later prove and price. When you record a delay, capture:
- What kind of delay it was — weather, an owner decision pending, a missing answer to an RFI, a late submittal approval, a differing site condition, a utility conflict, a sub no-show, a materials shortage.
- What it affected — which activity or area stopped or slowed.
- How long it lasted — hours or the portion of the day lost, not just "delayed."
- Who or what caused it — and whether you gave notice.
- Photos — a few date-stamped photos of the condition are worth pages of description.
The reason this matters: delay claims live or die on contemporaneous, specific documentation. If you can show, from logs written each day, that an owner-caused interference idled a specific crew for a specific number of hours across specific dates, you have a claim. If all you have is a memory and a calendar, you have an argument you'll probably lose. The same record also feeds your time-extension requests on change orders — the delay you logged today is the schedule impact you justify tomorrow.
What makes a log "dispute-grade"
Three things separate a record that holds up from one that doesn't:
1. It's contemporaneous. Written the same day, every day, not batched at the end of the week or reconstructed when a dispute appears. Consistency is itself evidence — a log with gaps invites the question of what else wasn't recorded. 2. It's specific and factual. Names, areas, trades, hours, quantities. It records what happened, not opinions about whose fault it was. ("RFI 042 still unanswered; framing on the north wall held" is stronger than "architect is holding us up again.") 3. It's complete and consistent in form. The same fields filled in every day, so a reader — a judge, an arbitrator, an owner's attorney — can trust that an empty "delays" field means there were none, not that nobody bothered to ask.
Where paper and spreadsheets fall short
The honest problem with daily logs isn't knowing what to capture — it's the discipline of capturing it every single day, from the field, in a form that survives. Paper logs get lost, coffee-stained, or filled out from memory on Friday. Spreadsheets live on one person's laptop and rarely have the photos attached to the day they belong to. And neither makes it easy to find "every weather delay in March affecting the slab" two years later when you need it.
A good daily-log system pushes the foreman to log from the field while the day is fresh, attaches photos to the entry, and stores delays as structured records you can search and pull — so the contemporaneous record actually exists when you need it, instead of being something you wish you'd kept.
> Free tool: Fill in and print a complete log with the free construction daily log template — no sign-up, nothing uploaded.
A cleaner way to keep the record
The daily log only protects you if it actually gets written, every day, with the right detail. Jobsite lets crews file the day's work, weather, manpower, deliveries, and delays from the field with photos attached — and captures delays as structured, dispute-grade records rather than a buried note, with a nudge so the habit doesn't slip. See how Jobsite handles daily logs →
FAQ
What should a construction daily log include?
At a minimum: the date and who prepared it, weather (conditions, temperature, precipitation), manpower on site by crew and sub, the specific work performed by area or trade, major equipment, deliveries, any visitors or inspections, and — most importantly — any delays, interferences, or problems, with enough detail to prove them later. Photos attached to the day strengthen all of it.
Why are daily logs important in a construction dispute?
Because they're a contemporaneous record — made at the time, in the ordinary course of business — which carries real evidentiary weight. When there's a later argument about delays, site conditions, or who was on site when, a consistent daily log is the proof. A log reconstructed after a dispute begins is far less persuasive, and no log at all can leave you unable to support your side.
How do I document a delay so it holds up?
Treat each delay as a structured event: record what kind of delay it was, what activity it affected, how long it lasted (in hours or the portion of the day), what caused it, whether you gave notice, and attach date-stamped photos. Specific, contemporaneous delay records are what support a delay claim or a time-extension request; a vague "lost time to weather" note usually isn't enough.
Is a daily report the same as a daily log?
The terms are used interchangeably on most jobs — both refer to the day-by-day record of site activity. Some teams use "daily report" for a summary sent to the owner and "daily log" for the contractor's internal record, but the content is the same. What matters is that it's captured every day and complete on the facts that matter.
Do small contractors really need daily logs?
Yes — arguably more than large GCs, because a small contractor has less margin to absorb a delay claim or payment dispute that goes the wrong way. A few minutes a day of disciplined logging is inexpensive protection, and it also feeds your change-order time extensions and gives you an honest record of how each job actually ran.
See how Jobsite handles this in practice: Project management on the platform →
About the author
The Jobsite Editorial Team — Construction safety & OSHA compliance
The Jobsite Editorial Team writes the safety and compliance library behind Jobsite, the construction safety, OSHA compliance, and training platform for contractors. Every article starts from the primary regulatory text — the CFR section itself, not a summary of it — and is fact-checked against that source before it publishes, so what you read here is what the standard actually requires of small and mid-size contractors in the field.