What Is UTC Time and How Do You Use It to Schedule Remote Meetings?
UTC (Coordinated Universal Time) is the time standard that never shifts for daylight saving, which makes it the safest common reference when people in different regions need to agree on a meeting time. Use it when your team spans multiple time zones or when a recurring meeting must survive daylight saving changes. If everyone shares one time zone, local time is usually simpler.
What UTC actually is
UTC is a time standard, not a time zone. It is the baseline that civil time zones are defined against, expressed as offsets such as UTC+01:00 or UTC−05:00. Unlike local zones, UTC has no daylight saving adjustment, so it stays constant all year.
That stability is why remote teams, developers, and schedulers often write times as "14:00 UTC" instead of naming a city. A city label can be ambiguous during daylight saving transitions; a UTC value cannot.
UTC vs GMT
GMT (Greenwich Mean Time) is a time zone used in the UK and some other contexts. In everyday scheduling, UTC and GMT show the same clock time, so people often use them interchangeably. The practical difference:
- UTC is the modern reference standard used in computing, aviation, and international coordination.
- GMT is a civil time zone name, and the UK switches to BST (UTC+01:00) in summer.
If you write "14:00 GMT" in July, a UK reader may wonder whether you mean GMT or British Summer Time. Writing "14:00 UTC" removes that doubt.
How to convert UTC to a local time
The conversion is a single addition or subtraction, but the offset you use depends on the date, because many regions change offset for daylight saving.
- Find the target region's current UTC offset. For example, New York is UTC−05:00 in winter and UTC−04:00 in summer.
- Apply the offset to the UTC time. 14:00 UTC minus 5 hours = 09:00 in New York (winter).
- Check the date, not just the season. Daylight saving start and end dates differ by country, so a March meeting can fall on different offsets in the US and Europe.
- Confirm with a converter or visualizer before sending the invite, especially for recurring meetings.
A quick reference for a 14:00 UTC meeting:
| Region | Winter offset | Local time | Summer offset | Local time |
|---|---|---|---|---|
| London | UTC+00:00 | 14:00 | UTC+01:00 | 15:00 |
| New York | UTC−05:00 | 09:00 | UTC−04:00 | 10:00 |
| Berlin | UTC+01:00 | 15:00 | UTC+02:00 | 16:00 |
| Tokyo | UTC+09:00 | 23:00 | UTC+09:00 | 23:00 |
Note that Tokyo keeps the same offset year-round, while London, New York, and Berlin shift. That mismatch is exactly where manual math goes wrong.
Why UTC helps when scheduling remote meetings
When you anchor a meeting to UTC, every participant converts from one fixed point instead of from each other's local times. This reduces two common errors:
- Double conversion mistakes. Converting from "my time" to "their time" invites sign errors. Converting from UTC to each local time is a single step per person.
- Daylight saving drift. A recurring meeting set in local time can silently move by an hour for some participants when their region changes offset. A UTC anchor keeps the intended moment fixed, though the local clock time will still shift for those regions.
For recurring meetings, state both: "14:00 UTC (09:00 New York, 15:00 London)" and note that local times may change with daylight saving.
Practical ways to avoid confusion
- Label the standard explicitly. Write "UTC" rather than leaving the time unmarked.
- Include a few local equivalents for the people most affected.
- Use a visual time zone tool to see multiple local times side by side. Zoneless, for example, presents comparisons such as London vs New York and San Francisco vs Tokyo, which lets you spot overlaps without doing the arithmetic yourself.
- Re-check before daylight saving transitions, since offsets change on different dates in different countries.
When not to use UTC
If your whole team is in one country and one time zone, local time is easier to read and less likely to be misread. UTC is most valuable when participants span regions, when a meeting recurs across a daylight saving boundary, or when you are coordinating with people whose local zone you are unsure of.
The rule of thumb: use UTC as the shared reference, and always show the local time for each participant so no one has to convert in their head.