The BRCKS WhatsApp Playbook

One message, many actions

Say: "Tiling done first floor, invoice from the tiler 3k, need to order more adhesive, and book Steve for Thursday morning."

BRCKS logs the progress update, files the £3,000 expense, creates a task to order adhesive, and books Steve for Thursday — all from one message.

Common examples

• Tick off a task. "Yeah I fixed the tap in Flat 4B" → task marked complete.
• Log an expense. "Sparky invoiced 5k for the rewire" → filed under electrical.
• Create a task. "Get the sparky to check the consumer unit at Elmwood" → assigned to Mike.
• Book a visit. "Book the BCO for Thursday 10am at Oakmere" → calendar event created.
• Morning briefing. "Morning" → today, overdue tasks and active projects.
• Fix a mistake. "Wait, I meant 800 not 8k" → updated automatically.

Safety alerts

If someone reports water dripping onto electrics, a gas smell or suspected asbestos, BRCKS Bot immediately issues a safety alert with the right action — isolate, evacuate, stop work — and notifies managers.

Why it works

The trades don't change behaviour. They already use WhatsApp. BRCKS simply captures and structures what they're already sending, so the office gets clean records without chasing anyone.

Setting your team up

1. Create the project. Add the site, plots and rooms in the web app — or in bulk if you're running a development.
2. Invite the group. Your company gets a dedicated BRCKS WhatsApp number. Add it to the existing site group, or invite trades individually.
3. Tell people nothing. Genuinely. Keep messaging as normal for a week and check the project record afterwards — the diary, snags and costs will already be there.
4. Tighten up. Once people see it working, add plot names to messages ("Plot 12 — …") so everything files itself perfectly.

Ground rules that keep it clean

• Name the plot or project first in the message — BRCKS files it there automatically.
• Send photos with a sentence, not on their own; the sentence becomes the record.
• Report a change as a change ("client wants…") so it becomes a priced variation instead of free work.
• Use voice notes freely — they're transcribed and filed like text.
• Ask questions of the bot ("what's overdue on Oakmere?") instead of scrolling.

A day of messages, and what BRCKS does with them

"Morning" — you get today's tasks, anything overdue and the active projects. "Plot 14 plasterboard finished, two sheets damaged in the delivery" — progress filed against Plot 14, plus a task to chase the supplier. "Client on site, wants the downlights moved 300mm" — a variation raised before anyone drills, so it gets priced. "Photo of the crack above the window in the master bedroom" — a snag with a photograph, assigned to the plasterer. "Sparky on site 8 till 4, two mates" — labour recorded for the day's diary. "What's outstanding on Oakmere?" — the list, grouped by trade, in seconds.

Nobody typed a command, opened a form or learned a syntax. That is the whole playbook.

Handling voice notes, photos and the messy stuff

Real site messages are not tidy. They are voice notes recorded in a van, photos with no caption, half-sentences and corrections. Voice notes are transcribed and filed like text. Photos sent on their own are attached to the current context, which is why a one-line caption is worth the effort. Corrections work the way they do in conversation — "wait, I meant 800 not 8k" updates the record instead of creating a second one. Nothing is deleted; the trail shows what was changed and when.

Rolling it out without a training day

The mistake is announcing it. Teams that succeed do the opposite: point the existing site group at the BRCKS number, say nothing, and look at the project record after a week. Once the site manager has seen the diary write itself, the small habits — naming the plot, captioning the photo — spread on their own because they are visibly useful rather than mandated.

If you manage several sites, do one first. A fortnight on a single live project tells you more than any demo, and it is the pattern in both of our case studies.

What the office sees at the other end

Everything that arrives by WhatsApp appears in the web app as structured records: diary entries by day, snags by plot and trade, variations awaiting pricing or approval, costs against the job, and a document store with every photograph in date order. The client sees a filtered version in the free portal. Subcontractors and clients never consume a paid seat — see pricing.

Try the playbook on your next job

How BRCKS Bot works · Snagging · Site diary · WhatsApp project management · Watch the demo · Start free trial · Talk to us