On-Call Handbook for a Small Team

Write an on-call handbook for a small team covering handover, first checks, escalation and status communication.

Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it (what [VERIFY] means).

Write an on-call handbook. Services: [SERVICES]. Team: [TEAM]. Tools: [TOOLS]. Past incidents: [PAST_INCIDENTS].

Cover responsibilities, handover, how to acknowledge an alert, first checks, when to escalate, how to communicate status, how to avoid heroics, and how to record actions. Provide a first-fifteen-minutes checklist, a template for status updates, and a compensation and rest policy to be agreed with staff [VERIFY].

Return the handbook, an escalation chart, and a training plan with two simulated incidents. Include wellbeing guidance: breaks, backup support and a debrief after a bad night.

Add a worked first-fifteen-minutes script. Minute 0 to 2: acknowledge the alert so others know someone has it. Minute 2 to 5: check the dashboard for user impact, and decide whether this is minor or serious. Minute 5 to 8: look at recent deploys and changes, and roll back if a recent change is the likely cause and rollback is safe. Minute 8 to 12: if unresolved, escalate to the secondary or to the specialist, giving a two-sentence summary. Minute 12 to 15: post a status update in the incident channel and note what you have tried. Add a template for the handover at the end of the week, listing open issues, flaky alerts and things to watch. Describe a fair rota with a primary and a secondary, limits such as no more than one week in four, and time off after a disturbed night, subject to local rules and agreement with staff [VERIFY]. Provide a tiny set of example incidents for practice. Include guidance on wellbeing: stop for water and food, ask for help early, and do not make risky changes when exhausted. Add a one-page quick reference that can be pinned in the team channel. Review the handbook every six months with the people who have been on call.

Add a short appendix with a list of useful commands and links to keep within reach, written as placeholders only, and a rule to keep the appendix current by checking it after every incident.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Invented first fifteen minutes for a payment error alert.
00:00 acknowledge. 00:02 check dashboard: 8 percent of payments failing, user impact yes. 00:05 check recent deploys: one at 13:40; roll back as the likely cause. 00:08 rollback complete; error rate falling. 00:12 post update: "Payment failures started 13:45; rolled back at 13:53; monitoring." 00:15 note actions in the log.
Handover note: open item, add an alert for failed share above 2 percent; watch the dashboard after 17:00.
Rest: the engineer takes the following morning off after a night page, as agreed with the team [VERIFY].

• incident