Scheduling across zones goes wrong in small ways: a missing zone name, an early start for the same person every time, a clock change nobody noticed. Here's how to avoid all three.
“How about 3 o'clock?” means different things to people in different places, and the usual fix, doing the conversion in your head, is where mistakes creep in. People forget which direction the offset goes, forget that not every region changes its clocks on the same date, and quietly accept a 6 a.m. call rather than ask. Most of the pain is avoidable by deciding a few things up front and letting the tool do the conversion.
Six ways to make cross-zone scheduling easier
Find the overlap before you pick options. Write down each person's reasonable hours, then look for the stretch they share. With people far apart, that might be only two or three hours a day, so offer options inside it rather than the whole day.
Pick a home zone and name it every time. Say “3:00 p.m. Central” or use a city, not “3:00 p.m.” Abbreviations like CST and IST are ambiguous, so a city name or the full zone name is safer.
Let people see their own local time. Asking someone to convert is how wrong answers happen. A scheduling link that shows each person the options in their own zone removes the step entirely.
Share the odd hours. If one person always takes the early or late slot, resentment builds fast. Rotate who gets the inconvenient time, or say plainly when you've asked someone to stretch.
Watch the weeks when clocks change. Regions change their clocks on different dates, so the gap between two places can shift by an hour for a week or two. If your options fall in one of those weeks, double-check the time in the calendar invite.
Confirm in writing with the zone. When you've picked a time, send it with the zone named and the date spelled out. A calendar invite does this well, since each person's calendar shows the event in their own zone.
A few situations that need extra care
One person is far from everyone else. Ask them what they can actually do before you share options, and keep every option inside their hours. It's easier than finding out later that nothing works.
A recurring meeting that spans zones. Revisit it when clocks change in either region, since the local time can shift for some people and not others.
A day-long event or trip. When you're only choosing a date, time zones matter much less. Choosing a day, not a time, is often the simplest option for a spread-out group.
Doing it with Commonhour
You set the plan up in one time zone, and each person who opens the link sees the options in their own zone, with a manual override if they're travelling or want to check another one. The ranked list shows which time works for the most people, with the best time on top and who's missing from each. When you pick a time, the calendar invite is free, with Google Calendar, Outlook or an .ics file, and it lands on each person's calendar in their own zone. Clocks changing partway through a plan are a known rough edge, so check the time in the invite if your options span one.
Time zone scheduling questions
What's the best time to meet across several time zones?
The time inside everyone's reasonable hours that hurts the fewest people. List each person's hours, find the overlap, and offer options inside it. If the overlap is tiny, rotate who takes the inconvenient slot.
Do I need to convert the times for everyone myself?
No. With a scheduling link that shows each person the options in their own time zone, nobody has to convert, and the calendar invite shows the event in each person's own zone.
Why do I need to name the time zone in every message?
Because a bare time is ambiguous and abbreviations can mean more than one zone. Naming a city or the full zone name prevents the most common mix-ups.
Is the calendar invite free?
Yes. Sending the calendar invite is free, with Google Calendar, Outlook or an .ics file, and everyone who said they're free is already added as a guest.