Construction site communication: when WhatsApp groups stop working

On most jobs, construction site communication starts with a group chat. The client, the workers, the supplier — everyone in one WhatsApp group. It is fast, free and familiar: everyone has a phone and already knows how to use it.

While you run only a few jobs, that is enough. The owner sits in every chat, remembers what was agreed and keeps track of who is doing what. The chat works because the whole picture lives in one person’s head.

With every new job there are more chats, and still only one head. At some point the owner notices that half the day goes on answering questions that were already answered somewhere in the thread. This is where the chat stops keeping up.

Why a chat is so good at the start

A chat has three strengths worth keeping:

• Speed. You write and get a quick reply.

• Everything in one place. Photos, voice notes, files, locations.

• Zero learning curve. Workers, clients and suppliers already use it every day.

So the goal is to keep the speed of a chat and remove what gets in the way as you grow.

Where site group chats start to fail you

1. Everything lands in one feed

A delivery photo, a receipt for adhesive, a question about sockets, a birthday message and a three-minute voice note — all in a row. A week later the message you need is a hundred messages up. You can find it, but it takes time, and it is always the person responsible for that process who spends it.

2. Decisions live in voice notes

The client asks by voice note to move a socket. The worker replies “will do”. Six months later the client says: “We changed that!” — and to find the confirmation you have to listen through voice notes one by one. Text can be searched; voice can only be replayed.

3. A question for everyone stays unanswered

Someone writes in the group: “Who’s picking up the profiles from the warehouse?” Everyone sees it and assumes someone else will reply. In the evening the profiles are still at the warehouse. A question in a group chat gets an owner only when the Owner assigns one personally.

4. The job history sits in people’s phones

When someone new joins the job — a manager, a subcontractor, a second worker — they see only what has been forwarded to them. The rest of the history stays in other chats and in the memory of the people who were there before. The owner once again becomes the one retelling the context.

5. The client sees too much

When the client sits in the same group as the crew, they see the internal discussion: arguments about deadlines, questions about prices, day-to-day friction. Talking to the client and talking inside the team are two different conversations, and they need two different chats.

Signs your chat has stopped keeping up

• You answer a question that was already answered in the thread.

• To find a client decision, you scroll the feed or replay voice notes.

• A worker arrives on site and calls to ask what exactly to do.

• Materials arrive, and who ordered them for which job is sorted out by phone.

• A new team member spends a week asking what everyone else already knows.

• You spend more time on work messages in the evening than during the day.

Six rules for crew and client chats

1. At least two chats per job. One with the client, one for the team. The client gets decisions and results; the team discusses the work.

2. Record client decisions and get them confirmed. Agreed by voice or phone? Record the outcome in writing straight away: “Move the bedroom socket 40 cm to the left, extra cost €40. Please confirm.” If there is a drawing or document, attach it. A “confirmed” reply turns into a decision you can find by search in seconds, even six months later. More on recording changes in Construction change orders: how to record client decisions.

3. A pinned message as the job card. Address, contacts, door code, stage deadlines, link to drawings. A new team member reads the pin and gets the basics without a retelling.

4. Photos with a caption. “Bathroom, screed, 12 Sept” instead of just a photo. A captioned photo becomes proof of how the work was done a year later.

5. Ask a specific person. “@Mark, can you pick up the profiles by 2 pm?” instead of “who’s picking them up?”. The question now has an owner and a deadline.

6. Materials in a separate list. Material requests are the first thing to get lost in a feed. Keep a separate sheet or note per job: what is needed, who buys it, where it goes. How to set up that list is covered in Construction material management.

Where these rules reach their limit

Rules work as long as someone keeps them up. And that someone is almost always the owner: reminding people to caption photos, recording decisions, checking the materials list, telling newcomers where things are.

Every rule adds a bit of manual work on every job. As the number of jobs grows, that work grows with it, and the owner once again becomes the keeper of all the information. Rules remove the chaos, but they keep the owner as the person who pulls everything together.

The next step is a single system: key agreements are stored in the task on the job, and the chat stays one of the tools for communication.

How DOMOD handles this

In DOMOD, the rules from this article are built into the structure of each job:

• Separate chats by purpose. Each project has a client chat, an internal project chat, stage chats with the workers on that stage, and direct chats. The client talks to the Owner and Managers; workers talk in their stage chat.

• Decisions are recorded in the task. Specs, deadlines, documents, drawings, photo reports and comments sit in the task. Anyone added to the task opens it and sees everything related to it.

• Materials as a separate list in the task. The Worker adds items, the Manager approves them, and you can see where each item is: bought, in delivery, in the warehouse or on site.

• Photo reports tied to the task and date. Final reports are automatically collected into the object passport that the Client receives.

The chat stays in use as one of the tools for reaching agreements. Key decisions are recorded in documents, specs and the reports on them, where anyone on the job can find them.

More in the help centre: Project chats and Projects, stages and tasks.

DOMOD works from your phone. Managers, Workers and Clients join for free, and the first 14 days are a free trial.

In short

• A chat is great for speed and weak for storage: as you take on more jobs, messages, decisions and materials get lost in the feed.

• Record decisions so they are easy to find later: as text, a document, a drawing or a schedule. Split client and team chats, caption photos, ask specific people, manage materials in a separate list.

• The rules depend on the owner. To take that load off, you need a single system: the chat stays one of the tools for agreements, and key points are recorded in documents, specs and the reports on them.

FAQ

How many chats does one job need?

At least two: a client chat and an internal team chat. If several crews work on the job, a separate chat for each stage keeps discussions focused.

Can you run a job on WhatsApp alone?

Yes, while you run a few jobs and follow the rules in this article: two chats, decisions in writing with confirmation, captioned photos, a separate materials list. As the number of jobs grows, keeping those rules up costs more, and decisions are easier to keep in tasks, with the chat left for conversation.

How do you keep an agreement made in a voice note?

Right after the conversation, write the outcome as one text message and ask the client to reply “confirmed”. That message can still be found by search six months later.