Daylight Saving Time - How Clock Changes Affect Global Coordination
Understand how daylight saving time works, which countries observe it, when transitions occur, and how DST complicates international scheduling.
The time difference between two cities equals the difference between their UTC offsets. Tokyo (UTC+9) and New York (UTC-5) differ by 9 - (-5) = 14 hours. Tokyo is ahead, so when Tokyo is at Monday 14:00, New York is at Monday 00:00. The math is simple, but sign mistakes are surprisingly easy and produce 28-hour or 0-hour answers that should be obviously wrong.
A reliable mental rule is "destination offset minus origin offset." A positive result means the destination is ahead; a negative result means it lags. From New York's perspective, 9 - (-5) = +14, so Tokyo is 14 hours ahead. Always include the sign even when one offset is negative, or you will keep producing the same off-by-one bugs.
Not every offset is a whole number of hours. India uses UTC+5:30, Nepal UTC+5:45, Iran UTC+3:30, Myanmar UTC+6:30, and the Chatham Islands UTC+12:45. These fractional offsets exist for political and historical reasons, sometimes deliberately to assert a national identity distinct from larger neighbors.
Tokyo (UTC+9) and India (UTC+5:30) differ by 9 - 5.5 = 3.5 hours, or 3 hours and 30 minutes. When Tokyo is at 15:00, India is at 11:30. The minute carry/borrow makes mental arithmetic error-prone, especially under time pressure. For these zones, a world clock tool eliminates the entire class of mistakes that would otherwise turn a clear meeting into a missed call.
Cities with daylight saving have two different offsets per year. Tokyo and London differ by 9 hours in winter (when London is on GMT) but 8 hours in summer (when London is on BST = UTC+1). Tokyo and New York differ by 14 hours in winter (EST = UTC-5) and 13 hours in summer (EDT = UTC-4). Memorize both numbers for any city pair you deal with regularly.
Even more tricky is that DST start dates differ across regions. The U.S. enters daylight saving on the second Sunday of March, while most of Europe waits until the last Sunday of March. For two to three weeks, the gap between U.S. and European cities is one hour different from the rest of the year. International teams that meet weekly often discover this only when someone shows up late, hopelessly off-schedule.
When the time difference exceeds 12 hours, the calendar date can shift along with the time. Tokyo (UTC+9) and Honolulu (UTC-10) are 19 hours apart. When Tokyo is at Tuesday 10:00, Honolulu is at Monday 15:00. If the resulting time goes past 24 hours or below 0, you need to add or subtract a day to the answer.
A reliable workaround is to convert through UTC as a checkpoint. Tokyo's Tuesday 10:00 is Tuesday 01:00 UTC (10:00 - 9 = 01:00). From there, Honolulu's time is Tuesday 01:00 - 10 = Monday 15:00. Using UTC as an intermediate step prevents most date-shift errors and forces you to think clearly about the two-step conversion rather than skipping straight to the answer.
If you regularly contact certain cities, memorize both their winter and summer offsets from your home zone. From Tokyo, the main pairs are London -9/-8, New York -14/-13, San Francisco -17/-16, and Sydney +1/+2 (Australia's daylight saving runs from October through April). Knowing the seasonal pair lets you eyeball times correctly across the year.
A useful complement is to know the overlap of business hours between any two cities. Tokyo's 9:00-18:00 maps to New York's 20:00-05:00, meaning there is no overlap with normal U.S. business hours. Once you internalize this, you stop trying to schedule synchronous meetings between Tokyo and New York and start designing asynchronous workflows instead. The team's productivity improves immediately, and one side stops getting stuck with chronic late nights.
Was this article helpful?
Understand how daylight saving time works, which countries observe it, when transitions occur, and how DST complicates international scheduling.
The cardinal rule of timestamp handling in software is store in UTC, display in local. This article covers the rationale, ISO 8601 formatting, JavaScript and Python patterns, the most common bugs, and a testing strategy that catches DST and date-line issues before they reach production.
Earth rotates 360 degrees in 24 hours, so 15 degrees of longitude equals one hour of time difference in principle. In practice, time zones follow politics and economics far more than meridians. This article explores the geographic principle and the many places where reality diverges from the rule.