Small Business
How to Read a Managed IT SLA Before You Sign
A Managed IT proposal gets read for the price and the pitch, while the service level agreement gets skimmed on the way to the signature line. This checklist covers what the SLA actually needs to spell out, from response time versus resolution time to severity tiers, coverage hours, uptime remedies, and exit terms, so you know what you're agreeing to before you sign.
Most business owners read a Managed IT proposal for the price and the pitch, then skim past the service level agreement to get to the signature line. That's backwards. The price tells you what you'll pay. The SLA tells you what you're actually buying: how fast someone answers when something breaks, what "covered" really means, and what happens if the provider doesn't hold up their end.
A vague SLA isn't automatically a bad provider, but it gives you much less to hold anyone to, and how much less depends on the rest of the contract and the law that governs it. This is a plain-English checklist for reading one before you sign, whether you're comparing quotes or reviewing a renewal.
Why the Fine Print Matters
Every hour a core system is down costs something, whether that's missed calls, an idle team, or a deadline slipping. A vague promise like "fast response" doesn't tell you what happens during that hour. A written SLA does, if it's specific enough to hold anyone to. The gap between "we'll get to it quickly" in a sales call and a defined response time in the contract is exactly what this checklist is for.
1Response Time vs. Resolution Time
These are two different promises, and providers sometimes let the line blur. What you want response time to mean is how long until a real person starts working the ticket, not just an automated "we got your ticket" email. Some contracts define it more loosely, as acknowledgment or assignment rather than a person actually starting work, so don't assume. Resolution time is how long until the problem is actually fixed. Ask your provider to define both in writing and to say plainly which one their advertised number refers to.
2Severity Levels Defined in Writing
A server outage and a printer that won't connect are not the same emergency, and a good SLA doesn't treat them like they are. Look for defined severity tiers, each with its own response time, and a clear description of what qualifies for each tier. Without tiers, "response time" usually means the fastest example the provider can point to, not what you'll get during a real outage.
3Coverage Hours and What Falls Outside Them
Check whether support is business hours only, extended hours, or genuinely 24/7, and what happens to your severity-one response time if your server goes down at 11 p.m. on a Saturday. Some agreements quietly downgrade to a slower after-hours tier without saying so outside the fine print. If your business depends on systems running outside a 9-to-5 window, this is worth asking about directly rather than assuming.
4What Counts as Covered
An SLA usually lists exclusions: personal devices, unsupported or end-of-life software, third-party vendor outages, or hardware past a certain age. None of that is unreasonable on its own, but you need to know it going in rather than discovering it mid-outage. Ask for the exclusions list specifically, not just the coverage summary.
5Uptime Commitments and What Happens When They Are Missed
If the agreement includes an uptime guarantee, find out what it actually applies to. A guarantee on the provider's own managed infrastructure is a real commitment. A guarantee that only covers systems already outside their control isn't worth much. Then ask what happens when the number is missed: a service credit, a formal review, or nothing at all. A number with no remedy spelled out gives you a weaker, less predictable position than one that does, so pin down which it is before you sign.
6The Escalation Path
Find out what happens when a ticket sits too long. A serious provider has a documented escalation path: who it goes to next, and after how long. If the only answer is "call your account manager," that's not a process, it's a workaround.
7Exit Terms
Read the section on ending the contract before you need it. Look for the notice period, any early termination fees, and how you get your data and documentation back if you switch providers. A provider confident in their service has nothing to lose by making the exit terms clear and fair.
Reading the SLA Before You Sign
None of this is about assuming the worst of a provider. It's about knowing exactly what you're agreeing to, the same way you'd read a lease before signing it. Our managed IT service documents response times by severity tier, defined coverage hours, and a real escalation path, in writing, before you commit to anything.
If you're actively comparing providers, our Managed IT buyers guide walks through the questions worth asking beyond the SLA itself, including staffing, tooling, and contract length. And if you already have an agreement in hand and aren't sure how it holds up, contact us and we'll help you read it.
Frequently Asked Questions
Is a Verbal Promise From a Sales Rep Enforceable?
Treat it as informal rather than something to rely on. Whether a spoken promise holds up depends on your contract's own terms and the law where you operate, and that's not something to find out the hard way. If a response time, coverage detail, or guarantee matters to you, get it written into the SLA document itself, not just the sales conversation, and have a lawyer review anything you're unsure about before you sign.
What Is a Reasonable Response Time for a Small Business?
It depends on the severity tier and your coverage hours, which is exactly why those need to be defined rather than left as one general number. A critical outage should carry a materially faster commitment than a minor request, and the contract should say so explicitly.
Does a Managed IT SLA Cover Everything on My Network?
Rarely everything. Most agreements exclude personal devices, unsupported software, and third-party vendor outages by name. Ask for the specific exclusions list rather than assuming broad coverage from a general summary.
What Happens if My Provider Misses Its SLA?
That depends on what the contract says and, if it's silent, on the law that governs it. Some agreements spell out service credits or a formal review process for missed commitments; an agreement that says nothing gives you a weaker, less predictable position, not necessarily no position at all. Confirming the remedy in writing before you sign is far simpler than sorting it out after a missed response.
Should I Negotiate SLA Terms Before Signing?
Yes, if something in the draft doesn't fit how your business actually operates. Response times, coverage hours, and exclusions are usually negotiable, especially for a business with genuine after-hours dependencies. A provider unwilling to discuss any of it is telling you something about how the relationship will go.