Best overlap: 8:00 AM to 9:00 AM in Manila is 5:00 PM to 6:00 PM in Seattle.
Your shared working hours run 8:00 AM to 9:00 AM in Manila (5:00 PM to 6:00 PM in Seattle). The window is short at 1 hour, so keep meetings tight and anchored to 8:00 AM in Manila (5:00 PM in Seattle). Double-check the weekday, too: Seattle sits on the previous day from Manila during these hours. Because only Seattle changes its clocks, the overlap above isn't fixed; expect a one-hour shift when Seattle 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 | ||||||||||||||||||||||||
Seattle America/Los Angeles |
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. -