What To Do If Your IT Supplier Misses An SLA

Mike runs a small online retailer in Manchester. His website is hosted by an IT supplier that promises 99.9% uptime, but over the last month the site has gone down three times during peak trading hours.

Customers are complaining, staff are spending hours raising support tickets, and Mike's supplier keeps saying, "we're looking into it". He knows there's a service level agreement somewhere in the contract, but he's not sure what it actually lets him do.

If your supplier missed the service level agreement, it's frustrating - especially when the issue is affecting sales, staff productivity or your customers' trust. The good news is that you usually have more options than just putting up with it or cancelling the contract on the spot.

What Should You Do First When Your IT Supplier Misses An SLA?

You should first check the contract, confirm what the SLA actually promises, and keep a clear record of what went wrong.

An SLA is often part of a wider contract, such as a master services agreement, SaaS agreement, IT services agreement, managed services agreement, hosting agreement or order form. Don't just look for a document called "SLA". The key terms may be spread across several documents.

Start by checking:

• The service being measured: Is the SLA about uptime, response times, resolution times, processing speed, backups, support availability or something else?
• The measurement period: Is performance measured daily, weekly, monthly, quarterly or across a rolling period?
• Exclusions: Planned maintenance, your own internet connection, third-party platforms, force majeure events or problems caused by your team may be carved out.
• Notice requirements: Some contracts require you to report an SLA failure within a set number of days or submit a credit request in a particular way.
• Remedies: The contract may give you service credits, escalation rights, audit rights, termination rights or another remedy.

Then create a simple incident timeline. For each outage or failure, record the date, start time, end time, what systems were affected, who noticed it, what the supplier said, and what impact it had on your business.

This doesn't have to be complicated. A spreadsheet, copied support tickets and screenshots can be enough to get the conversation onto firmer ground.

Is A Missed SLA A Breach Of Contract?

It depends on how the SLA is drafted, but a missed SLA can be a breach of contract if the service levels are binding obligations rather than targets.

Some SLAs are written as firm promises. For example, "the supplier will provide 99.9% uptime each calendar month" or "priority 1 incidents will receive a response within 30 minutes". If those promises aren't met and no exclusion applies, that may be a breach of service level agreement.

Other SLAs are softer. They may say the supplier will "aim to" meet a target or use "reasonable endeavours" to respond within a timeframe. Those words still matter, but they may be harder to enforce than a clear guarantee.

For business-to-business services under a service agreement in England and Wales, the written contract is usually the starting point. If the contract is silent or unclear, the Supply of Goods and Services Act 1982 may imply a term that the supplier must carry out the service with reasonable care and skill. Suppliers often try to limit or exclude certain liabilities in their terms, but exclusions and limitations can be tested under the Unfair Contract Terms Act 1977, especially where standard terms are involved.

A missed SLA won't always justify termination straight away. The practical question is usually:

• Was the SLA term central to the contract?
• Was this a one-off failure or a repeated pattern?
• Did the supplier fix the issue quickly?
• Did your business suffer measurable loss?
• Does the contract say service credits are your only remedy?

If you're dealing with a serious IT supplier breach of contract, get the contract checked before you make a strong allegation or threaten termination. Saying the wrong thing too early can make the dispute harder to resolve.

Can You Claim SLA Service Credits?

Yes, you can usually claim SLA service credits if your contract gives you that right and you follow the claim process.

Service credits are a common remedy for IT contracts. They usually reduce your next invoice rather than give you a cash payment. For example, the contract might say you receive a 10% monthly fee credit if uptime falls below 99.9%, and a 25% credit if it falls below 99%.

Here's a simple example. Say you pay your hosting provider 2,000 pounds per month, and the SLA promises 99.9% uptime each calendar month. In a 30-day month, 99.9% uptime allows about 43 minutes of downtime. If your website is down for 7 hours, and no exclusion applies, the supplier has missed the SLA by a long way.

If the contract gives a 10% credit for that level of failure, your service credit would be 200 pounds off the next invoice. That may not cover all your lost sales, but it gives you a contractual remedy you can claim without immediately escalating to a major dispute.

Before you claim, check:

• Claim deadline: Some contracts require claims within 5, 10 or 30 days after the month ends. Use the exact deadline in your contract.
• Evidence required: You may need monitoring logs, support ticket numbers or written confirmation from the supplier.
• Credit cap: Many contracts cap service credits at a percentage of the monthly fees.
• Exclusive remedy wording: Some contracts say service credits are your sole remedy for an SLA failure. That wording needs careful review if your losses are much larger than the credit.
• Repeated failure rights: You may get extra rights if the supplier misses the SLA for several months in a row.

If the credit is small but the disruption is large, don't ignore the credit. Claiming it can help create a paper trail and show the supplier that you're enforcing the contract properly.

How Should You Preserve Evidence And Communicate?

You should preserve evidence calmly and communicate in writing, because a service level agreement dispute is often won or lost on the records.

Avoid relying on memory or informal phone calls. When systems fail repeatedly, details blur quickly. Your aim is to build a clean file that shows what happened, when it happened, how the supplier responded and what your business did to reduce the damage.

Keep copies of:

• the signed supplier agreement, order forms, schedules and any SLA documents
• support tickets, emails, chat transcripts and incident reports
• screenshots of error messages, dashboards or status pages
• system logs, monitoring reports and uptime reports
• customer complaints, refund requests or internal staff reports
• notes of phone calls, including the date, people on the call and what was agreed
• invoices, payment records and any service credit calculations

Your messages to the supplier should be firm, factual and free from unnecessary blame. A helpful email might say:

We recorded outages on 3, 11 and 18 May, totalling approximately 7 hours. Based on clause 4 of the SLA, we understand the monthly uptime commitment hasn't been met. Please confirm the cause, the corrective action being taken, and the service credit to be applied to our next invoice.

If personal data has been affected, treat that as a separate issue as well. Under the UK GDPR and the Data Protection Act 2018, you may need to assess whether there has been a personal data breach. If you're the controller and the breach is likely to risk people's rights and freedoms, notification to the Information Commissioner's Office is generally required within 72 hours of becoming aware of it. Your supplier may also have processor obligations under your data processing agreement.

Can You Escalate, Terminate Or Withhold Payment?

Yes, you may be able to escalate, terminate or withhold payment, but the safest option depends on your contract and the seriousness of the failures.

Most IT contracts have an escalation process. This may require the issue to go from helpdesk support to an account manager, then to senior management, then to a formal dispute process. Follow that process where you can. It shows you've acted reasonably and gives the supplier a final chance to fix the problem.

Escalation

Escalation is often the best first step when the relationship is still worth saving. Ask for:

• a root cause analysis
• a corrective action plan
• named contacts for future incidents
• temporary workarounds
• extra reporting until performance improves
• confirmation of any service credits

Termination

Termination is a bigger step. Check whether the contract gives you a right to terminate for material breach, repeated SLA failures, prolonged outages or failure to fix a breach within a cure period.

Many contracts require a written breach notice and a chance for the supplier to remedy the breach, often within a period set out in the contract. Don't assume you can terminate immediately unless the contract clearly allows it or the breach is so serious that it goes to the heart of the contract.

If you terminate without a valid right, the supplier may argue that you have breached the contract instead. That can expose your business to unpaid fees, early termination charges or a dispute about damages.

Withholding Payment

Withholding payment can be tempting, especially if the service has been poor. Be careful. If the contract doesn't let you withhold or set off amounts, stopping payment may put you in breach.

A safer approach is often to pay undisputed amounts, claim any service credits, and clearly reserve your rights about the disputed part. The wording matters, so get advice if the sums are significant or the supplier is threatening suspension.

How Can You Renegotiate Without Making The Dispute Worse?

You can renegotiate by focusing on practical fixes, clear future obligations and a written variation to the contract.

If the supplier is otherwise valuable, renegotiation may be better than termination. This is especially true where switching providers would be expensive, technically difficult or risky for your customers.

Useful changes might include:

• higher uptime or response commitments for business-critical systems
• clearer definitions of downtime and severity levels
• stronger service credits for repeated failures
• a right to terminate after a set number of missed SLAs
• better reporting, incident reviews and root cause analysis
• data backup, disaster recovery and business continuity commitments
• migration help if you decide to leave later

Put any agreed change in writing as a contract variation. A friendly email chain can help show what was discussed, but it may not clearly amend the contract unless it meets the variation requirements in your agreement.

Fill-In Outline For A Supplier Escalation Notice

You can use this outline to organise your thoughts before sending a formal notice. It isn't a finished legal document, and a lawyer should tailor it before you use it for a serious breach or termination step.

1. Parties And Contract: Identify your business, the supplier, the contract name and the date it was signed.
2. Relevant SLA Terms: Quote the clauses that set the service levels, exclusions, service credits and escalation process.
3. Incident Timeline: List each outage or failure with dates, times, systems affected and ticket numbers.
4. Business Impact: Explain the practical effect on sales, staff, customers, compliance or operations.
5. Remedy Requested: Ask for service credits, a root cause analysis, corrective action and any urgent workaround.
6. Deadline For Response: Give a clear date for the supplier to respond, using any timeframe required by the contract.
7. Reservation Of Rights: State that you aren't waiving any contractual rights while discussions continue.

Keep the tone constructive. The goal is to protect your position while leaving room for a commercial fix.

Key Takeaways

• If your IT supplier misses an SLA, start by checking the contract, the measurement period, exclusions, notice requirements and remedies.
• A missed SLA can be a breach of contract, but whether you can terminate or claim losses depends on the wording and the seriousness of the failure.
• SLA service credits are often available, but you may need to claim them within a strict deadline and provide evidence.
• Keep a clear record of outages, tickets, screenshots, logs, customer impact and supplier communications.
• Escalation and renegotiation can often solve the problem without making the dispute worse, especially if switching suppliers would disrupt your business.
• If personal data or critical systems are affected, consider your UK GDPR, contract and business continuity obligations straight away.

If you'd like help with reviewing your IT contract, claiming service credits, preparing an escalation notice or renegotiating your supplier terms, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.