Reporting · 20 October 2026
Nobody reads the daily site report while the job is going well. Then a valuation is queried, a variation is refused or a delay is blamed on you, and that report becomes the only record that matters.
Most reports fail that test. Not because the writer was careless, but because the same five mistakes turn up on many small sites. Each one looks harmless on the day. Each one has a specific cost later, and a specific fix.
The report says "work continued", "plastering in progress" and "blockwork ongoing". The same three lines appear on Monday, Wednesday and Friday. There are no quantities, no locations and no statement of what was actually finished.
This costs money in three places. First, the project manager cannot tell whether the programme is holding, so slippage is found weeks late, when recovery is expensive. Second, the QS cannot verify a percentage complete from "in progress", so the valuation is cut or held back until someone proves the work. Third, if you later claim for a delay, a run of identical vague entries proves nothing about when an activity started, stopped or was blocked.
The fix is a format rule, not more effort. Every entry states the trade, the location, the quantity and the status: "Ground floor, units 3 and 4, internal plaster first coat, 62 square metres complete." If an entry cannot be measured, it gets rewritten before the report goes out.
The foreman takes forty photos a day. By the end of the month there are 300 of them in a camera roll and a chat thread. None is captioned. Half show walls, slabs and trenches that look identical from one week to the next.
A photo is only evidence if you can show what it is, where it is and when it was taken. Without that, it settles nothing. The client queries whether the reinforcement photo predates the pour. The QS rejects the valuation item because the photo could be from any floor. Worst of all, work that is about to be covered up (drainage, waterproofing, steel before concreting) cannot be proved once it is buried. If it is disputed later, you may be opening up finished work or accepting the deduction.
The fix takes ten seconds at the point of taking the photo. Caption it with the location and the element: "Block B, level 2, east side, slab reinforcement before pour." A captioned photo filed with that day's report is evidence. An uncaptioned one is decoration.
A delivery arrives, the ticket is signed and put in the cabin, and that is the last record of it. Usage is never logged. Stock is only checked when something runs out mid-pour or mid-shift.
Without a record, loss is invisible until the bill lands. Say 200 bags of cement are delivered across a month and only 140 can be accounted for in the work. Nobody can say whether the rest was waste, damage or theft, and by the time the totals are compared the chance to act has gone. The same gap causes the opposite problem: two people order the same material because neither knows what is already on site, cash is tied up in surplus stock, and the shortage nobody spotted is covered by an emergency delivery at a premium price.
The fix is two lines a day. Log every delivery on the day it arrives (item, quantity, supplier) and note usage and remaining stock against it. Theft, short deliveries and double-ordering all become visible while they can still be corrected.
The drain is blocked, the drawing contradicts the levels, the steel delivery is late. Each problem is mentioned at the gate, on the stairs, in a two-minute conversation at the end of the day. Everyone nods. Nobody writes it down.
Three weeks later the delay is yours. The client and the main contractor remember the conversation differently, or not at all, and there is no dated record that you raised the problem, when you raised it or who agreed to act. Contractual notice periods can lapse quietly in the same way: by the time the issue is formalised, the window to give notice has closed. Verbal instructions carry the same risk: work done on a spoken instruction, then refused as an unpaid variation because no written record exists.
The fix is to put every blocker in that day's report, the day it appears. State what it is, what it stops, who needs to act and the date it was raised, then carry it forward in each report until it is closed. An issue in writing is a shared problem. An issue said out loud is your problem.
The site day ends, and the report is written at a kitchen table at 10pm. The writer reconstructs eleven hours from memory: quantities are rounded, timings are approximate, and the awkward problem from the morning is softened or left out because reopening it at night, in writing, feels like starting an argument.
This is reconstruction, not record, and it degrades in predictable ways. Details are invented in good faith and then relied on by others. Problems read smaller than they were, so nobody escalates them in time. And the evening report is the first task dropped when the site gets busy, which means the record has gaps on exactly the days when the most happened and a clear record matters most.
The fix is to stop relying on recall. Capture the facts during the day, in short messages, photos and voice notes as the work happens, and let the evening task be a short review rather than an act of memory.
All five mistakes have the same cause. The report is written after the day, from memory, by a tired person, in a document nobody else contributed to. No template fixes that on its own, although structure helps: our daily report guide sets out the sections a complete report needs.
The real fix is timing and place. Capture the record during the day, where the crew already works: the site WhatsApp group. The crew already sends photos, voice notes and updates there as the work happens. If that stream is organised into the report, the quantities, captions, deliveries and blockers exist before anyone sits down to write anything. You can also see how that approach compares with app-based reporting.
That is what SiteTab does. It is a WhatsApp contact you add to the crew's existing group. It files the day's messages, photos and voice notes and drafts a daily site report (work done, materials, labour, issues and photos) that the project manager reviews before it goes out. It costs $10 per WhatsApp group per month, flat, and there is nothing to install.
Start your 7-day free trial No card needed.