SLA: Service Level Agreement
A formal agreement defining the expected level of service a vendor must deliver, including performance metrics, uptime guarantees, and remedies for non-compliance.
What is SLA?
SLAs specify measurable service targets such as uptime (e.g., 99.9%), response time, resolution time, throughput, and error rates. They include measurement methods, reporting frequency, escalation procedures, and penalties (service credits, fee reductions, termination rights) for failures. Effective SLAs distinguish between different severity levels and may include exclusions for planned maintenance, force majeure, or customer-caused issues. SLAs should be supported by operational level agreements (OLAs) and underpinning contracts.
Application to Vendor Screening
SLAs are critical for vendor governance. Beyond uptime, include security incident response times, data breach notification timelines, backup and recovery objectives (RPO/RTO), and compliance reporting deadlines. Monitor SLA performance regularly and enforce remedies for persistent non-compliance.
Practical Examples
- Negotiating 99.95% uptime SLAs with service credits for downtime exceeding thresholds
- Defining SLA severity levels with corresponding response and resolution times
- Implementing automated SLA monitoring and reporting dashboards
Frequently Asked Questions
What is the difference between SLA and SLO?
An SLA is a contractual commitment with penalties for non-compliance. A Service Level Objective (SLO) is an internal target that may be more aggressive than the SLA. SLOs help teams aim higher than minimum contractual requirements.
What SLA metrics should vendor contracts include?
Key metrics include availability/uptime, response time, resolution time by severity, data backup frequency, disaster recovery time (RTO), data recovery point (RPO), security incident notification time, and reporting frequency.