Time Zones and UTC Explained
Understand offsets, locations, and changing clock rules. Read a concrete example, examine the trade-offs, and try a small exercise to see whether the principle applies to your situation.
The core rule or calculation
- Start here. UTC is the reference time scale used for global coordination.
- Add context. A UTC offset alone may not identify a place with seasonal clock changes.
- Keep in mind. Use IANA zone names such as America/New_York for software scheduling.
Work through an example
When it is 15:00 UTC, a location at UTC+9 displays midnight the next day. A call planned using only the phrase “3 p.m.” can therefore be off by nine hours and by a calendar date if participants assume different zones.
Time-zone errors are primarily communication errors; always state the zone alongside the local time.
Where calculations go wrong
A UTC offset such as −5 does not uniquely identify a location because daylight-saving transitions change civil time. Software should generally store an IANA zone such as America/New_York, where supported.
Try the method
For an international meeting, record date, clock time and named time zone. Ask participants to confirm what their own calendar displays after importing the invitation.
Further reading and verification
Read the linked reference for additional background on time & numbers. Review the applicable rules and update dates before using any example in a consequential decision.
Related BlogJD guides
Published October 9, 2026 · BlogJD Editorial Desk · How we prepare and correct content · Report a correction.