Fundamentals
What Is UTC and Why It Matters for Global Teams
A plain-English explanation of Coordinated Universal Time (UTC), how it differs from GMT, and why every distributed team should standardise on it.
· 5 min read
Coordinated Universal Time — UTC — is the time standard the entire world coordinates against. It does not observe daylight saving time and never shifts, which makes it the neutral reference point every other timezone is described in terms of.
UTC vs GMT
People use UTC and GMT interchangeably, and for everyday purposes they are the same. The difference is technical: GMT is a timezone based on the position of the sun at the Royal Observatory in Greenwich, while UTC is a time standard maintained by atomic clocks. UTC is what computers, aviation, and finance actually run on.
Why teams standardise on UTC
- It removes ambiguity — "the deploy is at 14:00 UTC" means the same instant for everyone.
- It is immune to daylight saving changes, so recurring events never drift.
- Logs, databases, and APIs almost always store time in UTC, so your team speaks the same language as your systems.
How to use it day to day
Pick UTC as the canonical timezone for shared calendars, status pages, and incident timelines. Let each person convert to their local time when they need to — a converter does that instantly. The key habit is to never schedule a cross-border event in a local timezone without also stating the UTC offset.
Once a team adopts UTC as its backbone, an entire class of "wait, was that my 3pm or yours?" confusion simply disappears.