IT Support Contract Checklist: 11 Things to Check Before You Sign
Last updated: 27 October 2026 An IT support contract checklist covers twelve points. Check scope and exclusions, contract term, notice period and renewal mechanism. Check response and resolution SLAs by priority, service credits and price-rise limits. Check licence and tenant ownership, exit and data-handover steps, and early-termination costs. Check for a UK GDPR data processing…

Last updated: 27 October 2026
An IT support contract checklist covers twelve points. Check scope and exclusions, contract term, notice period and renewal mechanism. Check response and resolution SLAs by priority, service credits and price-rise limits. Check licence and tenant ownership, exit and data-handover steps, and early-termination costs. Check for a UK GDPR data processing agreement and named account management. Each is negotiable.
The contract on your desk decides who answers at 9am on payroll day. It decides who owns your Microsoft tenant when you leave, and what you pay in year three. Most of that sits in a handful of clauses that rarely get read.
A 36-month agreement at £100 per user for a 40-person firm commits roughly £144,000. That deserves clause-level review before anyone signs. Still comparing providers? Start with our guide on how to choose an IT support provider, then come back here.
Below are twelve checks. Each one gives you the benchmark, the red flag and the question to ask. Each also shows what Technical Drive's standard agreement says on that point.
What should an IT support contract include?
An IT support contract should include twelve things. Commercial terms: a scope and exclusions schedule, the term, notice period and renewal mechanism. Service terms: separate response and resolution targets, priority levels and service credits. Money and ownership: a capped price-rise clause, licence and tenant ownership, an exit clause and early-termination terms. Governance: a data processing agreement and named account management.
- Scope and exclusions schedule
- Contract term and notice period
- Auto-renewal terms
- Response time and resolution time, defined separately
- Priority levels with targets for each
- Service credits or remedies for missed SLAs
- Price-rise clause with a cap
- Licence, tenant, domain and admin ownership
- Exit and data-handover clause
- Early-termination fees
- UK GDPR data processing agreement and security baseline
- Account management, reporting and escalation
Vague wording on any of these resolves in the provider's favour later. You will be under pressure, and they will hold the passwords. Each check below takes one item in turn.
1. What exactly is included, and what is excluded?
An IT support contract must list what the monthly fee includes and, separately, what it excludes. Typical inclusions are remote helpdesk, monitoring, patching and backup checks. Typical exclusions are project work, on-site visits, out-of-hours cover, hardware and software licences. If the agreement has no exclusions schedule, ask for one in writing before signing.
What to look for
- A separate exclusions schedule, not a sentence saying "all-inclusive".
- A written definition of a chargeable "project" versus day-to-day support.
- The chargeable unit (per user or per device) and how often it is reconciled.
Our earlier post explains what a managed IT support package usually includes and excludes, so this check stays short.
Red flag: "Fully managed" or "unlimited support" with no exclusions list anywhere in the document.
Technical Drive's agreement: Technical Drive charges a fixed monthly fee.
Ask the provider: "Can you send the exclusions schedule as a separate document before we sign?"
2. How long is the term, and what notice period applies?
UK IT support contracts commonly run 12, 24 or 36 months with 30 to 90 days' notice. Thirty days favours the buyer; 90 days is common and favours the provider. Check how notice must be served and whether it must land before an anniversary date. Ask whether the provider sends a reminder. Diarise the last notice date on signing.
Notice mechanics matter as much as the number of days. Some agreements only accept notice by recorded post to a named address. Others require notice to arrive before the anniversary date, not within the final month.
Compare the Cloud's February 2026 guide treats 30 days as reasonable and 90 days as common. A 12-month term, or rolling monthly after an initial term, is the buyer-friendly position.
Ask the provider: "By what date, and by what method, must I give notice to avoid renewal?"
3. Does the contract auto-renew, and on what terms?
Auto-renewal clauses renew the agreement for a further fixed term unless one party gives notice by a set date. Auto-renewal is lawful in UK business-to-business contracts. A 36-month renewal with a narrow notice window may still fail the Unfair Contract Terms Act 1977 reasonableness test. Prefer rolling monthly renewal after the initial term.
The Unfair Contract Terms Act 1977 (UCTA) is the law that applies to business-to-business IT contracts. It does not ban auto-renewal. It requires clauses that restrict your rights to pass a reasonableness test.
Limited companies get no help from the Consumer Rights Act 2015. Its unfair-terms protections apply to consumer contracts only. As of January 2026, the Competition and Markets Authority has published draft revised unfair contract terms guidance (CMA37). It is aimed at consumer contracts but signals the direction of regulation.
Set a calendar reminder 120 days before any renewal date. Ask whether the provider is contractually required to send a renewal reminder.
Ask the provider: "After the initial term, does the contract roll monthly or renew for another full term?"
4. Does the SLA define response time and resolution time separately?
Response time is how long the provider takes to acknowledge and start work on an issue. Resolution time is how long until the issue is fixed. A contract that guarantees only response gives no right to a fix within any timeframe. A sound SLA states both for each priority level, or commits to a resolution target with update intervals.
| Measure | Response time | Resolution time |
|---|---|---|
| What it means | Time until the provider acknowledges the issue and starts work | Time until the issue is fixed and the user can work again |
| What it guarantees | Acknowledgement, a ticket, a call back | A working outcome |
| Common weakness | Stated in minutes, looks impressive | Often missing from the contract entirely |
| Question to ask | When does the clock start? | What is the target per priority, and what updates do I get? |
According to Andrew McLean, Studio Director at Disruptive Live, in February 2026, a response-only SLA is "a commitment to be acknowledged, not a commitment to be helped". He was writing for Compare the Cloud, and the distinction is the most common gap in UK support contracts.
A target and a measured result are different things. Ask every provider for their SLA attainment data from the last quarter. A provider that does not track it has a decorative SLA.
Technical Drive's agreement: Technical Drive's SLA guarantees connection to a qualified engineer in under 30 seconds, including out of hours. As of 2 October 2026, the 2026 average call pick-up is 23.39 seconds. The 2026 average resolution time is 3.48 hours, including third-party involvement. Both figures are published monthly on the helpdesk response and resolution times page.
Ask the provider: "What were your measured response and resolution times last quarter, by priority?"
5. Are priority levels defined, with targets for each?
Priority levels classify incidents by business impact, each with its own targets. A typical UK SME benchmark for P1 critical is 30-minute response and 4-hour resolution. P2 high is 1 hour and 8 hours. P3 medium is 4 hours and 24 hours. P4 low is 8 hours and 48 hours. The contract must define what qualifies as each priority.
| Priority | Example incident | Response target | Resolution target |
|---|---|---|---|
| P1 Critical | Server down, total email outage, suspected breach | 30 minutes | 4 hours |
| P2 High | One site or department cannot work | 1 hour | 8 hours |
| P3 Medium | One user cannot work, workaround exists | 4 hours | 24 hours |
| P4 Low | Minor fault, request, question | 8 hours | 48 hours |
Source: Compare the Cloud editorial benchmark, February 2026. Treat these as a yardstick, not a legal standard.
Two details decide whether the table has teeth. The contract must say who assigns the priority and whether you can escalate it. For open P1 incidents, a fixed update interval, such as every 30 minutes, should be written down.
Priority targets also depend on helpdesk capacity. Our post on why helpdesk capacity affects response times explains why staffing ratios matter more than the SLA wording.
Ask the provider: "Who decides an incident's priority, and can I escalate it?"
6. What happens if the provider misses the SLA?
Service credits are defined reductions in the monthly fee payable when the provider misses an SLA target. Without credits or a termination right for repeated misses, an SLA is a statement of intent, not an obligation. Check the credit amount, the cap per month, how a claim is made, and the claim window.
Credits do not need to be large to change behaviour. A missed target that costs the provider money is handled differently from one that only costs goodwill. Typical structures are a percentage of the monthly fee per breach, with a monthly cap.
Ask the provider: "What do I receive if you miss a P1 target twice in one month?"
7. Can the price go up, and by how much?
Price-rise clauses set when and by how much the monthly fee can increase. Fair wording caps annual increases to CPI or a fixed percentage, applied once a year with written notice. Uncapped, RPI-linked or discretionary rises should be struck out. Separate vendor licence price changes, such as Microsoft uplifts, from the provider's own service fee.
CPI and RPI are not the same index. The Retail Prices Index (RPI) usually runs higher than the Consumer Prices Index (CPI). A clause linked to RPI "or such other index as the provider selects" is open-ended.
Vendor increases are a separate matter. When Microsoft raises licence prices, a fair contract passes the change through at cost, with notice. It does not use the vendor change as cover for a service-fee rise.
User-count changes should have their own mechanism. Adding ten staff is a scope change, not a price rise, and the per-user rate should stay fixed.
Technical Drive's agreement: Technical Drive charges a transparent fixed monthly fee, set out on the managed IT support packages page.
Ask the provider: "Which index caps your annual increase, and how much notice do you give?"
8. What does the exit and data-handover clause say?
Exit clauses define what happens when the agreement ends. They cover offboarding steps, return of documentation, and handover of admin credentials and configurations. They also cover transfer of backups and secure deletion of client data from the provider's systems. Fair terms complete handover within 14 to 30 days of notice and require cooperation with the incoming provider.
The handover list
- All admin credentials: Microsoft 365, domain registrar, firewall, backup platform, line-of-business systems.
- Network and system documentation, including IP schemes, device inventories and licence records.
- Configuration exports for firewalls, email security and backup jobs.
- Backup data in a usable format, with the encryption keys.
- A written confirmation that your data has been deleted from the provider's systems.
Handover timing should run from the date notice is given, not from the end of the notice period. Your data remains your property throughout, and the clause should say so.
Cloudswitched's July 2026 analysis of UK managed IT agreements names the missing exit clause as the single most expensive omission. A provider holding your credentials and backups with no duty to return them holds leverage over your whole organisation.
Technical Drive's agreement: Technical Drive runs onboarding and offboarding to documented procedures audited under ISO 9001. It has held the certification for 13 consecutive years.
Ask the provider: "Within how many days of notice do we receive every credential and configuration?"
9. What does it cost to leave early?
Early termination fees are what a client pays to leave before the fixed term ends. A flat fee of two to three months, or a declining percentage of remaining value, is proportionate. A fee of 75 to 100 per cent of the remaining contract value is designed to prevent leaving. Check for a right to terminate for repeated SLA failure.
| Fee model | Cost to leave at month 12 of 24 (£2,000 per month) |
|---|---|
| 75% of remaining value | £18,000 |
| 50% of remaining value | £12,000 |
| Declining scale (50% at month 12) | £12,000 |
| Flat fee of three months | £6,000 |
Fee models above follow the structures compared by Compare the Cloud in February 2026. The arithmetic is simple: 12 remaining months at £2,000 is £24,000, and the model sets the share you pay.
Termination for cause is a separate right. A fair contract lets you leave without penalty after persistent SLA failure or provider insolvency. A material breach left unfixed for 30 days should also qualify. Also ask for a right to benchmark pricing annually, with an exit if the provider sits well above market.
Ask the provider: "If you miss the SLA for three months running, can we leave without a fee?"
10. Is there a UK GDPR data processing agreement and a security baseline?
Providers that access personal data on a client's behalf are processors under UK GDPR. Article 28 therefore requires a written data processing agreement. It must state the processing purpose, security measures, sub-processors, data location and deletion on exit. The contract should also name the provider's own certifications, such as ISO 27001 and Cyber Essentials Plus.
A data processing agreement (DPA) is the schedule that sets out those Article 28 terms. The Information Commissioner's Office publishes guidance on contracts between controllers and processors that lists the minimum clauses. Sub-processor changes need advance notice and a right to object.
Security is now a commercial issue. The Department for Science, Innovation and Technology published the Cyber Security Breaches Survey 2025/2026 on 30 April 2026. It found that 43 per cent of UK businesses identified a breach or attack in the previous 12 months. The same survey reports that 47 per cent of businesses hold some form of cyber insurance. Insurers increasingly ask what the IT provider is certified to.
Certifications belong in the contract as evidence, not in the brochure as marketing. Ask for the certificate numbers and expiry dates. Our Cyber Essentials Plus page explains what the certification covers.
Technical Drive's agreement: Technical Drive holds ISO 27001, ISO 9001 and Cyber Essentials Plus, listed on its accreditations page.
Ask the provider: "Where is our data stored, and which sub-processors can access it?"
11. How is the relationship managed, reported and escalated?
Contracts should name how the relationship is managed. That means a dedicated account manager and monthly reports covering response, resolution and satisfaction. It also means a review meeting cadence and a written escalation path with named contacts. Without these, SLA performance is invisible and disputes have no route. Documented processes, as ISO 9001 requires, make the commitments auditable.
A monthly report should show ticket volumes, response and resolution times by priority, SLA attainment, and satisfaction scores. Quarterly or annual reviews with a technical director turn that data into a roadmap. Escalation contacts should be listed by name and role, with a stated response time for the escalation itself.
Board-level attention to IT is still uneven. The Cyber Security Breaches Survey 2025/2026 found board-level responsibility for cyber security in only 31 per cent of UK businesses. A named account manager and a monthly report put the subject on the agenda without adding headcount.
Technical Drive's agreement: Every Technical Drive client has a dedicated account manager and receives monthly performance reports. Satisfaction is measured after every ticket through SimpleSat and published monthly; the September 2026 positive score was 99.4 per cent. The annual client survey, run by independent telephone interview, returned a Net Satisfaction score of +89 for 2025.
Ask the provider: "Who is my named escalation contact, and what does the monthly report contain?"
Weak clause versus fair clause: the twelve checks at a glance
Weak and fair IT support contracts can carry the same monthly price. The difference lives in the wording of twelve clauses. The table below puts a weak version of each clause next to a fair one. Mark your own agreement against it line by line.
| Check | Weak wording | Fair wording |
|---|---|---|
| Scope | "All-inclusive", no exclusions list | Inclusions and a separate exclusions schedule |
| Term and notice | 36 months, 90 days' notice by recorded post | 12 months or rolling, 30 days' notice by email |
| Renewal | Renews for another full term, no reminder | Rolls monthly after the initial term |
| Response and resolution | Response only, "best endeavours" | Both defined per priority, with update intervals |
| Priorities | Undefined | P1 to P4 defined with examples and targets |
| Remedies | None | Service credits or termination for repeated misses |
| Price rises | Uncapped, at provider's discretion | Capped to CPI or a fixed percentage, once a year |
| Ownership | Tenant and domain in provider's name | Client owns tenant, domain and Global Admin access |
| Exit | Silent on handover | Credentials, documentation and data returned within 14 to 30 days |
| Early termination | 75 to 100% of remaining value | Flat two to three months, plus termination for cause |
| Data and security | No DPA, no certifications named | Signed DPA, UK residency, certifications listed |
| Management | No named contact, no reporting | Named account manager, monthly reports, escalation path |
Frequently asked questions
What should an IT support contract include?
An IT support contract should define twelve things. Scope and exclusions, contract term, notice period and renewal mechanism come first. Then response and resolution SLAs by priority, service credits and price-rise limits. Then licence and tenant ownership, exit and data-handover steps, and early-termination costs. Finally a UK GDPR data processing agreement and named account management. Each is negotiable.
How long is the notice period on an IT support contract?
Most UK IT support contracts require 30 to 90 days' written notice before the end of the current term. Thirty days is buyer-friendly; 90 days is common and gives the provider more protection. Check how notice must be served and by which date, then diarise that date when you sign the agreement.
What is the difference between response time and resolution time?
Response time is how quickly the provider acknowledges an issue and starts work. Resolution time is how quickly the issue is fixed. A contract that only promises a response gives no right to a fix within any timeframe. Ask for both targets per priority level, plus the provider's measured attainment for the last quarter.
Are auto-renewal clauses legal in UK business contracts?
Yes. Auto-renewal clauses are enforceable in UK business-to-business contracts when clearly drafted and properly incorporated. They must pass the reasonableness test under the Unfair Contract Terms Act 1977. A multi-year renewal with a narrow notice window and no reminder could be challenged. Negotiate a rolling monthly renewal after the initial term instead.
What happens to my data and licences when I leave my IT provider?
Your data, Microsoft 365 tenant and domain remain your property. A fair contract requires the provider to hand over credentials, documentation, configurations and backups within 30 days of notice. It must also cooperate with the incoming provider and delete your data from its systems afterwards. Licence billing transfers to the new provider through Microsoft Partner Center.
Before you sign
Twelve checks fall into four groups: scope and money, time and exit, service levels, and data and governance. None of them is exotic, and every one is negotiable before signature. A provider that already meets the benchmark will show you its standard terms without being asked.
At an earlier stage? Our 2026 IT provider selection guide covers how to shortlist in the first place.
Compare your contract against ours
Technical Drive publishes its measured response and resolution times every month. Its notice, exit, handover and pricing terms sit in a standard agreement you can read before any meeting. Have a contract on your desk? Send it over and we will review it against the twelve checks, with no obligation. You can book a contract review or read the published helpdesk response and resolution times first.
Which of the twelve is missing from the contract on your desk?
Ready to take your business to the next level? Get in touch with us today and let’s drive your success forward together!
Call Us on 01527 880088
Want a Meeting?
Let’s discuss how implementing SharePoint into your business can enhance your team’s communications with ease.
Featured Blogs
Check out our featured blogs for the latest insights, tips and updates you won’t want to miss.





