Tool
Customer Support Shift Scheduler
Build a 24/7 support coverage plan across cities 鈥?with weekend fairness and a hand-off matrix.
Hand-off matrix (city A → city B at hour)
What makes this different
The hand-off matrix is the differentiator: it shows the hour at which each pair of cities hands off coverage, so you know which cities should brief each other and which should not. It also surfaces the "impossible" hand-offs (when a city has no overlap with any other) so you can fix gaps before publishing the rota.
How to use it
- Pick your support cities.
- Set the shift length (default 8h).
- Set the minimum weekend rotation fairness (how often the same city gets the weekend shift).
- Read the schedule grid and the hand-off table.
Building a 24/7 support schedule across multiple cities is mostly a constraint problem: every hour must be covered by at least one awake team, weekends should rotate fairly, and shift hand-offs should ideally happen when both cities are in working hours. This tool takes a city list and shift length, and produces a draft schedule with a hand-off matrix.
Frequently asked questions
Why is the schedule not always perfectly fair?
Because city timezones are not evenly distributed. A team in San Francisco and a team in London will inevitably shoulder more night-shift burden than a team in New York.
What is the "handoff" hour?
The hour at which primary coverage passes from city A to city B. If city A ends at 18:00 local and city B starts at 09:00 local with a 4h overlap, the formal handoff is at 14:00 city-A local.
Can I export the schedule?
Not in the current version 鈥?copy from the table. We deliberately avoid adding file-export buttons because they require client-side blob creation, which is overkill for a planning aid.