Getting your site off WhatsApp, without banning it

Nobody is going to talk you out of WhatsApp, and nobody should try. It is on every phone on site, it works on a bad connection, and your subbies already use it. Banning it does not work. Every builder who has tried has ended up with a second group chat they were not invited to.

The problem is not the chat. The problem is that WhatsApp has quietly become the place your site records live, and it is genuinely bad at being that.

What actually goes wrong

Photos disappear on a phone change. Unless someone has set up a backup properly, the photos of the waterproofing that went in before the tiles went down are on one phone, and that phone gets dropped in a slab pour or traded in.

Nothing is attached to a job. You run four jobs. The group is one stream. When you need the photo of the rough-in at the Kingsley Street job, you are scrolling by feel, using "that was around the time of the rain" as your search index.

Nothing is dated in a way that helps you. A photo has a timestamp, but a conversation does not have a record. "Move the laundry door" said in a voice note at 6:40pm on a Tuesday is not a variation record. It is a voice note.

People leave. A subbie finishes, leaves the group, and everything they photographed leaves with them. On paper that sounds minor. It is not, when the thing they photographed is now behind a wall.

You cannot hand it over. When a client, a head contractor or a surveyor asks for a record, you cannot send a WhatsApp group. You spend half an hour screenshotting and it looks exactly as unconvincing as it is.

The split that works

Do not migrate everything. Split by whether the thing needs to exist tomorrow.

Keep in WhatsApp: anything conversational. "Running twenty minutes late." "You right for Thursday?" "Gate code changed." "Concrete's here." Chat is good at chat, and moving this into a formal system just means people ignore the formal system.

Move out of WhatsApp: anything you might need to prove.

• Progress photos, especially of anything that is about to be covered up
• What got done each day
• Delays, and what caused them
• Instructions and variations, particularly verbal ones
• Who was on site
• Anything safety related: inductions, incidents, toolbox talks

The test is simple. If someone might ask you about it in six months, it does not belong in a chat thread.

How to do it without a fight

Start with photos of covered work only. Do not announce a new system. Pick the one category with the most obvious downside and move only that. Anything that goes behind plasterboard, under tiles, or under a slab gets photographed into the job record rather than the group. That is a rule anyone on site accepts immediately, because everyone has been burnt by it.

Make the new thing faster than the chat. This is the whole game. If logging the day takes longer than posting in the group, people post in the group. Whatever you move to has to work on an old phone, with one hand, in under a minute.

Leave the group open. The group keeps running. You are not replacing it, you are removing the four or five things it was never meant to hold.

Do the end-of-day note yourself for a fortnight. Do not delegate a new habit on day one. Once there are two weeks of entries, the subbies who need it will start using it, because it is where the answers are.

What this looks like in Foreman

Foreman's site diary is built for exactly this handover. Each entry belongs to one project, carries its own date, and holds the hours, what happened and the photos together. There is no app to install and it runs on whatever phone the crew already carry.

Project information covers the other half of what your group chat is currently doing: plans, specs, gate codes, contacts and safety information, in one place that a new subbie can be pointed at instead of being told to scroll up.

You can run one project on the free plan, which is the honest way to test whether the crew actually uses it before you commit anything.

The realistic outcome

You will not get to zero. Six months in, the group chat is still busy, and that is fine. What changes is that when a client asks what happened on the eleventh of March, or a head contractor wants a record, or a dispute turns up two years after handover, you have an answer that took two minutes a day to build, rather than a scroll through a chat thread and a shrug.

Read next: how to keep a site diary, which is the two-minute-a-day habit this depends on.