SLA compliance rate
SLA compliance rate is the percentage of jobs performed under SLA-covered agreements that meet their contractual response and resolution windows, calculated against all covered visits in a period.
The inputs.
- Visits inside the windowJobs that met their contractual response and resolution windows, per agreement and customer.
- Covered visitsAll jobs performed under SLA-covered agreements in the period.
- Distinct fromSchedule adherence, which tracks the day's dispatch schedule rather than contractual commitments.
What to know.
How to calculate SLA compliance rate
SLA compliance rate equals the number of covered visits that met their contractual response and resolution windows divided by total covered visits in the period. The windows come from the agreement itself, so the metric is only as meaningful as the SLA definitions — emergency, priority, and routine tiers each carry their own bar, and some shops weight emergency-tier misses more heavily. It's distinct from schedule adherence, which tracks the day's dispatch schedule; compliance tracks the contract.
Why SLA compliance rate matters for commercial contractors
It's the number a customer's facilities team actually checks against the contract, and the number that determines credits or penalties — a high rate is renewal evidence, and a low one is a liability you carry into every conversation. Tracking it honestly also answers whether the SLAs you've signed are deliverable in the first place. An over-promised window that the shop misses repeatedly isn't a performance problem; it's a contract problem that will surface at renewal either way.
What drives SLA compliance down
The drivers are over-promised windows, slow acknowledgment on the response side, dispatch that can't tell which jobs are SLA-covered, and reactive capacity overwhelmed by emergency volume. Most are visible before a breach if response and arrival are timestamped against the window — the miss is rarely a surprise; it's usually a window that was ignored until it closed.
How Thermal tracks SLA compliance automatically
SLA windows live on the agreement and flow onto every work order it generates, and status timestamps compare against those windows automatically — so compliance rate rolls up per agreement, per customer, and per branch from the same data dispatch works from. At-risk jobs surface on the dispatch board before the window closes, which is the difference between preventing a breach and reporting one.
Questions attached to this term.
How is SLA compliance rate different from schedule adherence?
Schedule adherence tracks whether the day's dispatched schedule was hit. SLA compliance tracks whether contractual response and resolution windows were met — the schedule and the contract can be out of sync, which is why both are worth tracking.
What happens when the SLA compliance rate falls?
Per the contract, typically credits or penalties, and a hit to the renewal conversation — facilities teams hold the document you signed to what it promised.
Should SLA compliance be tracked per agreement or company-wide?
Both — per-agreement is what the customer sees and what penalties are based on; the company-wide view shows whether the SLA portfolio overall is deliverable.
How do you improve SLA compliance without adding technicians?
Realistic windows, on-call routing for emergency tiers, and at-risk visibility at dispatch. Most missed windows are visible before they close — the fix is reacting while there's still time, not adding crew.
These numbers, on your own book.
If you want to see them calculated from real work orders and agreements rather than a spreadsheet, that's a demo.