Why does my calendar invite show the wrong time?
Almost always a time zone problem — and the specific mechanism determines whether the fault is yours, the sender's, or the software's.
How calendar events store time. A well-formed event stores a moment in time plus a time zone, so each participant's software converts it to their own local time. Done correctly, everyone sees the right local time automatically.
Where it breaks:
The device time zone is wrong. If your computer or phone is set to the wrong zone — frequently after travel, or where automatic setting failed — every event shifts by the difference. Check this first, because it produces a consistent offset across all events, which is the diagnostic signature.
The event was created without a time zone, or as a "floating" time. Some systems and imports create events that simply say 14:00 with no zone, which then displays as 14:00 to everyone regardless of location — correct for the organiser and wrong for everybody else.
Daylight saving transitions. This is the subtle one. An event created before a clock change, for a date after it, can shift by an hour if the software stored an absolute offset rather than a named zone. Recurring meetings spanning a clock change are particularly prone, and the change happens on different dates in different countries — so a transatlantic recurring meeting is wrong for a couple of weeks twice a year.
Mismatched zones between organiser and system, where a calendar account is configured for one zone and the device for another.
Imported or forwarded invitations, where an invitation forwarded as text loses the structured data entirely.
Different calendar platforms interoperating, where the conversion is imperfect.
How to fix and avoid it:
Set devices to update time zone automatically, and verify after travel.
Create events in the organiser's own zone, and let software convert — do not manually adjust times, which double-corrects.
State the time zone in the event title or description for cross-border meetings. Redundant when everything works, and invaluable when it does not.
Re-send rather than edit a badly created invitation, since editing frequently preserves the fault.
Check the time on the accepted invitation, not on the original email.