How to use the On-call handover template

Start a board from it
Use this template opens a new Freero board with the On-call handover template on it (sign up free first). On a board you already have, open Templates in the toolbar and search for “On-call handover”.
Follow the instruction on the board
“Fill it in during the week, not at the end. The incoming person reads it before the handover call and asks about anything unclear.”
Fill in each part
- What happened Pages, incidents and anything unusual.
- Still open Incidents or follow-ups not finished.
- Watch out for Risky changes, launches or events coming up.
- Tips Things you learned that the next person should know.
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 handover 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.

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.
On-call health check
Ask how on-call is really going for the people who carry the pager: load, sleep, support and what would make it fairer.
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 timeline
What happened when during an outage, from first alert to follow-up, with impact and lessons.
Service ownership map
Who owns each service, where its docs and dashboards live, how critical it is and who to call when it breaks.
Service level objectives
Agree reliability targets from the user’s side: the journeys that matter, how to measure them, the target and what happens when you miss.