How to check a meeting time in UTC for an online event

Planning a live online event for people in different countries? A time that looks clear to you can land on a different date for an attendee, or shift by an hour when daylight saving time changes.

Start with one time in UTC, then check what it means in each attendee’s city on the event date. The World Clock can help you compare local times without doing offset math for every person.

Check the UTC time for your event

1. Open the World Clock and use it to compare UTC with the cities where attendees will join.
2. Write down the event’s full date and time in UTC. Include the date, not just the hour, and label it clearly, for example, October 8, 6:00 PM UTC.
3. Check the event date in every attendee’s city. Confirm both the local clock time and the local calendar date.
4. Repeat the comparison for any other important time, such as a rehearsal, registration deadline, or recording release. A separate check prevents a time copied from another date from carrying the wrong offset.
5. Put the UTC time and the confirmed local time in the event notice. If you use a calendar invitation, set its time zone to UTC so the calendar can display the event in each guest’s local zone.

For example, at 6:00 PM UTC, New York is 1:00 PM when it is on standard time and 2:00 PM when it is on daylight time. London is 6:00 PM on standard time and 7:00 PM on daylight time. The UTC time stays the same, but local offsets depend on the date.

Choose how to show the event time

Use UTC as the primary time

UTC is a useful reference when attendees are spread across countries. It does not switch for daylight saving time, so an event set for 6:00 PM UTC remains at 6:00 PM UTC throughout the year. Include the date and the letters UTC to make the reference unambiguous.

Include local times for key attendees

For a small group, list the local time beside the UTC time, such as 6:00 PM UTC, 2:00 PM New York, 7:00 PM London. Check those conversions for the event date, not for today. Local time zones can change their offset on different dates, and some locations do not observe daylight saving time.

Send a calendar invitation

A calendar invitation can show each guest the event in their own time zone. Enter the event in UTC or select UTC as its time zone, then verify the displayed date and time before sending. Keep the UTC reference in the event description as a fallback for anyone whose calendar is configured incorrectly.

What a time mismatch means

The local hour differs by one hour

The city may be observing daylight saving time, or you may have compared dates on opposite sides of a clock change. Recheck the city’s offset on the event date. Do not assume a city always uses the same UTC offset year-round.

The local date is the day before or after

This is normal when the event is near midnight UTC. For example, an early-morning UTC event can fall on the previous evening in a city west of UTC. Put the local date in the announcement, not just the local hour, so attendees do not join on the wrong day.

Two cities show the same time now but not on the event date

The cities may change clocks on different dates, or only one may observe daylight saving time. A current clock comparison is not enough for a future event. Compare against the date you plan to meet.

The calendar invitation looks different from your announcement

Check the invitation’s selected time zone and event date. A calendar set to a different zone can display the same instant as another local time. If the UTC reference is correct, do not change the actual event to make one person’s display match. Correct the invitation’s zone or explain the local conversion.

Fix common UTC scheduling mistakes

1. Include the time zone label. Write 6:00 PM UTC, not just 6:00 PM. Avoid using a bare abbreviation such as EST as a universal label, because local abbreviations and daylight-saving rules can be confusing.
2. Check the full date. Confirm the year, month, day, and time before converting. An event at 12:30 AM UTC may be on the previous local date for some attendees.
3. Use a named city, not a remembered offset. A fixed offset like UTC-5 may not describe New York on the event date. Check the actual city and date in the World Clock.
4. Keep recurring events tied to a time zone. If a weekly session must stay at the same local time, set the recurring calendar event to the host’s local time zone. If it must always begin at the same UTC time, set it in UTC and tell attendees their local start time may shift seasonally.
5. Ask one attendee to verify the invitation. Have someone in another time zone confirm the date and time shown in their calendar. This catches a wrong zone or a missed date change before the event begins.

For a one-time event, publish the UTC reference and a date-checked local time for each main audience. For a recurring event, state whether the meeting stays fixed in UTC or fixed to the host’s local clock.