Most cross-border scheduling errors come from converting one city at a time. Comparing every city against a single anchor hour removes the guesswork, and it takes about thirty seconds.
Step 1 — pick one anchor city, not one anchor time
Choose the city with the least flexibility, usually where the majority of attendees or the decision maker sits. Every proposed slot is then expressed as that city's local hour, so there is one source of truth in the invite text.
Write the anchor explicitly: "14:00 New York" is unambiguous, while "2pm" in a thread with three countries is not.
Step 2 — find the overlap window before proposing a slot
List each participant's acceptable working band, typically 08:00 to 18:00 local. The overlap of those bands is your only usable window; if it is empty you need either an asynchronous update or a rotating call time so the same region is not always inconvenienced.
Stack the cities side by side in the time zone dashboard and slide through the hours. Slots where any city falls outside its band are immediately obvious, which is far more reliable than converting each city separately in your head.
Step 3 — check the daylight saving gap
Northern-hemisphere clock changes do not happen on the same date everywhere. In March and late October, Europe and North America drift for one or two weeks, so a recurring call can silently move by an hour for half the participants.
Southern-hemisphere zones such as Sydney shift in the opposite direction, which can change a US–Australia gap by two hours in a single week. Re-check any recurring meeting that crosses a clock-change week rather than trusting the original invite.
Time zone data in the browser comes from the IANA database, so a converter that computes locally applies the correct rule for the future date you are testing.
Step 4 — write the invite so nobody has to convert again
Include the anchor local time, the UTC time, and the local time for each major region. Attach the agenda so anyone who cannot make the slot can contribute asynchronously.
For recurring series, state whether the series follows the anchor city's clock or a fixed UTC offset. That single sentence prevents most "I thought it moved" cancellations.
Last reviewed 2026-08-31.