How to Read Time Zones
Time zones are easier to understand when you separate four ideas: place-based identifiers, abbreviations, UTC offsets, and daylight saving rules.
Updated May 20, 2026 · 6 min read
Key takeaways
- - Use place-based time zones for future scheduling.
- - Do not rely on abbreviations without context.
- - Treat UTC offsets as current snapshots unless a date is specified.
Place identifiers are the safest
Identifiers like Africa/Lagos, Europe/London, and America/New_York describe a rule set for a location. They are safer than abbreviations because they can account for seasonal changes.
When building schedules, use a city or country page tied to an IANA time zone instead of typing a fixed offset manually.
Abbreviations can be ambiguous
CST can mean Central Standard Time, China Standard Time, or Cuba Standard Time depending on context. IST can mean India, Israel, or Irish time in different contexts.
If an abbreviation matters, pair it with a city, country, or UTC offset.
Offsets are snapshots
An offset like UTC+1 tells you the current clock difference from UTC. It does not tell you whether that place changes clocks later in the year.
For a future meeting, confirm the exact date in the meeting planner.