Time Zone Confusion: A Practical Guide to Working Across Time Zones

Time zone arithmetic seems simple until you get it wrong and miss a meeting by an hour — or a day. UTC, GMT, offsets, DST, and the IANA database all interact in ways that catch people out regularly. Here's a ground-up explanation of how time zones actually work, and how to schedule reliably.

UTC vs GMT: Are They the Same?

For most practical purposes, UTC (Coordinated Universal Time) and GMT (Greenwich Mean Time) are interchangeable. Both represent the same base reference time. However, they are technically different:

• GMT is a time zone — it's the local time at the Greenwich meridian in the UK, which does not observe Daylight Saving Time. GMT is always UTC+0.
• UTC is a time standard, not a time zone. It is the successor to GMT and is maintained by atomic clocks. It is the international basis for civil time.

The difference matters in edge cases: the UK observes BST (British Summer Time = UTC+1) in summer, so "London time" is not always GMT. UTC+0 is always UTC+0, regardless of season.

What UTC Offsets Mean

Time zones are defined by their offset from UTC. UTC+5:30 (India Standard Time) means local time is 5 hours and 30 minutes ahead of UTC. UTC-8 (Pacific Standard Time) is 8 hours behind UTC.

The calculation is simple arithmetic: add the offset to UTC for ahead-of-UTC zones, subtract for behind-UTC zones. The catch is that offsets change with Daylight Saving Time.

The DST Trap

Daylight Saving Time (DST) shifts clocks forward by one hour in spring and back in autumn to extend evening daylight. It sounds simple. The problems:

• Countries observe DST on different dates. The US and EU switch on different weekends, creating a 1–3 week window where their offset difference is different from normal. A meeting scheduled as "always 3 hours apart" can suddenly be 2 or 4 hours apart.
• Not all countries observe DST. India, China, Japan, UAE, and most of Asia and Africa do not observe DST. A fixed UTC+5:30 stays fixed all year.
• Some regions within a country differ. Arizona (US) does not observe DST while the rest of the US does, so Phoenix can be on the same time as California or one hour behind depending on the time of year.
• Clocks spring forward, creating a missing hour. Schedules set for 2:30am on a DST spring-forward night jump to 3:30am without ever existing as a real time.

The IANA Time Zone Database

Behind every reliable time zone tool is the IANA Time Zone Database (also called the Olson database), a continuously maintained registry of all historical and current time zone rules. It uses named identifiers like America/New_York, Asia/Dubai, and Europe/London rather than offset strings, because offsets change with DST and political decisions.

This is why you should always schedule meetings using named time zones rather than offset strings. "4pm UTC+4" is ambiguous — it doesn't say whether DST applies. "4pm Asia/Dubai" is unambiguous because Dubai doesn't observe DST and is always UTC+4.

ISO 8601: The Right Way to Write Times

ISO 8601 is the international standard for representing dates and times. A complete ISO 8601 datetime with timezone offset looks like:

The format is: YYYY-MM-DD, T separator, HH:MM:SS, then the UTC offset. Using Z instead of +00:00 indicates UTC explicitly. This format is unambiguous: it specifies both the exact moment in time and the local clock reading, so there is no room for misinterpretation.

When sharing meeting times across teams, always include the UTC equivalent: "3pm Dubai time (11am UTC)" removes all ambiguity.

Practical Tips for Remote Teams

• Use UTC for internal communication. "Deploy at 18:00 UTC" is unambiguous. "Deploy at 6pm" is not.
• Book recurring meetings with the person furthest from UTC. If a meeting works for someone in Auckland and someone in London, it works for everyone in between.
• Beware the DST transition weeks. Double-check meeting times in the first two weeks of March and November (US DST changes) and the last week of March and October (EU changes).
• Use your calendar tool's time zone feature. Google Calendar, Outlook, and Calendly all support creating events that display in each attendee's local time.
• Avoid scheduling during DST transitions. A meeting at 2am in a region that's about to spring forward will either not exist or be one hour later than planned.

Best Overlap Windows by Region Pair

When scheduling across major regions, these windows represent the most common overlap during business hours (9am–6pm local):

• UK ↔ US East Coast: 14:00–18:00 UTC (2pm–6pm London, 9am–1pm New York)
• UK ↔ India: 09:30–13:30 UTC (9:30am London, 3pm–7pm Mumbai)
• US East ↔ US West: 12:00–18:00 UTC (8am–2pm LA, 7am–1pm New York) — full overlap possible
• Dubai ↔ London: 09:00–14:00 UTC (1pm–6pm Dubai, 9am–2pm London)
• Singapore ↔ UK: 09:00–10:00 UTC — only one hour overlap; consider asynchronous communication