Abbreviations like EST, CST, and IST feel convenient, but they are one of the most common causes of scheduling mistakes. The problem is simple: abbreviations are reused across regions, and some tools interpret them differently.
Why abbreviations fail
- They’re reused: “CST” can mean US Central, China Standard, Cuba Standard, and more.
- DST complicates them: “EST” is a specific standard-time offset; many people use it year-round even when the region is on daylight time.
- Apps guess: different software may map an abbreviation to different rules.
If the invite matters, avoid abbreviations. Use a city (“9:00 in New York”), a named zone (“America/New_York”), or a single UTC time.
What to write instead
Pick one of these patterns:
- City-based: “Tue 09:00 in New York” (then let calendars convert).
- IANA identifier: “Tue 09:00
America/New_York” (great for technical teams). - Single reference: “Tue 14:00 UTC” (everyone converts locally).
Quick verification step
Before sending, do a fast sanity check. Open TimeZoneMeet, look up each participant’s city, and confirm the local time. If you’re choosing a fair window between two cities, use Schedule.
Mini-FAQ
Are any abbreviations safe? “UTC” is generally safe. Beyond that, be careful.
What if someone insists on abbreviations? Include a second format, like “9:00 in New York (14:00 UTC).”
Why do calendars sometimes show a different local time? If the underlying time zone or DST rules differ, conversions can shift.