Facility Management SLAs and KPIs That Work

Almost every facility contract has an SLA section, and many of them are ignored in practice. Targets are copied from an old template, nobody agrees how to measure them, and the monthly review becomes an argument about whose spreadsheet is right. A good facility management SLA is different. It is short, specific, measurable from shared data, and linked to KPIs that both the client and the provider actually use to improve the service. This article sets out how to design one.

What is the difference between an SLA and a KPI?

The two terms are often mixed up, but they do different jobs.

In short, SLAs define the promise and KPIs show how well the promise is being kept and whether things are getting better.

What should a facility management SLA include?

1. Scope: which services, sites, assets and hours are covered.
2. Priority definitions: what counts as critical, high, medium and low, with examples for each service.
3. Targets: response time and resolution time for each priority, and frequency targets for scheduled work such as cleaning rounds and PPM.
4. Measurement rules: how and where each target is measured, including clock start, pause and stop conditions.
5. Reporting: what is reported, how often and from which system.
6. Consequences: service credits, incentives or improvement plans linked to performance.
7. Review: how and when targets are revisited.

How do you set priority levels and targets?

Priority levels should reflect impact on safety, operations and occupants, not who raised the request. The example below is illustrative; your own targets depend on the building, contract and available resources.

Separate response from resolution. Response means someone has acknowledged the issue and is on the way or has started work; resolution means the issue is fixed and verified. Merging the two hides where delays happen. For critical issues, it also helps to add a third stage, sometimes called make safe or temporary restoration, so that a lift entrapment or major leak is contained quickly even if the permanent repair needs parts or a specialist. Write examples for every priority level and every service, because the people logging requests at two in the morning will rely on those examples, not on the contract wording.

How should SLA compliance be measured?

Most SLA disputes are about measurement, not performance. Agree the rules before the contract starts:

• Clock start: when the request is logged in the helpdesk, not when a supervisor happens to see it.
• Clock pause: only for agreed reasons, such as waiting for client access or approved spare parts, and always with a note.
• Clock stop: when the requester or supervisor confirms the fix, ideally with photo evidence.
• Reclassification: who can change a priority and how that is recorded.
• Calculation: SLA compliance is the share of requests that met target in the period, by priority and by service.

To check compliance on a set of tickets quickly, use the SLA compliance calculator. For maintenance-heavy contracts, the maintenance downtime calculator helps with MTTR, MTBF and uptime.

Which facility management KPIs should you track?

A balanced KPI set covers several dimensions so that improving one does not quietly damage another. Aim for eight to twelve KPIs in total across the contract.

Responsiveness

• Response SLA compliance by priority.
• Resolution SLA compliance by priority.
• Backlog of open requests older than target.

Reliability

• PPM compliance: planned tasks completed on time.
• Uptime of critical systems such as HVAC, lifts and DG sets.
• MTTR and MTBF for key asset groups; repeat-failure rate.

Quality and compliance

• Housekeeping round compliance and audit scores.
• Statutory inspection and certificate status.
• Reopened ticket rate.

Experience and cost

• Occupant satisfaction or NPS from short surveys after request closure.
• Cost per square foot or per occupant against budget.

In integrated contracts, these KPIs sit across all services. Our explainer on integrated facility management covers how governance meetings use them.

How often should SLAs and KPIs be reviewed?

• Daily: open P1 and P2 issues and anything breaching target.
• Weekly: SLA compliance by service, backlog and reopened tickets.
• Monthly: full KPI review, root causes for misses, service credits or incentives, and improvement actions.
• Annually: reset targets based on a year of data, changes in occupancy and lessons learned.

Targets that are always met may be too loose; targets that are never met may be unrealistic for the resources in the contract. Both are signals to revisit, not reasons to stop measuring.

What are common SLA mistakes to avoid?

• Copying targets from another contract without checking whether the site’s staffing and spares can support them.
• Measuring only speed. A fast response that does not fix the problem is not good service; pair response targets with resolution, reopen and quality measures.
• One target for everything. A blanket four-hour resolution for all requests over-serves minor issues and under-serves critical ones.
• No scheduled-work SLAs. Reactive tickets are only part of the picture; PPM tasks and cleaning rounds need frequency targets too.
• Penalties without shared data. If service credits depend on figures each side calculates differently, every review becomes a dispute.
• Never revisiting targets. Occupancy, assets and budgets change; targets should change with them.

For housekeeping, frequency-based SLAs are often more useful than ticket-based ones. An illustrative example: each washroom on a busy floor is visited hourly during working hours, and at least 95% of those visits are completed within ten minutes of the scheduled time. The same logic applies to PPM, where compliance is measured as tasks completed within an agreed window around the due date.

Running SLAs on data both sides trust

An SLA is only as good as the data behind it. When requests come in by phone and are logged later in a spreadsheet, neither side can rely on the numbers. humblx captures every request through a helpdesk fed by QR, app or WhatsApp, timestamps each step, applies SLA clocks by category and priority, and escalates breaches automatically. Maintenance work orders and housekeeping rounds feed the same reports. The case studies show how hospitals and an airport have used this to cut response times and lift SLA compliance.

Start small: define four priority levels, agree the clock rules, pick a short KPI set and measure from one shared system. That foundation does more than a long SLA schedule that nobody can measure.