Updated April 2026 · Written by Andy Pickett, CTO at Connection Technologies
Your IT support contract is one of the most important business agreements you will sign, yet it is also one of the most frequently misunderstood. Too many UK businesses sign contracts without fully understanding what is included, what is charged extra, or how difficult it will be to leave if the service is poor.
This guide walks you through every clause that should be in a good IT support contract, the warning signs of a bad one, negotiation strategies, and how to protect your business from being locked into an agreement that does not serve your interests.
Essential Clauses Every IT Support Contract Must Include
A comprehensive IT support contract should contain the following sections as a minimum. If any of these are missing or vague, consider it a red flag:
1. Service Scope and Description
This is the foundation of your contract and the section most likely to cause disputes if it is not specific enough. It should clearly list every service included in the per-user or monthly price, the systems and devices covered (and any exclusions), support hours (business hours, extended hours, or 24/7), supported users and locations, and the method of service delivery (remote, onsite, or both).
A good contract will include an attached schedule of services with specific detail. A poor contract will say something vague like “IT support services” without defining exactly what that means.
2. Service Level Agreements (SLAs)
SLAs define the measurable quality of service you should expect. Every IT support contract should specify:
| SLA Element | What It Should Define | Good Standard | Red Flag |
|---|---|---|---|
| Response time | Maximum time to acknowledge a ticket | 15 min (critical) to 4 hours (low) | No defined response times or “best effort” |
| Resolution time | Target time to resolve an issue | 2 hours (critical) to 24 hours (low) | No resolution targets or only response targets |
| Uptime guarantee | Availability of managed infrastructure | 99.9% or higher | No uptime commitment |
| Reporting | Frequency and content of SLA reports | Monthly with ticket breakdown | No reporting obligations |
| SLA credits | Financial penalties for missed SLAs | Service credits on monthly fee | No consequence for missed SLAs |
3. Pricing and Payment Terms
The pricing section should leave no room for ambiguity. It should clearly state the per-user or monthly fee and exactly what it includes, any additional charges and the circumstances under which they apply, the payment schedule (monthly in advance is standard), annual price review mechanisms (and any caps on increases), and what happens if you add or remove users mid-contract.
4. Contract Length and Renewal
Understanding the commitment you are making is crucial:
| Contract Type | Length | Pros | Cons | Best For |
|---|---|---|---|---|
| Rolling monthly | Month-to-month | Maximum flexibility, easy to leave | Slightly higher per-user cost, less price certainty | Businesses testing a new provider |
| 12-month fixed | 1 year | Good balance of commitment and flexibility | Early exit penalties may apply | Most SMEs |
| 24-month fixed | 2 years | Lower per-user pricing, price locked for 2 years | Harder to leave, business may outgrow the service | Stable businesses with predictable IT needs |
| 36-month fixed | 3 years | Lowest per-user pricing | Significant lock-in risk, technology changes fast | Enterprise or very stable environments only |
5. Exit and Termination Clauses
This is the section most businesses overlook — until they need to leave. A fair contract should include a notice period of 30–90 days (not 6+ months), clear definition of what constitutes grounds for early termination (e.g., persistent SLA breaches), the provider’s obligations during the exit process (data handover, documentation, cooperation with the incoming provider), any early termination fees and how they are calculated, and data ownership confirmation — your data belongs to you, always.
6. Data Protection and Security
Your IT provider will have access to sensitive business data. The contract must address GDPR compliance and data processing agreements, the provider’s security certifications (Cyber Essentials, ISO 27001), staff vetting and security clearance processes, data handling and storage locations, breach notification procedures and timelines (GDPR requires 72-hour notification), and confidentiality and non-disclosure obligations.
Hidden Fees in IT Support Contracts: What to Watch For
The most common source of conflict between businesses and IT providers is unexpected charges for services the client assumed were included. Here are the hidden fees to watch for:
| Hidden Fee | How It Appears | Typical Cost | How to Protect Yourself |
|---|---|---|---|
| Onsite visit charges | “Onsite support available” (but not included) | £75–£150/visit | Ensure a defined number of onsite visits per month/quarter are included |
| Out-of-hours charges | “Extended support available” (at extra cost) | 50–100% surcharge | Verify whether your support hours include 24/7 or just business hours |
| Project work classification | Standard tasks reclassified as “project work” | £85–£125/hour | Get clear definitions of what constitutes support vs project work |
| Third-party licence pass-through | Microsoft 365, antivirus costs added on top | Varies | Confirm whether licence costs are included in the per-user price |
| Onboarding fees | “Initial setup and documentation” | £500–£3,000 | Negotiate waiver or offset against first months fees |
| Hardware markup | Provider procures hardware at inflated prices | 10–25% above trade | Request transparent pricing or retain right to source independently |
| Annual price escalation | “Prices adjusted annually in line with RPI/CPI” | 3–8% per year | Cap annual increases at CPI or a fixed percentage (e.g., 5%) |
| Early exit penalties | “Remaining contract value payable on early termination” | Months × monthly fee | Negotiate a reducing scale or break clause at 12-month intervals |
What Good vs Bad IT Contracts Look Like
To help you evaluate contracts you receive, here is a comparison of good and bad contract practices:
| Contract Element | Good Contract | Bad Contract |
|---|---|---|
| Service scope | Detailed schedule listing every included service | Vague “IT support services as required” |
| SLAs | Specific response and resolution targets by priority with credits for breaches | No SLAs or “best endeavours” language |
| Pricing | Fully itemised with clear per-user price and list of any extras | Single monthly fee with no breakdown of inclusions |
| Contract length | 12 months with option to extend, or rolling monthly | 36 months with auto-renewal and 6-month notice |
| Exit clause | 30–90 day notice with cooperation obligations | 6-month notice, full contract value payable on early exit |
| Price review | Annual review capped at CPI or fixed percentage | Annual increase at provider discretion |
| Data ownership | Explicit statement that all data belongs to the client | No mention of data ownership or ambiguous language |
| IP and documentation | Provider must hand over all documentation, passwords, and configurations on exit | No handover obligations specified |
Negotiation Tips for IT Support Contracts
IT support contracts are negotiable. Here are practical tips for getting better terms:
- Always get multiple quotes — approach at least three providers. Use competing quotes as leverage — providers will often improve terms when they know you have alternatives.
- Push for a trial period — ask for a 3-month rolling period before committing to a longer contract. This lets you evaluate the service before locking in.
- Cap annual increases — if the contract includes annual price reviews, negotiate a cap (CPI or a fixed percentage). Without a cap, providers can increase prices significantly.
- Negotiate the exit clause — push for 30-day notice on rolling contracts or a 90-day notice with no penalty on fixed-term agreements. Avoid any contract where the exit penalty is the full remaining contract value.
- Include a break clause — for contracts longer than 12 months, negotiate a break clause at the 12-month mark with 90-day notice. This gives you a guaranteed exit point.
- Get everything in writing — verbal promises made during the sales process mean nothing unless they are in the contract. If a salesperson says “we include that,” ask for it to be added to the service schedule.
- Review the auto-renewal clause — many contracts auto-renew for another 12–24 months unless you give notice 3–6 months before the end date. Set a calendar reminder or negotiate removal of auto-renewal.
When to Renegotiate or Switch Provider
Your IT support contract should be reviewed annually, even if you are happy with the service. Renegotiation triggers include your contract approaching its end date or renewal point, persistent SLA breaches that are not being addressed, significant changes in your business size or IT requirements, the discovery of hidden fees or unexpected charges, your provider being acquired by or merged with another company, and pricing that is no longer competitive based on market comparison.
If you decide to switch provider, start the process at least 3–6 months before your current contract ends. This gives you time to evaluate alternatives, negotiate terms, and plan a smooth transition. For more guidance on switching, see our guide to why businesses are switching IT provider in 2026.
Get a Transparent IT Support Contract
Connection Technologies offers fully transparent IT support agreements with no hidden fees, flexible terms, and clear SLAs. See exactly what you are paying for before you sign.
Or call us on 0333 015 2615
Frequently Asked Questions
What should be in an IT support contract?
Every IT support contract should include a detailed service scope, defined SLAs with response and resolution targets, transparent pricing with no hidden fees, clear contract length and renewal terms, fair exit and termination clauses, data protection and security obligations, and IP/documentation handover requirements. If any of these are missing or vague, request clarification before signing.
How long should an IT support contract be?
For most UK SMEs, a 12-month contract offers the best balance of price and flexibility. Rolling monthly contracts give maximum flexibility but may cost 5–15% more per user. Contracts longer than 24 months should generally be avoided unless you are confident in the provider and have negotiated fair break clauses and price caps.
Can I get out of a bad IT support contract?
Yes, but the cost depends on your contract terms. Check for persistent SLA breach clauses that may allow early termination without penalty. If no such clause exists, negotiate an exit — many providers will agree to a reduced settlement rather than retain a dissatisfied client. Always seek legal advice before attempting early termination.
What are typical hidden fees in IT contracts?
The most common hidden fees include onsite visit charges, out-of-hours support surcharges, project work reclassification, third-party licence costs not included in per-user pricing, onboarding fees, hardware procurement markups, and aggressive annual price escalation clauses. Always request a fully itemised quote and clarify exactly what is and is not included.
Related IT Guides
Related Reading
More from the Connection Technologies blog.