How we start with you — and everything you might ask.

A Rabaed subscription is annual and per project, and covers all of the project’s parties and users at no extra cost to them. If you have more than one active project, there is a multi-project discount that grows with the number of projects.

Rabaed’s guarantee runs for 60 days from activation: if you decide to stop within them, we refund the full amount paid and hand you a complete copy of your project’s record. The record is yours whatever happens.

Going live on Rabaed takes days, not months: our team comes to your site, sets up the project, its forms and its parties, and everyone starts from where the project has got to.

Yes, Rabaed’s forms are Saudi: work inspection requests (WIR), material inspections (MIR), non-conformance reports (NCR), approvals and letters — in Arabic and in the formats our projects use, tailored to each project.

Yes, Rabaed can go live on a project that has been running for a year: we start from where you have got to — your current approved documents are uploaded, and new requests start on the platform from day one.

Your project’s record in Rabaed is yours after the project or the subscription ends. You choose either to keep access to it with a nominal annual subscription, priced by the size of the data at the end of the project, or to receive a complete copy of it on an external drive.

An Excel file and a shared folder keep copies, not the process: two dates for the same document, an old number on the dashboard because nobody had time to update it, and access locked once the project ends. In Rabaed a document has one approved revision, every request and approval is documented and dated with the name of whoever made it, and the record outlasts the project.

Yes, Rabaed supports English for non-Arabic teams: the interface is Arabic first, and is available in English for engineers on the same project who do not speak Arabic.

WhatsApp, email and Excel carry messages but build no record: the request becomes a chat, the approval is buried in a thread nobody finds, and the file is copied until one document has two dates. In Rabaed a request has a reference number and a receipt with a name and a time, the approval and its notes sit inside the document itself, and there is one approved version.

A WhatsApp group delivers the message and proves nothing: no reference number for the request, no receipt with a name and a time, and no limits to stop one party reading another’s correspondence. Rabaed keeps the request and the approval in one record that the owner, the consultant and the contractor each see, within their own permissions.

Email delivers the message and keeps no record of the process: the approval arrives in another thread nobody can find months later, and there is no receipt with a name and a time to prove the request arrived at all. In Rabaed the approval and its notes sit inside the document itself, and the record outlasts the project — so an approval that exists can be proved.