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.
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
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
- Double-click any box to change its text. Replace the examples with your own content.
- 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.
- Sketch, then convert. Draw boxes and arrows with the pen, select the strokes and click Convert sketch: they become real boxes and links.
- 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
Metrics, logs and traces through OpenTelemetry into Prometheus, Loki and Tempo, with Grafana, alerting and SLO notes.
On-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
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
Ingress, services, deployments and pods in a namespace, with config, storage, control plane and add-ons around them.
Incident response
Detect, triage, mitigate, communicate, resolve and learn — an on-call runbook in one view.
Incident postmortem
A blameless postmortem: summary, timeline, five whys to the root cause, what went well or wrong, and owned actions.