Set against a 14-hour difference, Sydney and Philadelphia run their workdays on completely separate schedules. Block a single recurring off-hours slot that both teams agree on, rather than negotiating a new awkward time every week. To edit hours, add more timezones, and share with your team, create a free collaborative board.
| UTC (GMT+0) | 12am | 1am | 2am | 3am | 4am | 5am | 6am | 7am | 8am | 9am | 10am | 11am | 12pm | 1pm | 2pm | 3pm | 4pm | 5pm | 6pm | 7pm | 8pm | 9pm | 10pm | 11pm | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
10am | 11am | 12pm | 1pm | 2pm | 3pm | 4pm | 5pm | 6pm | 7pm | 8pm | 9pm | 10pm | 11pm | Next Day 12am | 1am | 2am | 3am | 4am | 5am | 6am | 7am | 8am | 9am | ||
8pm | 9pm | 10pm | Previous Day 11pm | 12am | 1am | 2am | 3am | 4am | 5am | 6am | 7am | 8am | 9am | 10am | 11am | 12pm | 1pm | 2pm | 3pm | 4pm | 5pm | 6pm | 7pm |
The Philippines sits 12 to 16 hours ahead of the US and never changes its clocks. Exact overlap windows for every US coast, the tomorrow problem, and a rotation rule that works for product and BPO teams. -
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. -
The US to Australia gap runs 14 to 19 hours depending on the month, and someone is always in tomorrow. Exact overlap windows for every US coast, the double-DST trap, and a rotation rule that keeps it fair. -