WhatsApp, email and Excel carry the message, but they do not create a record: no reference number, no receipt nobody can deny, and no single status all three parties see. Rabaed keeps all of it in one documented, dated place, so two months later you do not need a screenshot to prove you sent it.
The same approval… two ways
Take one material approval and go through it twice: once the usual way, and once on Rabaed. The four steps are the same — the request, the receipt, the approval, and the question two months later — but what is left at the end is entirely different, and that difference shows on the day of a dispute, not the day it was sent.
- The request — the usual way: printed, signed by hand, photographed on a phone. On Rabaed: an approval request with a reference number and its attachments.
- The receipt — the usual way: “send it as a formal email”, and the request turns into a conversation. On Rabaed: an automatic receipt with a name and a time, which nobody can deny.
- The approval — the usual way: a reply a week later, in another thread nobody can find. On Rabaed: an approval with comments, and the Owner sees the status as it happens.
- Two months later — the usual way: “I never got the approval”, and the proof is a screenshot. On Rabaed: open the document — sent, received, reviewed, approved.
WhatsApp: quick to send, powerless to prove
WhatsApp is the quickest way to alert a colleague, and the worst way to keep an approval. The message disappears into a conversation that runs for months; no reference number ties it to the document, and nothing in it tells a draft or a personal view from a formal decision. When there is a dispute the proof becomes a screenshot, and a screenshot is not proof.
And there is more to it: a conversation belongs to the phones it is on. An engineer leaves the company, and half the project’s history leaves with him.
Email: keeps everything, finds nothing
Email does keep the messages, and that is its problem: it keeps them all alike. The approval that came months ago is in there somewhere, but finding it takes someone who remembers the subject line and who was copied in. And nothing in email says that this particular message is the final decision.
Because each party has its own inbox, there is no single version of the truth: the Contractor has one thread, the Consultant another, the Owner a third — and all three are incomplete.
Excel: a picture of a day gone by
A spreadsheet describes the status; it does not make it. Someone opens it and writes in what they understood from a message they received, and the file becomes an opinion rather than a record. As soon as the engineer is busy for a week the number on the dashboard is out of date, and a decision that was meant to rest on reality rests on it.
Then come the copies: two files, two dates for the same document, and back to paper to be sure.
What exactly does Rabaed add?
Rabaed does not add a fifth channel to the four; it replaces the process itself. The request is raised once with a reference number, received automatically with a name and a time, approved with comments visible to all three parties, and kept with every one of its steps inside the document — not in four places, each needing someone to remember it.
- An automatic reference number for every transaction, and an automatic receipt with who received it and when.
- One status for each request, seen by the Owner, the Consultant and the Contractor at the same moment.
- One approved version visible to the site, and defined permissions for each party.
- A full internal review cycle within each party, which the other two never see.
- A Record that stays after the project ends, and belongs to the project’s Owner in every case.
So when is WhatsApp enough?
It is enough when a message has no contractual weight: a note that the concrete has arrived, or a question about when a meeting is. The trouble starts when something that costs time or money goes through it — a work inspection request, a material approval, an extension of time. Then what is needed is not a message that arrives, but a transaction that can be proven.
The four units, and what each party sees in them, are on the Product page.