How to keep a site diary that is actually worth something later
Two minutes at the gate, not an hour on Sunday. What to write, in the order that actually protects you, with a worked example.
Most advice on site diaries is written for a project engineer on a commercial job with a document controller and a template that runs to four pages. If you are a builder running three or four residential jobs off your phone, that advice is useless to you. This is the version for that.
The whole thing takes two minutes a day if you do it at the right moment. It takes an hour a week if you do it wrong.
Do it at the gate, not at the kitchen table
The single decision that determines whether your diary is any good is when you write it.
Written on site before you leave: accurate, specific, and it carries weight later. Written on Sunday night from memory and a camera roll: vague, hedged, and it reads like a reconstruction, because it is one. Anyone assessing it later can tell the difference immediately, and so can you when you go back to it.
So the habit is: last thing before you get in the ute. Not later.
Write for a stranger in two years
You are not writing for yourself tonight. You are writing for whoever reads this when something has gone wrong, which might be your own lawyer, an insurer, an adjudicator on a payment claim, or you in two years with no memory of the job at all.
That means:
- Name people and companies, not roles. "Dave" is useless. "Dave Mercer, Mercer Plumbing" is a record.
- Name the location on the job. "Leak" is useless. "Water pooling at the base of the retaining wall, north boundary" is a record.
- Give quantities and times. "Concrete late" is useless. "Concrete truck booked 7:00am, arrived 11:20am, four hours lost, two crew stood down" is a record.
You are not writing a report. You are writing the thing that stops an argument.
What to write, in priority order
If you only had thirty seconds, this is the order that protects you.
1. Delays, and what caused them. The highest-value line in any site diary. Time lost is money, and time lost is the thing you will be asked to justify. Write what stopped you, why, and how long.
2. Instructions and variations, especially verbal ones. Anything anyone told you to do differently. Who said it, how they said it, and what they said. Verbal directions on site are the ones that turn into disputes, precisely because there is no record. Your diary is the record.
3. Who was on site and for how long. By person. This is what you check invoices against.
4. Work completed. Specific enough that someone could tell what stage the job was at.
5. Deliveries and visitors. Quick, and they settle supplier arguments.
6. Safety. Toolbox talk, incidents or near misses, anyone newly inducted.
A worked example
Here is a real-shaped entry for a bad day, which is the kind that matters.
Tuesday 17 March. Overcast, showers from about 1pm.
On site: Me 7:00–15:30. Dave Mercer, Mercer Plumbing, 7:15–14:00, 6.75hrs. Two carpenters (Josh, Aaron) 7:00–15:30.
Completed: Second fix rough-in continued, kitchen and ensuite. Wall framing to the rear extension complete and braced.
Deliveries: Plasterboard from Hutchins, 9:40am, 40 sheets, stacked in garage. Two sheets damaged on delivery, noted with driver, photo taken.
Delays: Rain from 1pm stopped external work. Roof battens deferred. Approximately 2.5 hours lost, carpenters moved to internal framing.
Instructions: Client (Sarah Whitlam) attended site ~10am, asked to move the ensuite door opening approximately 300mm toward the hallway. Verbal, on site. Told her it affects the framing already up and would need pricing. Not actioned. Photo of current framing taken.
Safety: Toolbox talk held 7:00am on wet-weather access and slip hazards, all four attended. No incidents.
Photos: 6. Plasterboard damage (2), rear framing (2), ensuite framing before any change (2).
Read the instructions line again. That one paragraph, written on the day, is worth more than anything you will say about it eighteen months later. It records what was asked, that you flagged the consequence, that you did not action it, and that you photographed the state of the work before anything changed.
That is what a site diary is for.
Photograph anything about to be covered
Waterproofing before tiling. Rough-in before plasterboard. Reinforcement before the pour. Services before backfill.
The rule: if you will not be able to see it next week, photograph it today, and get the photo into the job record rather than into a group chat. This costs you nothing at the time and is the difference between a five-minute conversation and a destructive inspection.
Never leave a gap
An empty day is a problem. If nobody was on site, write "no work on site, rain" and move on. A diary with holes in it invites the question of what else was not recorded, and it undermines the entries that are there.
Same rule for bad days. Write down the mistake, the damage, the argument. A diary that only ever contains good news is not a record, and it will be read as one that was curated.
Doing it without paper
Paper diaries work fine right up until the folder is at one job and you are at another, which for most small builders is most of the time.
Foreman's site diary is the same habit on your phone: pick the job, pick who was on, log hours, write what happened, attach the photos. It also stamps each entry with when it was submitted and whether you were on site at the time, which is the difference between a record and a recollection. Every entry is dated and attached to the right project, and the whole project's diary exports as a CSV when a client, a head contractor or your bookkeeper asks for it.
If you would rather start on paper, take the free site diary template and use the headings above.
For the legal side of this, read is a site diary legally required in Australia.