AI made a calendar file. Does 9 a.m. mean the same instant for everyone?

For a shared meeting, give AI a date and time zone and verify the exported start and end. A time without a zone can mean local clock time wherever it is read.

Decide whether you mean a shared instant or the same clock time in each place. RFC 5545 calls an iCalendar date-time without a UTC suffix or time-zone reference “floating”. That can be appropriate for a personal routine but unsuitable for a shared meeting at one fixed instant.

Check one unambiguous example

Our fictional one-off meeting starts October 15, 2026 at 09:00 with a supplied UTC+09:00 offset and lasts 30 minutes. Subtracting nine hours gives 00:00 UTC. We checked the arithmetic and produced DTSTART:20261015T000000Z and DTEND:20261015T003000Z.

A missing Z changes the meaning

DTSTART:20261015T090000 without a time-zone reference is floating time under the standard. It does not encode our example’s shared instant. The Z in the tested UTC values matters; adding a human-readable zone name to the event title does not fix the date-time field.

Give AI the decision instead of an ambiguous time

Suggested input: “Create a one-off event for this date, explicit offset and duration. Encode the shared instant in UTC, show the conversion and preserve the end time. Ask if the zone or date is missing.” For recurring meetings, use the intended time-zone rules rather than assuming one fixed offset covers every date.

Preview before adding or sending

Our recommendation is to import into a temporary calendar and check the displayed start, end and date in the intended time zones before sharing. This guide does not provide a complete calendar file; the two property lines illustrate the timing only.

Published October 14, 2026. We tested the fictional fixed-offset conversion and exported property strings locally. No calendar app import, invitation delivery, recurring event or AI service was tested.

Sources: IETF · iCalendar.