WhatsApp Project Updates for UK Construction Sites

Discover the best way to manage WhatsApp project updates on UK construction sites without losing vital records or compromising site diaries.

By James Shorter ·

WhatsApp Project Updates for UK Construction Sites

Site supervisor sending a WhatsApp update

WhatsApp is where most UK site updates already happen, and for quick messages it works. It stops working when an update has to become a record: a snag, a materials order, a variation or a diary entry. The fix is to keep the chat but get each update filed to the right job as it is sent. That is what BRCKS does. The team chats as normal, one tap turns a message into a snag, order, site visit or checklist item, and subcontractors and clients stay in WhatsApp for free.

This guide covers how to write a good WhatsApp update, how to set up groups so the right people see it, and where the chat needs backing up with a proper record.

BRCKS
Keep WhatsApp Updates Tied to the Job
BRCKS turns site chat into snags, orders, site visits and checklist items filed to the right job, while clients and subcontractors stay on WhatsApp.
Visit

TL;DR

  • Site teams use WhatsApp because it is fast. A UK case study of subcontractor operatives found supervisors said group chats helped coordination and reacted to events in real time.
  • A good update names the job, says what is done, what is next, what is blocked and what decision you need, with a photo.
  • Money, changes and formal notices should not live only in a chat. UK solicitors and industry press advise separating them from day-to-day messages.
  • Messages sit on individual phones, so nobody holds one record for the job. BRCKS files updates per job, and subbies and clients stay on WhatsApp for free.

Table of Contents

Why site teams use WhatsApp for updates

Nobody has to be trained on it. Everyone already has it, a photo takes seconds, and a message reaches a subbie who would never open a portal.

The Innovation Driven Procurement programme looked at this in a case study on social media on UK sites. Operatives across several subcontractors used WhatsApp groups to communicate quickly. Supervisors said the groups helped them coordinate teams and react to events across different locations on a project.

That speed is the reason to keep WhatsApp in your workflow. The problems come later, when someone has to find a message from six weeks ago.

What a good WhatsApp project update contains

A vague “all going well, few issues” tells nobody anything. A useful update is short and has the same parts every time, so people know where to look.

The daily or weekly progress update

Use this order:

  1. Job and date. Address or job name first, so the message makes sense when forwarded or searched.
  2. Done. What was completed, in plain terms: “first fix electrics complete ground floor”.
  3. In progress. What is under way and who is on it.
  4. Next. What starts tomorrow or next week.
  5. Blocked. Anything waiting on a person, a delivery or an inspection.
  6. Decision needed. What you need from the client or contractor, and by when.
  7. Photos. Wide shot first, then close-ups of anything you are describing.

Example:

14 Alder Road, Fri 14 Nov. Done: first fix plumbing to bathroom and utility. Next: boarding Monday. Blocked: waiting on client choice of tap finish. Need by Tuesday or the vanity unit slips a week. Photos attached.

The deadline is what turns a message into a decision. Without it, the question sits unanswered under 40 other messages.

Photos that help

Take photos before you cover anything up: pipework behind boards, cable runs before plastering, a damp patch before it is painted over. Take one when a delivery arrives, and one of the finished stage. Add a line saying what the photo shows and where. A photo of a wall with no caption is a guess for the next person.

Cable runs visible in an unfinished room

Reporting an issue

Keep it factual and short. Say what you found, what it affects, what the options are and what you recommend. If the options have a cost or time effect, say so in the message. “Found rot in the joist under the bath. Replacing adds about two days and some timber. Recommend we do it now before boarding. Please confirm.” That one message gives the reader what they need to say yes.

Key details in a construction issue report

Setting up groups so updates reach the right people

One big group for everyone is the most common mistake. The electrician gets plumbing chatter, the client sees a heated exchange about a late delivery, and the important message is lost.

A structure that works for most residential jobs:

  • One group per job, not per trade. Name it with the address or job number.
  • A core site group for the people running the job: site manager, foreman, lead trades.
  • A separate client update group with a few people in it. Updates there are written for the client: progress, photos, decisions needed. Keep site banter out.
  • Subbies added for their work window, then removed when they finish. This also limits who can see client details and photos of the property.
  • Agree what goes where on day one. Quick logistics and photos in the group. Anything involving money, specification or a change goes somewhere it will be confirmed in writing (see below).

We cover house rules in more detail in our guide to WhatsApp rules for UK construction site teams.

Keep formal instructions out of the chat

This matters more than the format of your updates.

UK solicitors Thomson Snell & Passmore note in their advice on WhatsApp for site communications that standard form construction contracts require change instructions to be made or confirmed in writing. They also say recent case law supports WhatsApp as an effective way of serving notices, with the burden on whoever claims they gave notice to prove it. Two practical points follow from that:

  • A casual message could be treated as a formal notice, whether you meant it to be or not.
  • Some contracts name the individuals who must receive notices, so check those people are in the group.

Construction Management magazine makes the same recommendation in its piece on WhatsApp for site communications: keep WhatsApp for day-to-day site communication, and separate formal notices from it, for example by requiring change instructions to be confirmed by email. The authors say this should be adopted even on domestic projects.

In practice: when a message in the chat turns out to be a variation, log it as a variation straight away, with the instruction, the price and the person who approved it. In BRCKS that is one tap on the message, and it lands in the job’s variation log with an audit trail. If your contract is a standard form, check what it says about notices. If you are unsure, ask your solicitor.

The record problem: messages live on individual phones

WhatsApp has one big weakness for project records. The same Construction Management piece notes that the data is stored individually by each user, and that recent UK public inquiries have highlighted messages being routinely deleted or described as irretrievable. It does create a date-stamped record of when a photo or video was shared and seen, which can help in a dispute.

John Ryan, writing in Construction Management on consumer messaging apps among project teams, argues the material sits on each person’s device, so when someone leaves a project they take that data with them and the company has no single source of truth. The same article points out that any user can delete their information at any time, which undermines a chat as an audit trail for the Building Safety Act golden thread.

If you work on higher-risk buildings, that is a real compliance question. If you work on extensions, loft conversions and refurbs, the practical version is simpler: when the client says “you never told me that”, can you find the message in two minutes?

If your answer is “scroll back and hope”, the chat is not your record. We go through the data side in WhatsApp GDPR rules for UK builders.

Using WhatsApp updates to keep a site diary

A site diary is the daily record of who was on site, what was done, what arrived, what was held up and why, plus weather and visitors. Many builders write it at night from memory, with the chat open on their phone.

There is a better habit: treat the chat as the source and pull from it as you go. Practical rules:

  • Any instruction or decision given in the chat goes into the diary with a reference to the message.
  • Photograph progress weekly and events straight away: cover-ups, openings, deliveries, stop-work days.
  • Write down why work waited. That line is what you will need if a delay is ever argued over.
  • Record the weather on the day, not afterwards.

The test is whether someone who was not there could work out what happened by reading it cold a year later. If they could not do it from your diary, they will not manage it from 900 WhatsApp messages either.

In BRCKS, photos and actions in the project chat are filed to the right job as they arrive, so the diary draws on what the team already sent, with no writing up at night. We designed it to save site teams 30+ minutes a day on admin.

From chat to snag, order or booking

Here is the gap WhatsApp leaves. A message like “socket in bedroom 2 is cracked” is a snag. “Need 20 more sheets of 12.5mm board by Thursday” is an order. “Plasterer coming Tuesday, gate code 4471” is a site visit. In a group chat they are all just messages, and each needs someone to copy it into a list.

The habit that fixes it, with or without software:

  1. Decide the four or five things a message can become: snag, order, visit, checklist item, variation.
  2. Name one owner for each list.
  3. Move a message into its list the moment it is read, not at the end of the day.

In BRCKS the third step is a single tap. The snag, order, booked visit or checklist item goes into one list per job, with the photo attached. Our project updates guide shows how the updates and lists fit together.

How BRCKS handles WhatsApp project updates

BRCKS is a chat app for building sites. The core site team uses BRCKS Chat on iPhone or Android. The office uses BRCKS Web on a bigger screen. Subcontractors and clients use BRCKS on WhatsApp, which is free for them and needs no install. It is one job and one record, whichever way the update arrives.

It includes snagging and checklists, a shared team calendar, site diaries, variations and RFIs with audit trails, versioned project files (drawings, RAMS, quotes), gate, Wi-Fi and key-safe details per job, a client portal and 360° site tours.

Pricing is published on the pricing page: Solo is £20 per month, and Teams is £40 per seat per month billed annually (£50 monthly). Subcontractors and clients are free, and there is a 14-day free trial. If you would rather see it on one of your own jobs first, you can book a BRCKS demo.

BRCKS

For a side-by-side view, see WhatsApp vs BRCKS. For the wider picture, read about construction communication software for UK builders.

Our view: get the job out of the group chat

Most builders I know do not want new software. They want to stop writing things up at night.

WhatsApp is not the problem. Everyone is on it, and subbies reply to it. The problem is that a good message arrives, gets read, and then sinks. Someone has to turn it into a snag, an order or a variation by hand, and that someone is usually the foreman at 9pm.

That is why BRCKS works like a simple chat. The team uses it the way they already use WhatsApp, and one tap on a message files it to the job as a snag, an order, a site visit or a checklist item. Subbies and clients stay in WhatsApp and install nothing, so nobody is asked to learn a new system.

I started BRCKS after 20 years in construction, and it is built for UK residential trades: variations, RFIs, RAMS and all. The test I would give any tool is simple. When the client asks what was agreed about the kitchen, can you answer in a minute? One list per job gets you there.

James

A simple weekly routine

Whatever tools you use, this routine keeps updates useful:

  • Daily: one structured update per job with photos. Convert messages to snags, orders and visits as they arrive.
  • Weekly: a client summary with progress, photos and decisions needed. Ask the site manager what significant instructions or admissions came through the chat that week.
  • On any change: log the variation, get the price and approval in writing, and attach the original message.
  • At handover: export or gather the diary, photos, variations and files in one place, rather than collecting them from five phones.

FAQ

Can I use WhatsApp for project updates on a UK construction site?

Yes, and most teams do. Use it for day-to-day updates, photos and logistics. Keep formal notices, variations and anything involving money confirmed in writing, as UK solicitors and industry press advise. Check your contract for who must receive notices.

How do I keep a site diary from WhatsApp messages?

Treat the chat as your source. Record every instruction or decision in the diary with a reference to the message, photograph events as they happen, and note why work waited. BRCKS files photos and actions to the right job as they are sent, so the diary does not depend on memory.

Is a WhatsApp chat a reliable record for disputes?

It shows when a photo or message was sent and seen, but the data sits on each person’s phone and messages can be deleted. For a record you control, log instructions, variations and photos into one list per job.

Do subcontractors and clients need to install anything?

Not with BRCKS. Subcontractors and clients use BRCKS on WhatsApp, which is free for them and needs no install, while your team works in the BRCKS app.

Sources

Recommended


How BRCKS Can Help

While WhatsApp offers a quick fix for site communication, relying on fragmented chats often leads to critical data being lost in the noise. BRCKS bridges this gap by centralising your project updates into a structured, professional environment designed specifically for the UK construction industry. By integrating your site reporting into one reliable platform, you ensure every decision is documented and every team member stays aligned. Discover how BRCKS can bring clarity to your site management by exploring our features today. Learn more at BRCKS and explore our full feature set.


Sources