At 11:04 AM on a Tuesday, Ravi, the site engineer on a 3BHK in Whitefield, sends a voice note to the project group. Forty-one seconds. In it, somewhere after an update on the false ceiling and a question about the balcony light, he says the tile box for the guest toilet is short by about eight pieces, and the tiler can only work till lunch tomorrow unless more come.
The group has nineteen members. The owner, two designers, the PM, three vendors, the accounts person, a purchase executive, Ravi, two supervisors from other sites who were added once and never removed, and, for reasons nobody remembers, the client’s brother-in-law.
By 11:30, the group has moved on. A designer posts four renders for another room. A vendor sends a photo of a delivery. Someone forwards a good-morning image. The client’s brother-in-law asks if the modular kitchen will have a tall unit.
Arjun, the PM, finally opens the group at 6:10 PM in an auto between sites. There are 214 unread messages. He scrolls, skims, catches the renders, the delivery photo, the kitchen question. He does not play a 41-second voice note from 11 AM. Why would he? Ravi usually just gives updates.
He finds out about the tile shortage at 9:30 the next morning, when the tiler calls to say he is leaving for another job. The guest toilet slips by four days.
Everyone was in the group. Nobody had the message.
It is tempting to blame Ravi for burying it, or Arjun for not listening. Neither is fair. Ravi did exactly what he was asked to do: report on the group. Arjun did what any person does with 214 messages: triage by skimming. The group itself is what failed.
A WhatsApp group is a wonderful tool for one thing: getting everyone’s attention right now. It is a poor tool for almost everything a project actually needs, because it treats every message the same. A good-morning image, a render, a delivery photo and a blocking shortage all arrive with the same ping and sink at the same speed.
A group chat is a river. Decisions need a ledger. You cannot run a project from something that only flows one way and never stops.
Why a group fails as a record
Most firms already feel that the group is chaotic. What is worth naming is exactly why, because each reason points at a fix.
- No owner. A message to nineteen people is a message to nobody. Everyone assumes someone else saw it.
- No state. A message cannot be open or closed. The tile shortage at 11 AM is still sitting there, looking exactly as urgent or unurgent as it did, whether it was solved or not.
- No priority. Blocking issues and small talk look identical. Voice notes are the worst: you cannot skim them, so they get skipped.
- No memory you can search. Try finding “who approved the change to the wardrobe handle” three months later. It is in there. You will not find it.
- Too many people. Vendors see each other’s rates, clients see internal arguments, and old members never leave.
- One thread for everything. Design, site, purchase, payments and client questions all share one stream, so each one drowns the others.
None of this is WhatsApp’s fault. It was never meant to be a project system. The trouble is that most firms adopted it as one, by default, because it was the one tool everyone already had.
What a lost message really costs
The cost of the tile shortage is not eight tiles. It is the days the room waits, the tiler you lose to another job, the next trade that cannot start, and the evening Arjun spends rearranging three other sites to fit it back in.
| Tiler leaves for another job, returns after | 3 days |
|---|---|
| Plumber’s fixture installation pushed back | 1 day |
| Total slip on the guest toilet | 4 days |
| Tiler’s idle half-day, paid anyway | ₹1,800 |
| Rush delivery of 8 tiles from the dealer | ₹1,200 |
| PM time rearranging the schedule, 3 hours at ₹600 | ₹1,800 |
| Direct cost, plus a 4-day slip | ₹4,800 |
Every figure here is an illustrative example. Rates, delays and amounts vary by city, trade and project.
Four thousand eight hundred rupees and four days, from one voice note nobody played. Most PMs can name three or four of these from the last month alone.
And the shortage is the easy case, because it eventually announces itself when the tiler leaves. The harder cases are the decisions that sink without a sound: a client approving a change in passing, a vendor agreeing to a revised date, a designer confirming a finish. Those surface months later, at the final bill or at handover, when nobody can find the message and everyone remembers it differently.
Do not ban WhatsApp. Stop using the group as the system.
The instinct, after a week like this, is to say “from now on, no more WhatsApp, everyone uses the new app.” It almost never works. Your site team lives on WhatsApp. Your vendors live on WhatsApp. Your clients live on WhatsApp. Asking all of them to move is a fight you will lose by the second week.
The better move is to keep WhatsApp as the channel and stop treating the group as the record. Here is what that looks like in practice, with or without any software:
- Split the groups by audience. One internal site group (PM, engineer, purchase). One client group, where only updates and decisions go. Vendors are spoken to directly, not in a crowd. Nobody else gets added.
- Give every issue an owner and a state. When something blocks work, it goes onto a short list: what, which room, who owns it, by when. Open until someone closes it. A shared sheet works if the PM actually opens it.
- Ask for one line before the voice note. Teach the site team to start with the headline in text: “SHORTAGE: guest toilet tiles, 8 pcs, need by tomorrow noon.” Then the voice note for detail. Skimmers catch the headline.
- Fix a rhythm. A start-of-day message from site saying what is happening today, and an end-of-day message saying what got done and what is stuck. Two predictable messages are worth more than forty random ones.
- Put decisions somewhere else. Approvals from the client, changes to scope, and anything that affects money get written into a place you can find later, with a date and a name. The chat is where they are discussed, not where they live.
- Clean the group every project. When a project hands over, archive the group and start fresh for the next one. Old members, old jokes and old renders do not travel.
The client in the group
One word on clients, because they are often the loudest members of the project group. A client who sees every internal message also sees every internal problem: the vendor arguing about a rate, the designer and engineer disagreeing, the shortage that has not been solved yet. They lose confidence not because things are worse than usual, but because they are seeing the kitchen of the restaurant.
Clients deserve a calm, regular update: what happened today, what is next, what we need from you. That is a different thing from a seat in your site group. Most clients, given the choice, prefer the calm update.
How Pakka handles it
Pakka keeps the team on WhatsApp and takes the record out of the group. On the Ops Desk, site engineers send voice notes, photos and videos as they already do, and each one becomes a task, an issue or an approval, with an owner. Ravi’s tile shortage would have become an issue with Arjun’s name on it at 11:04 AM, not a 41-second clip in a stream of 214 messages.
The engineer’s day has a rhythm built in: a morning Starting today and an evening Update tasks, two taps a day. The office sees every site on one screen, marked on track, at risk or critical, and why. And the client gets a calm evening update on WhatsApp with a link to their portal, instead of a seat in the site group.
WhatsApp stays the channel. It just stops being the filing cabinet.