Site Pal
← All guides

How to write a site diary entry

Part of our complete guide: What Does a Good Site Diary Look Like?

Months after handover, nobody remembers what happened on a wet Tuesday in March. But if there's a claim on the table, that Tuesday might be worth thousands. The site diary is the document that remembers — and in most disputes, the winner isn't whoever was right. It's whoever can prove what happened.

Here's how to write entries that do their job.

Record facts, not opinions

The golden rule. "Groundworks gang stood down 8am–1pm, access road flooded" is evidence. "Another shambles with the groundworkers" is an opinion — and worse than useless if a diary ever gets read out in adjudication. Write what you saw, when, and who was involved. Leave the blame for the delay record.

What every entry should cover

A solid daily entry answers six questions:

  • Weather — morning and afternoon conditions and how they affected work, not just "rain"
  • Labour and plant — who was on site, how many, doing what, and anything stood idle
  • Progress — what actually got done, against what was planned
  • Deliveries and materials — what arrived, what didn't, any shortages
  • Instructions and information — drawings received, verbal instructions, RFIs answered or still outstanding
  • Events — access restrictions, stoppages, visitors, incidents, anything out of the ordinary

Miss the boring days and you weaken the good ones. A diary with gaps invites the question: what else wasn't written down?

Same day, every day

An entry written Friday about Monday is a memory, not a record. Consistency is what gives a diary weight — short and same-day beats detailed and reconstructed. Ten honest minutes at the end of each shift is enough.

And put a name on it. An entry signed off by the person who was actually there carries far more weight than an anonymous log — it says someone stands behind this record.

Photos turn a diary into evidence

A written line says work was done. A photo with a GPS location and timestamp shows it — where, when, and what state it was in. When entries carry tagged photos, arguments about "when was that actually taken" end before they start.

The lazy entry costs you later

"All ok on site" is the most expensive sentence in construction. It records nothing, proves nothing, and when a delay claim lands six months later, it leaves you arguing from memory against someone with better records.

Let the diary write itself

This is exactly what Site Pal was built for. Walk the site, take photos, talk — the AI turns it into a structured diary entry, every photo automatically GPS-tagged and timestamped, ready to export as a professional PDF report. The record gets done in minutes, on the day, every day.

Site Pal site diary PDF report