Service level agreement
A service level agreement (SLA) is the part of a continuing operations contract that names the measurable commitments a provider makes on a running system — availability, how fast it responds to an incident and how fast it resolves one — and what happens when a commitment is missed.
Submit a project Scope your operations arrangementReviewed by David Nguyen (CEO) · Updated 14 Oct 2026 · 3 min read
This term is one of the entries in the OutsourcingVN glossary of words buyers meet while agreeing a managed operations arrangement.
Why does a service level agreement matter?
Without a service level agreement, "we'll keep it running" means whatever each side assumes until the first serious incident forces the question. OutsourcingVN is operated by Netbase JSC, and a buyer comparing operations providers should expect a credible one to separate three things clearly: a measured indicator, such as how long a checkout request takes; a target for that indicator; and, only in an SLA proper, a consequence attached when the target is missed. Confusing the three is how a buyer ends up with a document that reads like a commitment but carries none.
What is an example of a service level agreement in practice?
A retailer's order-management system moves to a managed operations provider. Before setting any targets, the provider measures a month of real traffic and finds that order confirmations normally reach the warehouse system within ninety seconds. The SLA then sets a target just outside that normal range, with an agreed response time for an incident that breaches it and a credit if the response is late three times in a quarter. Because the target came from measurement rather than a template, both sides can tell a genuine incident from normal variation.
What are the common misreadings of a service level agreement?
A service level agreement is not the same as a service level objective: an objective is an internal target a team works to, while an agreement is the version with contractual consequences attached, and conflating the two makes an internal stretch goal look like a binding promise. It is also not a guarantee that nothing will go wrong — a well-written SLA assumes incidents happen and defines how fast they are met, not that the system never fails. And an SLA copied from a template before anyone has measured the system is a guess dressed as a commitment, which produces disputes rather than reliability once real traffic arrives.
Plan the next step for your project
Common questions
No. A support contract covers who does the work and under what terms; the SLA is the specific, measurable commitments inside or alongside that contract.
Ideally both sides, after a baseline measurement period, rather than one side proposing round numbers with no data behind them.
Which decisions does a service level agreement affect?
Agreeing what a managed operations arrangement covers, including coverage hours, objectives, change authority and exit terms, is the subject of the managed software operations scope guide. When you are weighing a continuing operations arrangement for a live system, describe it and Netbase will respond through Netbase's own outsourcing-services platform; submit a project when you are ready.