Remote work turned time zones from an occasional nuisance into a daily one. A call set for '3pm' means five different things to five people, and one small mistake means someone joins an empty room — or misses it entirely.
Here's how time zones actually work, the traps that cause most mix-ups, and how to convert any time reliably.
UTC is the anchor
Every time zone is defined as an offset from UTC (Coordinated Universal Time) — the global reference clock. New York is UTC−5 (in winter), London is UTC+0, Tokyo is UTC+9. To convert between two zones, you're really just going through UTC: subtract one offset to get to UTC, add the other to arrive.
That's why writing times in UTC (or always labeling the zone) removes ambiguity — everyone can translate from a single reference.
The trap: daylight saving time
The offsets above aren't fixed. Many regions shift their clocks an hour for part of the year, and — this is the killer — they don't all switch on the same date, and the Southern Hemisphere shifts the *opposite* way to the Northern. So the gap between, say, New York and London isn't always five hours; for a few weeks each year it's four or six.
This is exactly when meetings go wrong — around the DST switch dates, when a 'usual' time gap quietly changes for a week or two. Always re-check around late March and early November.
Convert any time in seconds
Don't do the offset math in your head — it's where mistakes creep in. The free Time Zone Converter takes a time in one zone and shows the same moment in cities around the world, with daylight saving handled automatically.
Time Zone ConverterConvert a time across world time zones.Habits that prevent mix-ups
- Always label the zone. '3pm ET' beats '3pm' every time.
- Use city-based zones (America/New_York), not just offsets — so DST is applied for you.
- Send calendar invites, which auto-convert to each attendee's local time.
- Double-check near DST switch dates, when the usual gap changes.
- For written schedules, consider UTC as a neutral reference everyone can translate.