Prompt chains for documenting on-call rotations

Here are several prompt chains you can use to document on-call rotations. These prompt chains are structured step-by-step to guide team members or AI assistants in collecting and organizing comprehensive, useful on-call documentation. These can be customized for your specific engineering or operations context.

Prompt Chain 1: On-Call Shift Summary Documentation

Goal: Record a detailed summary of what happened during an on-call shift.

1. Prompt 1:
   “What was the start and end time of your on-call shift?”

2. Prompt 2:
   “List all incidents or alerts received during this shift. For each, provide a timestamp, severity, system impacted, and a brief description.”

3. Prompt 3:
   “For each incident, describe how you responded, the resolution steps taken, and the final outcome.”

4. Prompt 4:
   “Were there any recurring issues or patterns noticed? If yes, describe them.”

5. Prompt 5:
   “What parts of the documentation, monitoring, or alerting were most helpful during this shift?”

6. Prompt 6:
   “What areas of the process or tooling caused confusion or inefficiency?”

7. Prompt 7:
   “List any suggestions for improving the on-call experience or system reliability.”

Prompt Chain 2: Postmortem Incident Documentation

Goal: Create a reliable postmortem after an on-call incident.

1. Prompt 1:
   “Describe the incident: When did it start, what was the first alert, and who was paged?”

2. Prompt 2:
   “What systems were impacted and what were the user-facing consequences?”

3. Prompt 3:
   “What was the root cause or suspected cause of the issue?”

4. Prompt 4:
   “What actions were taken to mitigate the incident? Include both temporary and permanent fixes.”

5. Prompt 5:
   “How long did it take to resolve the incident? What were the key blockers?”

6. Prompt 6:
   “What went well during the incident response?”

7. Prompt 7:
   “What didn’t go well, and what would you do differently next time?”

8. Prompt 8:
   “List action items and assign owners for follow-up.”

Prompt Chain 3: Weekly On-Call Handoff Notes

Goal: Share key information with the next person taking over the on-call duty.

1. Prompt 1:
   “Summarize all notable incidents or patterns from your rotation.”

2. Prompt 2:
   “List any systems or services currently in a degraded state, under maintenance, or behaving unusually.”

3. Prompt 3:
   “Are there any pending alerts or tickets that require follow-up?”

4. Prompt 4:
   “Highlight recent config changes, deployments, or infrastructure updates that may impact on-call.”

5. Prompt 5:
   “Add links to dashboards, runbooks, or logs relevant to ongoing issues.”

6. Prompt 6:
   “What tips or heads-ups would help the next on-call be better prepared?”

Prompt Chain 4: Team Retrospective for On-Call Quality

Goal: Evaluate and improve the overall on-call process from a team perspective.

1. Prompt 1:
   “Rate the overall on-call experience over the past month (1–5) and explain your rating.”

2. Prompt 2:
   “Were alerts actionable and relevant, or were there noise issues? Provide examples.”

3. Prompt 3:
   “What improvements were made to reduce alert fatigue or improve reliability?”

4. Prompt 4:
   “What new runbooks, playbooks, or documentation were added or updated?”

5. Prompt 5:
   “How effective was the escalation process?”

6. Prompt 6:
   “Did knowledge sharing happen between shifts? What can be done to improve knowledge transfer?”

These chains can be implemented in internal tools, Notion templates, or automated Slack/Teams bots to ensure consistent documentation. Let me know if you’d like these formatted into templates or auto-fillable forms.