Check a meeting time in UTC for a conference schedule

A conference time written as 15:00 UTC may be clear to the organizer, but attendees need to know what that means where they are. A local conversion can also fall on the previous or next calendar day, and daylight saving time can change the offset.

Use the World Clock to compare UTC with the cities where people will join. Then check the event date and timezone before sharing the schedule, so everyone is looking at the same moment.

Check the UTC meeting time

1. Open the World Clock and show UTC alongside the cities or time zones used by attendees.
2. Write down the meeting's full date and time, including the UTC label. For example, January 15, 15:00 UTC is more precise than just 3 p.m.
3. Compare the UTC time with each attendee's local time for the meeting date. If the World Clock view lets you choose a date, use the actual conference date rather than today's date.
4. Check whether the local date changes. A time just after midnight UTC can fall on the previous calendar day in the Americas, or the following day farther east.
5. Put the UTC time and the local time zones in the schedule or invitation. Ask one attendee in each major region to confirm the displayed local time before sending it widely.

If the clock only shows current times, it is still useful for comparing zones, but today's offsets may not match those on a future conference date. Check the offset for the actual date using a calendar or the attendee's local scheduling settings. For more on why comparing clocks is safer than mental conversion, see Why a world clock is safer than time zone math.

What the result means

Every city shows the intended local time

The schedule is consistent: the local times correspond to one UTC instant. Keep the UTC time as the reference in the announcement, especially if participants may update their location or travel before the meeting.

A city shows the previous or next date

This can be correct. Time zones are not just different clock readings, they can also be on different calendar dates at the same instant. For example, 00:30 UTC on January 16 is 4:30 p.m. on January 15 in Los Angeles during standard time. Include the local date as well as the time so nobody joins a day early or late.

One city is an hour out

Daylight saving time is a likely cause. Different countries, and even regions within a country, change clocks on different dates. A city can be five hours behind UTC in one season and four hours behind in another. Use the offset that applies on the meeting date, not a conversion remembered from another month.

The UTC time is clear, but an invitation shows another hour

The invitation may have been created in a different time zone, or a device may have the wrong date or time-zone setting. Compare its event time zone with the schedule's stated UTC time before changing the meeting itself.

How to fix a time mismatch

1. Check the timezone label. Make sure the scheduled time is explicitly marked UTC, not just a city name such as London. Local city times can shift when daylight saving starts or ends.
2. Check the meeting date. Recheck the local conversion for the exact date. If the event is near a daylight-saving change, verify each region separately because the changeover dates may differ.
3. Correct the event's time zone. In your calendar or meeting invitation, set the event to UTC or select the intended local zone, then verify the resulting time before saving. Don't fix a calendar mismatch by moving the meeting an hour without checking which zone is wrong.
4. Check the device's time-zone setting. On Windows 11, open Settings › Time & language › Date & time and check the time zone and automatic time settings. On macOS, open System Settings › General › Date & Time and check the time zone. On iPhone, go to Settings › General › Date & Time. On Android, look under Settings › System › Date & time; the wording can vary by device.
5. Send one unambiguous schedule. State the date, time, and UTC label, then add local times for the main attendee regions if useful. If you update an invitation, tell attendees which version is correct.

Why the date matters as much as the time

UTC does not shift for daylight saving time. Local clocks do. This makes UTC a stable reference for a global event, but it does not mean every participant sees the same calendar date or hour. The safest schedule states one UTC date and time, and treats each local version as a conversion for that specific date.

For recurring meetings, recheck the local times after seasonal clock changes. A weekly event set to a fixed local time may move relative to UTC, while an event fixed in UTC may move by an hour for attendees whose region changes clocks.