Running a construction project on WhatsApp: what works and where it breaks

Almost every construction project in India runs on WhatsApp groups, and for good reason. Here is what they do well, the five places they reliably break, and the rules that fix most of it — with a one-page communication plan to pin in your project group on day one.

By Space Team·Updated

Why every project runs on WhatsApp

Because it works. Everyone on a project already has it — the architect, the client, the site engineer and the plumber — on whatever phone they own, with nothing to install or learn. A photo from site reaches the office in seconds. A voice note says in ten seconds what would take five minutes to type. Nobody has to be convinced to use it.

For quick coordination — who is on site today, the delivery is late, the lift is down — a group chat is hard to beat, and nothing in this guide suggests giving it up. The trouble starts when the group chat becomes the only place a project keeps its questions, decisions and drawings, because a chat is built for conversation, not for records.

Where it breaks

The answer isn't with the question
A question that holds up work gets answered somewhere further down, between deliveries and greetings. Weeks later, finding which message answered which question means scrolling. It should have been an RFI.
Drawings travel as files
"Final.pdf", "Final-v2.pdf", "Final-v2-latest.pdf". The site builds from whichever one was opened last. It should have been a drawing issued against a register.
Decisions scroll away
"Going with Onyx" is a decision, but the options, the prices and who agreed are spread across forty messages. It should have been a recorded decision.
"Pls check" has no owner
A message to the group asks everyone and no one. Without a named person and a date, it is nobody's job. It should have been a task.
The memory lives on people's phones
When someone leaves the project, the conversation they were part of often leaves with them, and someone who joins later may never see what was agreed before they arrived.

One week in a project group

Eight messages from one week on a residential project, in the order they arrived. Four of them matter a great deal. On the right, what each of those should have become.

Project groupOne week · example project
  1. Architect

    Uploading revised ceiling RCPs for 601–603 this evening.

  2. Plumbing Agency

    Shaft clashes with the counter run in 602. Can it move 150 mm east?

    A question that holds up work

  3. MEP Consultant

    Will re-check diffuser positions once they land.

  4. PMC

    Site shut Friday for the slab pour. Plan deliveries around it.

  5. Civil Contractor

    Noted. Shifting the steel delivery to Saturday.

  6. Architect

    Shift approved by 150 mm. Update the drawing before execution.

    The answer — four messages later

  7. Client

    Going with Onyx. Please proceed with the shop drawings.

    A decision, with no options beside it

  8. Plumbing Team

    Starting shaft work Monday, once the shaft query is closed.

    Still waiting — nobody told them

What it should have become

  • Query

    Q-014 · Can the plumbing shaft be shifted 150 mm?

    Directed to Architect + PMC; answered by the architect on the query itself.

  • Task

    Confirm plumbing shaft location

    Marked “Waiting on Architect response”, and released the moment the answer landed — so the plumbing team knew.

  • Drawing

    A-602-E-104 · V9

    “Update the drawing” became a revision, issued 15 Sep 2026, with the previous one marked superseded.

  • Decision

    D-007 · Living room flooring

    Recorded as Onyx, with both options, their prices and who decided (Client).

Rules that fix most of it

If your project stays on WhatsApp — and many will — a handful of rules agreed on day one solves most of the problems above. The communication plan template sets them out on one page.

  1. One group per purpose. A group for the whole project, one for design coordination, one for site — and say in each group's description what it is for.
  2. Confirm decisions in writing, in a fixed format. Start the message with "DECISION:", say what was decided and who decided it. Then anyone can find every decision with one search.
  3. Write up RFIs. A question that holds up work goes on an RFI with a number, a location and a needed-by date. The group can carry the link; it should not carry the record. See our RFI template.
  4. Never send a drawing without its number and revision. And keep a drawing register, so "which one is current" has an answer outside the chat. See our drawing register template.
  5. Send the minutes as a PDF every week, within a day of the meeting. See our MoM template.
  6. Summarise voice notes that carry a decision. A ten-second voice note is fine for coordination; for a decision, follow it with one written line.
  7. Export the chat at milestones. At handover of each stage, export the main groups and keep them with the project files.

What to keep out of the group chat

  • Approvals that change cost, scope or programme. Those follow the contract's process, in writing.
  • The issue of drawings for construction. The chat can say a drawing has been issued; the transmittal and the register are the record.
  • RFIs that hold up work, beyond a link to the RFI.
  • Client decisions. Record them with their options, then share the outcome in the group.

Signs it's time for a project tool

  • There are more project groups than anyone can follow.
  • "Which drawing is current?" comes up every week.
  • People regularly cannot find an answer they know was given.
  • The client asks for status updates because they cannot see the project for themselves.
  • There are disagreements about what was agreed, and nobody can find the message.

How Space fits alongside WhatsApp

Space does not ask a site to stop using WhatsApp. It gives the questions, decisions and drawings a place of their own, and keeps the conversation about them attached to them.

  • Chat in Space works the way people already chat: a project group, private groups and one-to-ones, with photos and files.
  • Type # or / in a message to raise a task, query or decision from it, and the message and the record point at each other.
  • Conversations about a task, query or decision stay on that record instead of disappearing into a group.
  • Voice and video calls start from any chat, and anyone can join from a link without an account.
  • Everything outstanding for one agency, or for one room, prints as a PDF to send on WhatsApp — which is how most of a site receives instructions.

Questions

Is WhatsApp good for construction project management?
It is excellent for quick coordination and photos from site, and poor as the only record of questions, decisions and drawings. Most projects do best using it for conversation and keeping those records somewhere built for them.
How many WhatsApp groups should a construction project have?
As few as do the job — typically one for the whole project, one for design coordination and one for site. More than that, and people stop reading them.
Should the client be in the site WhatsApp group?
Usually not the day-to-day site group, which is busy and operational. A smaller group for the client, the architect and the PMC, with decisions and key updates, works better for everyone.
How do I keep track of decisions made on WhatsApp?
Agree a format — start every decision with "DECISION:" — and copy each one into a decision log or project tool with its options and who decided. Then confirm the outcome in the group.
Can WhatsApp messages be relied on as a project record?
Messages are often relied on later as evidence of what was said, but they are scattered, easy to miss and tied to people's phones. For anything with contractual weight, follow your contract's process and keep a proper written record; take legal advice where it matters.

Conversations

Keep chatting the way your team already does — and keep the conversation with the work it is about.