Why Your Calendar Event Is One Hour Off

Before moving an event that is one hour off, compare the original provider's website with the receiving calendar and device. The event may represent the correct instant while one app displays the wrong local time. If only one occurrence of a series differs, check the cities' daylight-saving dates too.

The event's original time

Open the calendar provider's website and inspect the event there. Check the date, start and end times, time-zone label, and whether it repeats.

For a meeting invitation, compare the organizer's original details. For a timetable or shift schedule, check the official source. A copied description saying “10 AM” may be old text even when the event time has changed.

Write down the expected date, time, and city, such as “10 AM London time on November 10.” Include the city when comparing devices in different locations.

If the source is correct but the destination is wrong, keep the source unchanged while investigating the connection.

The calendar's display time zone

In Google Calendar on a computer, open Settings → General → Time zone and inspect the primary zone. You can also inspect an event's own zone in its editing options. Google's time zone guide explains how events display in the viewer's local time.

In Outlook on the web or new Outlook, inspect Settings → Calendar → View → Time zones. Classic Outlook uses File → Options → Calendar. Follow the tab for your version in Microsoft's time zone guide.

Choose a city-based zone (such as London or New York) rather than a fixed offset like UTC+1, because a city zone follows that place's clock changes.

Add multiple time-zone scales in Google or Outlook for side-by-side reference.

Device settings and time-zone updates

Confirm the computer or phone has the correct date, time, and location-based time-zone setting. An app may use its own calendar setting, the device's zone, or a time-zone override.

Install pending operating-system and calendar-app updates. Time-zone rules can change, and older software may still use the old ones.

If the website is correct and only the phone is wrong, compare phone events with the web account before changing the appointment for everyone.

Different clock-change dates

Different countries do not always change clocks on the same date. A call between London and New York can temporarily have a different local-time gap even when the meeting correctly stays fixed to its organizer's city.

The UK publishes its dates on GOV.UK, while NIST describes US daylight-saving rules.

For a repeating meeting, check dates before and after each location's clock change. Decide which local time anchors the recurring series before shifting it for a transition week.

Inspect copied events and feeds

If only a copied event is wrong, compare its source and destination on their websites. Inspect whether the source uses a named zone, a fixed offset, or floating time with no zone.

An ICS feed can contain a publisher error or stale time-zone information. Ask the publisher to correct it; the subscription is read-only. A delayed feed refresh can make an already corrected appointment appear unchanged.

For an Avum-managed copy, inspect the source selected in its Sync Rule and compare the same date in the destination. The combined calendar view shows connected accounts together; inspect the event itself to find the zone that defines it.

Once you confirm the original event really is wrong, correct it at the source using the right occurrence or series scope. Then check the destination and notify guests through the provider's supported update flow if needed.

Ready to keep event times aligned across your calendars? Start your free 30-day trial with Avum today.