A timezone-safe calendar invite is a small document, not a click. It has to survive a forward, a delegate, a DST weekend, and a person who joins from an airport in Singapore while the series was created in New York. Most invites fail that test because they store a feeling (“nine my time”) instead of an IANA name.
Title like a grown-up
Bad: `Weekly sync`. Better: `Weekly sync — NY 09:30 ET / London 14:30`. Best: `Weekly sync — 09:30 America/New_York / 14:30 Europe/London`.
Civil abbreviations (ET, BST) are friendly and lie twice a year. IANA names (`America/New_York`, `Europe/London`) do not lie. Put the friendly form in the title and the IANA form in the description. Link the pair page: New York–London.
If three cities attend, either split the meeting or name all three. A title that only lists HQ trains people to ignore everyone else.
Never float a human meeting
Floating events are for “take medicine at 09:00 wherever I woke up.” They are not for standups. If two people in Tokyo and Sydney receive a floating 09:00, they will join at different instants on the UTC timeline. You wanted a meeting. You created two meetings.
Google Calendar and Outlook will happily let you do this. Do not.
Description checklist
- IANA zone for every required city. - Link to city verdict pages for anyone who might be on-call adjacent: Tokyo, London. - DST note if the series crosses 8 March, 29 March, 5 April, 4 October, 25 October, or 1 November 2026. - Recording permission. - The actual agenda in five lines so late-night attendees can skip.
Recurrence is where invites go to die
Create the series in one zone. On the Monday after a DST change, *inspect* a future instance in each attendee’s local view. If London shifted by an hour relative to New York, recreate from that date. Do not drag a single instance; dragging teaches the series a private folklore.
All-day events for holidays should be timezone-aware all-day in the *local* zone of the holiday, not HQ’s all-day. US Thanksgiving as an all-day floating event marks the wrong UTC day for Australia.
Room for the third city
If Sydney is optional, mark them optional and do not require 22:00 local attendance. If they are required, the invite is not timezone-safe unless their local time is in the title and the slot is inside 09:00–18:00 there at least on rotating weeks.
A safe invite is boring: both times, both zones, no floating, DST hygiene, a link to the overlap map. Send that. Stop sending `Quick chat?` at 09:00 with no zone at all.
Mobile, delegates, and the forwarded disaster
Executives forward invites to assistants in a third zone. If the title has no civil times, the assistant will "fix" it to the exec's preference and break everyone else. If the description has IANA names, a careful assistant can save you.
Mobile lock screens show a single local time. That is fine if the event timezone is correct. It is fatal if someone created `09:00` floating. Test by adding yourself a second Google Calendar in `Asia/Tokyo` and viewing the same event. If the instant differs, you failed.
Video-link tools sometimes create a parallel event with a different zone. Decline the duplicate. One timeline per meeting.
For interviews, always include the candidate's city. A 09:00 ET interview sent to someone in Sydney without AEDT in the title is how you lose a hire to a company that can tell time.
Paste this footer: "If this instance sits within 7 days of a DST change (US 8 Mar / 1 Nov 2026, EU 29 Mar / 25 Oct, AU 5 Apr / 4 Oct), verify both local times on the pair page before joining."
Field notes from the city desk
Treat New York as a place, not a resource pool. FiDi keeps 09:00–18:00 as the honest window. Slack after 19:00 is usually parked until the morning subway ride. A calendar title that omits America/New_York is how this city gets pinged in the dark.
In London, start from the City / Shoreditch. Sorry-culture is real: a 19:00 Slack gets a next-morning reply and a faint wince. The local prior remains 09:00–18:00 (Europe/London). If this article's advice conflicts with that desk, the desk wins — ask once and write it down.
Treat Tokyo as a place, not a resource pool. Marunouchi keeps 09:00–18:00 as the honest window. Nine-to-six on paper, later in practice. After 21:00 a Slack ping can feel like a fire alarm; Golden Week is a blackout. A calendar title that omits Asia/Tokyo is how this city gets pinged in the dark.
Treat Sydney as a place, not a resource pool. the CBD / Barangaroo keeps 09:00–17:00 as the honest window. AEDT in summer, AEST in winter. US calls eat breakfast or dinner — never lunch. After 18:00 a ping is tomorrow. A calendar title that omits Australia/Sydney is how this city gets pinged in the dark.
None of these notes replace the live verdict. Open the city page at send time. Clocks and holidays move; this paragraph does not.