Everything happens in the group, and nothing is recorded

One scroll containing the entire business

Orders go in the group. Complaints go in the group. A photograph of a delivery challan goes in the group. A price change announced by the owner at nine at night goes in the group, followed immediately by eleven replies of the thumbs up emoji, which push it out of sight.

Then someone asks a normal question. What address did we change that delivery to. Who approved the discount on that order. When exactly did the new rate start. The answer is definitely in there somewhere, and finding it means one person scrolling for ten minutes or, more often, phoning whoever was involved and asking them to remember.

The version of this that really hurts arrives later, when the person who was involved has left the company. Their phone leaves with them, along with everything they were the only one who knew.

Why a group cannot hold a record

It is not that people are careless in groups. A group is missing the features a record needs, and no amount of discipline adds them.

There is no status. A message cannot be open or done, so a request and a completed request look identical two days later. There is no owner. A task addressed to a group of nine is addressed to nobody, and everyone assumes somebody else picked it up.

Search fails on exactly the two message types this market uses most, because a voice note contains no text and a screenshot of a payment contains no text either, so the two things you most need to find are the two things search cannot see.

Then there is duplication. The same order exists in the dispatch group, the accounts group and a group somebody made for one customer, in three slightly different versions, and no one of them is authoritative. And the ordering works against you: the newest message is always the most visible, while a record needs the important thing to stay findable long after it stopped being new.

Muting completes the picture. Once a group is loud enough to be muted, it is no longer a way of telling people something, but everyone keeps posting into it as though it were.

• No status, so a request and a finished request look the same
• No owner, so anything addressed to everyone belongs to no one
• Voice notes and screenshots that search cannot read
• The same information duplicated across several groups
• Muted members who have not seen anything for weeks

Two tests that tell you how bad it is

The first takes two minutes. Pick a decision from last month that you know was made in a group and try to find it using search alone, without phoning anyone. Time yourself. If you cannot produce the message, the group is not a record and everything the business believes it has written down is actually being held in people's heads.

The second is a count. How many groups does a new employee have to be added to before they can do their job. Write the number down and read the list of names. Most businesses find several groups with overlapping purposes, at least one whose original reason nobody can remember, and two that should be one.

Neither test requires a meeting, and between them they usually produce the first honest list of what is actually going on.

The free fix: a charter, a keyword and a daily log

Start with one purpose per group, stated in the group subject line rather than implied. Give the names a convention so they sort together on everyone's phone and so a new person can tell at a glance which is which. Something like the branch or business name followed by the function works: Orders, Dispatch, Accounts. Then merge the overlapping ones and archive the dead ones deliberately instead of leaving them to rot at the bottom of the list.

Pin a short charter in each. Three lines is enough: what belongs here, what does not, and who owns this group. The owner line matters most, because a group with a named owner gets tidied and a group without one becomes a landfill.

The keyword convention is the part that costs nothing and changes the most. Agree that anything requiring action is typed as text starting with the word ACTION, and anything decided is typed as text starting with DECIDED. Amounts, addresses and dates get typed rather than spoken, even if a voice note follows for the detail. Search now works, because the two things you always need to find both begin with a word you can search for.

Finish with a daily log. One named person posts a short numbered list at the end of each day, in a separate log group or a shared document, covering what was decided and what changed. It takes five minutes and it becomes the thing people search first, which is how a record establishes itself without anyone being forced to use a new app.

• One purpose per group, named in the subject line, with a naming convention
• A pinned charter saying what belongs here and who owns the group
• ACTION and DECIDED typed as text so search can find them
• Amounts, addresses and dates typed, not left inside a voice note
• A five minute daily decision log posted by one named person

What a system adds, and when the group is fine as it is

The parts worth handing over are the ones the group structurally cannot do. A message that needs action becoming a tracked item with an owner and a due date. Voice notes transcribed and attached to the order they concern, so the content becomes searchable text. A history that lives somewhere other than a set of handsets, so a resignation does not take the record with it. And a single view of one customer's history rather than three partial views in three groups.

Adoption decides all of it. A tidy tool nobody opens is worse than a messy group everybody reads, because at least the messy group is where the information genuinely is. Anything you introduce has to be reachable from the same phone people are already holding, and it has to be faster than typing into a group, or people will simply keep typing into the group.

There are cases where you should leave it alone. A short project with one owner and a clear end date works fine in a group, and formalising it costs more attention than it saves. A group of five people who talk all day does not need a charter. And if the group is confusing because roles in the business are unclear, a new system will make the confusion neater without making it smaller, so sort out who decides what before you sort out where they type it.

A voice note is a message. A typed line with an amount in it is a record. The difference only matters on the day somebody disputes it.

After the charter, what turning a group into a record involves

Do the charter, the naming convention and the daily log with your own team first. They cost nothing, they can be in place by Friday, and for a business running two or three groups they are the whole answer. Keeping that in-house permanently is a legitimate outcome, and the article is right that a group is fine as it is for plenty of businesses. What breaks it is scale: a dozen groups, staff turnover, and a decision that has to be findable a year later by somebody who was not there.

There is no price on this site. What moves the number is how many groups have to be watched, whether messages have to be read out of images and voice notes, how many tracked items a day the traffic actually produces, and who maintains it afterwards. The audit takes the first week and its output is the charter written properly rather than any software. One piece is live inside a fortnight, and it is usually the daily log assembled on its own instead of typed by whoever remembered.

The system turns a message into a tracked item with an owner and a due date, and then stops. It does not decide whether something is a complaint, a price change or an instruction, and where it cannot tell it hands it to a person with the message attached. Any price, any commitment and any complaint wait for human approval. A system quietly interpreting a nine o'clock message from the owner as a policy change is worse than the scroll it replaced.

The published work behind this is RM Gulistan Engineers in Karachi, where three purpose built ERP systems cover accounts, HR and inventory inside an engineering and contracting business, which is the trade this problem tends to be worst in. Ibrahim owns build and workflows at Wobble, which works from Karachi, bills month to month and carries 25 engagements across six countries.

Common questions

How many WhatsApp groups should a business have?

As few as have distinct purposes, each with a named owner and a pinned line describing what belongs in it. A useful test is whether a new employee can be told which group to post in without a conversation. If they cannot, you have more groups than purposes.

How do I make WhatsApp searchable?

Agree a keyword convention and type the things that matter as text. Search cannot read a voice note or a screenshot, so any amount, address, date or decision that only exists in audio or an image is effectively unfindable. Starting action items and decisions with an agreed word makes them retrievable in seconds.

Should orders be taken in a WhatsApp group?

Taking them there is fine because that is where customers and staff already are. Leaving them there is the problem, because a group has no status and no owner. The workable pattern is that the group is where an order arrives and a single record elsewhere is where it lives once it exists.

What happens to our history when an employee leaves?

If the conversation lives on their handset and their personal number, it leaves with them. Register business numbers to the business, keep account ownership inside the company, and make sure at least the decisions are captured somewhere a departure cannot remove. This costs nothing at setup and is painful to unwind afterwards.

Is a project management tool the answer?

Only if people will actually open it, which is the question worth testing before buying anything. Many teams do better by keeping the conversation in WhatsApp and moving only the record out, rather than by asking everyone to change where they talk. The record has to be somewhere durable, but the talking can stay where it already happens.