How to Write a Construction Daily Log That Holds Up in a Dispute

Nobody starts a job planning for a dispute. But when one lands — a client claims the work wasn't done, wasn't done on time, or wasn't done right — the contractor with the better records wins. And the record that decides it is almost always the daily log.

A daily log scribbled on the back of a delivery slip won't carry much weight. A log written the same day, with photos, weather, and crew counts, is hard to argue with. Here's how to keep one that actually protects you.

Write it the same day, every day

The single biggest factor in whether a log holds up is when it was written. A log entry made on the day of the work is treated as a contemporaneous record. Notes reconstructed three weeks later from memory and text messages are treated as a story. Two minutes at the end of the day beats two hours of reconstruction later.

Record facts, not opinions

Write what happened, not how you feel about it. "Poured 12 m³ of concrete for footings, north wall. Client's architect visited at 10:00 and approved rebar placement." That's evidence. "Client is being difficult again" is not — and it can be read back to you in the worst possible light.

The six things every entry needs

• Date, project, and who wrote the entry
• Weather — it explains delays and justifies schedule changes
• Crew on site: how many people, doing what
• Work performed, with quantities where possible
• Deliveries, inspections, and visitors
• Problems, delays, and verbal instructions from the client — written down the day they happen

Photos turn a log into proof

A photo with a timestamp answers questions no written note can: what was actually built, what condition the site was in, what was covered up the next day. Photograph work before it gets buried — footings before backfill, pipe before drywall, waterproofing before tile. Those are the photos you'll wish you had.

Tie the log to the money

The log becomes truly powerful when it connects to your invoicing. If every invoice line traces back to logged days — with photos and crew — then a payment dispute stops being your word against theirs. The question "what am I paying for?" has a documented answer.

That's the workflow Temel is built around: log your day from the field in about two minutes, then generate the invoice straight from the logged work. The paper trail builds itself, one day at a time.