Practical security for everyday technology.

Check the time zone before accepting a shared calendar invitation

A person comparing calendar screens on a laptop and phone in a home office, no readable private details.
AI-generated photographic illustration; not documentary photography.

A meeting invitation says 10:00, but your calendar displays 11:00. Before changing the event, check whether the two views are showing the same instant in different time zones. Manually “correcting” a valid conversion can create the very error you were trying to fix.

Microsoft’s Outlook time-zone guide explains the calendar’s display settings. Other calendar products have their own controls, so use the help for the application and version you actually use.

Inspect the event and the display separately

Open the event details and note the named time zone attached to its start. Then check the time zone used by your calendar or device. A city’s current UTC offset is not always its offset on a future date because seasonal clock changes may intervene.

For a recurring event, inspect an occurrence on the relevant date rather than assuming today’s time difference applies throughout the series. Different regions may change clocks on different dates or not change them at all.

Confirm one concrete occurrence

If the invitation remains ambiguous, send the organiser the date, the named zone and the time your calendar shows. Ask them to confirm the intended occurrence. “Thursday at 10 in your time” is less useful than a complete date and a recognised time-zone name.

Do not create a second event as a workaround without tracking which one is authoritative. Duplicate reminders can survive after the original meeting is updated.

After a correction, check the invitation again on the device you will use that day. Travelling can change a device’s display zone while the event still represents the same instant.

A reliable calendar habit is to preserve the event’s intended time zone and verify the local display, rather than repeatedly moving the appointment until one screenshot looks familiar.