Best overlap: 2:00 PM to 6:00 PM in Manila is 8:00 AM to 12:00 PM in Copenhagen.
The overlap falls at 2:00 PM to 6:00 PM in Manila, or 8:00 AM to 12:00 PM if you're in Copenhagen. You get roughly 4 hours of shared time, so aim for the middle of that window to keep the call comfortable for both teams. Because only Copenhagen changes its clocks, the overlap above isn't fixed; expect a one-hour shift when Copenhagen enters or leaves daylight saving.
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Manila Asia/Manila | ||||||||||||||||||||||||
Copenhagen Europe/Copenhagen |
Most distributed teams either keep the daily standup and exclude someone, or kill it and lose the rhythm. There is a better third option. Here is how to redesign the daily standup so it works across nine time zones. -
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. -