SLA vs SLO

Purpose

This reference note explains sla vs slo in practical operating language. Use it to align vocabulary before turning the concept into a workflow, policy, or checklist.

Plain meaning

SLA vs SLO is included as a practical term because teams often use it inconsistently. Before a workflow or policy can work, the people using it need the same operating definition.

How to use this term

• Use the term in decisions, not as decoration.
• Pair it with an owner, evidence source, or review trigger when possible.
• If people disagree about meaning, add a short local definition to the relevant template or policy.

When to use

• When the work repeats often enough that memory is no longer reliable.
• When more than one person may request, perform, review, or inherit the work.
• When risk, approval, evidence, or handoff needs to be visible later.

Common failure modes

• Ownership is implied rather than named.
• Inputs are accepted before they are complete.
• The output is not easy to verify later.

Review guidance

Review this page after a material incident, after a role or system change, and on a normal cadence appropriate to its risk. During review, check whether the owner is still correct, whether inputs are still complete, whether the output is still useful, and whether related pages need updates.

Related DailyWF pages