"Let's talk Thursday at 3 PM EST." It looks precise. In October, it's probably wrong, because New York isn't on EST at all, it's on EDT. Most people won't notice. The one person who takes it literally will turn up an hour late.

The problem with abbreviations

Time zone abbreviations feel official, but they're shorthand, and they're ambiguous in two ways.

First, they change with the seasons. EST is New York in winter. EDT is New York in summer. GMT is London in winter, BST is London in summer. Writing "EST" in July technically means a time an hour off from what you meant, and anyone using a converter will get that wrong time back.

Second, the same letters mean different places. IST is India, Ireland's summer time and, informally, Israel. CST is US Central Time and China Standard Time, which are 13 or 14 hours apart depending on the season. If your reader isn't sure which one you mean, they'll guess, and they'll guess their own.

Use a city, not a code

The simplest fix is to write the city instead of the abbreviation. "3 PM New York time" is right all year. So is "10 AM London time". A city name carries its daylight saving rules with it, so you never have to know whether it's currently EST or EDT.

This is also how the IANA Time Zone Database, the reference list that phones and computers use under the hood, names its zones: America/New_York, Europe/London, Africa/Lagos. City-based names exist precisely because abbreviations can't be relied on.

A format that works for everyone

If you're emailing more than one country, give each reader their own time rather than making them convert. It takes ten seconds and it removes almost every chance of a mix-up. The order below works well for most emails:

  1. Lead with the anchor time, written with the city. "Thursday 12 November, 3 PM London time."
  2. Add the converted times for anyone in another zone, in brackets. "(10 AM New York, 8:30 PM Mumbai, 4 PM Lagos)."
  3. Write the day name and the date together. Across big gaps, a late-afternoon time in one city can already be tomorrow in another.
  4. Use the 24-hour clock if your readers are mixed. "15:00" can't be misread as 3 AM.
  5. If the meeting is recurring, say which city it's anchored to. "This stays at 3 PM London time, even after the clocks change."

Watch the clock-change weeks

Daylight saving dates differ between countries, and that's when written times cause the most trouble. The UK and the EU change clocks on the last Sundays of March and October. The US changes on the second Sunday of March and the first Sunday of November. India, Nigeria, the UAE and Singapore don't change at all.

So an email sent in early October that says "every Thursday at 3 PM London, 10 AM New York" will be wrong for one week at the end of the month, when London has gone back and New York hasn't. Naming the anchor city means everyone knows which side of the sentence is the fixed one.

Don't forget the date line

Across very large gaps, the day itself can differ. A 6 PM call in Los Angeles on a Monday is already Tuesday lunchtime in Sydney. If you only write the time, one side will turn up a day early or a day late. Writing the date for each city, or at least flagging "your Tuesday" for the reader ahead of you, closes that gap completely.

When to use UTC

For technical teams, or anyone coordinating across five or six zones, UTC is a fair choice. It doesn't change for daylight saving and it doesn't belong to any one country, so nobody gets home advantage. The trade-off is that most people don't know their own UTC offset off the top of their head, so it's worth adding local times for anyone outside engineering.

What this really comes down to

Writing time zones well is a small act of courtesy. It moves the work of converting from the reader to the writer, which is the right way round, because the writer knows what they meant and the reader can only guess.

It's also a sign that the time is being agreed in the wrong place. If the email has to do all this work, it's because the people involved can't see each other's clocks. The more of the arrangement that happens somewhere both sides can see their own local time, the less the wording has to carry.

Should I write EST or ET in an email?

Write ET, or better, "New York time". EST is only correct in winter. ET, short for Eastern Time, covers both EST and EDT, so it's right all year, and a city name is clearer still for readers outside the US.

How do I write a time for people in several time zones?

Lead with one anchor time and its city, then list the converted times in brackets for each reader's city. For example: "3 PM London time (10 AM New York, 8:30 PM Mumbai)." Include the day and date too, in case the time crosses midnight somewhere.

Is GMT the same as UK time?

Only in winter. The UK is on GMT from late October to late March, then switches to British Summer Time, which is GMT+1. If you write "GMT" in summer you're describing a time an hour behind London.

Skipping the Conversions

Wenya shows every person their own local time when you suggest a slot in WhatsApp, iMessage or Telegram, so nobody has to write out the conversions. Try it free at wenyawanna.ai