What is in a Saudi FM contract
The eight parts a facility management agreement has to carry, and the three clauses that decide whether the contract works or gets argued about every month.
A Saudi FM contract has eight load-bearing parts: scope split into hard, soft and specialist services, an SLA with priority-banded clocks, KPIs with a named data source, a capped service-credit regime, mobilisation, staffing and Saudization, reporting and CAFM data ownership, and term and exit.
Updated · 11 minute read
There is no FM law, so the contract is the regulation
Saudi Arabia has no dedicated facility management statute. A private-sector FM agreement is an ordinary commercial contract, with the Saudi Building Code and Civil Defence requirements driving the technical compliance layer for fire, life safety and building systems.
That has one consequence worth sitting with: anything the contract does not say, nobody will decide for you later. There is no default position on who pays for a failed chiller compressor, no statutory response time, and no implied right to the maintenance history when the contract ends. Every one of those is a drafting choice.
Public-sector FM contracts carry an additional layer. They are governed by the Government Tenders and Procurement Law, and that law is changing: a new GTPL was published on and takes effect on Government Tenders and Procurement Law: in force · , replacing the law issued under Royal Decree M/128 of 2019, with implementing regulations still to come. If you are drafting or bidding government work across that boundary, check which law governs your contract and do not plan against penalty figures quoted from the outgoing regime. We are not publishing any here for that reason.
Splitting the scope so it can be priced
Scope divides into hard services, soft services and specialist or statutory work. For every asset class the contract has to say whether the contractor does planned maintenance only, or planned plus reactive, and where the boundary between repair and replacement sits.
That repair-versus-replace boundary is the most common source of mid-term dispute in this market, and it is usually a single missing sentence. A compressor fails in year two. Is that a repair inside the fee, a repair chargeable as a variation, or a capital replacement for the client? A contract that does not answer it will produce a six-week argument and a strained relationship, every time it happens.
| Category | What sits inside it |
|---|---|
| Hard services | HVAC, electrical, plumbing and drainage, fire detection and suppression, lifts, BMS, generators and UPS, water treatment, façade and roofing. |
| Soft services | Cleaning, security, landscaping, pest control, waste, catering, helpdesk and front of house. |
| Specialist and statutory | Fire pump certification, medical gas, high voltage, lifting equipment, water tank cleaning and potable water testing, civil defence inspections. Usually subcontracted, and the contract should say who holds the certificate. |
| The boundary questions | Planned only or planned plus reactive, per asset class. Where repair ends and replacement begins. Who funds lifecycle. Who owns spares. What happens outside working hours. |
An SLA is a set of definitions before it is a set of numbers
Priority bands, commonly P1 to P4, each with separate clocks: response, meaning the ticket is acknowledged and assigned to a named person; attendance, meaning that person is on site; and resolution, meaning the fault is rectified or a temporary fix is in place with an agreed permanent-fix date.
Borrowed benchmarks with undefined terms are unenforceable, and most SLAs in circulation are borrowed. Practice clusters around minutes to hours for P1 and days to weeks for P4, but the numbers are the easy part. The definitions are what get argued about at month eight.
Three definitions carry the weight. The clock starts at ticket creation in the CAFM, not at the phone call and not when the technician is dispatched. The working-hours calendar is named, including Fridays, public holidays and Ramadan hours. And the valid pauses are listed exhaustively: awaiting parts, awaiting client access, awaiting a third-party warranty response. An unlisted pause is not a pause.
One more: define what a P1 is in terms a helpdesk operator can apply at two in the morning without ringing anybody. If the definition requires judgement, the priority assigned will track how angry the caller sounded.
A KPI you cannot compute is a monthly argument
Every KPI needs five things: a formula, a data source, a measurement period, a target, and a threshold at which it triggers something. Any KPI that cannot be computed from the CAFM without manual intervention will be disputed every month it is reported.
That last rule eliminates more bad KPIs than any amount of benchmarking. If producing the number requires someone to open a spreadsheet and make a judgement about which tickets to exclude, both parties will make a different judgement and the report becomes a negotiation.
- PPM completion on time, against the planned schedule rather than against a rebaselined one
- Reactive SLA achievement, reported by priority band and not as a single blended figure
- First-time fix rate
- Critical asset availability, with the critical asset list named in a schedule
- HSE incidents, with the reporting definition stated
- Energy against a baseline, with the baseline and the weather normalisation method fixed
- Helpdesk answer rate and abandonment
- Customer satisfaction, with the survey method and sample defined
- Staffing fill rate against the agreed establishment
Service credits, damages and the cap
Distinguish service credits, which are an automatic price reduction usually capped as a percentage of the monthly fee, from liquidated damages, which compensate for a defined breach. Decide explicitly whether service credits are the sole remedy, because silence there is expensive.
An uncapped penalty regime does not buy better service. It gets priced into the bid, and you pay for it whether or not anything goes wrong. A capped regime with a cumulative failure threshold behind it works better: miss enough to cross the threshold and the contractor owes a rectification plan, then a step-in right, then termination. That escalation is what actually changes behaviour.
Consider an earn-back. A contractor who has already lost the maximum credit for the month has no financial reason to recover before the month ends, which is precisely backwards. Letting credits be earned back on sustained recovery keeps the incentive pointed forwards.
For government contracts the cap is set by the governing procurement law rather than negotiated. Confirm which version of the GTPL governs your contract and take the cap from the instrument itself.
Staff transfer is a route you establish
Do not assume incumbent staff move with the contract. Before mobilisation, establish the transfer route for each person under the Labour Law and Qiwa rules: who is moving, on what contract, and how each work permit and iqama transfers through Qiwa.
Labour Law Article 18 addresses a change in the establishment's ownership or legal form, such as a merger or a partition: employment contracts remain in force, service is deemed continuous, and predecessor and successor are jointly and severally liable for accrued entitlements. That is a business transfer. Whether it reaches a service contract re-tender is a question for an employment lawyer with the facts in front of them.
The practical consequence for the programme is visa lead time. Transfers through Qiwa under the Labour Reform Initiative take as long as they take, and on a mobilisation plan that is usually the longest single item, longer than recruitment. Price it and schedule it first.
Then contract for the rest of the employment layer explicitly: Saudization band commitments under Nitaqat, Wage Protection System compliance, GOSI registration, and who bears iqama, medical and levy costs. Leaving those to be assumed is how a bid that looked competitive stops being deliverable.
Mobilisation is a schedule, not a period
Four to twelve weeks depending on headcount and asset count, written as a contract schedule with named deliverables and sign-off gates. Unpaid mobilisation is under-resourced mobilisation, and it shows up as a bad first quarter every time.
The asset register is the deliverable that matters most and the one most often carried over unverified from the last contract. A tendered asset register that nobody has walked means every bidder priced a different building, and the cheapest bid is simply the one that guessed lowest.
- Verified asset register, walked and reconciled rather than inherited
- CAFM configured and loaded, with the asset hierarchy agreed
- PPM schedules built from manufacturer and statutory intervals, not from a generic library
- Critical spares identified and held
- Permits and statutory certificates transferred into the incoming provider's name
- Manpower recruited or transferred, inducted and site-familiar
- HSE documentation submitted and approved
- Go-live sign-off, with anything incomplete carried as a named open item
Reporting, data ownership and getting out cleanly
Specify the monthly report's format, deadline and review cadence, and state that the CAFM data, asset records and O&M documentation are the client's property, exportable in a named format on request and at exit. If the contract is silent, you find out who owns the data at exit.
Not owning the CAFM data is the quiet failure that compounds. Three years of maintenance history, asset condition and failure patterns sit in the contractor's system, and at re-tender the client goes back to market as blind as last time. Every subsequent bid is a guess, every mobilisation rebuilds the register, and the incumbent has a structural advantage nobody intended to give them.
The exit plan belongs in the contract at signature, not negotiated at termination: handover period, data and asset handback in a named format, spares transfer, and a duty to cooperate with the incoming provider. Alongside it, the commercial frame that stops the whole thing drifting: term and renewal, price review or indexation, variation pricing, performance bond and retention, assignment and novation, insurance limits, and termination both for convenience and for cause.
The three clauses worth an extra hour of anyone's time, because they cause most of the disputes: the repair-versus-replace boundary, the SLA clock definition, and CAFM data ownership.
What clients ask before going to tender
Do employees transfer automatically to a new FM contractor?
Do not plan on it. Establish the transfer route under the Labour Law and Qiwa rules before mobilisation, with the work permit and iqama moved through Qiwa. The timeline for that is usually the binding constraint on mobilisation.
What is a reasonable penalty cap?
Commercially, service credits are usually capped as a percentage of the monthly fee, with the level negotiated against the criticality of the estate. For government contracts the cap comes from the governing procurement law, so confirm which version applies to your contract rather than using a figure from an article.
How long should mobilisation be?
Four to twelve weeks, driven by headcount and asset count. Visa processing rather than recruitment is normally what sets the date, so build the schedule backwards from that.
Who owns the CAFM data?
Whoever the contract says. If it says nothing, you will discover the answer during exit, which is the worst possible moment. Make the client the owner, name the export format, and put a right to extract on request rather than only at termination.
Should hard and soft services be bundled?
Bundling gives one accountable party and one mobilisation, which is worth a lot on a complex estate. Unbundling gives price transparency and makes benchmarking possible. Neither is automatically right, and the decision should be made on how much internal capacity you have to manage interfaces.
Is ISO 41001 relevant?
ISO 41001 is the facility management system standard and ISO 41012 gives guidance on strategic sourcing and developing FM agreements. Useful as drafting references. Neither is a legal requirement in the Kingdom.
What is the single most common drafting mistake?
Buying headcount instead of outcomes. A contract that specifies twelve technicians has bought twelve technicians, and when the response times slip there is nothing to enforce, because the deliverable was attendance and attendance is happening.
Next
Integrated facility management
Hard, soft and specialist services run as one programme with one accountable party.
Read moreITF FMVendor and subcontractor management
The specialist layer, and who holds the statutory certificate when it is subcontracted.
Read moreToolFM scope builder
Assemble a scope split, an SLA priority skeleton and a mobilisation deliverable list for your own building.
Read moreITF FMHow the FM cycle runs
Enquiry to closed work order with evidence attached, which is the thing a monthly report is drawn from.
Read morePart of one system
Every division keeps records to the same standard, so the second one you need works the way the first one did.
Start from the asset register
A verified asset register is what makes every other clause enforceable: it sets the scope, it prices the PPM, it defines the critical list the SLA protects. Tendering without one guarantees you compare four different buildings.