Skip to content

Construction administration guide · By Yes AI

What should a construction site diary record?

Published 5 min read

A site diary written on the day is the record a contract administrator reaches for first when a delay claim or variation is disputed months later. This guide lists what each entry should contain, how to record weather and incidents, and where software can help turn daily notes into reports.

Quick answer

A construction site diary should record, for every working day, the weather and any time lost, labour on site by company, plant and deliveries, visitors and inspections, instructions received, delays and their cause, work areas started or finished, and incidents. Each entry needs a date, an author and photos where relevant. Make entries on the day, and correct them with a dated addition instead of editing the original.

Site supervisor in hi-vis writing a diary entry on a tablet beside a partly built concrete frame

Why does the site diary matter after the job?

Delay and variation disputes are argued from records, and the diary is usually the record closest to the event. A claim for more time needs evidence of when a delay started, what caused it and what was done about it. Under the ACT Government's modified GC21 contract, for example, the contractor's initial notice of delay must set out the cause, the steps taken to minimise it and the relevant facts, within 7 days of the delay starting. Those facts come from the diary. An entry written on the day carries more weight than a reconstruction from memory in month seven.

What should each daily entry include?

Use the same headings every day so a missing item is obvious. Short, factual entries are better than long narratives, and a time against each event is more useful than a summary at the end of the shift. Record what was seen and heard, and leave out opinions about fault. If something cannot be recorded on the day, add it the next morning as a dated late entry that says so.

Photos should be referenced from the entry they support, with the location noted, so that someone reading the diary in a year can find the image of the flooded excavation or the blocked access road without searching a phone camera roll.

  • Weather at start, midday and finish, and any hours lost, with who made the call to stop.
  • Labour on site by company and trade, with head counts.
  • Plant on site and deliveries received, with docket numbers.
  • Instructions or directions received, from whom and how, word for word where possible.
  • Delays, disruptions and their cause, and the work areas affected.
  • Inspections, visitors, tests and any incidents, with photos referenced.

How should weather and wet days be recorded?

Record the conditions, the time work stopped and restarted, who made the decision and which trades were stood down. The Fair Work Ombudsman notes that some awards and enterprise agreements include inclement weather rules, which set out what counts as inclement weather and what employees are paid, so your records may be needed for payroll as well as for the contract. Back the entry up with observations from the nearest Bureau of Meteorology station; Climate Data Online provides daily rainfall and temperature records by station. Note the station number in the diary so the comparison can be repeated later.

What about incidents and safety events?

A diary entry is not a WHS notification. Safe Work Australia's guidance under the model WHS laws says a notifiable incident must be reported to the WHS regulator immediately, by the fastest possible means, that the site must be preserved so far as is reasonably practicable until an inspector releases it, and that records of each notification must be kept for at least 5 years. Its December 2025 fact sheet notes that changes to the model laws apply only where adopted locally, so check your state regulator. In the diary, record the time, what happened, who notified the regulator and the notification reference.

Paper, app or platform: does the format matter?

Consistency matters more than format. A paper diary written every day is better evidence than an app used twice a week. What digital tools add is a timestamp on each entry, photos linked to the entry, and search across the whole job, which makes later claim preparation faster. If the diary lives in a project platform, check that entries cannot be silently edited after the day and that the export includes photos. If supervisors prefer voice notes, keep the original recording alongside the transcribed entry.

How can software help with site diaries?

Software can transcribe voice notes into the standard headings, summarise a week of entries into lost time, labour trends and open instructions, and flag entries that mention a direction, a delay or a change for the contract administrator to review. It can also report missing days before the gap becomes permanent. It should not decide the cause of a delay or whether an entry supports an extension of time claim. The supervisor confirms each entry, and the contract administrator decides what to do with it.

Site diary entries and what they support later

EntryWhat to recordUsed later for
WeatherConditions at set times, hours lost, who decided to stopExtension of time claims and inclement weather pay
LabourHead count by company and tradeDelay and disruption claims, subcontractor disputes
Plant and deliveriesEquipment on site, docket numbers, late or wrong deliveriesSupplier claims and back charges
InstructionsWho gave it, when, how, and the words usedVariations and RFI follow-up
DelaysCause, start time, areas affected, steps takenNotices of delay and EOT claims
Inspections and visitorsWho attended, what was inspected, outcomeHold point records and handover
IncidentsTime, event, notification referenceWHS records and insurance claims

Practical checklist

  • One person writes each day's entry, with a named backup for leave.
  • Entries are dated on the day, and corrections are added as dated notes rather than overwriting.
  • Weather entries name the Bureau of Meteorology station used for comparison.
  • Instructions recorded in the diary are copied to the variation or RFI register within the week.
  • Incidents are cross-referenced to the WHS notification and its reference number.
  • A weekly review flags missing days, missing photos and unexplained lost time.

Common questions

Is a site diary a legal requirement?

That depends on your contract, your client's procedures and your own quality system, so check each head contract. Even where nothing requires one, the diary is the record a contract administrator relies on when a delay or variation is disputed, and keeping it costs a few minutes a day.

Can supervisors keep the diary on their phones?

Yes, if entries are timestamped, backed up to a project system and kept with their photos. Personal phones get replaced and photos get lost, so the diary should not live only on one device. Agree the app or platform for the whole company so entries can be searched across jobs.

How long should site diaries be kept?

Keep them for at least as long as claims could arise under the contract and the law, which can be years after practical completion. Records of notifiable incidents must be kept for at least 5 years under the model WHS laws. Ask your lawyer to set a retention period for project records.

Should we collect subcontractors' diaries too?

Where a subcontract requires them, yes. Subcontractor records help when a delay passes up the chain, and they can confirm or contradict your own diary. Collect them at the same interval as payment claims so they are filed while the period is still fresh.

Can AI write the site diary?

It can structure and transcribe what the supervisor says or types, and remind them about missing headings. The facts must come from the person on site, who confirms each entry. A diary written by software from other records would lose the value of being a first-hand account made on the day.

Sources and further reading

Continue planning

Plan the next improvement to your project administration

Describe the document workflow, project systems and handover causing delays. We can discuss a bounded admin pilot and the checks your project team needs. Keep contracts, personal records and confidential project files out of this enquiry.