Definitions that matter
UTC (Coordinated Universal Time) is the atomic clock reference everything serious uses—aviation, satellites, APIs. GMT (Greenwich Mean Time) is a historical label tied to the mean solar time at the Royal Observatory. The UK government runs GMT in winter, then switches to British Summer Time (BST, UTC+01:00) in summer. Drop “10:00 GMT” into a July invite and half the world argues about whether you meant BST. UTC never shifts, so it removes the guesswork.
When the difference appears
Example: March product launch
A launch stream scheduled for March 24, 2026 includes production staff in London and viewers in Toronto. The UK moves to British Summer Time on March 29, so on the 24th both UTC and GMT align at 0 offset. If the run shifts to April 3, London becomes UTC+01:00 while UTC holds steady. Calling the show “18:00 GMT” would actually refer to 19:00 London after the shift. Basing the invite on UTC keeps the slot stable for crew and broadcast partners.
Example: November maintenance
Many SRE teams freeze deployments during the North American DST rollback because 01:30 repeats. If your runbook says “maintenance window 00:30–02:30 GMT” on November 1, UK-based responders assume the window occurs overnight locally. American responders read it as UTC. Clarify by stating “00:30–02:30 UTC” and linking to the World Clock wallboard that highlights London, New York, and UTC simultaneously.
How to communicate clearly
Keep tooling, APIs, and incident docs in UTC. When speaking to humans, show UTC plus their local time. The TimeyKit Timezone tool makes it painless: set one row to UTC and the other to the target city, screenshot the overlap, and paste it into the invite. For shared displays (ops centers, pubs), pin UTC in the World Clock wallboard so everyone can compare without mental math.
If contracts or broadcasters require GMT wording, include the date and note whether the UK is on BST. Example: “Doors open 17:00 GMT (18:00 London during BST).”
Operational checklist
- Store timestamps in UTC even if the UI mentions GMT/BST.
- Include weekday + date on every schedule notice so ambiguity dies immediately.
- Link to a World Clock view with UTC, London, and your home base so stakeholders can double-check in one glance.
Try the tools
Related guides
FAQ
- Is GMT obsolete?
- Not entirely, but outside UK legal contexts UTC is the safer reference. Aviation, networking, and APIs all lean on UTC.
- Does UTC observe leap seconds?
- Yes—every few years UTC inserts a leap second to stay aligned with Earth’s rotation. Most business systems smear or absorb it silently.
- What about Zulu time?
- Zulu (Z) is NATO phonetic for UTC+00:00. “14:00Z” equals 14:00 UTC.
Need to translate another offset? Use the Timezone tool.