How to Schedule Across Time Zones Without Getting It Wrong

Almost every cross-border scheduling mistake comes from one of five causes. None of them are hard to avoid once you know what to look for.

1. Never write a bare time

"Let's talk at 3pm" is not information — it's a guess about whose clock you meant. Always attach a zone, and prefer the unambiguous form: "15:00 UTC", or "15:00 IST (UTC+5:30)". If the audience is mixed, list two or three local equivalents in the invite itself. It takes ten seconds and removes the entire class of error.

2. Watch for the daylight-saving gap

This is the biggest trap. The Americas, Europe and Australia change their clocks on different weekends, so for a few weeks each year the gap between two cities is not what it usually is. New York and London are normally 5 hours apart — but for about two weeks in March, and one in late October/November, they are 4. If a recurring call was set in one of those windows, it will drift for everyone.

The fix: schedule with real calendar dates and zone names (not offsets), and re-check any recurring meeting each March and October. The DST tracker lists the exact transition dates for each region.

3. Remember the southern hemisphere runs backwards

When Europe springs forward, Australia and New Zealand are falling back. Between about April and October the Europe–Sydney gap swings by two hours, not one. Any Europe–Australia or US–Australia recurring call needs checking twice a year, in both hemispheres' shift weeks.

4. Check the date, not just the hour

A 9 a.m. call in New York is 7:30 p.m. in Mumbai and 11 p.m. in Tokyo — and a 4 p.m. New York call is the next morning in Asia. Whenever a conversion crosses midnight, say the date out loud. Our time zone converter shows the resulting weekday and date, not just the clock time, for exactly this reason.

5. Respect the working window

With more than about eight hours of separation there is no time that's comfortable for everyone; someone takes the early morning or the late evening. The fair approach is to rotate which side absorbs it, and to agree a standing "overlap window" — the couple of hours where everyone is genuinely awake — for anything that needs live discussion. Everything else can be asynchronous.

The 30-second checklist

• State the time in UTC and each participant's local time.
• Include the full date and weekday.
• Use zone names (Asia/Kolkata), never bare offsets, for anything recurring.
• Send a calendar invite — it converts automatically and survives DST changes.
• Re-check recurring invites in March, April, October and November.

Comparing several cities at once? Pin them side by side on the world clock, or open a city time page for the live local time anywhere.