Time zone mistakes come from daylight saving dates, not arithmetic. The places that break assumptions, UTC vs GMT, and habits that prevent 3 AM invites.
Time zone mistakes are rarely arithmetic errors. They come from daylight saving shifting on different dates in different countries, from cities that don't observe it at all, and from offsets that aren't whole hours. A converter handles the maths — the traps below are what actually causes the bad invites. Try the free Time Zone Converter → The Daylight Saving Trap The gap between two cities is not a fixed number. It changes several times a year, and the changes don't line up. Europe shifts on the last Sunday of March and the last Sunday of October The United States shifts on the second Sunday of March and the first Sunday of November The Southern Hemisphere shifts in the opposite direction, since its seasons are reversed Much of Asia and Africa doesn't observe DST at all The practical consequence: for a few weeks each spring and autumn, London and New York are four hours apart rather than the usual five. A recurring meeting set during one period silently moves for one side when the clocks change on different dates. This is why recurring cross-timezone meetings drift. The invite holds a fixed local time for whoever created it, and everyone else's local time shifts underneath them. Places That Break the Usual Assumptions India is UTC+5:30 — a half-hour offset. So are Iran (+3:30), Afghanistan (+4:30), and parts of Australia (+9:30). Nepal is UTC+5:45, a 45-minute offset. So are the Chatham Islands (+12:45). China uses a single time zone across the entire country despite spanning roughly five geographic ones. Sunrise in western China can be well after 9 AM. Arizona doesn't observe DST, except the Navajo Nation within it, which does. Its relationship to California and Denver changes twice a year in opposite directions. Australia has states that observe DST and states that don't, so internal Australian scheduling has the same problem international scheduling does. Practical Habits That Prevent Mistakes Write the time zone explicitly. "3 PM" is ambiguous. "3 PM CET" is not. In writing, always include the abbreviation or offset. Use UTC as the reference for technical coordination. Deployments, maintenance windows, and incident timelines should be stated in UTC — it doesn't observe DST and doesn't move. Let the calendar do the conversion. Create the event in your own time zone and let each attendee's calendar render it in theirs, rather than converting manually and typing a local time into the invite. Confirm the date, not just the hour. A 9 AM Tuesday call in Sydney is Monday afternoon in London. Cross-timezone scheduling crosses date boundaries more often than people expect. Double-check near DST transitions. Any meeting scheduled in March, October, or November between regions that shift on different dates is worth verifying. Watch for AM/PM errors on 12-hour clocks. Half the world reads 15:00 without hesitation and the other half needs to think about it. Where confusion is costly, 24-hour format removes the ambiguity. UTC, GMT, and Offsets UTC (Coordinated Universal Time) is the modern global time standard. It never changes for daylight saving. GMT (Greenwich Mean Time) is a time zone that happens to equal UTC+0. The UK uses GMT in winter and BST (UTC+1) in summer — so "GMT" is not a synonym for "UK time" year-round, though it's frequently used that way. Offsets express a zone's distance from UTC: UTC−5 is five hours behind, UTC+9 is nine ahead. Note that a city's offset changes with DST — New York is UTC−5 in winter and UTC−4 in summer. Related Tools World Clock - current time in multiple cities at once Countdown Timer - for deadlines and launches across regions Frequently Asked Questions Why does the time difference between two cities change during the year? Because daylight saving time starts and ends on different dates in different countries, and some places don't observe it at all. During the weeks when one region has shifted and the other hasn't, the gap between them is an hour smaller or larger than usual. What's the difference between UTC and GMT? UTC is the global time standard used as a reference point and never observes daylight saving. GMT is a time zone equal to UTC+0. The UK follows GMT in winter but switches to BST (UTC+1) in summer, so GMT and UK local time are not the same year-round. Which countries have half-hour time zones? India (UTC+5:30), Iran (UTC+3:30), Afghanistan (UTC+4:30), Myanmar (UTC+6:30), and parts of Australia (UTC+9:30) use half-hour offsets. Nepal (UTC+5:45) and the Chatham Islands (UTC+12:45) use 45-minute offsets. How do I schedule a meeting across time zones without errors? Create the event in your own time zone and let attendees' calendars convert it automatically, always state the time zone explicitly in writing, and confirm the date as well as the hour meetings frequently land on a different day for the other party. Does China really have only one time zone? Yes. Despite spanning roughly five geographic time zones, the entire country officially uses a single standard time, which is why sunrise in the far west can occur we