WhatsApp groups are a liability on site because messages, photos and instructions get buried within days, nobody owns the thread, and there’s no record you can point to if a job or a dispute is ever questioned. It works for a quick “running 20 minutes late” — it doesn’t work as a system of record for a live building project.
Most site-based teams didn’t choose WhatsApp on purpose. It’s just what’s there — every worker already has it, it’s free, and it’s faster than a phone call. The problem shows up later, when something goes wrong and you go looking for proof.
Where it falls apart
Messages get buried. A site group with five or six people easily produces 100+ messages a day. The one photo that actually mattered — the one showing the drainage was done to spec before it got covered — is three days back, mixed in with banter and “who’s got the key to the van.”
There’s no ownership per job. A task mentioned in a WhatsApp message isn’t assigned to anyone in any real sense. It’s just… said. Nobody gets notified when it’s done. Nobody can pull up “what’s outstanding on Plot 4” without scrolling.
Evidence isn’t timestamped against the job. If a client later disputes whether something was done, a photo in a WhatsApp chat has a timestamp, sure — but it’s not tied to the job, the plot, or the task in any structured way. Try explaining that to a solicitor.
You end up with five groups you mute. One site becomes one group. Three sites, three groups, plus a general one. Within a few weeks most people have muted at least one, which defeats the point.
Drawings go stale. Somebody shares a PDF of the latest drawing in the group. Two revisions later, half the site is still working off the old one because nobody removed it or made clear it was outdated.
What a site actually needs instead
Not a big enterprise system with a six-week rollout — just a place where:
- Every task is assigned to someone, and marked done with a photo attached
- Photos and updates are tied to the specific job, not floating in a chat
- Drawings are on every phone, labelled by version, not in a PDF buried in the chat
- Messaging still happens, but per site, in one thread — not scattered across five group chats
That’s a smaller ask than it sounds. It’s the difference between a chat app and a system that happens to include messaging.
Banksman keeps tasks, photos, drawings and messages per site in one app — try the live demo, no card required.
FAQ
Is WhatsApp actually bad, or just not ideal?
It's fine for casual, low-stakes chat. It becomes a liability specifically around anything you'd need to prove or find later — task completion, photo evidence, drawing versions.
What should replace it?
A site management tool with messaging built in per job or per site — so you get the speed of a chat app without losing task tracking, photo evidence, and document control.
Can I keep using WhatsApp for quick chat and something else for records?
You can, but in practice teams that run two systems tend to only maintain one properly — usually whichever is easier, which ends up being WhatsApp again. A single tool that does both tends to stick better.