How to write a meeting invite that survives every time zone

Why plain text fails

An email saying "let's meet Tuesday at 3pm" carries no zone. The sender means their own; the reader assumes theirs. Between London and New York that is a five-hour error, and between London and Los Angeles an eight-hour one — comfortably enough to miss the meeting entirely.

Calendar software solves this properly. It stores an absolute instant plus the organiser's zone, then renders it in each attendee's own zone. Nothing is interpreted twice.

The five-point invite

1. Send an actual calendar invitation. Not a message describing a time.
2. Set the organiser time zone explicitly. Most clients default to your device zone, which is usually right — but check it if you are travelling.
3. Put the city in the title for the widest audience. "Q3 review (9am New York)" gives everyone an anchor even in a screenshot.
4. Include a joining link, not a dial-in ritual. Late joiners lose more time to access than to arithmetic.
5. Add an agenda line. If the overlap is one hour, protecting it matters more than the invite mechanics.

Recurring series need one extra check

Create the series once and let it recur. The failure mode is a well-meaning person deleting and re-creating it each quarter, typing the clock time from memory — which quietly re-anchors it to whatever season they are in.

Attendees in fixed-offset countries

If anyone on the invite sits in a country that does not change clocks — India, Japan, most of the Gulf, Arizona within the US — the gap to your zone moves twice a year even though your local time does not. The calendar handles it, but the human impact is real: a call that was comfortable for them in January can land an hour into their evening in April. Worth a check each spring.

The one-line rule

Never let a time exist only as text. If the only record of a meeting is a sentence in an email, the meeting has no time zone, and somebody will get it wrong.

What each calendar client actually stores

All three major clients store the same thing underneath — an instant plus a zone reference — but they expose it differently, which is where habits diverge.

Floating events, and when you want them

A floating event has no zone at all: 09:00 means 09:00 wherever you are. That is right for a daily habit — a workout, a medication reminder — and wrong for anything involving another person. If a colleague is expected, the event needs a zone.

Handling an attendee who travels

Someone flying between regions will see the meeting re-render on landing, which is correct but disorienting mid-trip. Two things help: enable a secondary home zone in their calendar view, and avoid moving a recurring series purely because one attendee is temporarily elsewhere. Move the exception, not the series.

A checklist worth keeping

1. Invitation sent from a calendar, not described in a message.
2. Organiser zone visible and correct on the event.
3. City name in the title for anything with more than three attendees.
4. Recurring series created once, never re-typed.
5. A reminder in March and October to re-check standing cross-region invites.

None of this is difficult. It fails because it is invisible — an invite with the wrong zone looks exactly like one with the right zone until somebody joins an empty call.