Note
Site Diary as a Billing Tool
Most site diaries capture one thing well: weather, headcount, and a note that work happened. None of that helps when a billing stage is rejected or a variation claim lands on the main contractor’s desk six weeks after the work was done.
This post is about building the connection between the daily record and the billing stage before you need it, not after a dispute has started.
Why does the standard site diary fail at billing time?
Most site diaries are designed by safety managers and filled in by supervisors with twelve other things to do before noon. The forms record headcount, trade, weather, and safety incidents. Those fields serve an insurance audit, not a payment application.
When a QS reviews a billing stage claim and asks for supporting evidence, the standard diary gives them a headcount. It does not tell them which zones were closed, which items from the BOQ were completed, who accepted them, or whether the work matched the drawing revision current on that day.
The result is a billing stage that rests on the invoice and nothing else. If the QS disputes the completion date or questions quantities, there is no contemporaneous record to fall back on. The contractor has the invoice. The main contractor has a question and time on their side.
What should you record every day to support a billing stage?
The gap is not about adding more paperwork. It is about recording four specific things in a running document that is easy to maintain and credible to a third party.
Zone or area closed that day. A stage that covers three zones needs a record of when each zone closed, not just when the invoice was submitted. One line per zone: “Zone 4 suspended ceiling: all tiles set, perimeter trim fixed, 14:30 Tuesday 3 June.” That line makes the billing pin checkable.
Drawing revision used. Many disputes about what “completed” means come down to which revision of the drawing was current. Record the revision number alongside the zone. RFA12-Rev3, not just RFA12.
Instruction received, from whom, and by what method. Every verbal instruction, LINE message, and site engineer’s request goes into the log the same day it arrives. An instruction received Tuesday and recorded Friday looks like it was recorded Friday. Recorded the same day, it looks like what it is.
Who was present for any walkthrough or inspection. A main contractor’s site engineer who walks a zone and makes no objection is not providing written acceptance, but their presence is still worth recording. Name and date. If they raise a snag, record the snag alongside their name. That record proves when the issue was known and whether it was corrected before the billing stage closed.
A concrete example: Zone 4 and a delay that was not your fault
A fit-out contractor installs ceiling systems across six zones on a commercial project. The billing stage covers zones three, four, and five. Zone four runs into a coordination problem: the MEP contractor does not clear the zone until ten days later than planned.
Without a daily log, the billing stage lands on the main contractor’s desk claiming all three zones are complete. The QS queries the date. The contractor says zone four finished on the twenty-second. The QS says their site engineer visited on the twentieth and found the zone incomplete. Nobody has a written record of the MEP delay. The back-and-forth takes three weeks, and one zone gets pushed to the next billing stage.
With a daily log, the contractor has the LINE message from the MEP coordinator, a dated entry showing zone four closed after MEP cleared, and the site engineer’s name from the zone three walkthrough where no snag was raised. The query resolves in one exchange rather than three weeks of back-and-forth.
How does a daily record change a variation claim?
The capture habit that supports billing stages is the same habit that makes variation claims defensible. An instruction recorded the same day it arrived has a timestamp, a sender’s name, and a description of what was asked. An instruction reconstructed three weeks later from memory has none of those things.
The daily record is not a separate variation log. It is the same document, updated daily. Variation instructions sit alongside zone completion notes in the same running file. When a billing stage closes, the evidence for any included variations is already there. The QS is reading a record built in real time, not a reconstruction made the night before submission.
When does a billing stage need a separate evidence summary?
For a stage that covers straightforward scope with no disputed quantities, the daily record is enough. For a stage where the main contractor is likely to scrutinise quantities closely, for example after a scope change or a programme revision, it helps to compile a brief one-page summary: zones covered, drawing revisions referenced, variation instructions with reference numbers, and the date each zone closed. That summary attaches to the invoice and reduces the follow-up round to a check rather than an investigation.
The daily record is the primary evidence. The one-page summary is drawn from it and makes it faster for the QS to check.
How far back should I keep records to support a billing stage claim?
As far back as the stage definition goes. If a stage covers six weeks of work, records from the full six weeks make the completion date credible; records from only the final two days are easier to question. For retention release, records may need to go back to the original completion date of the zone, which can be several months before the release claim. Daily records that start before the project does are far more useful than those started after a dispute appears.
Can a photo timestamp replace a written record?
A timestamped photo confirms that a specific area looked a specific way at a specific moment. It does not confirm the drawing revision being worked to, who gave the instruction, or whether the main contractor’s site engineer was present. Photos are useful evidence alongside a written record. On their own they leave gaps that an experienced QS will find. A full zone closure entry is: date, zone name, drawing revision, who was present, and any conditions noted. A photo with a date is one-fifth of that.
What if you only started keeping records mid-project?
Start now. A record covering the second half of a project is better than none. For stages already closed without a contemporaneous log, reconstruct from LINE messages, call logs, and existing photos, and present that reconstruction clearly as a reconstruction. A QS knows the difference, but a well-organised reconstruction is still better than nothing, especially when the main contractor’s site records can cross-reference dates. Make the daily log a standing item in your weekly project review so it does not fall off when the site gets busy.
If you want to see how a daily record connects to a billing stage pin on a project timeline, a 45-minute call is the fastest way to check. We open one project together and work through where the evidence gaps are.