The short answer: write the meeting time in the recipient's local zone, name your own zone too, and anchor everything to UTC as the unambiguous reference. Always include the full date, and use either 24-hour time or an explicit AM/PM. One unambiguous line beats three vague ones.
Most "sorry, I thought it was an hour later" mix-ups are not failures of attention. They are failures of formatting. The time was written in a way that could be read two ways, so someone read it the wrong way. Fixing it is mechanical.
Why do meeting times get misread?
A bare time carries hidden assumptions. Write "let's meet at 3" and the reader silently fills in three blanks: which zone, which day, morning or afternoon. If any of their assumptions differ from yours, the meeting is wrong before it starts. The cure is to write the time so none of those blanks are left for the reader to guess.
Give the time in the recipient's local zone
The single most considerate thing you can do is state the time as it will appear on their clock. A reader in Berlin should not have to do mental arithmetic from your time. If you are writing to several people in different places, list each one:
- 09:00 in San Francisco
- 12:00 in New York
- 17:00 in London
- 18:00 in Berlin
It looks like more text, but it removes all conversion from the reader's plate. Nobody is left translating your zone into theirs at the moment they are deciding whether they can make it.
Always name your own zone
If you only have space for one time, name the zone it belongs to. "14:00 (London time)" is unambiguous; "14:00" is not. Prefer the full name or region over an abbreviation, because abbreviations collide: "CST" means Central Standard Time in the US, China Standard Time, and Cuba Standard Time, three different offsets. "America/Chicago" or "US Central" leaves no doubt.
Use UTC as the unambiguous anchor
For any audience spread across zones, give a single UTC reference alongside the local times. UTC is fixed, it never observes daylight saving, and anyone can convert from it. It is the one value every reader can check against their own clock with confidence.
A common slip is writing GMT instead. GMT and UTC line up in winter, but GMT does not shift for daylight saving, so in summer the UK is on BST (UTC+1), and a "GMT" label can land your reader an hour out. That single hour matters more than it sounds: Harvard Business School research analysing over 12,000 employees found that synchronous communication such as calls and video chats fell by 11 percent for every extra hour of time difference between colleagues. Use UTC. For the full distinction, see UTC vs GMT, and for when to lean on UTC in the first place, should you schedule in UTC.
Include the date and an explicit AM/PM
Two more details close the remaining gaps. First, write the full date, not just "tomorrow": a time near midnight can fall on a different calendar day depending on the reader's zone, so your Tuesday evening can be their Wednesday morning. Second, kill the AM/PM ambiguity. Either use 24-hour time (17:00) or write the period out (5:00 PM). A lone "5:00" can be read twelve hours wrong.
Good versus bad, side by side
| Don't write | Write instead |
|---|---|
| Let's meet at 3 tomorrow | Let's meet Thu 5 June, 15:00 London / 10:00 New York (14:00 UTC) |
| Call at 8 GMT | Call at 08:00 UTC on 5 June (09:00 BST in London) |
| 9am CST works | 09:00 US Central (14:00 UTC), Wed 4 June |
| Same time next week | Same time, 16:00 UTC, on Tue 10 June |
Prose in an email is a courtesy; the calendar event is the source of truth. A proper invite stores the time in a real zone and shows each guest their own local time automatically, daylight saving included. With Atlas you pick the overlap once and it adds the meeting to your calendar in everyone's correct local time, so the email line and the invite always agree.
A simple template you can reuse
When in doubt, follow one pattern: weekday, full date, local time + zone for each side, then the UTC anchor in brackets. For example: "Wed 4 June, 09:00 New York / 14:00 London (13:00 UTC)." It reads cleanly, it survives forwarding to someone in a fourth zone, and it gives every reader something they can verify.
What it means for scheduling
Writing the time well is the last step, not the first. Before you can write a good line you have to find a slot that actually works for everyone, which is the real work when waking hours barely overlap. That is what Atlas is for: it shows each person's current local time, shades their working hours, suggests the best overlap, and adds it to your calendar in one tap. Then the email is easy, because you are just describing a time you already know is right.
Frequently asked
How should I write a meeting time in an email?
Should I use GMT or UTC when writing a meeting time?
What is the most common mistake when writing meeting times?
Do I need to include the date as well as the time?
Stop doing timezone math
Atlas finds the time everyone's awake and adds it to your calendar in one tap.
One-time purchase, yours forever.