Time Zones Explained

Why time zones exist

Time zones are political borders painted on a clock. Governments—not physicists—decide which cities share the same legal time, so rules can shift whenever a parliament votes. UTC is the baseline; every other zone is described as UTC±offset (UTC-05:00, UTC+09:30, etc.), which explains half-hour quirks like India’s UTC+05:30 or Lord Howe Island’s UTC+10:30.

To stay accurate you need three things: the IANA zone name (America/Los_Angeles), the current UTC offset, and the next daylight saving change. That combo kills ambiguity, which is why the TimeyKit Timezone planner leans on IANA names instead of vague abbreviations.

Offsets and abbreviations

IANA zones beat local abbreviations

Abbreviations like PST, BST, or CST are overloaded. PST can mean Pacific Standard (UTC-08:00) or Philippine Standard (UTC+08:00), and they rarely indicate whether daylight saving is active. In contrast, America/Los_Angeles maps to the full DST history, so schedulers can compute the correct offset for any date—future or past.

Example: Seattle vs Singapore

Seattle (America/Los_Angeles) vs Singapore (Asia/Singapore): on 22 Feb 2026, LA is UTC-08:00 and Singapore UTC+08:00, a 16-hour gap, so 08:00 Seattle equals midnight Singapore. When U.S. daylight saving hits on 8 Mar, LA jumps to UTC-07:00, shrinking the gap to 15 hours. If your invite just says “PST,” nothing auto-adjusts; storing the IANA zone handles it.

Daylight saving ripple effects

About 70 regions still observe DST. They spring forward and fall back at different times, and some never move at all. The U.S. shifts on the second Sunday in March, the UK waits until the last Sunday, Queensland ignores DST entirely. Those in-between weeks wreck overlap unless you plan.

Best practice: log the date you care about, pick each teammate’s IANA zone, and inspect the overlap grid. The Timezone tool highlights shared hours and shows how DST warps them. Need a visual? Pin both cities on the World Clock wallboard and leave it running.

Example: US vs UK DST gap

Imagine a daily stand-up between New York (America/New_York) and London (Europe/London). In mid-March the U.S. has sprung forward but the UK has not. For two weeks the usual 5-hour difference shrinks to 4 hours, so a 09:00 New York stand-up shifts from 14:00 UK to 13:00 UK. If you schedule without checking, your UK crew wonders why the invite suddenly begins during lunch.

Building reliable workflows

Store base times in UTC

Keep raw timestamps in UTC (database, spreadsheet, whatever) and convert when you render them. UTC ignores DST, so math stays predictable. When you need something readable, use Intl.DateTimeFormat or the Epoch converter.

Tests and runbooks

Document which zones your team cares about and list the messy weeks. Maintain a “DST gotchas” page with a saved Timezone link so on-call folks can see overlaps in one click during March/October chaos.

FAQ

Why do some zones have half-hour offsets?

Local governments set legal time. India, Nepal, and parts of Australia chose half- or quarter-hour offsets to stay centered on their sun without adopting a neighbor’s schedule.

Is GMT the same as UTC?

GMT was historically the sun time at Greenwich. Modern systems use UTC, so treat GMT as UTC except during British Summer Time, when the UK shifts to UTC+01:00.

Do calendar apps handle DST automatically?

Yes—if the event stores an IANA zone. Problems happen when invites use floating times or “call me at 9am PST” text with no metadata.

How often do time zone laws change?

Every year multiple countries tweak DST windows or offsets. Refresh the tz database and double-check critical events in a planner before trusting memory.