Time Zones and Daylight Saving Explained: How to Schedule Across Countries Without Mistakes

Almost everyone who works with people in other countries has a story about the meeting that went wrong. You show up on time and nobody's there. Or you get a polite message asking where you are, an hour after it started. Usually nobody did anything silly. The time difference just changed, and nobody noticed.

Here are time zones explained in plain terms, including the bits that catch people out, and a simple way to avoid those mix-ups for good.

Everything starts at UTC

The world sets its clocks relative to one reference time called UTC, Coordinated Universal Time. You can think of it as the time at zero degrees longitude, without any seasonal changes.

Every place on Earth is a certain number of hours ahead of or behind UTC. Doha is UTC+3. Nairobi is also UTC+3. New York is UTC-5 in winter. Tokyo is UTC+9. That number is called the UTC offset, and the difference between two places is just the gap between their offsets.

If that were the whole story, time zones would be easy. Doha to New York would always be eight hours. It isn't.

Daylight saving moves the goalposts

Many countries shift their clocks forward by an hour in spring and back again in autumn, to get more daylight in the evenings. That's daylight saving time, and it's why the gap between two cities changes during the year.

New York moves to UTC-4 in summer. London moves from UTC+0 to UTC+1. Doha, Nairobi, Riyadh, Dubai, India, China and Japan don't change their clocks at all. So the difference between Doha and New York is eight hours in winter and seven in summer, even though nothing happened in Doha.

This is also why it's risky to say "we're three hours ahead of London." That's true for half the year.

The weeks that catch everyone out

Here's the part most people don't know. Countries that use daylight saving don't all switch on the same day.

The United States moves its clocks forward on the second Sunday in March and back on the first Sunday in November. The UK and the European Union move forward on the last Sunday in March and back on the last Sunday in October.

That leaves a gap of two or three weeks in March, and about a week around the end of October, when America has switched and Europe hasn't, or the other way round. During those weeks, New York and London are four hours apart instead of the usual five. Recurring meetings between the US and Europe suddenly land an hour off for one side.

Here's what a 4:00 pm Doha meeting looks like across the year:

Period	Doha	London	New York
Winter	4:00 pm	1:00 pm	8:00 am
March gap (US switched, UK not yet)	4:00 pm	1:00 pm	9:00 am
Summer	4:00 pm	2:00 pm	9:00 am

Notice that Doha never moves. Everyone else moves around it, at different times.

The southern hemisphere adds another twist. Its summer is our winter, so places like most of Australia, New Zealand and Chile change their clocks in the opposite direction, at different times again. Some regions in the same country don't change at all. Queensland, for example, stays put while Sydney shifts.

Not every offset is a whole hour

Most time zones are whole hours from UTC, but not all. India is UTC+5:30. Nepal is UTC+5:45. Parts of Australia, like Adelaide and Darwin, are on half-hour offsets, and Newfoundland in Canada sits at UTC-3:30. If you schedule with India regularly, that extra half hour is easy to drop by accident when you do the maths in your head.

Abbreviations are a trap

Time zone abbreviations look precise, but many of them are shared. CST can mean Central Standard Time in the US or China Standard Time, which are fourteen hours apart. IST is used for India, Ireland and Israel. Writing "3 pm CST" in an international email is asking for trouble.

City names are much safer. "3 pm New York time" is clear to everyone. Computers do the same thing behind the scenes: they store time zones as region and city names like Asia/Qatar or America/New_York, because a city's rules can be looked up, including every daylight saving change.

When the date changes too

Time differences can also move a meeting to a different day for someone. If you set a 9:00 am Monday call from Doha, it's still Sunday night in Los Angeles. A 10:00 pm Monday call from Doha is already Tuesday morning in Auckland during the New Zealand summer. Always check the day, not just the hour, when someone is far away.

How to schedule without mistakes

A few habits fix almost all of this.

Put meetings in a calendar app instead of writing times in messages. Calendar invites carry the time zone with them and adjust automatically for every attendee.

When you do write a time, name the city: "4 pm Doha time (1 pm London)." It takes a few seconds and removes all doubt.

Double-check recurring meetings in March and around late October. Those are the weeks the gaps between countries change.

Be careful with times near 2:00 am on the night the clocks change. In spring, that hour can be skipped entirely, and in autumn it happens twice.

And keep the cities you work with in front of you. A world clock that shows each city's current time, offset and whether it's already tomorrow there does the maths for you. WakeMode's World Clock uses the same city-based time zone data your computer does, so daylight saving changes are handled automatically.