
OLA vs SLA: the agreements behind your SLA that your provider makes with itself
In the OLA vs SLA question, most buyers only ever see the second: the agreement they sign. But an SLA is only as strong as the agreements behind it, between your provider’s own teams and with the third parties it relies on. You rarely see those, and that is usually where it goes wrong.
An SLA is the agreement between you and your provider. An OLA is the agreement between that provider’s teams, and an underpinning contract (UC) is the one with an external party such as a carrier or manufacturer.
An SLA target is met or missed in the handovers between teams. Without an OLA, a ticket sits with the second team in a queue that nobody is watching.
You are not entitled to your provider’s internal documents, but you are entitled to an answer on who touches your ticket and whether their hours and targets fit your SLA.
OLA, SLA and UC: three agreements in one chain
The terms come from ITIL, and they describe three layers of the same promise:
- SLA (service level agreement). The agreement between the provider and you: which service, which response and resolution targets, within which hours, and how it is reported.
- OLA (operational level agreement). The agreement between two teams inside the same provider: the service desk and the network team, the workplace team and the field engineers. What one team can expect from the other, and how quickly.
- UC (underpinning contract). The contract between your provider and an external party it depends on: a connectivity carrier, a manufacturer with a warranty scheme, a partner supplying hands on site at a remote location.
So the difference between an OLA and an SLA is not the content but who agrees with whom. An SLA is external and contractual; an OLA is internal and carries no service credits, but it decides whether the SLA can be met.
Why an SLA without OLAs is an unfunded promise
Follow one ticket: a branch cannot print or reach the shared drive. The service desk logs it, sees a network problem and passes it to the network team. They find a faulty switch and request a field engineer, who turns out to need a replacement part from the manufacturer.
Four handovers, and the SLA only measures the total. If the network team has no agreed time within which it picks up a transferred ticket, the call waits in a queue between other work. Nobody breaks a rule, because there is no rule, and the SLA target is missed before anyone has started.
That is what an OLA is for: it makes every handover visible and gives each team ownership of its own slice of the time. Without one, the provider finds out at the monthly report that a target was missed, and by then nobody knows where the time went.
The targets and the hours have to fit together
An OLA only has value if it fits inside the SLA. That sounds obvious, but it hides two traps you will not find in any contract.
- The sum. The internal targets of every team in the chain, plus the time of the external party, must together be shorter than the SLA target, with room left for the handovers themselves. If the second team may use almost the whole SLA window, nothing is left for the third.
- The hours. If the SLA promises cover outside office hours, every team in the chain has to be reachable then too. A service desk that answers in the evening does not help if the network team only works days; you then have evening cover that stops at the first escalation.
The same applies to the UC. A carrier’s repair time or a manufacturer’s delivery time is a fixed part of the chain, and no provider can promise below it. How to handle that in the SLA itself is covered in our article on SLAs you can actually meet. Here the question is whether your provider knows those times and has built them in.
What belongs in an OLA
An OLA does not need to be a long document. What makes it usable:
- Which teams and which service. Who delivers to whom, and for what kind of work.
- The handover point. When a ticket counts as transferred, and with what information attached. An escalation without the error message, the location and what has already been tried costs the next team a round of questions first.
- The internal targets. How quickly the receiving team picks up and reports back, per priority, derived from the SLA rather than invented separately.
- Availability. The hours the team works and who is called outside them.
- Escalation. What happens when an internal target is at risk, and who may decide.
- Measurement and review. From the ticketing system, with a fixed moment where the teams look together at where time was lost.
If a provider works with a single team that does everything, there is less to hand over. The dependence on external parties remains, though, and that belongs in the UC.
OLA vs SLA: what you can ask as a customer
An OLA is an internal document and you have no right to it. What you can ask, and what a good provider answers without effort:
- Who touches my ticket? Which teams and external parties sit between my call and the fix, for the three or four types of fault we see most often.
- Do your internal hours fit my SLA? Especially if you have agreed cover outside office hours or on Saturdays.
- Which UCs sit underneath? Which carrier, manufacturer or partner holds part of my resolution time, and what have they committed to.
- Where did the time go? Can the monthly report show, for a missed target, which link in the chain held the ticket, rather than only that the target was missed.
The last one is the sharpest test. A provider that can show per handover where a ticket waited is working with OLAs, even if it calls them something else. A provider that cannot is steering on the SLA without knowing how it meets it.
The OLA on your side of the table
One link is almost never drawn in the chain: your own organisation. A field engineer needs someone to open the building or the server room. A change to a till system needs approval from someone reachable at that moment. A software vendor you hold the contract with has to be called by you, or has to know that your provider may call on your behalf.
Those are internal agreements on your side, and they cost just as much time as a queue at the provider. Record them as named contacts with availability and a deputy, and have the SLA state that the clock stops while the provider is waiting on you. That also shows you where you can speed up yourself.
Where our work stops
What we do. We work with internal agreements between our own teams and with agreements with the parties we depend on, and on request we explain how the chain behind your SLA runs: who touches your ticket, in which hours and where the time sits. We are ISO 9001 and ISO/IEC 27001 certified; that describes how we work, not a verdict on other providers.
What we do not do. We do not make agreements on your behalf with suppliers you hold the contract with, such as your software vendor; that agreement stays between you and them. We are not lawyers and do not review contracts legally, including another party’s SLA or UC. And where we supply your internet connection, the infrastructure underneath remains the network operator’s: their repair time is a fixed part of the chain that we can plan for but cannot shorten.
Questions we get about this
The five that come up most often.
What is an OLA?
An OLA (operational level agreement) is an agreement between two teams inside the same IT provider, for example the service desk and the network team. It sets when a ticket counts as handed over, with what information, how quickly the receiving team picks it up and the hours it is reachable. An OLA is internal and carries no service credits.
What is the difference between an OLA and an SLA?
An SLA is the agreement between a provider and its customer about the service and its performance. An OLA is the agreement between teams inside that provider, and it decides whether the SLA can be met in practice. The SLA measures the whole; the OLAs divide that whole across the links in the chain.
What is an underpinning contract?
An underpinning contract (UC) is the contract between your IT provider and an external party its service depends on, such as a connectivity carrier, a manufacturer or an on-site partner. The times that party commits to are a fixed part of the resolution time under your SLA. A provider cannot promise below them.
Am I entitled to see my provider’s OLAs?
Usually not, because they are internal documents. You can ask which teams and external parties touch your ticket, whether their hours fit your SLA and whether the monthly report shows where the time went when a target was missed. A provider that works with OLAs answers those questions without effort.
Can you align our other suppliers’ contracts with our SLA?
We can map the chain and point out where another supplier’s times or hours do not fit your SLA. The agreement itself stays between you and that supplier, and we do not negotiate or sign on your behalf. A legal review of those contracts is a job for a lawyer.
Further reading
What the agreements behind your SLA connect to.
Shall we map the chain behind your SLA together?
Bring your current SLA and the three faults that come back most often. We will show which teams and parties sit behind them and where time can be lost; the legal side we leave to your lawyer.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.