There is no standard 8-to-6 overlap. Someone joins early or late.
Toronto and Jakarta are 11 hours apart, and that gap is wide enough that their normal 9-to-5 workdays never quite touch. If you meet regularly, fix one off-hours slot and rotate it between Toronto and Jakarta so the burden doesn't fall on one team. Remember that Toronto shifts for daylight saving and Jakarta doesn't, so recalculate the overlap after each clock change.
| Local time | 12am | 1am | 2am | 3am | 4am | 5am | 6am | 7am | 8am | 9am | 10am | 11am | 12pm | 1pm | 2pm | 3pm | 4pm | 5pm | 6pm | 7pm | 8pm | 9pm | 10pm | 11pm |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Toronto America/Toronto | ||||||||||||||||||||||||
Jakarta Asia/Jakarta |
24/7 support sounds great until a P1 ticket falls into the gap between Manila signing off and Dublin signing on. Here is how to design a follow-the-sun support model that actually catches tickets at the boundary. -
Discover simple, effective strategies and powerful tools to eliminate timezone chaos for your distributed team. -