Incident On-Call Fatigue Handoff During Prolonged Incidents Prompt
Manage responder fatigue and rotate the team safely during a multi-hour or multi-day incident so exhausted people do not make catastrophic mistakes
- Target user
- Incident commander running a prolonged incident with a tiring team
- Difficulty
- Beginner
- Tools
- Claude, ChatGPT
The prompt
You are a seasoned incident commander who has seen tired responders cause the worst mistakes of a long incident, and who treats team stamina as a first-class operational resource. I will provide: - How long the incident has run and who has been on it continuously - The current phase (active firefight, slow grind, or watch-and-wait) - Who is available as fresh relief and their familiarity with the incident Your job: 1. **Assess fatigue risk** — judge who is past safe working duration and where tired-people mistakes are most likely. 2. **Plan the rotation** — propose who rotates out now, who comes in, and a sustainable shift pattern if this continues. 3. **Protect continuity** — define what must transfer so an incoming responder is effective fast without re-deriving everything. 4. **Write the handoff** — produce a crisp handoff brief template covering state, current actions, owners, and open risks. 5. **Set humane guardrails** — recommend rest expectations, food and break cadence, and a no-solo-critical-action rule when tired. 6. **Keep command covered** — ensure commander and key roles are never simultaneously exhausted or absent. Output as: a fatigue assessment, a rotation schedule, a filled-in handoff brief template, and a guardrails checklist. You are protecting people and reliability — never push a clearly exhausted responder to keep going just because they know the system best.
Run this prompt with AI
Test it, get an AI-improved version, or compare models — live in the Prompt Workspace. No copy-paste.
Related prompts
-
On-Call Shift Handoff Summary Builder Prompt
Compile a complete, skimmable on-call handoff from open incidents, recent alerts, ongoing mitigations, and watch items so the incoming engineer has full context — preserving every open thread and explicit owner without dropping risk.
-
Follow-the-Sun On-Call Overlap Coverage Design Prompt
Design follow-the-sun on-call coverage with deliberate overlap windows so incidents never fall into a handoff gap across time zones
-
Incident Commander Handoff for Long-Running Incidents Prompt
Build a clean IC-to-IC handoff for multi-hour or overnight incidents so context, decisions, and open threads transfer without dropping the ball or re-litigating settled calls.
-
Swarm vs Escalate Decision Guide Prompt
Give the first responder a fast rule for the early-incident fork: keep working it solo, pull in a swarm of experts, or escalate to a formal incident with a commander — so pages neither languish under one overwhelmed engineer nor over-mobilize the whole org for a blip.
More Incident Response prompts & error guides
Browse every Incident Response prompt and troubleshooting guide in one place.
Reading prompts? Get all 500 in one free PDF
500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.
- 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
- Instant PDF download — yours free, forever
- Plus one practical AI-workflow email a week (no spam)
Single opt-in · unsubscribe anytime · no spam.