How to Find a Meeting Time Across Time Zones

Find a shared hour, then check the date

You are in Portugal, a friend is in Seattle, and someone joining the call is in London. Knowing the current time in each city is a start. Finding an hour that works for everyone requires one more step: compare the same future moment against each person's actual availability.

The reliable workflow is to choose the date, collect the cities, agree on acceptable hours, and look for an overlap. Once you find one, send a calendar invitation with the time zone attached. A message that says only “let's talk at ten” leaves too much room for interpretation.

Mapsake's World Clock can help you compare cities already represented in your travel history. For a meeting farther ahead, use a date-aware planner or calendar so the calculation reflects the rules on the day of the call.

Start with cities instead of abbreviations

Time-zone abbreviations are convenient when everyone shares the same context. They become less helpful across countries, and people often keep using a standard-time abbreviation during daylight saving time.

“New York, October 27, noon” is easier to check than “12 EST” without a date. A city-based time zone also lets software account for seasonal changes instead of assuming a fixed difference all year.

Ask each person which city or time zone they will be in on the meeting date. A home office in Seattle does not establish the correct clock for someone spending that week in Lisbon. Travel changes the planning inputs even when the recurring meeting has not changed.

Agree on the hours that are actually acceptable

A clock can tell you whether it is morning. It cannot tell you whether someone is free, commuting, putting children to bed, or working a different schedule.

For a work call, start with each person's working hours and the meeting duration. For a personal call, use the windows they offer. A half-hour overlap is not enough for a ninety-minute meeting, and a slot that starts just before someone's day ends may still be inconvenient.

On October 27, 2026, these three clock readings describe the same instant:

For people working 9 a.m. to 5 p.m., that gives a reasonable one-hour window. Adding Tokyo would put the call at 1 a.m. the following day there. The first three cities having a convenient overlap does not make the fourth participant available.

Use this as a calculation example, not a suggested schedule for everyone in those cities.

Compare your city clocks in Mapsake

Apri. World Clock from Passport. It draws its city clocks from places you have visited or lived in, so it is useful for keeping familiar destinations together.

1. Find the cities you want to compare and star them as favorites.
2. Use the favorites filter to keep the list focused. You can arrange favorites in pinned order or west to east.
3. Move the Meeting planner slider to preview another moment. Every city moves to the same instant, with its own local date and time.
4. Compare the displayed times with the hours each person said would work. Check the date as well as the hour for cities across midnight.
5. Tocca Now to return to the live clocks.

The slider moves in five-minute steps across a range of 24 hours before and after now. It is a near-term comparison tool, not an arbitrary future-date scheduler. It also does not inspect calendars, send invitations, or automatically decide which local hours count as a person's workday.

Daylight and night labels describe the local sky. They can provide useful context, but daylight is not the same thing as availability.

If a participant's city is not part of your travel history, use a general city-based planner for that comparison. There is no need to add a visit you did not make just to create a clock.

For next month's meeting, use next month's date

A common mistake is to look up today's difference and reuse it for a call several weeks away. That can fail around daylight-saving changes.

In 2026, the United Kingdom returns to standard time on October 25. Under the United States' daylight-saving rule, New York and Seattle change on November 1. For the intervening week, London's difference from those cities is one hour smaller.

The New York meeting time has not moved, but London's local time has. Repeating an old conversion without checking the date would hide that change.

For a date outside Mapsake's near-term slider range, a tool such as timeanddate's Meeting Planner lets you choose the date and cities together. Your calendar's time-zone support is also useful for checking the exact invitation before sending it.

Put the agreed instant in the invitation

Once the group has chosen a time, create a calendar event with the intended date and time zone. Check its displayed time in the relevant cities, then include a short human-readable confirmation if the call crosses several zones.

For the October 27 example, that could be: “Tuesday, October 27: 9 a.m. Seattle, noon New York, 4 p.m. London.” The invitation remains the shared event; the written comparison makes a mistake easier to spot.

For a recurring meeting, decide whose local time should stay fixed. “Every Tuesday at noon in New York” and “every Tuesday at 4 p.m. in London” do not describe the same series throughout the year. Check the weeks when either location changes clocks, and revisit the arrangement when someone travels.

When there is no comfortable overlap

Some combinations of cities simply do not share ordinary working hours. A better converter cannot create an overlap that does not exist.

Try shortening the live meeting, moving part of the discussion into a written update, or rotating the inconvenient slot. If the same person is always joining before dawn, make that tradeoff explicit instead of allowing the organizer's clock to become the default rule.

For a travel catch-up, two shorter calls can be easier than fitting every friend into one session. For a team, a written handoff can keep a decision moving without requiring everyone to be awake together.

The useful result is a time people understand and can reasonably attend. Cities, dates, availability, and a clear invitation get you there more reliably than memorizing one permanent offset.

• Explore Mapsake's travel tools
• Understand flight arrival times across time zones