Missing daily reports creates gaps in your record that are hard to fill later. Disputes over delays, variations, incidents, and subcontractor performance all depend on site records made at the time. Without them, your position in any claim weakens significantly, regardless of what actually happened on site.
Is there a legal obligation to keep daily site records?
Under Australian WHS legislation, employers and principal contractors are required to keep records of workplace incidents, hazards, and safety inspections. This isn't optional.
Most construction contracts also impose an express obligation to maintain a site diary as a condition for making delay or variation claims. Miss the obligation, lose the ability to claim. Some contracts are explicit about this: no record made at the time, no entitlement to claim. Check yours.
For a detailed breakdown of what records Australian site supervisors are required to keep, see What records does a site supervisor legally need to keep in Australia?
What happens during a dispute or claim?
In a dispute, the party with records made at the time has a big advantage. Site diaries, incident logs, and delivery dockets all carry weight in adjudication and litigation. Memory does not.
A gap in the diary for the specific days at issue in a delay claim can be the difference between a successful extension of time and a rejected one. Adjudicators look at the record. If the record is silent on the days the delay allegedly occurred, the claim has a problem.
The other side will have records. Make sure you do too.
What if I missed a few days?
A few missed days early in the project are workable if nothing significant happened during those gaps. Missed records during a delay event, incident, or disputed variation are a different situation.
Fill gaps as soon as you realise they exist, but note that the entries are written after the fact, and you should mark them that way. Presenting a backdated record as made at the time creates a credibility problem that's worse than the gap itself.
Consistent logging from here forward is the practical answer. The best time to start was the first day on site. The second best time is today.
How do I build a consistent reporting habit?
End-of-day reporting fails because it competes with everything else at knockoff. Log as you go instead. A 15-second voice entry when something happens is faster than it takes to walk back to the site office. No decision, no friction, no "I'll do it later."
Set a daily reminder for end of shift to generate the report. The entries are already done. Generating takes 30 seconds.
The cost of inconsistency
A project diary with gaps looks like a diary that was never taken seriously. Even if you logged diligently for most of the project, missing records on the critical days, the day the variation was instructed, the day the delay started, leave you in the same position as if you'd logged nothing at all.
Consistency is the asset. Every day logged is insurance. Every missed day is exposure you can't recover after the fact.