A service level agreement, or SLA, is the part of a support contract that says how quickly the supplier will respond to a problem, during which hours, and what happens if it does not. It is a good idea to have one for any software the business depends on, because without it the word “urgent” has no agreed meaning and you have nothing to measure the service against.
In short, a software support SLA should contain the hours of cover, three or four severity levels defined by their effect on the business, a response time for each level, an escalation route and a regular performance report. The checklist below shows what to look for in each.
What a software service level agreement covers
An SLA belongs to an ongoing service. For software, that means support and maintenance after a system has gone live. A project to build something new is governed by different things: a scope, a price and acceptance checks.
We list everything a contract should contain, including the SLA, in what a software support contract should include.
It helps to separate two kinds of SLA that are often confused. A hosting provider’s SLA promises availability: the servers will be running for a stated proportion of the time. A support SLA promises attention: a qualified person will start work on your problem within a stated time. A bespoke system usually needs both, from different parties, and one does not substitute for the other.
An example severity table
The table below shows the usual shape of severity levels. The figures are illustrative, to show how the levels relate to each other, not our terms or a recommendation for your system.
| Severity | Effect on the business | Example | Example response target |
|---|---|---|---|
| 1. Critical | Nobody can work, or data is being lost or exposed | The order system will not open for anyone | Within a few working hours, possibly with cover outside office hours |
| 2. Major | An important function has failed, but there is a way round it | Invoices will not print, but can be exported and sent by hand | Same or next working day |
| 3. Minor | Inconvenient or cosmetic | A report column is mislabelled | Planned into routine work |
Describe each level by its effect, not its technical cause, so that whoever reports the fault can class it without knowing the code.
Why it is worth having
Priorities are settled in advance. The worst moment to negotiate how serious a fault is, and how fast someone should act, is during the fault. An SLA makes that decision calmly, months earlier, with both sides in the room.
You can measure the service. With targets written down and tickets timed against them, a review of the supplier rests on a report. Without them it rests on how the last conversation went.
It tells you what you are paying for. A supplier that commits to respond within hours has to keep people available, and that costs more than a commitment to respond next day. Seeing the levels side by side lets you buy the cover the business needs and no more.
It outlasts the people. Informal arrangements work while the two people who made them are still in post. A written agreement stays when they move on.
What an SLA cannot do
An SLA is a promise about behaviour. It is not a guarantee about the software.
A response time is not a fix time. Most suppliers of bespoke software commit to how soon work starts, because how long a repair takes depends on a cause nobody yet knows. Be wary of a promise to fix any fault within a fixed number of hours. Either it is hedged somewhere else in the document, or it will be met with hurried patches.
Service credits rarely cover the loss. Many SLAs give a credit against the fee when a target is missed. The credit is a signal and an incentive. It will be small beside the cost of a day without your order system. Some contracts also state that credits are your only remedy for poor service. Whether an SLA is enforceable, and what you can claim if it is breached, depends on how the contract is written, so have a solicitor read it before you sign.
It does not make a neglected system reliable. If the software is on an out-of-support platform, has no tested backup and can only be released by one person, quick responses will not prevent the outages. The planned work matters as much as the reactive work, which is why we treat support and maintenance as two halves of one job.
It means little from a supplier who does not know the system. A team that has never built your application from its source code cannot honestly promise how it will handle a fault. This is why we set the terms of an agreement after assessing the system, not before.
Five things to check in a draft
-
How severity is defined. Each level should be described by its effect on the business, as in the table above. Check who decides the level when you and the supplier disagree.
-
What “response” means. An automatic email saying the ticket has been received is not a response. Look for wording that requires a person able to work on the problem to have started.
-
When the clock runs. A four-hour response within working hours means a fault reported at five in the afternoon may be picked up the next morning. Check the hours of cover, the treatment of bank holidays, and whether the clock stops while the supplier waits for information from you.
-
What happens when a target is missed. Look for a named person to escalate to, and for a consequence of repeated misses, such as the right to end the contract early.
-
How performance is reported. You should receive a regular report showing each ticket, its severity and whether the target was met, drawn from the ticket system and not compiled from memory. Our guide to software support ticket systems covers what to expect from one.
Choosing the right level of cover
More cover is not always better: it costs more, and the money may do more good spent on preventing faults. Work out what an hour and a day without the system cost. A system used by six people in one office to produce monthly reports can wait until the next working day. A system that takes customer orders, runs a production line or pays people is a different matter, and may justify cover outside office hours. Look at when it is used, too: cover from nine to five is no help to a warehouse that starts at six.
Suppliers usually publish a few levels of cover so that you can match one to the system. Ours are set out under the support plans on our software maintenance page. If the system is already in trouble and there is no agreement at all, emergency software support deals with the immediate problem first.
What if you have no SLA, or inherit a system?
Many businesses have no written terms at all, or inherit a system when a supplier stops trading or a developer leaves. Start by gathering what exists: the ticket or email history of faults, the hours actually worked, and any contract or quote that mentions support. That history shows what faults the system has and how often, which is the evidence you need to choose a level of cover.
Then agree interim terms in writing, even if they are only a page long: who to contact, in which hours, and how soon they will respond to a critical fault. Replace them with a full agreement once the supplier has assessed the system. If the current supplier is withdrawing, see what to do when your supplier stops supporting your software and our software takeover process.
Making it work after you sign
An SLA that nobody looks at decays. Report every problem through the agreed route: a call to a helpful developer gets the fault fixed but leaves no record. Read the report when it arrives, review it with the supplier every quarter, and ask which faults recurred and why. Try the urgent route once before you need it.
Before you sign a draft, take the last three serious faults the system suffered and ask the supplier how each would have been classed and handled under the agreement. The answers will show whether the document describes a service you would have been happy with.
Frequently asked questions
What is a service level agreement for software support?
It is the part of a support contract that sets hours of cover, severity levels, response times, escalation and reporting. It turns “we will look after it” into terms both sides can measure.
What is the difference between a support SLA and a hosting SLA?
A hosting SLA promises the servers will be available. A support SLA promises a person will start work on a fault within a stated time.
What response time is reasonable for a business-critical system?
It depends on what an hour without the system costs and when it is used. Work that out first, then choose the cover, as described above.
Is an SLA legally binding?
If it is part of a signed contract, its terms are contractual. What you can claim for a missed target depends on the wording, so take legal advice before you sign.
Can a supplier who did not build my software offer an SLA?
Yes, once it has assessed the system and shown it can build, release and restore it. Firm response times offered before anyone has seen the code are a guess.
What should I do if my supplier keeps missing its SLA?
Escalate through the agreed route with the ticket report that shows each miss. If misses continue, check what the contract says about ending it, and plan an orderly change of supplier before you serve notice.