Announcing an online event so nobody arrives an hour late

Almost every online event that goes wrong on timing goes wrong the same way: the announcement gives one local time, in the organiser's zone, with no date-safe anchor, and a slice of the audience does the conversion wrong or does it against the wrong date. The fix is not more explanation. It is publishing a moment that each reader's own device can translate for them.

Give the instant, then the readings

An instant is a single point in time that every clock on Earth agrees on. Expressed in UTC, it is unambiguous by construction. Lead with it, then give two or three local readings for your main audiences, and mark any that fall on a different calendar date:

Thursday 16:00 UTC (18:00 Berlin, 12:00 New York, 01:00 Friday in Tokyo).

That last parenthesis is the part people leave out and the part that causes the most confusion. For anyone far enough east, your Thursday event is a Friday event, and every later reference to "Thursday's session" is then wrong for them.

Link something that converts itself

Written readings help, but they age and they only cover the cities you thought of. A link that shows the event in the reader's own local time covers everyone and needs no maintenance. That is what the event time announcer is for: you set the moment once, name the event, and share a link that each visitor sees in their own zone, with the date adjusted where it needs to be.

Send a calendar invitation as well as a message

A calendar file carries the time zone with it, so the recipient's software does the conversion and keeps doing it if either side later changes its clocks. A message in a chat channel does not. For anything with a real audience, publish both: the invitation for people who will add it to a calendar, the written readings for people who are deciding whether to bother.

Watch the changeover weeks

If your event is more than a few weeks out, check whether it falls near a daylight saving transition in any of your main markets. An event announced in September for late October can be an hour off for North America, Europe or both, depending on which side has already changed. Anchoring in UTC protects the instant, but your written local readings still need to be computed for the event's date rather than today's.

A checklist worth keeping

• State the instant in UTC.
• Give two or three local readings, with the date marked where it differs.
• Include a self-converting link for everyone you did not list.
• Attach a calendar invitation with a real time zone, not a floating time.
• Recompute the local readings if the event is near a clock change.
• Repeat the instant in the reminder, not just "starting in one hour".

None of this is difficult, and it removes an entire category of avoidable absence. People who miss an event because of a botched time conversion rarely come back for the next one.