An SLA (service level agreement) is the part of a managed services contract that defines the service you will receive: uptime targets, response and resolution times, support hours, responsibilities on each side, and what happens if the provider falls short. A good SLA makes expectations measurable and enforceable. Before signing a managed services contract, check these components carefully, they are where the real value sits.
What an SLA is
A service level agreement is the section of a contract that turns a provider promises into measurable commitments. It states the standard of service you can expect, how it will be measured, and the consequences if it is not met. Without a clear SLA, service is a matter of goodwill. With one, it is a matter of record.
The key components of an SLA
- Scope: exactly what is and is not covered.
- Availability: uptime targets for key systems, for example 99.9 percent.
- Response and resolution times: how fast the provider reacts and fixes, by severity.
- Support hours: business hours or 24×7, and what counts as out of hours.
- Responsibilities: what the provider owns and what stays with you.
- Reporting and reviews: how performance is measured and discussed.
- Remedies: what happens, such as service credits, if targets are missed.
Response time vs resolution time
This is the single most misunderstood part of an SLA. Response time is how quickly the provider acknowledges and starts work. Resolution time is how quickly the issue is actually fixed. Many weak SLAs promise a fast response but say nothing meaningful about resolution, so you get a quick reply and a slow fix. Make sure both are defined, by severity.
A fast response to a problem that then takes three days to fix is not good service. It is a well-worded delay.
Common SLA metrics
| Metric | What it measures |
|---|---|
| Uptime / availability | Percentage of time systems are available (e.g. 99.9%) |
| Response time | How fast the provider acknowledges an issue |
| Resolution time | How fast the issue is actually fixed |
| Severity levels | Priority tiers, from critical outage to minor request |
| First-contact resolution | Share of issues fixed on first contact |
Red flags in managed services contracts
- Response times defined, but no resolution commitment.
- One target for everything, with no severity levels.
- Vague scope, so new work keeps falling outside the contract.
- No remedies, so missing a target costs the provider nothing.
- Unclear security and data protection responsibilities.
Questions to ask before you sign
Ask the provider: what exactly is covered; what are the uptime, response and resolution targets by severity; are you covered 24×7 or only in business hours; what happens when a target is missed; and how is performance reported. Clear, confident answers are a good sign. Evasive ones are a warning. For how these contracts fit the wider decision, see managed services vs in-house IT and how much managed IT services cost. Schnell Technocraft works to clear, honest SLAs, ask us for an example.