Track service-level objectives and the error budget they spend — when a service burns its budget, feature work pauses and reliability work takes the wheel.
SRE and platform teams enforcing reliability with error budgets.
Quick answer
The SLO & error budget template is a ready-made workspace for SRE and platform teams enforcing reliability with error budgets.
SLO & error budget template in short
Included when you apply it
Applying this template creates the 1 board below — with every list — and pre-loads 3 sample issues, all yours to edit. The automation rules further down are suggestions you can wire up next; they aren't created for you yet.
A preview of how this template lays out — the boards, their custom workflow states, and where the sample issues land. WIP caps show a badge.
SLOs
Checkout API — 99.95% availability SLO
30-day rolling window; 21m 54s monthly budget.
Search latency SLO — p99 under 400ms
Freeze feature work — auth service budget exhausted
These rules aren't created when you apply the template — they're recipes you can wire up in Settings → Automations once your board exists.
When
Service moves to 'Budget exhausted'
Then
Apply a feature-freeze label and notify the service owner + EM
When
Burn rate exceeds 2x for 1 hour
Then
Move the SLO to 'Budget burning' and open a reliability issue
Ready to spin this up?
Sign-up takes seconds. We build this template's boards, lists, and sample issues in your new workspace, all yours to edit.
FAQ
Sprint planning
A cycle-driven sprint board with WIP limits, estimates, and PR-linked issues — the default starter pack for product engineering teams.
View templateBug triage
An intake-to-resolution pipeline that separates triage from active fixing, with severity labels and reproduction notes on every card.
View templateRelease checklist
A repeatable release runbook as a sub-issue tree — cut, verify, ship, announce — so nothing ships half-checked.
View template