Product

Rabaed’s units — and what each party sees of them.

Four units that cover everything passing between the parties, then what each party sees when it opens the platform, then what stays inside its own side and never crosses to the others.

Parties using Rabaed right now
Nawah Real Estate InvestmentStaterraAlsharq Engineering ConsultantsShaheen Engineering ConsultantsNorth InjazatAmak BuildSmart DirectionsSika
The platform

Four units. One record gathers them.

01 / 05

Official correspondence

A letter with a reference number, and a receipt nobody can deny.

Letters, meeting minutes, RFIs — numbered automatically, with an automatic receipt that records who received what, and when.

Any party→Any party
Official correspondence in Rabaed: letters with reference numbers, their reply status and how long each party has waited
02 / 05

Approvals and requests

From material approval to inspection: one path, contractor to consultant.

Supplier, material, drawing and document approvals · inspection requests (WIR), material inspections (MIR) and permits to work · and the other way: NCRs, site instructions and final snag lists.

Contractor→Consultant·Consultant→Contractor
Rabaed’s approvals board: draft, internal review in the contractor engineer’s and project manager’s lanes, then awaiting approval and approved
03 / 05

Daily site report

What happened on site today, with the owner before the day is out.

Labour, equipment, weather, the day’s output, photos — sent from a phone on site, and on the owner’s dashboard at once.

Site→Consultant→Owner
A daily report in Rabaed: weather and site, the site staff and labour by headcount and hours, and the activities and photos
04 / 05

Documents and revisions

Everyone on the latest approved revision — and nobody sees more than is theirs.

One repository for the project: drawings and documents with their revisions, only the approved revision visible on site, and set permissions for each party.

OwnerConsultantContractor
Rabaed’s document store: folders, and a table of files by version, type, source ID and who uploaded each
The output

The documented Record

Three parties. One record.

Every document in Rabaed carries its full history: when it was sent, who received, checked and approved it — with what notes, and when. Not a feature you switch on, but the result of every step.

Rabaed’s stamped approval sheet: four signatures by role, company and time of action, approval code B, and the stamp
Tailored to the project

Does your project need more?

Per project

Schedules and progress

Import Primavera P6 and MS Project schedules, the critical path, and the effect of every schedule update on the handover date.

Ask about them in the demo →
Per project

Bills of quantities and payments

An interactive bill of quantities, and payment applications built on the requests actually approved — not on what gets written at month end.

Ask about them in the demo →
For each party

What does each party see when it opens the platform?

In Rabaed each party opens its own part of one record: the owner, a dashboard of every project and what awaits approval; the consultant, one list of the contractor’s requests and their status; the contractor, one request, knowing who got it and when. Each side has its permissions, and Arabic forms to Saudi standards.

One dashboard for all your projects.

What is waiting for your approval, what is past its deadline, and what happened on site today — without a progress meeting, and without an Excel file that needs someone to update it.

“I don’t have time to keep up with a new system.” You don’t go in to keep up; you go in to approve. Everything else reaches you, ready to read, on one dashboard.

What the owner sees in Rabaed: one project dashboard with its approval indicators and the project’s parties

The contractor’s requests in one list.

Every inspection and approval request in front of you with its status. Approve with your notes from the office or on site, and issue NCRs and site instructions from your phone — all recorded with your name and time.

“It will make us answer for delays.” The opposite: it records that you answered on time, and records a request that reached you incomplete just as it arrived.

What the consultant sees in Rabaed: the table of approvals and requests by status, discipline and type

One request instead of five messages.

Submit the request, know who received it and when, and know its status without a phone call. And if the approval is late, your record is ready to show when you sent it and when it arrived.

“It will be used against us.” The record is the same for everyone: it records your submission on time just as it records a late reply to it.

What the contractor sees in Rabaed: the request’s details, and approvals naming everyone who acted and when
Arabic forms to Saudi standardsOne approved revisionPermissions for each partyWorks from your phoneIn English for non-Arabic teams
Inside each party

What stays with you, and what crosses to the other side?

Each party in Rabaed — contractor, consultant and owner — has a full internal review and approval cycle before it sends anything, which the other two never see: not its drafts, not its notes, not how many times it went round. What crosses officially is the transaction alone, dated, with the name of who sent it.

Contractor
Prepares the request before sending it.
Internal cycle · private
  1. 1Site engineer
  2. 2Technical office
  3. 3Project manager
Revise and review inside — no limit, no trace outside
Crosses officiallyWork inspection request · material approval · letter — dated, with who sent it.
Consultant
Reviews and decides before replying.
Internal cycle · private
  1. 1Discipline engineer
  2. 2Supervision manager
  3. 3Project manager
Revise and review inside — no limit, no trace outside
Crosses officiallyApproval or rejection with notes · non-conformance · site instruction.
Owner / developer
Weighs the decision before approving.
Internal cycle · private
  1. 1Project manager
  2. 2Contracts
  3. 3Decision maker
Revise and review inside — no limit, no trace outside
Crosses officiallyConsent · reply to a letter · payment approval.
What stays inside your sideDrafts, internal notes, objections, and how many review rounds it took. Work freely inside your own walls — nothing counts against you until you send it.
What crosses to the othersOnly the official transaction, at the moment it was sent and with the name of who sent it. From that moment it becomes part of the documented Record.
How we start with you

Our team on your site. All three parties on the platform within days.

  • 01 · Set upWe set up the project and its forms, invite the owner, the consultant and the contractor — and spend 15 minutes with each team.
  • 02 · Go liveIn under a day, with no stoppage. Everyone starts from where the project has got to.
  • 03 · Guarantee60 days from activation — or we refund the full amount, and hand you a complete copy of the record.
Details and FAQs →

Book a live demo on your project

30 minutes · on one of your own projects
60 days full money-back guarantee
Enter your full name (at least two letters)
Enter a valid email address
Choose your role on the project
Enter a valid mobile number (6 to 15 digits)
The company name is too long
Enter the number of projects in figures only
We use your details only to arrange the demo, and never share them with any third party.