Death by WhatsApp: Why Your Site Diary Must Be More Than a Chat Group

Ask a project manager where the site record lives and you will usually get the same answer: "the WhatsApp group".

Scroll back far enough and the truth is there — photos of progress, complaints about late deliveries, "as discussed, the area will be handed over tomorrow", a voice note from the MEP foreman. It is all there, buried under two years of Good mornings, job circulars and a hundred photos of somebody else's concrete cube tests.

Then a claim lands, or a dispute starts, and the WhatsApp group becomes useless.

Why chat is not a site record

A site diary has one job: prove what happened, and when, in a form someone else accepts. Chat fails that job in four ways:

Nobody can find anything. "Check the group" is not a document. The photo of the flooded basement exists, but finding it among 40,000 messages is a day's work.
The order of events is unclear. Which came first — the NCR or the instruction to pour? Chat timestamps get scrambled by edited messages, replies and forwarded images with no original date.
Everyone edits history. Deleted messages, edited messages, photos re-saved and re-sent with new dates. Opposing counsel will attack every part of it.
It has no author. A diary entry needs a name behind it. "Someone in the group said" proves nothing.

What a defensible diary looks like

Whatever tool you use, the test is the same. A site diary entry should be:

Written on the day, by the person who saw it. Not reconstructed on Friday from memory.
Timestamped and locked. Once saved, the record does not change. Corrections go in as new entries, not overwrites.
Structured enough to search. Date, location, activity, weather, manpower, what was delivered, what was delayed. A judge or contract administrator should be able to find "the second week of March" in seconds.
Carrying its evidence. Photos, files and links to related records — the NCR raised that morning, the RFI still open — attached to the entry, not scattered across five apps.
Exportable. You will need to hand it over as a PDF or a pack. If it cannot leave the system cleanly, it is not finished.

Multiple entries, not one summary

Real sites do not produce one neat paragraph a day. The concrete pour at 6 AM, the crane standing idle at 11, the inspection passed at 3 PM — these are separate facts, often from different people.

BuildRevu therefore allows multiple diary entries per day, each its own timestamped record, each carrying its author. Entries can only be made inside an open project, so the record starts and ends where the work does. And because every entry is written on the phone in the field — online or offline — it is captured while the memory is fresh, not reconstructed later.

When a claim needs support, the relevant entries, photos and linked records come out as a report with the project's own cover details. The diary stops being archaeology and becomes a document you can actually submit.

The WhatsApp test

Here is the simple test for your current arrangements: pick a dispute from last year. Time yourself finding the evidence — the date, the photo, the instruction, the person. If the answer is more than five minutes, you do not have a site record. You have a chat group.

You do not have to ban WhatsApp; the team coordination will continue there regardless. Just stop pretending it is your record.

Try it

Take the guided tour of BuildRevu — no signup — at buildrevu.com/demo, and see how site diaries, snags and inspections connect into one record. Or start at buildrevu.com.

Ashwani Bhalla is the Founder of BuildRevu and Principal at AEAS Concept Project Management Services, Dubai.