How to use the Service level objectives template

Start a board from it
Use this template opens a new Freero board with the Service level objectives template on it (sign up free first). On a board you already have, open Templates in the toolbar and search for “Service level objectives”.
Follow the instruction on the board
“Pick journeys users would complain about, not servers. Agree up front what the team does when the error budget runs out.”
Fill in each part
- Table Columns: User journey · Indicator · Target · Window · When we miss it
Bring your team and your agents
Invite people to the board or share a link, and work on it together live. The timer is in the top bar, private mode and voting in the board menu, and Claude or ChatGPT can join through Freero’s MCP server.

Work on it with an AI agent

Connect an assistant once and it works on the board with you, with your permissions: by default it reads and proposes, and people decide.

You ask: “Fill in the Service level objectives board from these notes.”
What happens It reads the board, then proposes sticky notes for it. Nothing changes until someone on the board accepts them.
You ask: “Group what we wrote into themes and list the actions.”
What happens It proposes clusters with a title each and task cards for the actions, labelled with its name and yours.

Error budget policy
Agree in advance what the team does as a service uses up its allowance for failure, from business as usual to stopping releases.
Game day plan
Plan a practice failure in a safe window: what you break, what you expect to happen, how you stop it and what you learn.
Postmortem action tracker
Follow the fixes agreed in incident reviews through to done, so the same failure doesn’t come back next quarter.
On-call handover
Hand the pager over cleanly: what happened this week, what’s still open, what to watch and what the next person needs to know.
Service runbook
What an on-call engineer needs at 3am for one service: how to tell it’s broken, first checks, safe fixes and who to wake.
Toil inventory
List the manual, repetitive work that keeps an operations team busy, measure what it costs each month and pick what to automate.