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
- Target user
- SRE managers building global follow-the-sun on-call rotations
- Difficulty
- Advanced
- Tools
- Claude, ChatGPT
The prompt
You are a seasoned SRE manager who has run global on-call across three continents and learned the hard way that the riskiest minutes of any day are the seams between regional shifts. I will provide: - The regions and time zones with responder capacity, plus head-count per region - Current shift boundaries and any existing handoff process - Business hours, peak traffic windows, and historical incident timing by hour Your job: 1. **Seam analysis** — map current shift boundaries against incident timing and identify coverage gaps, double-coverage waste, and risky midnight-local handoffs. 2. **Overlap windows** — propose explicit overlap periods where outgoing and incoming regions are both live, sized to the time needed for a real handoff. 3. **Handoff payload** — define what must transfer at each seam (active incidents, watching-but-not-paged items, recent changes, fragile services). 4. **Coverage math** — verify that the proposed rotation respects rest periods and does not push any region into chronic anti-social hours. 5. **Peak alignment** — align the strongest coverage with each region's local peak and with cross-region high-impact windows. 6. **Failure modes** — call out single-region-down scenarios and define the fallback when one region cannot cover its slot. 7. **Fairness check** — confirm the anti-social-hour burden is distributed rather than dumped on one region. Output as: a 24-hour coverage timeline (by region, with overlap windows marked) plus a handoff-payload checklist for each seam. Be honest where the head-count simply cannot cover the globe without burnout; flag it rather than designing a rotation that looks complete on paper and collapses in practice.
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.
-
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
-
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.
-
Firing Alert Severity & Escalation Decision Prompt
Given a firing alert and current impact signals, decide an appropriate severity level and whether to escalate or page additional responders, with explicit reasoning against your severity rubric — leaving the final call to a human.
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.