How Time Zones Actually Work (And Why 9am Is Never Just 9am)
Almost every scheduling mistake comes from treating a time zone as a fixed number of hours. It is not. It is a rule that can change twice a year, and occasionally by an act of parliament.
By Nishanth Narayanan · 2026-08-06 · 8 min read
A time zone is a rule, not a number
Most people carry a mental table: India is five and a half hours ahead of London, New York is five hours behind it. Those numbers are right often enough to feel reliable, and wrong often enough to cost you a meeting.
The reliable way to think about it is that every place on earth keeps a local time defined as an offset from UTC, Coordinated Universal Time. India is UTC+5:30. New York is UTC-5 for part of the year and UTC-4 for the rest. London is UTC+0 in winter and UTC+1 in summer. The offset is a property of a place at a moment, not a property of the place forever.
This is why the gap between two cities is not constant. Between London and New York it is five hours for most of the year, but for two short windows in spring and autumn it is four hours, because the two countries change their clocks on different dates. Anyone who books a recurring call in late March or late October has met this personally.
Why the offsets are so strange
If time zones were tidy, there would be twenty four of them, each an hour wide, following lines of longitude. In practice there are around thirty eight distinct offsets in use, because time is set by governments, not by geography.
India runs a single zone across a country wide enough to justify two, which is why the sun rises well over an hour earlier in Arunachal Pradesh than in Gujarat while both read the same clock. China does the same thing on a far larger scale with one zone across five geographic zones worth of territory. Nepal sits at UTC+5:45, deliberately fifteen minutes off its neighbour. The Chatham Islands use UTC+12:45.
These are not errors. A country picks the time that suits its administration, its trade partners and sometimes its politics, and the map follows the decision rather than the other way round.
Daylight saving is the part that breaks calendars
Roughly seventy countries move their clocks forward in spring and back in autumn. Most of Asia and Africa does not. That mixture is the real source of trouble, because it means the gap between a country that changes and a country that does not moves twice a year.
India never changes its clocks. The United States does. So the difference between Mumbai and New York is nine and a half hours in one part of the year and ten and a half in another. If you agreed a standing 8pm IST call in January with a colleague in New York, they were joining at 9:30am. Come March, when the United States springs forward and India does not, that same call lands at 10:30am for them and nobody sent an email about it.
The changeover dates do not line up either. The European Union moves on the last Sunday in March and October. The United States moves on the second Sunday in March and the first Sunday in November. That leaves several weeks each year where the usual London to New York gap is simply not what everyone assumes.
The abbreviations lie to you
Time zone abbreviations look authoritative and are genuinely ambiguous. CST means Central Standard Time in North America, China Standard Time in Asia and Cuba Standard Time in the Caribbean, and those are hours apart. IST is India Standard Time, Irish Standard Time and Israel Standard Time. BST is British Summer Time, but it was also British Standard Time in a different era.
Worse, an abbreviation often encodes whether daylight saving is active. A calendar invitation that says EST in July is either wrong or means something unusual, because the American east coast is on EDT in July. Writing "3pm New York time" removes every one of these problems, because the reader looks up the city rather than decoding the letters.
What to do instead
Three habits remove most of the risk.
Name the city, not the abbreviation. "14:00 in Berlin" cannot be misread. "14:00 CET" can, especially in summer when Berlin is on CEST.
Fix the moment, not the local time, for recurring meetings. If a series matters, decide whose morning is protected and let the other side drift when the clocks change, rather than pretending the gap is fixed.
Check the actual date you care about. The gap in November may not be the gap in April. Our time zone converter and meeting planner shows every city side by side for a date you choose, including the day boundary, so a call that lands on tomorrow for someone is visible before you send the invitation.
The short version
A time zone is a rule maintained by a government, expressed as an offset from UTC, and it can change. Two cities do not have a fixed difference. Abbreviations are ambiguous and sometimes encode the season. Name cities, check the date, and let a tool do the arithmetic rather than your memory.
Frequently asked questions
Why is India five and a half hours ahead instead of a whole number?
India chose a single national time based on a meridian near Allahabad, which sits at five and a half hours from UTC. A whole hour offset would have put the clock noticeably out of step with the sun across a country this wide, and running two zones was rejected for administrative reasons.
Does the gap between two cities ever change?
Yes, whenever one of them starts or ends daylight saving and the other does not. Between London and New York the gap is normally five hours but drops to four for a few weeks each spring and autumn, because the two change on different dates.
Is GMT the same as UTC?
They refer to the same instant for everyday purposes, but they are defined differently. UTC is a modern atomic standard, GMT is a historical solar one, and GMT is also the winter time of the United Kingdom. Use UTC when you mean the reference standard.
About the author
Nishanth Narayanan builds and maintains GlobalTimeTools from Coimbatore, India. He works with distributed teams across Indian, European and US time zones, which is where most of these questions came from.