SLA management - quick start guide
SLA management - quick start guide
Your team promised a 15-minute response time on critical incidents. But when the CEO's laptop died at 4:47 PM on a Friday, nobody knew who to escalate to, or that the clock was already ticking. This schema fixes that.
The SLA Management schema gives you three object types that structure how your organisation defines response targets, wires up escalation rules, and links everything back to the services you actually run. Paired with the Priority Matrix, you get end-to-end incident management: priority calculation feeds SLA selection, SLA targets trigger escalation rules.
When to use this schema
Deploy SLA Management if you need to:
-
Formalise SLA targets: move from informal "we try to respond quickly" expectations to documented response and resolution targets per priority level with defined support hours.
-
Configure escalation governance: specify who gets notified, when, and through which channels as SLA breach approaches or occurs.
-
Differentiate service levels: manage different SLA commitments for different services (24x7 for production, business hours for internal tools).
-
Support MSP operations: track contractually different SLA tiers across multiple clients.
SLA management vs priority matrix
These two schemas address related but distinct concerns:
| Concern | Priority Matrix | SLA Management |
|---|---|---|
| Determines priority | Yes (impact x urgency matrix) | No (consumes priority as input) |
| Defines time targets | No | Yes (response and resolution per priority) |
| Escalation rules | No | Yes (trigger thresholds, notification methods, auto-reassign) |
| Service linkage | No | Yes (service offerings linked to SLA policies) |
| Best for | Consistent incident classification | SLA enforcement and breach prevention |
Use both together for the full picture: Priority Matrix determines the priority level, and SLA Management applies the correct targets and escalation rules. This is the recommended approach for mature ITSM implementations.
Pro tip: If you are unsure which to deploy first, start with Priority Matrix. It provides the classification foundation that SLA Management builds on. You can add SLA Management later without rework.
Schema overview
Three object types
| Object Type | Role | Key Attributes |
|---|---|---|
| SLA Policy | Response/resolution targets, support hours, breach notification | Priority, Response Target, Resolution Target, Support Hours, Calendar Type |
| Escalation Rule | Trigger thresholds, notification targets, auto-reassignment | Trigger, Escalation Target, Notification Method, Auto-Reassign, Escalation Level |
| Service Offering | Service scope, ownership, availability, link to governing policy | Service Type, SLA Policy (reference), Service Owner, Availability Target |
Relationship architecture
Service Offering ──(Governed By)──> SLA Policy ──(Escalates Via)──> Escalation Rule
Screenshot coming soon
A Service Offering (e.g., "Corporate Email") is governed by an SLA Policy (e.g., "High: 30m response, 4h resolution"). That SLA Policy escalates via an Escalation Rule (e.g., "Notify Team Lead 15 minutes before breach"). Every service has documented commitments and every commitment has a defined escalation path.
Reference types
| Reference Type | Colour | Direction | Purpose |
|---|---|---|---|
| Governed By | Blue (#0052CC) | Service Offering → SLA Policy | Links a service to its SLA commitment |
| Escalates Via | Red (#FF5630) | SLA Policy → Escalation Rule | Links a policy to its breach escalation |
| Owned By | Purple (#6554C0) | Flexible | Establishes ownership accountability |
Documentation
This guide is split into three focused pages:
Object type reference Full attribute tables for all three object types, allowed values with meaning and usage guidance, implementation best practices, and real-world examples.
Deployment guide Step-by-step deployment, population order, starter records for escalation rules, SLA policies, and service offerings, relationship wiring, and verification queries.
Integration and operations Integration patterns with Priority Matrix, incident management, service catalogue, and change management. Reporting metrics and recommended dashboards.