Book within 3:00 PM to 6:00 PM Manila time (8:00 AM to 11:00 AM in Lisbon) and both teams will be at work. Lisbon is 7 hours behind Manila, so the practical overlap is about 3 hours — generous enough for meetings, tight enough to be worth booking ahead. For part of the year the maths changes: Lisbon observes daylight saving, Manila does not, shifting the overlap by an hour. 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Manila Asia/Manila | 8am | 9am | 10am | 11am | 12pm | 1pm | 2pm | 3pm | 4pm | 5pm | 6pm | 7pm | 8pm | 9pm | 10pm | 11pm | Next Day 12am | 1am | 2am | 3am | 4am | 5am | 6am | 7am |
Lisbon Europe/Lisbon | 1am | 2am | 3am | 4am | 5am | 6am | 7am | 8am | 9am | 10am | 11am | 12pm | 1pm | 2pm | 3pm | 4pm | 5pm | 6pm | 7pm | 8pm | 9pm | 10pm | 11pm | Next Day 12am |
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 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. -
Why timezoners.com has no login, how Supabase realtime keeps a shared board in sync, and the timezone math behind the overlap grid. -