calendar invite showing wrong time: support explanation

TL;DR

A calendar invite almost never shows the wrong time because the time changed. It shows the wrong time because the organizer and the attendee are reading it in different timezones, or because one of them crossed a daylight-saving boundary. Every invite stores the event in UTC and renders it in the viewer's local zone. When it looks wrong, check which zone each side is viewing in before moving the meeting.

The query

calendar invite showing wrong time: support explanation

Use this when

• A user says a meeting shows up an hour off, or at 3am
• An invite looks right for the organizer and wrong for the attendee
• A recurring meeting shifted after a daylight-saving change
• You are writing help docs for a scheduling feature

Not for

• Building calendar integrations or sync engines
• Timezone library internals (IANA database, Olson files)
• Debugging server-side scheduling logic
• One-off typos where the organizer booked the wrong hour

Steps

1. Get the two concrete times

Ask the user what time they see and what time they expected, plus their current city or timezone. "Wrong" is vague. Two times and a zone turn it into a checkable fact.

Expected output: the seen time, the expected time, and the user's timezone.

2. Put the organizer zone next to the attendee zone

Most invites print the event's timezone on the invite. If the organizer in New York booked 3pm ET and the attendee is in London, 8pm local is correct behavior, not a bug. Lay the two zones side by side and do the arithmetic out loud for the user.

Expected output: organizer zone and attendee zone confirmed, math shown.

3. Rule out daylight saving

Events created before a DST change shift by an hour for zones that observe it. Ask whether the region recently moved clocks forward or back, and check recurring events especially: a series created in summer renders an hour off in winter for some calendars.

Expected output: a yes or no on DST involvement.

4. Check the all-day versus timed trap

An all-day event stored in the wrong zone renders as the previous or next day. Verify the event type and confirm the organizer meant all-day, not midnight-to-midnight in their zone.

Expected output: event type confirmed as all-day or timed.

5. Give the one-line explanation and the fix

Tell the user the time is correct in the organizer's zone and show them how to view the event in that zone, or have the organizer re-send with the zone printed clearly. Do not move the meeting.

Expected output: the user confirms the time is right once zones line up.

Template: the reply

Thanks for flagging this, [Name]. Your calendar stores every invite in UTC and shows it in your local zone, so this is almost always a timezone view, not a wrong time.

What I see: the organizer booked [time] in [organizer zone], which is [time] in your zone ([user zone]). That matches what you are seeing.

Quick check: did [region] recently change clocks for daylight saving? That shifts recurring meetings by an hour.

If the time still looks off after that, send me a screenshot of the invite's timezone line and I will dig in.

Variant phrasings

meeting shows at the wrong time on my calendar

Start at step 2. Zone mismatch is the cause nine times out of ten.

invite says 3am

Somebody booked across zones without checking. Steps 2 and 5.

calendar event an hour off after daylight saving

Step 3 first. Recurring series are the usual victims.

Why it happens

Calendars store one canonical time (UTC) and render it per viewer. That design is correct, but it means "wrong" is almost always "rendered for a different zone than the user expected." DST adds a second layer: the offset between two zones is not constant through the year. Travelers get a third layer when the laptop zone no longer matches the body zone.

Edge cases

• Recurring events spanning a DST change: some calendars pin the local time, some pin UTC. Know which yours does.
• External invites with no zone header: ask the organizer for their zone directly.
• Users who travel: their laptop zone and their calendar zone can disagree. Check both.
• All-day events for global teams: pick one reference zone and print it on the invite.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstQTVPoICgG2ZDeavUD72RA