A construction site diary records what happened on a particular day, where it happened and which supporting information helps explain it. For a small UK project, a consistent factual record is more useful than a long narrative written from memory at the end of the week. Agree who writes it, when it is reviewed and where the record is stored.
The template below is an editorial starting point. Adapt it to your project’s arrangements; it is not a prescribed form or a replacement for the team’s safety, inspection, instruction or notice procedures.
Decide what the diary needs to explain
Begin with the reader. A colleague reviewing the week should be able to identify the work area, activities carried out and matters requiring follow-up. Avoid entries such as “normal work continued”, which give little help when someone later asks what actually progressed.
Use clear descriptions of the location and work package. Where a drawing or query matters, record its reference and link to the controlled document rather than attaching an unidentified screenshot. The diary should help someone find the relevant information.
A practical daily entry template
| Field | Useful detail |
|---|---|
| Date and author | Day covered, author and review status |
| Work areas | Location and activities observed |
| Resources | Relevant teams, plant or deliveries |
| Conditions | Observed conditions and any recorded effect on work |
| Information | Drawing revisions, queries and records referred to |
| Follow-up | Issue, agreed owner and next review point |
Choose a manageable level of detail. If another project record already holds a delivery inspection or a test result, reference it instead of copying incomplete information into the diary. Decide who can access the linked material.
Write observations separately from explanations
Consider this fictional example: “The delivery reached the gate at 10:40; unloading began at 11:05. Delivery note DN-014 is linked.” That is clearer than “supplier caused a major delay”. If the effect on a task needs investigation, identify it as an issue to review rather than presenting an unsupported conclusion.
Record when information came from someone else. Distinguish what you observed from what a colleague reported. If an entry needs correction, use the agreed correction process and keep the change understandable; do not quietly replace an earlier account with a different story.
Make photographs retrievable
Give a photograph enough context to be useful: location, date, what it shows and the diary entry it supports. An album of unnamed images can be difficult to interpret later. Use the project’s arrangements for permission, access and storage rather than scattering working records across personal messaging threads.
The CIOB Code of Quality Management treats filing, distribution and retrieval as parts of document control. The practical lesson here is to make your record findable and assign responsibility for maintaining it.
Turn an unresolved question into an action
A diary entry can identify that a drawing conflict was noticed, but the question still needs an agreed route to the person who can answer it. Give the follow-up a reference and an owner. Review whether the answer was received and whether the diary should link to a later record.
At the end of a week, sample a few entries with a colleague. Can they understand the location, find the evidence and identify outstanding work without asking the original writer? Use their questions to improve the next week’s record.
Related project information guides
Read our construction RFI guide and advice on writing a construction project brief. For related records, see our site diary, progress report and drawing register guides.