Scheduling a call across time zones feels like it should be basic arithmetic -- add or subtract a few hours and you're done. Then you hit a country on a half-hour offset, or your meeting shifts by an hour overnight because one side just changed its clocks, and the "simple" math falls apart. Here's what's actually happening under the hood.
UTC is the anchor, not a timezone you live in
Every timezone is defined as an offset from Coordinated Universal Time (UTC), which doesn't observe daylight saving and doesn't belong to any single country. When someone says a city is "UTC+5:30" or "UTC-4," they're describing how far that location's clock is from UTC at this moment -- not a fixed, permanent number. Computers and servers generally store timestamps in UTC internally and only convert to local time for display, which is exactly why so many scheduling bugs come from mixing up when that conversion happens.
Why offsets aren't always whole hours
Most people assume every timezone sits on a clean hour boundary, but that's not true. India, for example, runs on UTC+5:30. Parts of Australia and Canada use 30- or 45-minute offsets. If you're mentally converting by counting whole hours on your fingers, these half-hour zones are where the math quietly breaks.
Daylight Saving Time breaks the math twice a year
Even within a single timezone, the offset from UTC isn't constant. Many countries shift their clocks forward in spring and back in autumn, which means the gap between, say, London and New York is four hours for part of the year and five hours for the rest -- and the two regions don't always switch on the same date. This is why a recurring meeting that was fine in March can suddenly land at the wrong hour in November: one side observed a DST change and the other didn't, or they changed on different weekends.
Not everywhere observes it
A meaningful number of countries and regions don't use daylight saving at all, and stick to a single offset year-round. That means a gap that's consistent for six months of the year can change for the other six, purely because the other party's country does something yours doesn't.
Convert without guessing
The safest way to handle any of this is to stop doing the mental math and just look up the actual current offset, since it can silently shift depending on the date. The World Clock shows the current time in major cities at a glance, and the Timezone Converter lets you convert a specific time between any two zones directly, accounting for whichever DST rules are in effect on that date.