Understanding Time Zones

Scheduling a Call Across 9 Time Zones Without Getting It Wrong

You're in New York trying to schedule a call with a colleague in Tokyo. New York is UTC-5 in winter (UTC-4 during daylight saving). Tokyo is UTC+9 year-round. The difference is 14 hours (or 13 hours when New York observes daylight saving). When it's 3pm Monday in New York, it's 5am Tuesday in Tokyo — which means there's almost no overlap during normal business hours.

Getting this wrong costs deals, misses flights, and schedules meetings at 2am. Here's how time zones actually work, what UTC means, and how to convert reliably.

The Baseline: UTC (Coordinated Universal Time)

UTC — Coordinated Universal Time — is the global time standard from which all other time zones are measured. It's based on atomic clocks and is the successor to GMT (Greenwich Mean Time). For practical purposes, UTC and GMT are the same; UTC is the technically precise term.

UTC is the zero point. Every time zone on Earth is described as UTC+ (ahead) or UTC- (behind) UTC, with the offset expressed in hours (and sometimes minutes).

Current UTC time is the same everywhere on Earth. When it's 15:00 UTC, that's the same moment in time whether you're in New York, London, or Tokyo — the clocks just display different local times:

• London in winter: UTC+0 → 15:00
• New York in winter: UTC-5 → 10:00 (5 hours behind UTC)
• Tokyo: UTC+9 → 00:00 next day (9 hours ahead of UTC)

The 24 Standard Zones — And Why Reality Is More Complicated

Theoretically, the Earth's 360° longitude divided by 24 hours creates 24 zones, each 15° wide, each offset by exactly 1 hour from the next. Reality is messier because countries and regions choose their offsets for political, economic, and geographic reasons.

Non-whole-hour offsets:

• India: UTC+5:30 (30-minute offset from the hour)
• Nepal: UTC+5:45 (45-minute offset)
• Iran: UTC+3:30
• Myanmar: UTC+6:30
• Sri Lanka: UTC+5:30
• Australia's Northern Territory: UTC+9:30

Half-hour offsets exist because some countries straddle "natural" zone boundaries and chose a compromise. India uses a single time zone for the entire country (despite its east-west span of nearly 30°) to maintain national unity — creating the 30-minute offset.

Same offset, multiple names: Eastern Standard Time (EST), which is UTC-5, is also called Colombia Time, Peru Time, Ecuador Time, and Cuba Standard Time. The same moment in time has different names depending on country.

Daylight Saving Time: The Layer That Breaks Everything

Daylight Saving Time (DST) shifts clocks forward 1 hour in spring and back in fall. Approximately 70 countries observe some form of DST; approximately 130 countries don't.

Crucially: Countries that do observe DST don't all do it on the same dates. The US and Canada change clocks on the second Sunday of March and first Sunday of November. The EU changes on the last Sunday of March and last Sunday of October. These dates don't always align.

The result: The time difference between New York and Paris changes three times per year:

1. January–March (before either changes): NY is UTC-5, Paris is UTC+1 → 6 hours apart
2. March (US switches, EU hasn't yet): NY is UTC-4, Paris is UTC+1 → 5 hours apart (~2 weeks)
3. After both switch: NY is UTC-4, Paris is UTC+2 → 6 hours apart again
4. Fall (EU switches first, US hasn't yet): NY is UTC-4, Paris is UTC+1 → 5 hours apart (~1 week)

This variability is why "just add 6 hours" breaks down — you need to know the current DST status of both locations.

Countries that don't observe DST at all: Japan, China, India, most of Africa, most of the Middle East, and significant parts of South America. Arizona in the US (except Navajo Nation) also doesn't observe DST, creating an interesting situation where Arizona and neighboring Nevada can be the same time zone in winter but 1 hour apart in summer.

Practical Conversion: New York, Paris, Tokyo

Using winter (UTC standard time) values:

• New York: UTC-5 (Eastern Standard Time)
• Paris: UTC+1 (Central European Time)
• Tokyo: UTC+9 (Japan Standard Time, no DST)

From New York 3pm:

• UTC: 3pm + 5 = 20:00 UTC
• Paris: 20:00 + 1 = 21:00 (9pm)
• Tokyo: 20:00 + 9 = 29:00 = 5am next day

Using summer (daylight saving) values:

• New York: UTC-4 (Eastern Daylight Time, when DST active)
• Paris: UTC+2 (Central European Summer Time, when DST active)
• Tokyo: UTC+9 (unchanged, no DST)

From New York 3pm in summer:

• UTC: 3pm + 4 = 19:00 UTC
• Paris: 19:00 + 2 = 21:00 (9pm — same result, both offset)
• Tokyo: 19:00 + 9 = 28:00 = 4am next day (1 hour earlier than in winter)

Notice: during summer, New York is actually 13 hours behind Tokyo instead of 14. Japan's lack of DST means the New York-Tokyo difference changes depending on whether the US has switched.

The International Date Line

The International Date Line runs roughly along 180° longitude through the Pacific Ocean. Crossing it eastward (toward the Americas) moves you back one calendar day; crossing westward (toward Asia/Australia) moves you forward one day.

A concrete example: A flight from Honolulu (UTC-10) to Auckland, New Zealand (UTC+13) crosses the date line. The clock difference is 23 hours. If you depart Honolulu at 9pm Monday, you arrive in Auckland at 8am Wednesday — even though the flight is only about 9 hours long.

The date line is why Pacific island nations like Kiribati, which spans either side of 180°, chose UTC+14 for its eastern islands — technically "ahead" of the date line — to keep the same calendar date across its territory.

The Practical Rule for Scheduling

For scheduling calls and meetings across time zones:

1. Convert both parties to UTC first. If you're UTC-5 and they're UTC+9, the difference is 14 hours.
2. Account for DST by checking whether each location currently observes it. DST status changes seasonally.
3. Find the overlap: A Tokyo colleague's 9am–5pm workday (UTC 00:00–08:00) barely overlaps with a New York colleague's 9am–5pm workday (UTC 14:00–22:00 in winter) — you'd need a very early morning in Tokyo or a late evening in New York to find any overlap.

The safest approach for cross-timezone scheduling: always share meeting times in UTC (e.g., "let's meet at 14:00 UTC") and let each person convert to their own local time. This eliminates the confusion from DST transitions and non-standard offsets entirely.