Facility management across Egypt, the Gulf, and the broader MENA region has matured unevenly. In Dubai, Abu Dhabi, and Riyadh, the integrated FM market is dominated by a handful of large operators delivering hard and soft services under multi-year performance contracts. In Cairo, Alexandria, and most secondary MENA cities, the reality is closer to a fragmented mix of reactive vendors, in-house teams, and a small number of contracted operators serving the top tier of commercial real estate, hospitals, and education campuses.
This article is for multi-site operators and institutional property owners evaluating how to procure FM in this environment. It describes the service models actually in use, the SLA realities behind the marketing language, what coordinated multi-site delivery looks like in practice, and the structural difference between a contracted operator and an incident-by-incident vendor.
Section 1
The service models actually in use
FM contracting in the region falls into four broad models. Each has a legitimate place; the failure mode is procuring under one model expecting the behaviour of another.
- Total FM (TFM): one contract covering hard services (HVAC, electrical, plumbing, BMS), soft services (cleaning, security, landscaping), and management — typical in Gulf prime real estate.
- Integrated FM (IFM): one contract covering hard and soft services with the operator coordinating sub-specialists, but management retained by the client — common for institutional campuses.
- Bundled services: two or three services under one contract (e.g. HVAC + cleaning) with the rest procured separately — the practical Egyptian institutional default.
- Single-service contracts: one specialist discipline per contract — cheapest unit price, highest coordination burden on the client.
Section 2
SLA realities behind the marketing language
Most FM RFPs in the region include an SLA schedule. Most contracts do not measure against it after month three. A workable SLA regime requires response and rectification times tied to a graded fault classification, a CAFM system both parties actually use, and a service-credit mechanism with real financial bite. Without these three elements, the SLA is decoration.
- Fault grading: P1 (safety/critical), P2 (significant impact), P3 (degraded service), P4 (cosmetic) — each with its own response and rectification time.
- CAFM system: tickets, work orders, asset register, and PPM schedule all in one platform, accessible to both parties — not in the operator's internal system only.
- Service credits: percentage of the monthly service fee withheld for missed SLAs, with a cap and a dispute mechanism — meaningless if set at 0.5% of the monthly fee.
- Monthly performance review: scheduled, attended by both sides, with a documented agenda and minutes — the operator's monthly report alone is not a review.
Section 3
Multi-site coordination in practice
Multi-site operators (retail chains, bank branches, healthcare networks, education groups) face a coordination problem that single-site FM contracts do not solve. The realistic options are a regional master service agreement with a single operator, a panel arrangement with two or three operators by geography, or a centrally-managed network of local vendors with the client retaining the coordinating role.
- Single regional MSA: simplest governance, but exposes the client to operator dependency and limits competitive tension at renewal.
- Panel by geography: two or three operators covering different regions, with consistent SLA terms — the institutional sweet spot for networks of 20+ sites.
- Client-coordinated local vendors: cheapest in unit price, but requires a real in-house FM function — usually fails when staffed by a single coordinator.
- Reporting: a single dashboard across sites is the differentiator; per-site reports that the client has to consolidate manually defeat the purpose.
Section 4
Contracted operator vs incident-by-incident vendor
The structural difference between a contracted FM operator and a reactive incident-by-incident vendor is not the work performed — it is who carries the planning, the asset register, and the institutional knowledge of the building. Reactive vendors do work when called; contracted operators own the lifecycle of the building's mechanical and electrical systems and prevent the calls.
- Asset register: a contracted operator maintains it as a deliverable; a reactive vendor does not have one.
- Planned preventive maintenance (PPM): contracted operators run a calendar against the register; reactive vendors do not.
- Spares and consumables: contracted operators hold a defined min/max inventory on or near site; reactive vendors source on demand.
- Knowledge transfer: a contracted operator's exit obligations include handing over the asset register, PPM history, and runbook — a reactive vendor leaves nothing behind.
Conclusion
The FM procurement mistake we see most often in the region is buying a contracted operator's contract structure while pricing it like an incident-by-incident vendor. The operator's margin pays for the planning, the register, and the on-site presence that prevents failure; if the buyer is unwilling to pay for those, the right answer is a reactive vendor and an honest internal acknowledgement of the risk that carries.
Procuring or restructuring an FM contract? We support institutional and multi-site buyers on FM scoping, SLA design, and operator evaluation. Get in touch via the contact page for a structured review.
