Documentation and Daily Logs

The daily log is the project’s contemporaneous record: what happened on site today, written today, by the person who watched it happen. Years later, when a dispute turns on what occurred the third week of March, the daily log is the closest thing to a time machine either side will have, and courts and arbitrators treat records made at the time as far more credible than anyone’s memory. That is the discipline’s real name: the daily log is the litigation shield.

Why it matters on the job

Construction disputes are contests of proof. Delay claims, backcharges, differing site conditions, payment fights: each one reduces to whose account of past events is believed. The contractor with a complete, boring, consistent daily log usually wins that contest before it starts, because the other side’s lawyer reads a year of logs and advises settling. The shield works in both directions, though: logs also prove what you knew and when you knew it, which is why the habit must be honest, factual and unbroken, not curated.

What goes in, every day

A useful log entry is structured and fast, fifteen minutes at the end of the shift:

• Date, weather and site conditions. Temperature, precipitation, wind, and what the weather actually did to the work: “rain 0700 to 1100, slab pour postponed.” Weather claims live or die on this line.
• Manpower, by contractor. Each sub on site with headcount: “framing 9, plumbing 3, electrical 4.” The single most powerful line in a delay dispute: a sub’s claim of full staffing collapses against ninety logs showing three workers.
• Work performed, by area. What was built today and where, specific enough to reconstruct progress: “hung drywall level 2 east, corridor 2A complete.”
• Delays, disruptions and idle time. What stopped or slowed work, when, and why, with who was affected. Written the day it happened, this is claim evidence; written at closeout, it is storytelling.
• Deliveries, inspections, visitors and instructions. Materials received, inspections passed or failed, who came to site, and any direction received from the owner or architect, quoted, with the name attached. A verbal instruction recorded same-day in the log is the anchor for the confirming email and the change order that follow.
• Incidents and safety items. Accidents, near misses, corrective actions.

Photographs multiply the log’s power: date-stamped, tied to the entry, especially at cover-up points and wherever conditions are about to change.

The rules that make it a shield

Contemporaneous: written the same day, never reconstructed on Friday for the week. Factual: what happened, not who is a problem: “electrical crew of 2 on site, 6 scheduled” rather than an opinion about the electrician. Opinions in logs get read aloud in depositions. Unbroken: an entry every working day, including the uneventful ones, because gaps swallow credibility, and the log that exists only on bad days looks manufactured. Unaltered: corrections are made as new dated entries, never by editing history; an edited log is worse than no log.

Worked example: the log that paid

An owner deducts $21,000 in liquidated damages for 14 days of late completion. Your logs show, day by day: owner’s flooring selection outstanding for 9 working days past the date required by the submittal schedule, with the areas idled and the crews affected named, plus 2 days of documented postponements from measured rain. Notice letters, sent at the time, reference the same dates. The claim resolves as an 11-day excusable extension, cutting the deduction to $4,500, and it was won in March, in fifteen minutes a day, not in the December negotiation.

Fifteen honest minutes a day: the four lines that decide disputes years later

Where it bites

• Logs written from memory at week’s end. Reconstructed entries carry wrong dates and merged days, and a single provable error infects the credibility of every other page.
• Editorializing. “Plumber lazy again” helps the other side twice: it proves animus and it replaces a fact with an opinion. Record counts, times and events.
• Stopping when things are calm. The boring months are what make the eventful entries believable. An unbroken log is the whole point.
• One log per company, uncoordinated. If your superintendent’s log contradicts your own notice letters, the other side will find it. One system, one habit, consistent fields, every project.