How to use the On-call health check template

Start a board from it
Use this template opens a new Freero board with the On-call health check template on it (sign up free first). On a board you already have, open Templates in the toolbar and search for “On-call health check”.
Follow the instruction on the board
“Bring last quarter’s page counts by person and by hour. Let people answer anonymously first, then talk about the patterns, not individuals.”
Fill in each part
- How many times were you paged, and when?
- How many pages needed you to act?
- Did you feel able to handle what came up? Runbooks, access, someone to call.
- How did on-call affect your life outside work?
- What would make it fairer or lighter?
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 On-call health check 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.

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.
Incident timeline
What happened when during an outage, from first alert to follow-up, with impact and lessons.
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.
Alert review
Go through last month’s alerts one by one and decide which to keep, tune, turn into a ticket or delete, so pages mean something.
Incident response roles
Who does what when a serious incident starts: the incident lead in the middle, and the roles that support them.
Service ownership map
Who owns each service, where its docs and dashboards live, how critical it is and who to call when it breaks.