A free site diary template
Blank, in the layout SiteVector produces automatically. Deliveries through the gate, tasks and their outcomes, and a fixed list of reasons work did not proceed. Use it with a pen, a printer or a spreadsheet.
No sign up and no email address. Download it and go.
The Excel version works out turnaround and the day's figures for you, with the codes as dropdowns. The PDF is one page per day, with the codes on the back.
What a site diary should contain.
A site diary is read months after it was written, usually by somebody who was not there, and usually because something went wrong. What it needs to hold is decided by that moment rather than by the day it was written.
- The day itself
- Project, date, who recorded it, whether it was a working day, and the weather. Obvious, and the first thing missing when somebody goes looking a year later.
- Deliveries through the gate
- What arrived, from whom, when it was booked, when it arrived and when it left. Arrival against booking and the turnaround between the two are the figures that matter afterwards.
- Tasks committed, and their outcome
- What the team said they would do that day, and whether it happened. A record of only the problems is a record nobody can count anything from.
- The reason a task did not happen
- Picked from a short fixed list rather than written in a sentence. This is the part most diaries get wrong, and the part that decides whether a month of records is worth anything.
- Whether it sat on the critical path
- Marked on the task itself by whoever was there. Months later it separates the days that cost time from the days that did not.
- Notes
- Anything the fields do not cover. Alongside a reason, never instead of one.
Three things that decide whether it is any use later.
Every day, not the interesting ones
The day somebody needs is almost never the day anybody expected to need. A diary with gaps in it is close to useless whatever shape it takes, which means it has to be quick enough that keeping it every day is not a chore.
Written at the time, by the person who was there
A record made at five o'clock from memory is a different category of thing from one made as the day ran. Fill in arrival and departure times at the gate and mark tasks off as they happen.
Reasons from a list, not from your head
This is the one most diaries get wrong. A reason chosen from a short fixed list can be counted across a month and set against the month before. A sentence cannot. Three weeks of “material not ready” is a supply problem somebody can act on; three weeks of sentences is a filing cabinet. The template carries the same sixteen reasons SiteVector uses.
One limit worth knowing about a spreadsheet: anybody can change it afterwards, and nothing shows that they did. If you are keeping records against a possible claim, save each finished day as a PDF, store it somewhere read-only and keep the date it was created.
Or have it kept for you.
SiteVector records the day as it happens, in a few taps at the gate and on the plan, builds this record from those entries, then locks and seals it at the end of the day so anybody you send it to can check it has not changed since.
