Set up your daily logs before spring, not after the first dispute

There is a particular kind of meeting that happens in August. Somebody claims you were three weeks late. Somebody else says the ground was never like that. A quantity is short and nobody can say which day it went in. And everyone around the table turns to the contractor, who is now trying to reconstruct May out of text messages, a few photos with no captions, and a foreman's honest best guess.

You will lose that meeting. Not because you are wrong — usually you are right — but because the other side has documents and you have a recollection. In a dispute, a contemporaneous record beats a confident person every single time, and that is not a quirk of construction. It is how every arbitrator, engineer and judge weighs evidence.

The frustrating part is that the fix costs about four minutes a day per crew. The reason it does not get done is never the four minutes. It is that nobody ever sat down in the off-season and decided exactly what goes in the box.

Why the log you already keep probably does not help

Most contractors are keeping something. A notebook in the truck, a group chat, a daily text to the office. It feels like a record. It almost never functions as one, for three reasons:

• It records activity, not conditions. “Ran pipe on Maple St” proves nothing about anything. What settles claims is the surrounding facts: who was there, what equipment, what the weather did, what you were told, and what stopped you.
• It is not dated in a way anyone believes. A notebook written up on Friday for the whole week is not a contemporaneous record, and the other side's attorney will say so. The value of a daily log is entirely in being daily.
• It has gaps exactly where it matters. People log the ordinary days and stop logging during the chaotic ones — which are the only days anyone ever asks about. A log with holes on the disputed dates is worse than no log, because it invites the question of what you chose not to write.

The eight fields that make a log worth having

This is not a form to admire. It is the shortest set of fields we have found that will still answer the questions that actually get asked a year later.

• Date, and the weather with numbers. Temperature, precipitation, ground condition. “Rain” is an opinion; “0.7 in. overnight, subgrade saturated, no work in the trench until 11:00” is evidence. Weather claims live or die on this line and it is the one most often left blank.
• Who was on site, by name and by hours. Your crew, your subs, the inspector, the owner's rep, anyone who showed up. Headcount with hours is what converts a delay into a dollar figure later.
• Equipment on site, and what sat idle. Idle equipment is a cost you can only recover if you wrote down that it was idle and why.
• Work performed, by contract item, with quantities and locations. This is the line that doubles as your quantity register: item number, quantity, station or address. Written daily, it is the “more accurate data” that beats a disputed pay-estimate count.
• Anything that stopped or slowed the work, and who caused it. Late material, an unmarked utility, a missing answer to an RFI, an owner-directed change in sequence, differing soil. Name the cause plainly and without heat.
• Instructions received verbally, and from whom. Most expensive disputes start as a conversation on a tailgate that nobody wrote down. One line here — who said what, when — is often the whole case.
• Deliveries and tests, with ticket numbers. Tickets go missing. Numbers in the log survive.
• Photos, tied to the day. Not a camera roll. A handful of frames per day that are findable by date and location, with a caption. An uncaptioned photo of a trench, two years later, proves that at some point there was a trench.

Eight fields. The crew answers it in four minutes because nothing on it requires a decision — it is the same eight things every day.

The two rules that keep it admissible

First: it gets filed the same day, every day, including the days nothing happened. Days with nothing on them matter, because a run of thin days is what proves the site was shut and what makes the busy days credible. A log that only exists on interesting days looks assembled, and anything that looks assembled gets discounted.

Second: never edit yesterday. If a number was wrong, add a correction to today's entry and say what it corrects. A log that can be silently rewritten is a log with no evidentiary weight, and that is the single biggest advantage a dated, append-only system has over a notebook: nobody has to take your word for when it was written.

Getting a crew to actually do it

Everything above is the easy half. The hard half is that a foreman at 4:45pm, covered in mud, is not going to fill out a form with twenty-two fields on a phone.

What has worked for us, in order of how much it mattered:

• Keep it to one screen. If it scrolls, it does not get finished. Everything optional comes off the form, no matter how much the office wants it.
• Pre-fill everything you already know. Date, job, crew, equipment, yesterday's weather, the contract items that are currently open. The foreman should be confirming and amending, not typing from scratch. This is the single biggest difference between a log that gets filed and one that does not.
• Make it work with no signal. Half the jobs we work have no usable data. If the form needs a connection it will be abandoned in a ditch in week two. It has to save locally and sync when the truck gets to pavement.
• Make somebody notice when it is missing. A log nobody checks stops existing within a month. One list, every morning, of which crews filed yesterday and which did not — and somebody whose actual job it is to look at that list.
• Tell them why, once, with a specific job. “The office wants it” buys you about two weeks of compliance. Naming an actual week on an actual job where the record was the reason a claim went your way buys you the season. Crews are not indifferent to the company getting paid; they are indifferent to paperwork with no visible purpose.

Why the off-season is the only time to do this

In March you can decide the eight fields, build the form, run it past the two foremen who will tell you honestly that it is too long, cut it down, and have it boring and habitual by the time real work starts. Every one of those steps is free in March.

In July, the same project competes with actual production, so it gets half-built and abandoned. And in August, when the dispute lands, the window closed months ago. The evidence you needed was supposed to be created in May, by somebody who did not yet know it would matter. That is the entire point of a daily log and the entire reason it has to be set up before the season, not during it.

One honest caution: do not design this around the worst dispute you can imagine. A log built to win a lawsuit is a log nobody files. Build the one your crew will actually complete every day for seven months, because a merely adequate record that exists on every working day beats an excellent one that exists on nine of them.

See how HardHatOps handles daily logs and sign-offs →