01
What a facility management SLA should achieve
A facility management service level agreement, or SLA, translates an accepted scope into visible operating expectations. It should explain which events are measured, when the clock starts, what evidence confirms the result and how exceptions are handled. The SLA normally sits beside the service scope, asset information, responsibility matrix and commercial terms; it cannot repair uncertainty in those documents by itself.
For a Dubai property, useful service levels should reflect the building type, occupancy, operating hours, access controls, maintained systems and the consequence of service loss. The objective is not to choose the shortest headline time. It is to create a practical standard that gives urgent conditions an appropriate route, keeps routine work visible and produces information the owner and provider can use to improve delivery.
02
Define the scope before setting service levels
Begin with the properties, areas, assets and activities included in the proposed agreement. Identify planned maintenance, reactive requests, inspections, helpdesk handling, reporting, contractor coordination and specialist interfaces. State whether the provider performs the work, coordinates another party or only reports the condition. A response measure is misleading when the responsible party has not been defined.
Document operating hours, access arrangements, permit requirements, warranties, existing specialist contracts and tenant-controlled equipment. Where the asset list or condition is incomplete, record the assumption and how it will be verified during mobilisation. Also distinguish recurring services from corrective projects, replacement, materials and third-party work that may need separate approval. Clear boundaries make later KPI results comparable and reduce avoidable disputes.
03
Build priority categories around property consequence
Priority should be assigned according to consequence rather than the wording or emotion of the request. Factors can include immediate safety concern, loss of an essential shared service, active risk of damage, effect on occupied areas, availability of an alternative and the likelihood that delay will worsen the condition. A short priority matrix helps the helpdesk, site team and client representative classify similar events consistently.
Each category needs examples, but examples should guide judgement rather than replace it. A visible water leak and a minor fixture defect may both involve plumbing while requiring very different routes. Define who may raise or change a priority, how a disputed classification is reviewed and what happens when new information changes the consequence. This prevents priority inflation while preserving a route for genuine escalation.
04
Separate acknowledgement, attendance, restoration and closure
One word such as response can hide several different events. Acknowledgement confirms that a request was received and classified. Attendance records when a suitable resource begins an on-site assessment where attendance is required. Restoration means the affected function has returned, possibly through a temporary measure. Final closure confirms that the agreed permanent work, evidence and communication are complete. The SLA should name the stages it measures.
For each stage, define the start and stop event, applicable service hours, required timestamp and acceptable evidence. Do not report an automated message as technical attendance or a temporary reset as permanent repair. Some faults depend on access, client approval, parts or a specialist. The record should show the provider-controlled action, the dependency and the next committed step instead of hiding the issue behind a closed ticket.
05
Set realistic planned-maintenance measures
Planned maintenance is better measured against an approved schedule than against visit volume alone. The schedule should identify the asset or area, task, frequency, responsible party, permitted window and evidence required. A completion measure then needs a clear denominator, treatment of approved deferrals and rules for assets that are inaccessible, removed, duplicated or found outside the accepted scope.
Quality matters alongside timing. A task marked complete without readings, observations, photographs or a resulting action may offer little assurance. Consider measures for completed scheduled work, overdue tasks, open findings and closure of recommendations, but avoid counting the same activity several times. Where specialist reports produce corrective actions, assign an owner and due date even if the follow-on work needs a separate quotation.
06
Choose a focused set of FM KPIs
A useful facility management KPI answers a management question. Examples include whether agreed planned tasks were completed, whether high-priority requests progressed through the required stages, how many open actions are overdue, which issues repeat and whether specialist recommendations have an owner. Measures should connect service data to risk, continuity, property condition or a decision rather than rewarding ticket creation.
Every KPI needs a written formula, data source, reporting period, target basis, permitted exclusions and accountable reviewer. Percentages can be distorted when the denominator is small or when cancelled and duplicate records are treated inconsistently. Show the underlying count and explain material exceptions. A compact dashboard supported by an action log is usually easier to govern than a large set of indicators that nobody reviews.
07
Define evidence and data responsibility
The SLA should state the minimum evidence for each measured event. Depending on the task, this may include a request timestamp, attendance record, asset reference, technician note, condition observation, photograph, reading, specialist report, client approval or completion confirmation. Evidence should be proportionate: the purpose is a reliable operating history, not unnecessary administration that delays the work.
Assign responsibility for entering, checking and correcting the data. Confirm how duplicate requests, reopened issues, cancelled work and system outages are handled, and ensure sensitive occupant or access information is protected. The owner should be able to understand the result without relying on undocumented calculations. If records are exported or handed over at contract end, their format and ownership should also be defined.
08
Create escalation and service-recovery routes
Escalation should identify who is informed when an urgent condition, missed stage, recurring fault or overdue decision requires attention. The route may move from the operating contact to the provider manager and client representative, with specialist or leadership involvement where appropriate. Names can change, so the contract should define roles and require the live contact list to be maintained separately.
A missed target should lead to understanding and recovery, not only a coloured dashboard. Record the immediate containment, cause, affected responsibility, corrective action, owner and review date. Repeated exceptions may indicate an unrealistic target, weak workflow, incomplete asset data, access restrictions or insufficient control. The agreed commercial consequence, if any, belongs in the contract and should use verified data and clearly defined rules.
09
Govern reporting, review and change control
Agree the reporting cycle and the purpose of each review. An operating report can show priorities, overdue work, planned-maintenance status, recurring issues, recommendations, quotations awaiting decision and emerging risks. A meeting should finish with decisions, named actions and due dates. Items that depend on the owner or another contractor should remain visible without being incorrectly reported as provider-controlled performance.
Service levels may need adjustment when assets, occupancy, hours, access, systems or service responsibilities change. Use a documented change process that records the proposed revision, operational reason, data or cost effect, approval and effective date. Periodic review can test whether definitions remain useful, but targets should not be changed retrospectively to improve a result. Preserve the version that applied during each reporting period.
10
Prepare an SLA brief for a Dubai FM proposal
A decision-ready brief should include the property and operating profile, available asset information, service boundaries, priority logic, required service stages, proposed KPIs, evidence standards, reporting expectations, escalation roles and known dependencies. Ask each bidder to identify assumptions, exclusions and any target that cannot be supported by the proposed delivery model. This creates a more useful comparison than collecting unrelated headline promises.
Use the same comparison sheet for every proposal. Record the bidder’s definition for each priority, service stage, measurement window, dependency and exclusion, then check whether the staffing and operating approach can support it. Note which items are included in the recurring amount and which require separate approval. Any clarification agreed during procurement should be incorporated into the final contract schedule rather than left in meeting notes or email.
Friends Facilities Management can review a Dubai property requirement and discuss how service levels may be structured within an annual or outsourced facility management proposal. Final priorities, attendance, measurement rules, targets, specialist responsibilities, exclusions and commercial terms must be confirmed for the specific building in an accepted written agreement. The result should be an SLA the operating team can apply and the owner can govern.