ROTATION STARTER KIT · OnCallManager
Fictional example: Alice, Ben and Casey are not customers.
Use this template without installing any app.

AGREE ON THE RULES
Schedule: Engineering support duty
Order: Alice → Ben → Casey → Alice
Timezone: UTC. Handoff: Monday 09:00 UTC.
This example assigns continuous weekly ownership, including weekends.
For business-hours coverage, explicitly define hours and ownership outside them.
Source of truth: [schedule link]
Maintainer: [name]
Escalation: [existing procedure]
A schedule assigns ownership; it does not establish paging or escalation.

FOUR-WEEK EXAMPLE
Start (inclusive)       End (exclusive)         Owner
Nov 2, 2026 09:00 UTC   Nov 9, 2026 09:00 UTC    Alice
Nov 9, 2026 09:00 UTC   Nov 16, 2026 09:00 UTC   Ben
Nov 16, 2026 09:00 UTC  Nov 23, 2026 09:00 UTC   Casey
Nov 23, 2026 09:00 UTC  Nov 30, 2026 09:00 UTC   Alice
At each boundary, the incoming owner takes over. Replace the example dates and names.
UTC stays fixed. A fixed local-time handoff can move relative to UTC during daylight-saving changes. Check upcoming dates in your chosen timezone.

PTO COVERAGE EXAMPLE
Ben cannot cover November 11 at 09:00 UTC through November 12 at 09:00 UTC.
Casey agrees to cover that interval. Ben resumes afterward.
Nov 9 09:00 → Nov 11 09:00 UTC: Ben
Nov 11 09:00 → Nov 12 09:00 UTC: Casey (agreed override)
Nov 12 09:00 → Nov 16 09:00 UTC: Ben
Nov 16 09:00 UTC: Casey's normal weekly turn begins.
Record the change in the source of truth and confirm the return to Ben. Keep the base order unless the team agrees to rebalance it. Casey has extra coverage in this example; review fairness together.

COVERAGE CHANGE RECORD
Original owner: [name]
Covering owner: [name]
Start + timezone: [date/time/zone]
End + timezone: [date/time/zone]
Both people confirmed: [yes/date]
Schedule updated by: [name/date]
Next normal handoff checked: [yes]

HANDOFF CHECKLIST
[ ] Incoming owner acknowledges the handoff.
[ ] Current owner and next handoff match the source of truth.
[ ] Upcoming PTO and coverage changes are reflected.
[ ] Open requests have links, status and a named next action.
[ ] Incoming owner has working access and notifications.
[ ] The team knows who handles gaps and how to escalate.
[ ] Verify the first actual handoff, not just the saved schedule.

COPYABLE SLACK HANDOFF
Duty handoff: [outgoing] → [incoming]
Effective: [date/time/timezone]
Coverage ends: [date/time/timezone]
Open work and next actions: [links + owners]
Coverage exceptions: [details or none]
Schedule: [source-of-truth link]
Escalation: [existing process]
Incoming owner: please acknowledge after reviewing.

TRY ONE LIVE ROTATION
If maintaining the schedule in Slack is still manual, OnCallManager can help manage recurring rotations and coverage changes. Start with one schedule and check its first handoff.
OnCallManager requires paid Slack with user groups; administrator approval may be needed. This template does not require paid Slack.
Setup: https://oncallmanager.app/slack-on-call-rotation
For assisted setup, contact contact.oncallmanager@gmail.com with your team size, current scheduling method and timezone. Do not share credentials or private incident details.