How to Schedule Meetings Across Time Zones Without Losing Your Mind

"Let's meet at 3" is a perfectly clear sentence right up until one person is in Dublin, another is in New York, and a third is in Singapore. Suddenly "3" needs a footnote.

The mistakes almost everyone makes

• Proposing a time in your own time zone and assuming everyone will "just convert it"
• Manually typing out "3pm GMT / 10am EST / 8pm SGT" and hoping nobody misreads it
• Forgetting daylight saving shifts — a time that worked in March can be off by an hour in October
• Picking a time that's convenient for you and merely tolerable for everyone three time zones away

A better process

1. Let each person see times in their own zone

Nobody should have to do mental math to know if a meeting works for them. The proposed time should automatically display in each participant's local time, detected from their browser — not a shared UTC number they're expected to translate themselves.

2. Propose a spread, not a single slot

With more than two time zones involved, no single time is going to be comfortable for everyone. Propose 3–5 spread-out options — some earlier, some later — and let the group's actual availability decide which one wins, rather than guessing upfront.

3. Weight the people who matter most

Not every invitee carries equal weight. If your CEO is only free at one specific hour across three time zones, that constraint should count for more than a "nice to have" attendee's mild preference.

How PrestoCal handles it

Every slot you propose is automatically converted to each participant's local timezone when they open their ranking link — nobody sees a number they need to convert. And you can mark key attendees as priority, so their availability is weighted more heavily when PrestoCal calculates the best overall slot.

Time zones don't have to be a scheduling tax. They're only painful when a human is doing the conversion by hand.