The construction daily log: what to write down and why it saves you later

Free construction daily log template

Every box on the template maps to a section below, so you can read this guide once and then just fill in the sheet. The only rule that matters: write it the same day.

What a daily log is, and who ends up reading it

A daily log is a contemporaneous record. That word does a lot of work. It means the entry was made on the day, not reconstructed months later once there was a reason to remember things a particular way. A note written the same afternoon carries weight an email written eight months later never will.

Most contractors write logs assuming nobody reads them. That holds right up until the day it does not, and the list of readers is longer than it looks.

• You, when a client asks why a phase took longer than the schedule said
• The general contractor or project manager above you, building their own delay narrative
• The owner, when they want to know what they paid for during a slow week
• An insurance adjuster after a water event, a fire, or a theft on site
• A lender or draw inspector confirming progress before releasing the next payment
• A lawyer, yours or theirs, if the job ends in a claim or a lien dispute
• You again next spring, pricing a similar job and trying to remember how many days the excavation really took

That last one is underrated. A year of honest logs is the best estimating data a small contractor will ever have.

The specific moments a log saves you

Four situations come up over and over, and each turns on whether you wrote something down at the time.

The delay claim. The schedule slipped and somebody has to own it. If your logs show that the slab pour sat for six days waiting on an inspection you requested on the 3rd, that is a different conversation from you insisting the inspector was slow. Dates and requests beat adjectives every time.

The weather dispute. You lost four days to rain in March. The client remembers two. If each of those days has an entry with conditions, ground state, and a photo of standing water where the trench was meant to go, the argument ends before it starts.

The change order nobody signed. The client walked the site on a Tuesday and asked for the outlet moved, the doorway widened, and a second hose bib. Nobody wrote it up. You did the work. Six weeks later the invoice lands and the extras are a surprise. A log entry naming the date and the three requests will not turn an unsigned change into a signed one, but it moves the argument from whether it happened to what it costs.

The defect blamed on you a year on. Something fails. The question becomes who did what and in what order. If your log shows the subfloor was dry and inspected on the day the finish crew started, and photos back it, you have separated your work from whatever came after it.

What to record every day

Keep the list short enough that it gets filled in. Eight items covers almost everything that has ever mattered in a dispute.

Photos do more work than paragraphs

A photo has a timestamp, it does not need to be believed, and it survives you forgetting the details. Three photos and two sentences beat six paragraphs of careful prose. Prose invites argument about what you meant. A picture of a flooded footing does not.

What is worth photographing:

• Anything about to be covered up: rough plumbing, electrical, insulation, waterproofing, work going behind drywall or under concrete
• The site at the start and end of any day something significant changed
• Deliveries as they land, including the packing slip and any damage
• Existing conditions before you touch anything, especially on remodels
• Whatever caused a delay: standing water, blocked access, another trade in your way, a red-tagged notice
• Safety incidents and the conditions around them
• Completed phases, before the next trade starts on top

Get context in the frame, not just the detail. A close-up of a cracked joist proves a crack exists somewhere. Shoot the room first, then the close-up. And caption it in one line, because a photo with no note is a mystery in eighteen months.

Making it a two-minute habit instead of a Friday catch-up

Almost every log system fails the same way. Set up in week one, skipped on a busy Wednesday, and by Friday there are three days to reconstruct. Reconstructed logs are vague, because vague is all you can honestly remember, and vague logs are worth very little.

The fix is boring: attach it to something that already happens every day at a fixed time. The end of the shift, sitting in the truck before you pull off site, is the natural slot. Nobody has to remember a new task; they just do it before the engine starts.

1. 1Pick one person per site who files it. If everyone is responsible, nobody is.
2. 2Set a fixed trigger. In the truck at the end of the shift, before leaving the site.
3. 3Photos first, while you can still see what you shot. Then the notes.
4. 4Keep it to five lines and three photos. A short log filed daily beats a thorough log filed monthly.
5. 5Check on Monday that last week is complete. A missing day is easier to fill in after two days than after two months.

The cost is the usual objection, so do the arithmetic. Two minutes a day, five days a week, is roughly eight hours across a year. One working day, illustrative rather than measured, buys you a full record of the year.

What good looks like, and what useless looks like

The difference is specificity, not length. Both columns took the same effort to write.

Two habits separate a log that holds up from one that does not. Write in plain, neutral language, because anything you write may be read by somebody who is not on your side, and heat reads as bias. And never backdate. If you missed Tuesday and are filling it in on Thursday, say so in the entry.

Paper, phone, or software

A weatherproof notebook in the truck genuinely works, and plenty of good contractors have run on one for thirty years. Its weakness is that the photos live somewhere else, on a phone, unlabeled, and pairing them back up a year later is close to impossible.

A shared folder with one document per day per job costs nothing and fixes that. Name folders date-first, as 2026-07-27, so they sort correctly, and keep the photos beside the notes.

Job software is the third option. SiteLedger, for instance, pre-fills the date, job, weather, and the crew who clocked in, so the entry is a couple of notes and a few photos from the phone already in your hand. It is one way to do it, not the only way. The system matters far less than whether the entry gets made on the day it happened. A notebook filled in every afternoon beats the best software on earth opened once a month.

Common questions

How long should a daily log take to write?

About two minutes. Five short lines and three photos is enough for almost every day on almost every job. If it is taking fifteen minutes you are writing an essay, and the entry that takes fifteen minutes is the entry that gets skipped on a busy week.

Do I still need a log if the job is going well?

Yes, and the quiet days are the cheapest to record. A log only proves anything if it is continuous. A file with entries on the four bad days and nothing else looks like a record built for an argument, which is exactly how it will be read.

Who should write the daily log, me or the crew lead?

One named person per site, and usually the crew lead, because they were there all day. Split responsibility is how logs go missing. If you run several jobs, each site needs its own person and its own log.

What is the most commonly missed item?

Verbal instructions from the client. Requests made during a site walk feel casual at the time and look like invented extras when they hit the invoice weeks later. Write down the date, who asked, and exactly what they asked for.

Can I fill in a few days at once on Friday?

You can, but the entries will be vaguer and carry less weight than notes made on the day. If you do have to catch up, say so in the entry rather than backdating it. An honest late note is far better than a false same-day one.