How to Propose a Meeting Time Across Time Zones

“Can we talk Thursday at 3?” is a complete sentence in an office and an incomplete one everywhere else. Whose Thursday? Whose 3? The person on the other end now has to guess, or convert, or write back to ask, and each of those costs a round trip you were trying to avoid.

Most missed calls across time zones are not caused by anyone’s carelessness. They come from a message that left one small fact implicit. Fixing it takes four extra lines in the invitation, and none of them is clever.

Name The Zone Every Time

An abbreviation feels precise and often is not. “CST” can mean Central Standard Time in North America, China Standard Time, or Cuba Standard Time. “ET” covers both standard and daylight time, so it does not say which one is in force on the day you mean. Even “GMT” gets used loosely for UK local time in summer, when the UK is actually on British Summer Time.

The W3C’s internationalization group makes a useful distinction in its note on working with time zones: an offset from UTC is a fixed number, while a time zone is a set of rules, and those rules change the offset during the year. For a scheduling message, the practical version is this. Give the city or region the time refers to, and add the UTC offset when the date falls near a clock change.

Before:

Can we do Thursday at 3 Eastern?

After:

Can we do Thursday 12 November at 15:00 in New York (UTC-5)?

The second version names the date, uses a 24-hour clock so nobody has to ask about a.m. and p.m., and anchors the time to a place rather than a label.

Show Each Person’s Local Time

Do the conversion for the other person. Do not make them open a converter, because the moment they do, they are doing your work and are one typo away from the wrong answer.

Put the times in a short list, one line per participant or location:

Wednesday 11 November, proposed:

14:00 in London (UTC+0) 09:00 in New York (UTC-5) 22:00 in Singapore (UTC+8)

That last line is also the honest part. Writing out 22:00 for the person in Singapore makes the cost of the slot visible to everyone, including you. If the time is bad for someone, it is better to see it in your own draft than in their reply.

Check the arithmetic yourself, and use a clock tool you trust for the dates near a daylight saving change. The United States and the United Kingdom, for example, do not change their clocks on the same weekend, so for a couple of weeks a year the usual gap between them is off by an hour. A rewriting tool does not know your calendar and will not catch that for you.

Offer Two Options And Rotate The Pain

A single proposed time reads as a decision. Two or three reads as a question, and it gets answered faster. Offer options that are not all the same kind of inconvenient:

Option A: Wednesday 11 November, 14:00 London / 09:00 New York / 22:00 Singapore. Option B: Thursday 12 November, 08:00 London / 03:00 New York / 16:00 Singapore.

Notice that Option B is awful for New York. Do not send it. The point of offering options is that each one should be survivable for everyone, and if no slot is, say so plainly and propose to rotate who takes the early or late call across the next few meetings. People accept an unpleasant time far more readily when it is clearly shared than when it is quietly assigned to whoever is farthest away.

If the group is spread too widely for any shared hour, that is a signal to change the format, not to keep hunting for a slot. A written update, like the one in how to replace a status meeting with a written update, may do the job without anyone staying up.

Ask For A Specific Reply

End with the action you need, not an invitation to discuss. “Let me know” produces nothing. A closing line with a deadline does:

Please reply with A or B by end of day Friday in your time, and I will send the invite then.

“End of day in your time” is a small kindness that removes yet another conversion. If you need to change the slot later, the same discipline applies, and how to write a reschedule request email covers the wording.

For teams that span several cultures and working norms, the broader habits are in cross-cultural email etiquette for global teams, and the twice-a-year problem of clocks changing is covered in how to tell a global team about the clock change.

Let Wrivio Tidy The Wording, Not The Times

A rough draft is fine; the structure is the part worth standardizing. A Wrivio Context for scheduling messages could say:

Rewrite this as a short scheduling message. Lead with the purpose of the meeting in one line. List each proposed time on its own line with the city and UTC offset. Use a 24-hour clock. End with one specific request and a reply-by date. Keep every name, date, time, city, and UTC offset exactly as written. Do not convert, add, or remove any time.

Press Ctrl+Shift+Space, paste the draft, and read the result against your original before copying it. The last sentence of that Context matters most: a rewrite should change the phrasing, never the numbers, so compare every time and date by eye.

Common Questions

Should I use UTC in a scheduling email?

Use it as a supplement, not a replacement. Listing each person’s local time is kinder, and adding the UTC offset helps anyone who wants to double-check against their own calendar.

Is it better to use a scheduling link instead of writing out times?

A link works well when the other person controls their own availability, but it does not replace a clear message when a group has to agree on a slot. Writing the options out also shows that you thought about their day.

How do I handle a clock change in the middle of a recurring meeting?

Tell the group in advance which clock the meeting follows, either a fixed UTC time or a fixed local time in one city, because the two will drift apart for some participants when clocks change. Then restate the new local times for each region the week before.

What is the safest time format to write?

A date with the month spelled out, a 24-hour time, and a named city is hard to misread. Numeric dates such as 11/12 are read differently in different countries, so avoid them when the audience is international.

Download Wrivio for Windows to turn a rough scheduling note into a clear, convert-free invitation without retyping it.