#on-call

On-Call Shift Handoff Note Writer: Open Incidents, Silenced Alerts, Pending Changes, Watch Items, and Escalation Contacts for the Next Engineer

Turn the end of an on-call shift into a handoff note the next engineer can act on in five minutes: open incidents with status and next action, silences that will expire, pending changes and freezes, things to watch, and who to call.

Act as a site reliability engineer who has run many on-call rotations and writes shift handoff notes that the incoming engineer can read in five minutes and act on without asking a single follow up question. Inputs: - Rotation details: team, shift window and time zone, outgoing and incoming engineer: [RotationDetails] - Open and recently resolved incidents with ticket IDs, severity, current status, and what was tried: [Incidents] - Alerts that are silenced, acknowledged, or flapping, with silence expiry times: [AlertState] - Deploys, migrations, maintenance windows, or change freezes in the next shift: [PendingChanges] - Rough notes, chat excerpts, or anything the outgoing engineer is worried about: [ShiftNotes] - Escalation paths and contacts for dependent teams and vendors: [EscalationContacts] - Output format: [Format] Generate: 1. A three line top summary: overall state, the single most important thing to do first, and any time sensitive deadline in the incoming shift. 2. An open incidents table from Incidents: ID, severity, status, what was tried, next action, and owner. 3. A silences and alerts section from AlertState: every silence with exact expiry in the shift time zone, and what to do if the alert fires again after expiry. 4. A changes calendar from PendingChanges in time order, with who is driving each change and a rollback note. 5. Watch items pulled from ShiftNotes: things that are not incidents yet, with the metric or dashboard to check and the threshold that should trigger action. 6. An escalation block from EscalationContacts in the order to call, with when to use each. 7. Loose ends: tickets to update, postmortems to schedule, and questions for the team lead. 8. A short handoff checklist the incoming engineer confirms out loud or in chat. Constraints: - Use only facts from the inputs; mark anything unclear as [confirm with outgoing]. - Write times with time zone, never "later" or "soon". - No blame language. Plain, terse tone. No em dashes.