How to schedule a meeting across time zones without anyone getting confused

Scheduling across time zones is one of those things that feels like it should be simple. You pick a time, you send it, people join the call. Except somebody shows up an hour early, somebody else shows up the next day, and one person just never responds because they gave up trying to calculate whether 3pm EST is morning or evening in Sydney.

If you've ever been the person organizing a call for friends spread across continents, or a team meeting with a few remote members, or a family reunion with relatives in different countries, you already know the pattern. This post is about how to stop repeating it.

Why this is harder than it should be

The core problem is that human brains are bad at relative math on two different clocks. When someone says "let's meet at 3pm my time," your reader has to:

Figure out what time zone "my time" is
Figure out what the current offset is between their zone and yours, accounting for daylight saving
Apply that offset correctly in their head
Decide whether that lands in their workday, sleep hours, or dinner
Remember to check daylight saving shifts if the meeting is in two weeks and one of the zones just switched

Nobody does all five steps carefully. Most people do step one, guess at step three, and hope for the best. This is why meetings get missed.

The five rules

Here's what actually works, in order of importance.

1. Always name the time zone explicitly

"Let's meet at 3pm" is not a time. It's half a time. Write "3pm London time" or "3pm UTC" or "3pm PT" so the reader doesn't have to guess. This sounds obvious. It is. People still don't do it.

If you want to be extra clear, include a second zone that you know matters to your group. "3pm London / 10am New York" is immediately scannable for both sides.

2. Use UTC as a neutral anchor when the group is spread out

For small groups in two zones, naming both works fine. For bigger groups spread across three or four zones, pick UTC (sometimes written as GMT) as the anchor. UTC doesn't shift for daylight saving, so it's stable. Anyone can convert from UTC to their own zone quickly, and nobody feels like they're the "other" zone.

"The call is at 14:00 UTC" is a proposal everyone can work with.

3. Prefer tools that auto-convert over tools that don't

If you can send people a link where they see the time in their own local zone automatically, use that. The worst scheduling tools make everyone see the same time and force them to convert. The best ones know who's looking and show them their local time.

Calendar invites from Google Calendar, Outlook, and Apple Calendar do this by default. Scheduling polls usually do too, but some older tools still display times in the creator's zone only. Those are the ones that cause the "I thought it was 3pm my time" confusion.

4. Watch out for daylight saving transitions

Two weeks of the year will trick you. In early November, the US shifts back one hour but Europe already did weeks earlier. In March, the US shifts forward three weeks before Europe. During those gaps, the normal offset between, say, New York and London is wrong by an hour.

If your meeting is scheduled around one of these transitions, double-check the specific date. Don't rely on memory. "New York is five hours behind London" is true most of the year and wrong for about three weeks of it.

Countries on different hemispheres also flip the problem. When Europe goes into daylight saving in March, Australia is going out of it. The Sydney-London offset changes by two hours in a six-week period. This breaks a lot of recurring meetings.

5. Make it easy to respond, not polite to respond

A text message that says "can you do Tuesday at 2pm London or Wednesday at 4pm New York?" gets a better response rate than a message that says "please let me know your availability for the week of the 21st."

The concrete version gives your reader something to say yes or no to. The vague version makes them do homework. People put off homework.

Common mistakes

A few specific patterns that go wrong more often than they should.

Mixing 24-hour and 12-hour formats

Someone in Europe writes "14:00." Someone in the US reads "1400" as a number and asks what it means. Someone else tries to interpret it and thinks it's 2am. Pick one format and stick with it in the invite.

If you're writing to a mixed group, "2pm / 14:00" covers both.

Half-hour time zones

India is UTC+5:30. Nepal is UTC+5:45. Newfoundland is UTC-3:30. If you're scheduling with anyone in these zones, the half-hour offset surprises people who are used to whole-hour math. Write the exact time, not the offset, and let the other person do the conversion to their side.

Assuming everyone's calendar handles conversions

They mostly do, but not always. Calendar invites sent as plain-text emails strip the time zone metadata. Calendar invites forwarded through a bridge (like from one company's Exchange to another company's Google Workspace) sometimes land in the wrong zone. If the meeting is important, confirm the time in the conversation rather than trusting the calendar invite to arrive correctly.

Forgetting that "tomorrow" is relative

If you're in Los Angeles and you text a friend in Tokyo on Friday evening saying "let's talk tomorrow," their tomorrow is already almost over by the time you wake up. Use specific dates when the group is in different zones, not relative words like "tomorrow," "tonight," or "this weekend."

When a scheduling tool helps

Everything above is about how to communicate times. The other half of the problem is deciding which time to propose in the first place, especially when you have five people in four zones and no obvious overlap.

This is where a scheduling poll helps. Instead of proposing one time and negotiating, you propose a range of options, everyone marks what they can do, and the overlap becomes visible. The best group-scheduling tools display the grid in each person's own local time zone, so nobody has to do math while responding.

Meetwisely was built for exactly this. Create an event, pick a range of times and dates, share the link. Everyone sees the grid in their own local time zone automatically. No accounts, no signup, no app to install.

Try it for your next cross-timezone meeting.

The short version

Name the time zone. Prefer tools that auto-convert. Watch for daylight saving. Use concrete proposals, not vague asks. And when the group is spread across more than two zones, stop trying to do the math in your head and use a tool that does it for you.

The goal isn't to be impressive at time zone math. The goal is to have the meeting.