Whether you manage commercial towers in Business Bay, residential communities in Arabian Ranches, or a mixed-use building under a jointly owned property declaration, the operational complexity of UAE facility management is significant. And generic, imported FM software rarely fits the specifics of how this market actually operates.
The UAE FM market context
The UAE’s facility management sector has grown alongside the country’s expansion of master-planned communities and mixed-use developments, and it operates under a regulatory context that shapes day-to-day requirements. Dubai’s Law No. 6 of 2019 governs jointly owned property, replacing the old owners’ association model with a RERA-licensed Managing Agent and an elected Owners Committee. With service charge budgets and financial reporting submitted through RERA’s Mollak platform. Dubai Municipality health and safety requirements apply on top of that, across commercial and residential FM operations. Software built without this context in mind tends to miss requirements that are, for UAE FM companies, non-negotiable.
DEWA compliance: what FM companies must track
Utility management is a core, recurring responsibility for UAE FM companies, and it centres on DEWA (Dubai Electricity and Water Authority):
- Meter readings: captured consistently per unit or building, forming the basis for accurate tenant and owner billing.
- Utility billing to tenants and owners: reconciled against actual consumption, not estimated or averaged figures that create disputes later.
- DEWA demand notices: tracked and actioned promptly, since a missed notice can escalate into a larger administrative issue.
Most FM companies currently manage this with a spreadsheet per building, updated manually whenever someone remembers to walk the meters. It’s a process that degrades quietly. Readings get delayed, billing disputes take longer to resolve because there’s no clean audit trail, and demand notices occasionally get missed entirely because nobody was specifically watching for them.
SLA management in UAE FM
Clients (whether a commercial landlord, a developer, or an owners’ association) expect service level agreements to be met and, increasingly, expect to see evidence of that performance. Most UAE FM companies currently track SLA compliance through a combination of WhatsApp threads, email, and institutional memory, which creates a specific problem: when a client asks for an SLA compliance report, someone has to manually reconstruct performance from scattered messages, and the resulting report is only as good as what people remember to log in the first place.
Systemised SLA tracking changes this by attaching SLA terms directly to each contract, flagging breaches automatically as they happen, and generating performance reports on demand rather than under pressure when a client asks.
Planned versus reactive maintenance: why UAE FM companies lose money on reactive work
Reactive maintenance (fixing something after it breaks) is inherently more expensive and more disruptive than planned preventative maintenance (PPM) that catches issues before they escalate. Yet many UAE FM companies operate predominantly in reactive mode, simply because there’s no systemised PPM schedule driving proactive work. The result is a maintenance budget that’s consistently higher than it needs to be, and client relationships strained by avoidable emergency call-outs.
Planned maintenance scheduling in software means PPM tasks are generated automatically based on asset type and maintenance intervals, assigned to technicians ahead of time, and tracked to completion. Shifting the balance of work from reactive fire-fighting to proactive, budgeted maintenance.
Contractor management
FM companies coordinate a network of subcontractors (MEP, cleaning, landscaping, security) and the paperwork around that coordination matters as much as the work itself:
- Purchase orders raised against specific jobs, so costs are traceable rather than lumped into a general expense category.
- Job assignments tracked with clear ownership, so accountability for a completed (or incomplete) job is never ambiguous.
- Completion sign-offs documented with evidence, protecting both the FM company and the client if a dispute arises later.
- VAT-compliant contractor invoices, generated correctly rather than reconciled manually after the fact.
Owners’ association-specific requirements
Where an FM company is acting as the Managing Agent for a jointly owned property, additional requirements apply: transparent communication with individual owners, service charge management that’s auditable, and budget reporting structured for submission through RERA’s Mollak platform ahead of the AGM. Owners’ associations operate under closer scrutiny than a typical commercial FM contract, because owners have a direct financial stake in how service charges are collected and spent. Software that supports this needs to produce budget transparency and Mollak-ready documentation as a standard output, not a special request.
Getting started with a facility management system
For an FM company evaluating a move away from spreadsheets and messaging apps, the starting point is usually the area causing the most pain right now. Often SLA reporting, since that’s the most visible to clients, or DEWA utility tracking, since billing disputes are the most immediately costly. A phased approach tends to work better than trying to systemise everything at once: get SLA tracking and PPM scheduling live first, since these deliver the clearest immediate value, then layer in DEWA tracking and Mollak-ready owners’ association reporting once the core operational workflow is stable.
The scoping conversation should cover the number of sites and contracts under management, whether any properties are managed as a Managing Agent under a jointly owned property declaration, and what reporting clients currently expect versus what they’d ideally receive. From there, a realistic implementation timeline and cost range can be set, rather than assuming every FM company needs the same configuration regardless of portfolio size or complexity.