SiteTab Site Notes · Guide

Guide · 20 October 2026

The WhatsApp-for-Construction Playbook: How Well-Run Crews Organise a Site

Most small crews already run the job on WhatsApp. The problem is rarely the app. It is whether the group is run as a record, or left as a stream of chat nobody can find anything in a week later.

This playbook is how well-run crews do it. No new software, no training session, just small habits that keep the group readable and useful when anyone asks what happened on a given day.

One group per site, per crew

Start with the structure. Everything else depends on it.

  1. One group for one site and one crew. That group is the site's single record.
  2. Not one company-wide group where three jobs are mixed together.
  3. Not three parallel groups for the same site (photos, client, crew) where the full picture exists in none of them.

When a second site starts, open a second group. When a crew splits, the new crew gets its own group. Consolidating feels tidier. Resist it: you do not want to scroll through another job's deliveries to prove what happened on yours.

Name it so a stranger can find it

A group name has one job: a stranger (a new starter, a PM covering for someone, you in six months) should find the right group in seconds. Use the same pattern every time: PROJECT – SITE OR AREA – CREW. For example:

Avoid names like "Site Team", "New Job" or a client's first name on its own. They made sense on the day the group was created. In a list of fourteen groups they make no sense.

Who belongs in the group

Keep the group work-only, and small enough to stay readable. Include:

Leave out anyone who only needs the finished report. They can receive it without living in the chat. Every extra member adds noise, and a chance for discussion to drift into a private thread.

Pin the essentials

Pin the few messages anyone should reach in two taps (WhatsApp lets you pin up to three):

Update the plan pin each morning or the night before. A pinned plan three days old is worse than none, because people trust it and act on it.

Photo discipline

Photos are the strongest part of a site record and, badly handled, the fastest way to ruin one. Hundreds of uncaptioned photos prove almost nothing.

  1. Caption every photo at the moment it is taken. Where it is and what it shows. "Block B, first floor, bathroom waste run before screed" takes ten seconds. Without that line, the photo is unidentifiable in a fortnight.
  2. Shoot deliveries together with the delivery note. Materials in one photo, the note in the next. Quantity disputes get shorter when the evidence is paired.
  3. Take before, during and after shots of anything that will be covered up. Foundations, reinforcement, pipework, cabling, waterproofing: once buried or boarded over, the photo is the only record it was done properly.

If a photo matters, it goes in the group, captioned, that day, not left in a camera roll.

Voice notes beat typing on site

On site, typing is slow, gloves are on, and screens are hard to read in bright light. Voice notes are how information actually moves. Keep them factual and short:

"Need twenty more metres of 110 pipe, Block B ground floor, delivery ran short" is a complete report. A two-minute note mixing three subjects is not. One subject per note, and follow anything important with a short typed line so it can be found in search.

Flag problems early, confirm decisions in writing

Flag problems the moment they happen, in the group, in plain words. A wrong delivery, a drawing that does not match the building, a trade held up waiting on another: post it when you find it, with a photo if it helps. A problem buried in chat scroll is a problem lost. Raised three days later it reads as an excuse; raised on the day, it reads as management.

Then confirm decisions and approvals in the group, in writing. If a client agrees a change on a call, post the summary: what was agreed, by whom, and any cost or time effect. Side calls leave no record.

The end-of-day wrap

At the end of the day, the foreman closes with one short summary message:

Five minutes at 5pm saves the 10pm reconstruction from memory and three separate conversations. It also gives the PM a fixed point each evening, instead of two hundred messages to read through. If only one habit survives, it should be this one.

What quietly breaks groups

Groups rarely fail at once. They erode. Watch for these:

None of these need a rulebook. They need the foreman to hold the line for the first two weeks. After that the habit holds itself.

Where the reporting layer fits

Even a disciplined group is still a chat thread. The information is there (work done, materials, labour, issues, photos, approvals) but it sits in scroll order. Someone still has to pull it out into a report that can be filed, searched and sent on. That job usually lands on the PM, in the evening.

That is the gap SiteTab fills. It is a WhatsApp contact you add to the crew's existing group, and the team keeps chatting exactly as now, with no new app and no behaviour change. SiteTab files the day's messages, photos, voice notes and documents under issues, progress, materials, approvals and documents, and drafts a daily report. The PM reviews it before it goes out.

If you are weighing that approach against dedicated site apps, our comparison sets out the difference plainly.

The cost is flat: $10 per WhatsApp group per month, however many people are in the group. Run the playbook first, because it improves any group. Then let the report be pulled from the group you already run.

Want a format your crew will actually send? See how to write a daily construction site report from WhatsApp.

Start your 7-day free trial No card needed.