How to Schedule Meetings Across Time Zones Without the Headache

Anyone who’s worked with a distributed team knows the special dread of “let’s find a time that works for everyone.” Get it wrong and someone joins at 5 AM, or worse, a day late. Here’s how to schedule across time zones without the mental gymnastics.

Pick one reference time

The biggest mistake is reasoning in everyone’s local time at once. Instead, choose a single reference — your own zone, or UTC — and convert from there. Decide the moment first, then translate it for each attendee. Drop the time into the Time Zone Converter and you’ll see it laid out for every city at once, including the weekday, so a Tuesday call in New York doesn’t quietly become Wednesday in Sydney.

Respect daylight saving time

The painful truth: the offset between two cities is not constant. The US, Europe and Australia change their clocks on different dates, so there are a few weeks each year when “London is 5 hours ahead” is simply wrong. Always convert for the specific date of the meeting rather than relying on a remembered offset — a good converter applies each region’s DST rules automatically.

Find the humane overlap

For teams spread across many zones, there’s rarely a time that’s convenient for all. Aim for the window that’s least bad:

Favor late-morning-to-early-afternoon for the majority.
Rotate awkward slots so the same person isn’t always taking the 10 PM call.
For Asia–Americas splits, accept that someone is doing early or late, and share the pain over time.

Write it down unambiguously

When you send the invite:

Include the time zone abbreviation (e.g. “3:00 PM EDT”), not just “3 PM.”
Better still, let calendar software attach the zone so each person sees their own local time.
For async announcements, write “14:00 UTC” — it’s unambiguous and never affected by anyone’s DST.

Keep the meeting itself on time

Cross-zone calls are expensive — everyone paid something to be there. Protect the agenda with a visible countdown timer for time-boxed segments so the call ends when it should, and nobody’s 6 AM sacrifice gets wasted on a meeting that runs long.

Coordinate once, convert carefully, and write it down clearly — that’s the whole game.