- 01
Market
Saudi Arabia
- 02
Written for
COO, Plant Manager
- 03
Decision
Run work orders, planned maintenance, SLAs and contractors on one system
- 04
Languages
EN · AR
Information security for software delivery

ISO/IEC 27001
ISO/IEC 27001 certified
One fault, end to end
Where a reported fault becomes a provable response
The stages below are where estates lose the record today — a report in a chat thread, a dispatch by phone call, a completion nobody verified. The software’s job is to make each stage write to the same record.
The report
A tenant, a guard or a cleaner notices the fault and tells whoever is nearest.
The report becomes a work order against the specific asset and location, whatever channel it arrived on — and the SLA clock starts at that moment, not when someone gets around to logging it.
- Work orders
- Asset register
Triage and dispatch
Someone decides how urgent it is, who attends, and whether it is an in-house or contractor job.
Priority follows the SLA category, and the assignment reaches the technician or contractor as a job with the asset history attached — not a forwarded photo with “can you look at this”.
- Dispatch
- Contractor portal
The job on site
The technician diagnoses, fixes or escalates, and uses parts.
Arrival, work done, parts used and photos land on the work order from the technician’s phone, so the evidence is captured where the work happens rather than reconstructed at month end.
- Mobile app
- Parts inventory
Verification and closure
The job is declared done — the point where a recurring fault either gets noticed or gets closed into invisibility.
Closure requires the evidence and, where the SLA says so, the reporter’s confirmation; the asset’s history accumulates, so the third repair of the same chiller in a quarter surfaces as a pattern instead of three closed tickets.
- Work orders
- SLA reporting
The planned half
Estates that only fix what breaks pay for it twice
A facilities operation visible only through its reactive work orders is running blind on the larger half of its job. Planned maintenance — the filter changes, the pump inspections, the lift servicing that keeps plant inside its warranty and its lifespan — either exists as generated, scheduled work orders or it exists as good intentions. The software’s contribution is mechanical and decisive: every asset carries its maintenance schedule, the system generates the jobs ahead of due dates, and an overdue planned job is as visible as an open fault. Over time the ratio between planned and reactive work becomes the single most honest indicator of whether an estate is being managed or merely rescued.
This matters doubly for the estates Saudi Arabia is building now. A new district, campus or tower delivered this year arrives with thousands of assets under warranty and a defect-liability period that expires whether or not anyone recorded what failed during it. An operation that starts its FM software after handover has already lost the asset registers, the commissioning data and the early failure patterns — the cheapest information it will ever have about its own buildings.
The contractor layer
Managing the companies that do the wrenching
Most Saudi estates deliver hard FM through contractors, which means the software has to manage firms, not just technicians. These are the four records that keep that relationship honest.
The scope each contract actually covers
Which assets, which fault categories, which hours. When this lives in the system, a job routes to the right contractor automatically — and a claim that something is out of scope is settled by the record, not by whoever argues longest.
The SLA the contractor signed, measured on their jobs
Response and resolution clocks run per job against the contract’s own targets, so the quarterly review reads from the system instead of negotiating from memory.
Evidence before invoices are approved
A contractor invoice line reconciles against completed, verified work orders. The gap between what was billed and what the record shows is where an estate quietly loses money every month it goes unmeasured.
Access that expires with the contract
Contractor accounts and site permissions are created against the contract and closed with it, so the technician of a supplier you parted with two years ago is not still receiving work orders — or holding a gate pass.
Our role
What we build for an FM operation and what the operation keeps
- 01
The record everything writes to
We build the work-order, asset and SLA model that every report, job, part and sign-off lands on — sized to your estate’s asset structure rather than a generic template.
- 02
The field reality designed in
The technician’s app works in Arabic and English, tolerates the plant room with no signal, and asks for less typing than the WhatsApp thread it replaces — because software the field refuses is a report generator, not a system.
- 03
Reporting that reads, never re-keys
SLA performance, planned-versus-reactive ratios and contractor scorecards are drawn from the operational record itself, so the number in the client report is the number in the system.
The maintenance itself — the technicians, the contracts, the service levels you promise your clients — stays with your operation and its suppliers; we build the system that lets you run it on evidence and prove what it delivered.
Common questions
What buyers ask
We run FM on WhatsApp groups and Excel today. Where do we start?+
With the reactive work order, because it is the record everything else hangs from and the one your team touches every hour. Getting one flow live — report in, job dispatched, evidence captured, closure verified — replaces the chat threads with a record within weeks and builds the habit the rest depends on. The asset register grows as work orders are raised against real equipment, planned maintenance follows once the register is trustworthy, and contractor management follows the jobs. Starting with everything at once fails for a predictable reason: the field team is asked to change every habit in the same month, and the WhatsApp group quietly wins.
Can contractors work inside the system without licences for every technician?+
That is a commercial design question we settle in scoping, and in a custom build it is yours to decide rather than a vendor’s per-seat price list. The usual shape is a contractor portal: the firm receives jobs, its technicians capture evidence through a lightweight mobile flow, and your team sees the same record throughout — without per-technician licensing making the record expensive precisely where you need it most. What matters operationally is that contractor work lands on the same work orders and the same SLA clocks as in-house work, because two systems of record for one estate is how disputes about response times become unwinnable.
What should FM software capture during a building’s handover year?+
Three things that are cheap to capture then and expensive to reconstruct later. First, the asset register itself, loaded from the commissioning and O&M documentation while it is still complete and the contractor who produced it is still answerable. Second, every defect and failure, recorded against the specific asset — this is the evidence that turns a defect-liability claim from an argument into a list. Third, the maintenance schedules the warranties require, set up as generated planned work from month one, because a warranty voided by unperformed servicing is a cost the operation carries for years. An estate that starts its system after this window has permanently lost its cheapest data.
In this cluster
Map it to your portfolio
A walkthrough of one real fault on your estate — from report to closure — marking every point where today the record lives in a phone, a chat thread or nobody’s system at all.
Start the conversation