Site diary template

A site diary is worth something in a dispute only if it was written on the day it describes. That is the entire difference between a diary and a reconstruction, and every decision in the format below follows from it.

A diary is not a progress report. A progress report is written for the client and argues that things are going well. A diary is written for whoever opens it two years from now, and it argues nothing at all.

A rough note made that day outranks a polished one made later

Someone rebuilding a week from a camera roll and memory produces a document that reads more fluently and proves considerably less. The authority comes from the timing, and no amount of editing adds it afterwards.

Three rules follow, and they are the ones people break.

Entries are dated the day they describe and written that day. Nothing is back-edited: if you got something wrong on Tuesday, the correction is a new entry on Thursday saying what it corrects and why. And a day with nobody on site is still an entry. "No site attendance, site closed for the public holiday" is a record. A blank space is a question.

Eight header fields, then get into the entries

Weather is not small talk, and it is the field most people fill in with one word. "Rain" covers a ten minute shower and a day that sent everyone home. The times are what turn the line into evidence, so write the times.

Headcount is a count. Resist writing "a good turnout from the groundworkers" when the number is six.

Write what you saw, and attribute everything else

"Steel delivery was late because the haulier messed up" holds one fact and one guess, and the guess is the half that gets attacked. The same day, written properly:

Steel delivery scheduled 08:00, arrived 13:20. Driver stated the vehicle had been held at the depot overnight. Four erectors stood down 08:00 to 13:20.

You saw the arrival time. You did not see the depot. The word "stated" is doing the work there, and it costs you one word.

The test for any sentence in a diary: could you be asked about this under oath and stand behind every word of it? Anything you worked out rather than witnessed either gets its own sentence saying so, or it does not go in.

The entries that get read are about somebody being told something

Most diary entries are never opened again. The ones that are opened are almost always about an instruction, and they are the ones worth slowing down for.

Four kinds to write carefully. An instruction given on site: who gave it, who received it, what was asked, and the time. A disagreement: what each side said, in their own words, not smoothed into a consensus that did not happen. Something that stopped work: the time it stopped, the time it resumed, and how many people were standing. And anything you were asked to accept. "Asked by the site manager to accept the blockwork at grid C4 as built" is the entry that matters when the crack appears in March.

Number these within the day. Entry 3 on September 8 is a thing you can point at in a letter.

A filled day, from a project that does not exist

Date: Tuesday, September 8, 2026. Project: Harbour Lane Block B, contract 2024-118. Author: R. Okonjo, site engineer. On site 07:15 to 16:40. Weather dry to 11:00, heavy rain 11:00 to 15:00, 12C. Crews: groundworks 6, steel erectors 4, electrical 2.

Entry 7 is the one that will be read. Notice that it records a refusal rather than an outcome, which is what actually happened at 15:30. Whether the blockwork is eventually accepted is a different day's entry.

Entries 1, 4 and 6 are the delay record. Between them they say that four people stood for five hours and that the groundworks stoppage was weather, not sequencing. Neither of those claims is arguable from this page, which is the point.

Keep three things out of it

Opinions about people. "The electrical foreman is useless" helps nobody and damages the document, because a diary with one insult in it invites the argument that the rest is also coloured.

Conclusions about liability. That is not your call, and writing "this is clearly the contractor's cost" in a diary hands the other side a sentence to read aloud. Record the facts that support the conclusion and let somebody else draw it.

Anything you did not see. Second-hand reports go in attributed ("the foreman reported that") or they stay out.

Sign it the day you wrote it, then leave it alone

The signature and the date are what make the entry contemporaneous rather than undated. Whoever kept the diary signs their own entries. A countersignature from the site manager is useful on the instruction entries and unnecessary elsewhere.

Then stop touching it. The temptation to tidy up last week's phrasing is strong and it ruins the document, because an edited file with no edit history is a file somebody can argue was written at any time. If you keep the diary digitally, keep it somewhere that records when each entry was created.

Sitewise covers the capture half of this on iPhone and iPad. Photograph the standing water and the blockwork, dictate the entry instead of typing it with wet hands (the voice note transcribes on the device), and sketch on the photo when the defect is hard to point at. Every capture carries a timestamp and, with location on, a GPS pin, which is what makes the entry hard to argue with later. It works with no signal and syncs once you are back in range, so the haul road entry gets written at 11:05 rather than at 18:00. The day exports as a PDF or DOCX. It does not manage schedules, budgets or e-signatures, and the diary's legal status is a matter for your contract, not for an app.

For the client-facing summary that sits alongside the diary, the daily construction report template covers the manpower and delay format. If your site diary is really a record of visits rather than a continuous presence, how to write a site visit report is the closer fit.

The diaries that turn out to be worth keeping are almost never the well-written ones. They are the ones where somebody wrote down the time.