Skip to content

SLO and OLA

Adrià Castany 2 min

What is an SLO and OLA?

An SLO and an OLA are the internal commitments that make it possible to meet an SLA. The SLO, or service level objective, is the measurable target a team sets itself, nearly always stricter than what was promised to the customer. The OLA, or operational level agreement, is the deadline two teams in the same company give each other.

Also called

service level objective, operational level agreement, SLI, internal service target

Topic
Support concepts
On this page
  1. SLA, SLO and OLA
  2. Why it matters
  3. SLA, SLO and OLA, the differences
  4. How to set an SLO
  5. What an OLA contains
  6. The most common mistake
  7. How Intake handles it
  8. Frequently asked questions

SLA, SLO and OLA

The SLA is the commitment to the customer and usually carries financial consequences if missed.

The SLO is an internal objective with no penalty. The OLA splits that objective between the teams involved, for example support and engineering. A fourth term, the SLI or indicator, is the actual measurement the other three are set on.

Why it matters

An SLA with no internal objectives is missed in the first bad month.

The SLO leaves room between what is promised and what is achieved, and the OLA stops support from promising a customer a deadline that depends on another team that never agreed to one.

SLA, SLO and OLA, the differences

All three talk about deadlines and levels, and what changes is who agrees them.

SLASLOOLA
BetweenThe company and its customerThe team and itselfTwo teams in the company
Where it livesIn the contractIn the team’s objectivesIn an internal agreement
If missedWhatever the contract saysThe process is reviewedThe teams review it
ExampleFirst response in four hoursFirst response in two hoursEngineering answers support in a day

How to set an SLO

An SLO is set tighter than the SLA and looser than what the team already achieves comfortably.

The figures in the example are illustrative.

  • Choose the indicator, such as first response time.
  • Look at what the team achieves in a normal month and in a bad one.
  • Set the objective, for example 95% of conversations within two hours.
  • Leave room up to the SLA, for example four hours.

What an OLA contains

An OLA contains the same as an SLA, in miniature and without penalties.

  • Which teams agree it and for which kind of case.
  • The response and resolution deadlines, by priority.
  • The information a case must carry when it moves between teams.
  • How it is measured and how often it is reviewed.

The most common mistake

Signing the SLA before the OLA exists.

If the resolution time promised to the customer depends on engineering, engineering has to have accepted a shorter one first.

How Intake handles it

Frequently asked questions

What is the difference between an SLO and an SLA?

The SLA is what the contract promises the customer. The SLO is the internal objective the team sets to meet it with room to spare, and it carries no penalty.

What is an OLA?

An operational level agreement. It is the deadline two teams in the same company agree on, such as support and engineering, so that the commitment to the customer can be met.

What is an SLI?

The service level indicator, the actual measurement being watched. First response time and availability are indicators. The SLO is the value you want that indicator to reach.

Does a small company need an OLA?

It does as soon as a commitment to a customer depends on a team other than the one that signs it. With few people, one page with the deadlines and what each case must carry is enough.

Glossary

Keep reading

Glossary

Related terms

See the full glossary

Add it without dropping what you use

15 minutes, no commitment