- An SLA is a contractual commitment about the performance of a service, not the service itself.
- Most SLAs make clear that a service credit is the customer's sole and exclusive remedy for a missed commitment, meaning the customer generally can't also sue for damages caused by the…
If your business depends on a software vendor's platform staying online, or on an IT provider fixing problems quickly, the promises around how reliably and how fast usually live in a separate document from the main contract: the service level agreement, or SLA. Understanding what an SLA actually guarantees — and what it doesn't — matters whether you're the customer relying on it or the vendor offering it.
What an SLA Is (and Isn't)
An SLA is a contractual commitment about the performance of a service, not the service itself. It typically sits alongside — and is incorporated by reference into — the main software or services agreement. An SLA is not a guarantee that nothing will ever go wrong; it's a defined set of remedies for when things do.
The Core Components of an SLA
| Component | What It Covers |
|---|---|
| Availability commitment | A stated commitment to how often the service will be operational, usually expressed as a target over a defined measurement period |
| Response time | How quickly the vendor will acknowledge a reported issue, often tiered by severity |
| Resolution time | How quickly the vendor commits to actually fixing or working around a reported issue, also often tiered by severity |
| Severity definitions | Clear criteria for what counts as a critical outage versus a minor issue, since response commitments usually differ by tier |
| Exclusions | Circumstances the availability commitment doesn't cover — scheduled maintenance windows, events outside the vendor's control, problems caused by the customer's own systems |
| Remedies / service credits | What the customer receives if the vendor misses the commitment, typically a credit against future fees calculated according to a defined formula |
| Measurement and reporting | How performance is actually measured and how disputes about whether a target was met get resolved |
Why Service Credits Are Usually the Only Remedy
Most SLAs make clear that a service credit is the customer's sole and exclusive remedy for a missed commitment, meaning the customer generally can't also sue for damages caused by the outage, only claim the defined credit. This is a significant limitation that customers often don't notice until they're negotiating a contract after a bad experience with a different vendor. If your business would face real losses from an outage, negotiate this point specifically rather than assuming the credit will make you whole.
What to Check Before You Rely on an SLA
- [ ] Does the availability commitment measure the whole service, or only certain components? A platform can technically be "available" while a feature you depend on is down.
- [ ] Are the exclusions reasonable, or broad enough to swallow the commitment (such as an unlimited maintenance-window exclusion)?
- [ ] How is a missed target actually calculated, and who is doing the measuring — an independent tool, or only the vendor's own internal reporting?
- [ ] Is there an escalation path if the vendor disputes that a target was missed?
- [ ] Does the SLA commitment survive if the vendor is acquired, changes its infrastructure, or subcontracts hosting to a third party?
- [ ] Are service credits capped, and if so, at what point does a chronic problem give you a right to terminate rather than just collect credits?
For Vendors: Setting SLA Terms You Can Actually Meet
If you're the one offering an SLA, resist the temptation to promise a commitment your infrastructure can't reliably support just to win the deal. An SLA you regularly miss creates ongoing credit obligations, damages the relationship, and — if a customer can show a pattern of chronic failure — can support an argument that the service is fundamentally not what was promised, beyond just the service-credit remedy.
Frequently asked questions
Is an SLA a separate contract, or part of the main agreement?
Usually it's a schedule or exhibit attached to and incorporated into the main services or licence agreement, rather than a standalone contract. It should be read together with the liability and remedy provisions in the main agreement, since they often interact.
Can I negotiate SLA terms, or are they always take-it-or-leave-it?
Large platform vendors often treat their standard SLA as non-negotiable for smaller customers, but that's not universal, and even where the SLA itself is fixed, the exclusions, escalation process, and interaction with your broader contract can sometimes be negotiated.
What happens if a vendor misses its SLA repeatedly?
Well-drafted agreements include an escalating remedy for chronic failures — for example, a right to terminate without penalty if the vendor misses its commitment more than a defined number of times in a period. If your contract doesn't have this, a pattern of failures may still support other legal arguments, but you're in a weaker position.
Do service credits actually compensate for the harm caused by an outage?
Rarely fully. Service credits are typically a percentage of the fees you paid for the affected period, which is often far less than the actual cost of a serious outage to your business. This is exactly why the exclusivity of the remedy matters so much in negotiation.
This is a corporate question
Start a file online — flat, published fees, reviewed by a licensed Ontario lawyer before a dollar is owed.