- The SLA should define priority levels, a response target and a fix (resolution) target for each, and the hours those targets apply.
- Response time is how quickly someone starts work; fix time is how quickly it's resolved. A fast response with no fix target tells you little.
- Scope: a clear list of what's included and what's charged extra (projects, out-of-hours, on-site visits, hardware and licences).
- If the provider processes personal data for you, UK GDPR Article 28(3) lists terms the contract must contain, including acting 'only on documented instructions' and deleting or returning data at the end.
- Check the minimum term, notice period, auto-renewal, price rises during the term and any early exit or handover charges.
- Ask what happens if SLA targets are missed: service credits, reporting and a route to escalate.
What should an IT support SLA include?
Priority levels with plain definitions, a response target and a fix target for each, the hours of cover, how to log a ticket, how performance is reported and what happens when targets are missed.
- Priority 1Critical: the whole business or a key system is down, for example no email or no internet for everyone.
- Priority 2High: a team or important function is affected, or one person can't work at all.
- Priority 3Normal: one person has a problem but can carry on working.
- Priority 4Request: a change or question: a new starter, a permission, some advice.
| SLA item | What to check |
|---|---|
| Priority definitions | Plain examples of what counts as each priority, and who decides |
| Response target | Time to a person starting work on it, for each priority |
| Fix or resolution target | Time to resolve or work around it, for each priority |
| Hours of cover | Whether the clock runs only in business hours, and the cost of out-of-hours |
| Ticket channels | Phone, email, portal; and whether phone calls are answered by a person |
| Reporting | Monthly reports on tickets and SLA performance |
| Missed targets | Service credits, escalation contacts and review meetings |
What's the difference between response time and fix time?
Response time is how quickly the provider acknowledges and starts working on a ticket. Fix (or resolution) time is how quickly the problem is solved or worked around. A contract with only response targets doesn't commit to getting you working again.
- Automatic acknowledgements don't count. Check that 'response' means a technician starting work, not an automated email.
- Look for fix targets, or at least targets to a workaround. Some problems need a third party (a broadband supplier, a software vendor); the contract should say how those are handled.
- Check when the clock stops. Many SLAs pause outside business hours or while waiting for you.
What should the contract say is included and excluded?
List what's covered (users, devices, servers, sites, software, Microsoft 365, backup, network) and what's charged extra (projects, out-of-hours, visits beyond an allowance, hardware, licences), with the rates for extras.
- Covered users, devices and sites. Including how they're counted and how changes are billed.
- Covered software. Is your line-of-business software supported, or only 'best endeavours'?
- On-site visits. Included number, then the rate.
- Projects. How they're quoted and approved before work starts.
- Third parties. Whether the provider will deal with your broadband, phone or software suppliers for you.
- Equipment. Anything rented from the provider, and what happens to it when you leave.
What data protection terms does the contract need?
If the provider processes personal data for you, the contract must include the UK GDPR Article 28 processor terms. Check it covers instructions, confidentiality, security, sub-processors, helping you with data subject rights, deletion or return at the end, and audits.
| Article 28(3) term | In plain English |
|---|---|
| (a) processes 'only on documented instructions' from you | They act on your instructions, not their own |
| (b) people processing the data are bound by confidentiality | Their staff keep your data confidential |
| (c) takes the security measures required by Article 32 | Appropriate security, including being able to restore data |
| (d) conditions for engaging another processor | They need your authorisation to use sub-processors |
| (e) and (f) helps you meet your obligations | Help with rights requests, breaches and assessments |
| (g) deletes or returns the data at the end, at your choice | Your data back (or securely deleted) when you leave |
| (h) makes information available and allows audits | You can check they're doing what they say |
What should you check about the term, price and leaving?
The minimum term, notice period and how to give it, auto-renewal, price increases during the term, early exit charges, and a written exit plan: documentation, passwords and data handed back.
- Minimum term and auto-renewal. When can you leave without a charge, and does it roll over automatically?
- Notice. How much, in what form, and to whom.
- Price changes. Annual increases and how they're calculated.
- Exit assistance. What the provider will do to hand over, and whether it's charged.
- Ownership. Your domains, Microsoft 365 tenancy, admin accounts and documentation stay yours.
Quick checklist before you sign
Have you got the SLA targets, inclusions and exclusions, rates for extras, data protection terms, term, notice and exit terms in writing, and compared them across at least two quotes?
- SLA targets by priority, with hours of cover.
- Inclusions and exclusions, with rates for extras.
- Onboarding plan and any setup fee.
- UK GDPR processor terms.
- Term, notice, auto-renewal, price rises and exit.
- Ownership of accounts, domains and documentation.
Get quotes for business IT support
Tell us about your business and the IT support you need, once. We pass it to a UK IT support provider (a managed service provider), who will:
- Talk through your setup: staff, devices, sites, Microsoft 365 or other systems, and what keeps going wrong.
- Quote in writing, showing how it's priced (per user, per device or hours), what's included and what's extra.
- Set out the service levels: help desk hours, response and fix targets, onboarding and how you leave.
For businesses and organisations. Prefer email? Write to [email protected] with your staff numbers, sites and the support you need.
Related guides
IT support contract checklist: frequently asked questions
What is an SLA in IT support?
A service level agreement: the part of the contract that sets priority levels, response and fix targets, the hours they apply, how performance is reported and what happens when targets are missed.
What's a good IT support response time?
It depends on your business and budget, so we don't suggest a figure. Decide what an outage would cost you, then compare providers' targets for each priority, especially fix times.
What's the difference between response and resolution time?
Response is how fast someone starts work on the problem; resolution is how fast it's fixed or worked around.
Does my IT support contract need GDPR terms?
If the provider processes personal data for you, UK GDPR Article 28 says the processing must be governed by a contract containing specific terms. Check the provider's terms or ask for a data processing agreement.
How long are IT support contracts?
It varies. Check the minimum term, notice period and whether it renews automatically before you sign.
What happens if the provider misses its SLA?
Whatever the contract says: often service credits, reports and an escalation route. If it says nothing, ask for it to be added.
Sources
We checked the facts on this page against these sources on 18 November 2026. Guidance changes: check the current version before you rely on it.