How to Find Meeting Overlaps Across Time Zones for Remote Work

To find a meeting overlap for remote work, convert each participant's working hours into one common reference (UTC works well), then look for the window where those converted ranges intersect. A visual time zone converter does this in one view instead of manual offset math. This works for any team size, but the wider the spread, the smaller the overlap — and some spreads have none at all, which you should confirm early rather than assume.

Step 1: Collect each person's local working hours

Ask for hours in their own local time, not in yours. "9:00–17:00 London" is usable; "4am my time" is not, because it breaks the moment anyone's offset changes.

Record for each participant:

• City or time zone (a city is safer than an abbreviation — "CST" means at least three different things)
• Local start and end of their working day
• Any fixed constraints, such as a school pickup or a standing call

Step 2: Convert everything to one reference

Pick a single reference point — UTC is the standard choice because it has no daylight saving shifts. Convert each person's window into UTC.

For example, a team spanning three zones:

The overlap of all three is empty. London and New York share 14:00–17:00 UTC; Tokyo's window ends before London's begins. This is the kind of result that's easy to miss with mental math and obvious on a chart.

Step 3: Use a visual converter to see the overlap

Zoneless is built for exactly this: its stated purpose is to find the overlap instantly and schedule remote meetings visually, and its page lists ready-made comparisons such as London vs New York, San Francisco vs Tokyo, Berlin vs Sydney, and London vs Sydney. The site describes itself as free and requiring no login, and it presents a sign-in option alongside the tools.

A visual tool helps because:

• Overlapping bands are shown as a shared region, so you read the answer instead of computing it
• Half-hour and 45-minute offsets (common in India, Nepal, parts of Australia) render correctly
• You can add or remove cities and watch the window move

If you prefer to work without a tool, the UTC table above is enough — but recheck it whenever a daylight saving change is near.

Step 4: Choose a slot that works for everyone, not just you

The overlap is a candidate, not a decision. Within it, weigh:

• Who is worst off. A slot at the edge of one person's day is a real cost; rotate inconvenient times if the meeting recurs.
• Meeting type. A 30-minute sync tolerates a slightly awkward hour better than a 2-hour workshop.
• Frequency. A one-off can stretch someone's day; a weekly call cannot.

If no overlap exists inside working hours, the honest options are: shorten the meeting, split it into two regional sessions, make it async, or accept that one person joins outside their hours — and say so explicitly rather than hiding it in a calendar invite.

Step 5: Confirm and share with local times spelled out

Send the confirmed time with every participant's local time listed, plus the date. A slot near midnight or on a DST transition day is where misreads happen.

A usable confirmation looks like:

Thursday 15:00 UTC London 15:00 · New York 10:00 · Berlin 16:00 · Sydney 02:00 (Friday)

Include the UTC value and the date, because "Thursday" is not the same day in every zone.

Common traps

• Daylight saving. The US and Europe change on different dates, so offsets between them shift for a few weeks each spring and autumn. UTC avoids the ambiguity; local abbreviations don't.
• Abbreviations. IST is India, Ireland, and Israel. Write the city.
• Half-hour zones. Not every offset is a whole hour, so a converter that only handles whole hours will misplace some participants.
• The date line. A meeting late in your day can be the next calendar day for a teammate, which matters for deadlines and invites.
• Assuming the organizer's hours are the default. The overlap belongs to the group, not to whoever set up the call.

Quick checklist

1. Get local hours and cities from each participant.
2. Convert to UTC (or load the cities into a visual converter).
3. Read the intersection — if it's empty, change the format, not the math.
4. Pick a slot and check who bears the worst hour.
5. Send the time in UTC plus each local time, with the date.