City clock changed time rules? Fix your schedule

A conference time that looked right last month may now be an hour off. A city can change when daylight saving time starts or ends, or stop using it altogether. Your calendar, computer, and attendees may not all have the same updated time zone rules.

Use a date-aware world clock or calendar to check the meeting date in the city where it will take place. Then confirm the event is tied to the city’s time zone, not just to a fixed offset such as UTC-5. For more on comparing attendee locations, see how to choose a meeting time across three time zones.

Check the conference time

1. Write down the exact conference date, local start time, and city. A city name matters because nearby places can follow different rules.
2. Check that date in a date-aware world clock or calendar that lets you choose the city. Compare the displayed time with the schedule, not just with the city’s current time.
3. Check the time in at least one attendee’s location as well. Make sure you are comparing the same date, especially if the meeting is near a daylight saving transition.
4. Open the calendar event and look for a named city time zone, such as America/Los_Angeles or Europe/London. A fixed UTC offset does not automatically follow future rule changes.
5. Ask the organizer to confirm the intended local start time. If the event is wrong, update the event itself and send an updated invitation rather than asking each attendee to calculate a correction.

What the result means

The city time differs by one hour only on some dates

This often points to a daylight saving rule change or a date near the transition. Daylight saving time, often shortened to DST, is a seasonal clock change used in some places. The date and amount of the change are set by local rules, which can change. Confirm the specific conference date before changing the schedule.

The time is wrong by the same amount all year

The event may use the wrong city or a fixed offset instead of a city time zone. An offset describes a location’s difference from UTC at a particular moment. It does not tell a calendar how that difference may change later. Check the event’s time zone and city before editing the start time.

Your device and a world clock disagree

Your device may have outdated time zone data, or its time zone may be set manually to a different location. A browser world clock can also use its own time zone data. Compare another date-aware calendar or clock, then check for system and app updates before changing the invitation.

Different attendees see different local times

That can be correct. Attendees in different regions may observe seasonal clock changes on different dates, or not observe them at all. The event should keep the organizer’s intended local time in its named time zone, while each attendee’s calendar converts it for their location.

How to fix the schedule

1. Confirm the intended city and start time. Ask the conference host whether the time means local time at the venue or a specific time in the organizer’s location. Include the date and city when confirming.
2. Use a city time zone, not a UTC offset. In the calendar event, choose the named time zone for the conference city if the option is available. Avoid entering a time such as UTC-5 as a permanent substitute, because the city’s offset may change by date.
3. Update time zone information on your computer. On Windows 11, open Settings › Time & language › Date & time, check the time zone, and install available system updates. On macOS, open System Settings › General › Date & Time, check the time zone setting, and install available macOS updates. Automatic time zone settings can help keep your device aligned with your location, but they do not replace checking the conference city’s rules.
4. Check the calendar on your phone. On iPhone, open Settings › General › Date & Time. On Android, look under Settings › System › Date & time; some manufacturers place it under a different settings section. Turn on automatic date and time if it is appropriate for your device, then reopen the event.
5. Refresh the invitation for everyone. If you are the organizer, correct the date, time, and city time zone in the original event, then send the update. If you are an attendee, do not edit a copy of the meeting and assume others will see the change. Ask the organizer to resend the corrected invitation.
6. Recheck after updates. If your computer or calendar had old time zone data, check the event again after installing updates or restarting the calendar app. Compare the meeting date in two date-aware calendars if the time is important.

Why a future date can be the problem

Time zone rules are software data as well as local policy. A calendar uses that data to calculate the city’s offset on a particular date. If a government announces a rule change, your device or calendar may not reflect it until its time zone database is updated. This can make a future event appear wrong even when the invitation was created correctly.

Do not fix a future time by subtracting or adding an hour everywhere without checking the date. The change may apply only during part of the year, and attendees in other cities may have different transition dates. Keep the conference tied to its named city time zone, and confirm the final local start time with the organizer.