Finding Meeting Overlap Across Time Zones: New York, London, and Singapore
October 29, 2026
Scheduling a meeting across time zones becomes easy if you convert everything to one reference, UTC. Convert each participant's working hours to UTC, then find the range where all the ranges overlap. Convert the overlap back to each local time.
Suppose everybody works 9:00 to 17:00 local time in standard time. New York (UTC−5) works from 14:00 to 22:00 UTC. London (UTC+0) works 09:00 to 17:00 UTC. The overlap is 14:00 to 17:00 UTC, which is 3 hours: 9 am to 12 pm in New York, and 2 pm to 5 pm in London.
Skip the math and get your answer instantly:
Open the Time Calculator →Overlap Table for Standard Hours
For Singapore (UTC+8), 9:00 to 17:00 local is 01:00 to 09:00 UTC, so there is no overlap with London (09:00 to 17:00 UTC); the ranges just touch. San Francisco (UTC−8) works 17:00 to 01:00 UTC, which also does not overlap with London, except at the boundary of 17:00. Extending the day to 8:00 to 18:00 gives two hours: San Francisco 16:00 to 02:00 UTC overlaps London 08:00 to 18:00 UTC from 16:00 to 18:00, which is 8 to 10 am in San Francisco and 4 to 6 pm in London.
A three-way meeting across New York, London, and Singapore has no overlap even with extended hours, and someone must take an early or late slot.
| Pair | Overlap (9-17 local) | In local times |
|---|---|---|
| New York and London | 3 hours (14:00-17:00 UTC) | 9 am-12 pm NY, 2-5 pm London |
| London and Singapore | 0 hours | None (ranges only touch) |
| San Francisco and London | 0 hours | None; with 8-18 day: 2 hours |
| New York and San Francisco | 5 hours | 12-5 pm NY, 9 am-2 pm SF |
Fair Rotation for Global Teams
When no overlap exists, rotate the burden. If a recurring meeting is at 21:00 Singapore time (13:00 UTC, 8 am New York, 1 pm London), the Singapore team bears the late-evening inconvenience. In alternate weeks, move it to 07:00 Singapore (23:00 UTC the day before, 6 pm New York, 11 pm London), where the London team stays late. Using a rotation prevents one location from always taking the bad slot. Record meetings so people outside the window can catch up, and use asynchronous updates for routine information.
Daylight Saving Time Traps
Time zones do not shift on the same dates: the US typically changes in March and November, while Europe changes a few weeks later in March and earlier in the autumn, and Singapore does not observe daylight time. For a few weeks each year, the New York–London gap is 4 hours instead of 5, shifting the overlap. Always check meetings around the transitions. Use calendar software that stores meetings in UTC and displays them in local time, and state the time zone in invitations.
Practical Tips
Use the 'meeting planner' feature of your calendar, or a world clock. Identify core hours for the team (for example, 14:00 to 16:00 UTC) and keep a few. Keep meetings short and necessary when the time is inconvenient. Be explicit in writing with both time zones: '9:00 am New York / 2:00 pm London'. Don't forget regional weekends and holidays; some countries work Sunday to Thursday.
Frequently Asked Questions
How do I find overlapping working hours?
Convert each person's hours to UTC and find the shared range.
How many hours do New York and London overlap?
About 3 hours in a 9-to-5 day.
Do London and Singapore overlap?
Not in a standard 9-to-5 day.
Why can daylight saving time cause trouble?
Regions change on different dates, so the offset between cities shifts temporarily.
How can I make meetings fair for global teams?
Rotate the inconvenient time slot among locations.