SLOs & error budget policy template

Define SLIs and SLOs per service, turn them into an error budget, and agree what happens to releases as the budget burns.

Use this templateFree, opens in your browser. No sign-up.

SLOs & error budget policy template
Service
SLI (good events ÷ valid events)
SLO
Window
Error budget
Checkout API
Requests returning non-5xx in < 800 ms
99.9%
30 days
0.1% of requests (≈ 43 min)
Search
Queries answered in < 300 ms
99.5%
30 days
3 h 36 min
Order emails
Emails sent within 5 min of the order
99%
30 days
1% of emails late
Mobile app launch
Cold starts under 2 s
95%
28 days
5% slow launches
Error budget left this window?
> 50%: ship normally, run chaos experiments
10–50%: extra review for risky changes
< 10%: only low-risk releases, reliability work first
Exhausted: feature freeze until back within SLO
Postmortem for any incident using > 20% of budget
Error budget policy
Burn-rate alerts (Checkout, 99.9%)
Burn rate
Look-back window
Budget used
Action
14.4×
1 h (and 5 min)
2%
Page on-call
6×
6 h (and 30 min)
5%
Page on-call
1×
3 days
10%
Ticket for the team
99.9% over 30 days = 43 min 12 s of allowed downtime
Budget policy agreed by product + engineering, reviewed every quarter
SLOs & error budget
The SLOs & error budget policy template as it opens in Kelvo: 6 boxes, 1 decision among them, 2 sticky notes, 2 tables and 6 links.

What's on the board

Table 1 columns: Service, SLI (good events ÷ valid events), SLO, Window, Error budget.

Table 2 columns: Burn rate, Look-back window, Budget used, Action.

  • Burn-rate alerts (Checkout, 99.9%)
  • 99.9% over 30 days = 43 min 12 s of allowed downtime
  • Budget policy agreed by product + engineering, reviewed every quarter
  • Error budget policy
  • Error budget left this window?
  • < 10%: only low-risk releases, reliability work first
  • > 50%: ship normally, run chaos experiments
  • 10–50%: extra review for risky changes
  • Exhausted: feature freeze until back within SLO
  • Postmortem for any incident using > 20% of budget

How to use this template

  1. Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
  2. Double-click any box to change its text. Replace the examples with your own content.
  3. Link by dragging. Hover a box and drag one of its dots onto another box. The whole box is the target, and links stay attached when you move things.
  4. Sketch, then convert. Draw boxes and arrows with the pen, select the strokes and click Convert sketch: they become real boxes and links.
  5. Group by environment or region. Draw a frame (F) around a group of services; moving the frame moves everything inside it.

Good for

  • sre
  • slo
  • error budget
  • reliability
  • monitoring
  • Design reviews and architecture decision meetings
  • Runbooks and onboarding for on-call engineers
  • Planning a migration or a cost-cutting pass

Related templates

  • Observability stack template previewObservability stack

    Metrics, logs and traces through OpenTelemetry into Prometheus, Loki and Tempo, with Grafana, alerting and SLO notes.

  • On-call incident runbook template previewOn-call incident runbook

    What the on-call engineer does when a page fires: acknowledge, judge impact, declare, mitigate first, then escalate and follow up.

  • AWS three-tier web app template previewAWS three-tier web app

    A highly available web app on AWS: DNS and CDN, load balancer, auto-scaled app servers and Multi-AZ database in a VPC.

  • Kubernetes cluster overview template previewKubernetes cluster overview

    Ingress, services, deployments and pods in a namespace, with config, storage, control plane and add-ons around them.

  • Incident response template previewIncident response

    Detect, triage, mitigate, communicate, resolve and learn — an on-call runbook in one view.

  • Incident postmortem template previewIncident postmortem

    A blameless postmortem: summary, timeline, five whys to the root cause, what went well or wrong, and owned actions.

All cloud and devops diagram templates · All templates

Use the SLOs & error budget policy template