Why WhatsApp fails
as a site record.
It is the system most sites actually run on, and it works right up until somebody asks a question about March. Six specific failures, and the one that arrives when a person leaves.
Published ·6 min read·Written by Unibuild
WhatsApp is excellent at moving information between people right now and poor at holding it. It cannot be searched usefully, the history belongs to the phone rather than the business, photographs are compressed below evidential quality, there is no version of anything, and it creates data protection obligations a firm cannot meet on devices it does not own.
Start with why it won
It is worth being straight about this, because an article that treats the reader's current system as a failure of judgment persuades nobody.
WhatsApp won on site because it is genuinely better than what it replaced. Everybody already has it. It needs no account, no licence and no training. It works on a bad signal. Photographs go from a phone to the office in four seconds. There is no login to forget at seven in the morning in the rain, which is exactly the failure mode that kills field apps, as why field rollouts stall in week three sets out.
Any argument for replacing it that ignores those advantages will lose, because the people who chose it were right about the thing they were solving. The question is not whether WhatsApp is good at communication. It is whether communication and record-keeping are the same job.
It is not a bad tool. It is a superb messaging app being asked to be a filing system, which is a different product.
Six ways it fails as a record
- You cannot find anything. Search across a year of site groups for one instruction about one detail and you will not find it. The information exists; it is simply unreachable at the moment somebody needs it, which for a record is the same as not existing.
- The history leaves with the person. This is the one that costs most. A site manager resigns and the entire correspondence for three jobs walks out on their personal phone. You cannot compel it, you did not back it up, and no handover recovers it. Firms discover this about a fortnight after the resignation.
- Photographs are compressed. Images sent in the normal way are reduced for transmission. For a quick look that is fine. For evidence of a defect, a condition on opening up, or the state of a neighbouring property before you started, the detail that mattered has gone. Sending as a document preserves the original, and almost nobody on site does that.
- There is no version of anything. A drawing shared in a group is a drawing shared in a group. Nothing marks it superseded when the next one arrives, so both are in the thread, both look equally current, and the one somebody scrolls to first is the one they build. That failure has its own article, document control, and the revision everybody was working to.
- Nothing is attached to the job. Messages are attached to a group. Groups are made per site, per phase, per argument, and they multiply. Six months later the question is about a job, and the answer is spread across four groups, two of which have been archived by somebody.
- It is not accepted as a record where it counts. An HSE inspector asking for evidence that an operative was briefed on a version of a RAMS before starting, or an adjudicator asking what was applied for and when, wants a dated record tied to the work. A screenshot of a chat is not nothing, but it is a long way from a signed record against a version, and the party that arrives with the latter tends to be the one still standing.
The data protection problem, stated accurately
You will read that WhatsApp is not GDPR compliant. That is not a claim anybody can properly support, and it is not the useful point.
The useful point is that when your business uses it to process information about people, your firm is the controller of that data regardless of whose phone it is on. Four obligations then follow that are difficult or impossible to meet on personal devices.
- Subject access. If an operative asks for the personal data you hold about them, you have to find and provide it. On personal phones you cannot search it and cannot compel it.
- Retention. You are supposed to keep personal data no longer than necessary. Nobody is deleting site groups on a schedule.
- Erasure and leavers. When somebody leaves, the data they hold about colleagues and clients goes with them and stays there.
- Security and breach. A lost personal phone with two years of site groups on it is a potential personal data breach in a business you do not administer.
None of that means anybody is doing something unlawful today. It means the arrangement carries obligations the firm has no mechanism to discharge, and the moment somebody asks is the moment that becomes a problem.
What actually replaces it
Not a ban. Bans fail for the reasons the adoption article sets out: the old route stays open on the bad day, and every day on a site is somebody's bad day.
What works is narrower and more honest. Keep WhatsApp for what it is good at, which is talking to each other. Move the things that have to survive, which is a shorter list than people expect: photographs that evidence something, instructions and variations, drawings and revisions, inductions and briefings, hours, and anything that would be asked for at an audit or a valuation.
Two conditions decide whether that move sticks. The capture has to be at least as fast as taking a photograph and sending it, or site will not use it. And the office has to stop accepting the WhatsApp version, because the moment a record arrives by message and somebody in the office transcribes it, the message has become the system again.
The parts of this Unibuild answers directly: site diaries, progress photographs, drawings, permits and RAMS hang off one job record rather than a group, with the weather captured and the trades on site logged daily, so a question about March is answered from the job rather than by scrolling. Documents carry their versions, and access is granted per person so the record belongs to the business rather than to a handset. Hours come from a QR clock-in with a photograph and a server timestamp that cannot be back-dated. The honest limit: the field app is a real app, so on the adoption question it faces the same test as anything else, and the answer to that is a rollout run properly rather than a promise. It will not make somebody stop using WhatsApp to say the skip is full, and it should not.
Where to start, on Monday
Pick a question you would struggle to answer and try to answer it from WhatsApp. Something real: what instruction were we given about the third-floor risers, and when. Time yourself. Most people give up.
Then ask a smaller question with a larger answer: if the site manager on your biggest job left on Friday, what would you lose. If the answer is the correspondence for that job, you already know what this article is about, and the fix does not have to be a system change this week. It can start with one rule, that photographs and instructions get filed against the job the same day, whatever the route they arrived by.
The follow-up questions.
Why replacing it is an adoption problem rather than a software one is in why field rollouts stall in week three.
Is WhatsApp acceptable as a construction site record?+
What happens to site WhatsApp groups when someone leaves?+
Are WhatsApp photos good enough as site evidence?+
Is using WhatsApp for work a GDPR problem?+
Should we ban WhatsApp on site?+
What makes a replacement actually stick?+
More from Insights.
RAMS that hold upWhat an inspector is actually looking for in a risk assessment and method statement, and the difference between a document that exists and one that is doing its job.Read it →
Retention, and the money that goes missing after practical completionWhere cash quietly disappears between the last valuation and the release of the second half of retention, and the four dates that decide whether you ever see it.Read it →
Why field rollouts stall in week threeMost site software is not rejected. It is quietly outlived by the paper route nobody switched off. What the firms that got it to stick did differently.Read it →