At a Glance
A Service Level Agreement (SLA) is the part of a managed IT contract that defines exactly what your provider is obligated to deliver and what happens when they fall short. A professional managed IT SLA specifies response times and resolution times for different categories of incident, defines priority tiers ranging from critical outages through to routine requests, documents escalation procedures, and clearly states any exclusions. Most Australian SMEs sign managed IT contracts without fully understanding what their SLA actually guarantees. Knowing what to look for — and what the red flags are — helps you hold your IT provider accountable and make better decisions when comparing providers.
What an SLA Actually Is (and What It Is Not)
An SLA is not a general description of services. It is a specific, measurable commitment about how those services will be delivered. A managed IT agreement typically consists of two components: the scope of services (what is covered) and the SLA (how it will be delivered and to what standard). Without a well-constructed SLA, a provider can technically meet the terms of a contract while delivering a poor experience — because the standard of delivery was never defined.
The Core Elements Every Managed IT SLA Should Cover
- Response Time Commitments: The maximum time between a user logging an issue and the provider acknowledging it and beginning work.
- Resolution Time Targets: The maximum time the provider has to resolve or escalate an issue before it moves to a senior resource.
- Priority Tier Definitions: A clear taxonomy of issue types, from business critical outages through to minor requests.
- Coverage Hours: Whether the SLA applies during business hours only or extends to after hours and weekends.
- Escalation Procedures: The defined path for when an issue is not resolved within target time.
- Exclusions and Carve-Outs: Situations where SLA obligations do not apply, such as delays from third party vendors.
Response Time vs Resolution Time — The Distinction That Matters
These two terms are frequently used interchangeably, but they represent very different commitments. Response time is the period between when an issue is logged and when the provider acknowledges receipt. Resolution time is the period between when an issue is logged and when it is resolved or escalated. A provider with an excellent response time and a poor resolution time can technically claim SLA compliance while leaving your staff waiting for a fix for hours or days.
Priority Tiers — How Professional MSPs Categorise Incidents
We do not view the SLA as boilerplate; it is the commercial backbone of the relationship. If you are unsure what your current agreement covers, our structured infrastructure assessment provides a plain language explanation of your entitlements.
Frequently Asked Questions
What is a Service Level Agreement (SLA) in managed IT?
A Service Level Agreement (SLA) in a managed IT contract is a documented commitment from the provider specifying response times, resolution times, priority tiers, escalation procedures, exclusions, and remedies. It defines not just what services are provided but the standard to which they will be delivered and what happens if the provider falls short.
What is the difference between response time and resolution time in an SLA?
Response time is the period between when an issue is logged and when the provider acknowledges it and begins work. Resolution time is the period between when an issue is logged and when it is resolved or escalated. Both should be defined separately in a professional SLA, as a fast response time with no resolution time commitment offers limited protection.
What priority tiers should a managed IT SLA include?
A professional managed IT SLA typically defines four priority tiers: P1 (critical — complete business outage), P2 (high — major degradation affecting multiple users), P3 (medium — single user affected), and P4 (low — minor or cosmetic issues). Each tier should have its own response time and resolution time targets.
What are the red flags in a weak IT service level agreement?
Red flags in a weak managed IT SLA include: no differentiation between issue priority tiers, a stated response time but no resolution time commitment, broad exclusions with no remedy provisions if targets are missed, no reporting obligation, unclear or absent after hours coverage, and vague escalation procedures.
Does my managed IT SLA need to cover after hours support?
Whether your SLA needs to cover after hours support depends on your business operations. If your business or its critical systems operate outside standard business hours, after hours coverage is worth reviewing explicitly in your agreement. Many contracts appear comprehensive but include exclusions for after hours incidents unless a separate arrangement is in place.
