Service Level Agreement (SLA)

A service level agreement (SLA) is a formal contract component that defines the minimum performance standards a service provider commits to delivering, the metrics used to measure them, and the consequences of non-compliance.

In professional services, SLAs most commonly govern retainer engagements, managed services, and post-go-live operations work where the firm holds ongoing responsibility for system or service performance.

What an SLA must define

An SLA that lacks any of these elements is not enforceable:

• Metric: the specific measure, such as response time in hours, availability as a percentage, or defect rate per deliverable.
• Target: the minimum acceptable value, for example “initial response within 4 business hours” or “99% uptime over the calendar month.”
• Measurement method: how compliance is tracked and who tracks it.
• Reporting cadence: how often the provider reports performance against the SLA.
• Breach definition: the threshold at which a remedy is triggered.
• Remedy: what the provider owes when a breach occurs, such as a service credit, root cause analysis, or escalation obligation.
• Exclusions: events that do not count against SLA performance, including force majeure, client-caused delays, and scheduled maintenance windows.

SLA tiers in professional services

Most managed services offerings define tiered SLAs by incident severity:

• Severity 1 (Critical): system down or business operation halted. Response target: 1 hour. Resolution target: 4 hours.
• Severity 2 (High): major function impaired. Response target: 4 hours. Resolution target: 1 business day.
• Severity 3 (Medium): function degraded but a workaround exists. Response target: 1 business day. Resolution target: 5 business days.

Exact targets vary by contract; these are illustrative benchmarks.

SLA vs. scope of work

A statement of work defines what work will be done and what will be delivered. An SLA defines the performance standards to which that work must be done. The SOW answers what; the SLA answers how well. Both can appear within the same contract or as separate documents referenced by a master services agreement.

Common SLA mistakes in professional services

• Defining response time but not resolution time, leaving the provider able to acknowledge incidents promptly while resolving them slowly.
• Not excluding client-caused delays from SLA measurement, which distorts compliance data.
• Setting targets without a clear measurement and reporting mechanism, making breach determination contested.
• Setting breach remedies so minor they create no performance incentive.

A runbook or playbook linked to each SLA tier makes it easier to meet response and resolution targets consistently.