Approvals over WhatsApp: the compliance risk nobody has written down

Ask most operations teams how a request gets approved and the honest answer, after enough follow up questions, is a WhatsApp thread or an email chain. Someone asks, someone with authority replies with a thumbs up or a one line yes, and everyone moves on.

Why this works right up until it does not

It works because the people involved trust each other and the decisions are usually correct. It stops working the moment anyone needs to answer a very specific question: who approved this, exactly when, under what version of the request, and what did they actually see before they said yes.

Where this becomes expensive

• A disputed invoice, where the only evidence of sign off is a message that has since been deleted or a phone that has since been replaced.
• A safety incident, where an auditor wants a documented approval chain and finds a text message instead.
• A vendor payment approved by someone who was, on paper, not authorized to approve it, and nobody can say who actually gave the go ahead.

None of this means the team is careless. It means the approval process was never built as a process. It grew, informally, out of whatever tool was fastest to open.

What an approvals app actually buys you

Not more bureaucracy. The opposite: a request moves through the same number of steps it does today, but each step is logged, timestamped and tied to a specific person's login instead of a phone number. When an auditor or a dispute asks the question, the answer already exists, instead of needing to be reconstructed from memory and screenshots.