It's 9:40 PM. A site supervisor posts a photo of a quotation in the project group chat: "Boss, need this by tomorrow morning." Twenty minutes later, someone replies "ok proceed." The PO goes out the next day.
Three months later, the finance team is reconciling the project. Which "ok proceed" was that? Who sent it — the project manager or the director? Was it for the original quotation or the revised one sent an hour later? Was it within budget? Nobody is sure, and the one person who might remember has since changed phones.
This is how procurement approvals work on a lot of Malaysian construction and O&G sites. This guide is about moving those approvals onto a proper record — without making the site slower.
Why WhatsApp Became the Approval Tool
It's worth being fair to WhatsApp. It became the default for good reasons: everyone already has it, it works on any phone with patchy site coverage, and it's the fastest way to reach a busy approver. When a job is waiting on materials, speed matters more than process.
So the goal isn't to ban WhatsApp. The problem is narrower than that: a chat message is being used as the approval record, and a chat message was never designed to be one.
Where Chat Approvals Break Down
Chat approvals don't usually fail in a dramatic way. They fail quietly, in ways that only surface later — at month-end, during an audit, or when a client disputes a bill.
- The approval isn't attached to anything. "Ok proceed" isn't linked to a requisition number, a PO, a vendor, or a budget line. Matching it back to a specific purchase means scrolling and guessing.
- It's not clear who approved, or what. A thumbs-up emoji, a "noted", a voice note — which of those counts as approval? And if two quotations were posted, which one was approved?
- Records disappear. Messages get deleted, phones get replaced, people leave the company and take their chat history with them. The approval existed, but it can't be produced.
- Thresholds can't be enforced. Most teams have an informal rule about who can approve what. In a group chat, nothing stops the wrong person from saying "ok", or a large order from being split into smaller ones to avoid a director's sign-off.
- Nobody checks the budget in the moment. The approver sees a photo of a quotation, not the remaining balance on that BQ line.
None of this is anyone being careless. It's what happens when the fastest channel also becomes the system of record. (For more on what a complete approval trail looks like, see PO Approval Basics for Malaysian Construction Teams.)
A Five-Step Plan to Move Approvals Off WhatsApp
1. Map the approval chain you actually use
Before choosing any software, write down how approvals really work today — not how the policy document says they should. Who approves small consumables? Who clears mid-size material orders? What value needs a director? Are some categories (fuel, hired equipment, subcontract works) handled differently?
You'll usually find the logic is sensible; it just lives in people's heads. Writing it down is the step most teams skip, and it's the one that decides whether everything else works.
2. Define what counts as an approval
Agree on a simple standard: an approval is a named person, at a recorded time, approving one specific request. That rules out emoji, "noted", and approvals given verbally and never written down. It sounds strict, but it's what anyone checking the record later will expect.
3. Start with one project, not the whole company
Pick one active project — ideally one with a cooperative project manager and a steady flow of purchases — and move its approvals first. A single project surfaces the real questions quickly: which approver is always unreachable, which categories need a different route, where the site team gets stuck.
If you run several companies or JV entities, resist the urge to set them all up at once. Get one right, then copy the pattern. (If that's your situation, see how multi-company routing handles separate approval hierarchies in one system.)
4. Keep WhatsApp for talking, move the decision to the record
A simple rule works well here: discuss it in the chat, approve it in the system. The site team can still post a photo and ask a question. But the request itself is raised as a requisition, and the approval happens against that requisition — not in the thread.
This keeps the speed people like about WhatsApp while making sure the decision lands somewhere permanent.
5. Set a cut-over rule and stick to it
Pick a date and one rule: no approval on record, no PO. Purchasing or the project office simply doesn't issue a PO unless the approval exists against the requisition. After the first few weeks, the new flow becomes the habit — mostly because it's the only way to get materials ordered.
What to Look For in a Replacement
Whatever you move to, it needs to be at least as easy as WhatsApp for the people using it, or they'll drift back. A short checklist:
- Easy to raise a request from site. If submitting a requisition is harder than sending a photo, it won't happen.
- Quick for approvers. Approving should take a tap or two, not a login and a form.
- Routing by value and category. The chain you mapped in step 1 should be enforced automatically, not remembered.
- One connected record. Requisition, approval, PO, and delivery/payment should link to each other, so the trail exists by default.
- A register of vendors. Approvals should be made against known, registered vendors, not whoever sent the last quotation.
- An audit trail anyone can read. When someone asks "who approved this, and when?", the answer should take seconds — see what an unbroken audit trail looks like.
What Changes for Site Teams
The biggest worry about moving off WhatsApp is that it will slow the site down. It doesn't have to. When requests live in one place, they stop getting lost in long threads, approvers see exactly what they're being asked to approve, and nobody has to chase "did you see my message?" at 10 PM.
Bilaro was built for exactly this shift — site requisitions raised from the field, multi-tier approval routing, POs issued from approved requests, and every step linked in one timestamped audit trail — so the approval your team already gives in the chat becomes a record you can actually find later.
Why isn't a WhatsApp message a good approval record?
Because it isn't tied to anything. A chat approval isn't linked to a specific requisition, PO, vendor, or budget line, it can be deleted or lost when a phone is replaced, and nothing enforces who is allowed to approve what. It shows a conversation happened, not that a specific purchase was properly approved.
Do we have to stop using WhatsApp completely?
No. WhatsApp is still useful for quick questions and site coordination. The change is narrower: discuss it in the chat, but raise the request and record the approval in a proper system, so the decision itself doesn't live in a chat thread.
Where should a company start when moving approvals off WhatsApp?
Start by writing down your real approval chain — who approves what, by value and category — then move one active project first. Set a clear cut-over rule, such as no PO without a recorded approval, before expanding to the rest of the company.