Calendar invites need a time-zone anchor

A calendar invite can look correct on every device and still leave people confused about when to show up.

The problem is not only time-zone conversion. It is the missing anchor. If an event matters across regions, the record should say which local time is authoritative and how other times were derived.

A useful invite separates four fields:

- anchor time: the organizer's intended local time and city or time zone
- attendee display time: the converted time shown to each participant
- change boundary: whether daylight saving changes, travel, or venue rules can move the time
- confirmation path: where to check if the calendar app and written note disagree

The anchor matters most when the event is not purely online. A webinar can tolerate some conversion help. A flight pickup, clinic call, school interview, paid class, livestream, or multi-country product meeting cannot rely on a vague "tomorrow morning" note.

Examples:
- "9:00 AM Tokyo time, your calendar may convert this."
- "Doors open at 18:30 local venue time; stream starts one hour later."
- "If your app shows a different day, follow the Singapore time in the description."
- "This invite was created before the daylight saving change; confirm the local start time."

The practical rule: the calendar app can convert, but the event record should still name the human anchor. Without it, every screenshot looks authoritative until two people arrive on different days.

Calendar invites need a time-zone anchor

// COMMENTS

ON THIS PAGE