Canada · calendar time observatoryPinned IANA 2026e · Oct 2026—Feb 2027

Calendar time, explained

All-day dates and recurring meetings need different checks

An ICS file is not just a list of timestamps. Date-only events, recurrence rules and exceptions carry relationships that an hour shift can destroy.

An all-day event is a date, not midnight UTC

DTSTART;VALUE=DATE:20261104
DTEND;VALUE=DATE:20261105

This example covers November 4. The end date is exclusive: November 5 marks the boundary after the event. The checker reports one calendar day and does not convert either date to an hourly timezone value. A two-day event would use November 6 as the exclusive end.

If another system turns a date-only value into midnight and then shifts it between zones, the displayed date can move. The right first question is whether the original value was a DATE or a DATE-TIME. Adding an hour to an all-day event does not answer that question.

A recurring DTSTART is only the start of a series

DTSTART;TZID=America/Vancouver:20261028T090000
RRULE:FREQ=WEEKLY;COUNT=4

The stored start is before November 1. A correct mapping of October 28 does not prove that the November occurrences will be correct. Different timezone definitions may agree in October and diverge later. ClockShift deliberately reports the stored start and flags the recurrence instead of presenting four invented verified results.

To test the series, inspect actual occurrences on both sides of the transition in the source application. Export representative instances when the application supports it. Record whether you changed one occurrence, following occurrences or the entire series; those operations have different consequences.

An exception is connected to its original slot

RECURRENCE-ID;TZID=America/Vancouver:20261104T090000
DTSTART;TZID=America/Vancouver:20261104T100000

This fictional exception moves one occurrence from its original 09:00 slot to 10:00. The recurrence identifier still describes the slot being replaced. Treating those two fields as interchangeable can disconnect the exception from its series.

EXDATE properties exclude occurrences. RDATE properties add dates. The checker detects their presence but does not reconstruct a complete occurrence list. It also does not validate attendee responses, conference links or room bookings. Keep an original export and compare those relationships in the application before replacing a series.

Reproduce the difference safely

  1. In the file checker, load “Series with an exception.”
  2. The October 28 stored start should match the pinned reference. The November 4 exception uses the old embedded rule and differs by 60 minutes.
  3. Notice the two components and the recurrence flags. Two components are not proof that the series has only two occurrences.
  4. Use the round-trip workflow for a fictional series before changing a real schedule.

Standards reference: VEVENT and exclusive end semantics, and RECURRENCE-ID. The test-case page lists the evaluator’s exact limits.

Two invitations say 17:00. They do not mean the same thing.

These original fictional files differ in one important start-time character. The fixed-instant file contains DTSTART:20261104T170000Z. The floating-time file contains DTSTART:20261104T170000, with no TZID. Both last thirty minutes and contain no attendees or meeting link.

The first names 17:00 UTC. Displaying that instant at UTC−07 gives 10:00; displaying it at UTC+02 gives 19:00. Those clock readings disagree by nine hours while still referring to the same moment. The second records a floating wall time. It does not name one universal instant that this checker can recover by guessing a city.

RFC 5545’s DATE-TIME forms distinguish UTC, local time with a timezone reference and floating time. A missing suffix is not permission to assume that the sender meant UTC.

Inspect the original before “correcting” the hour.

  1. Download each fictional file and open it in the local file checker. Keep them separate so the result belongs to one component.
  2. For the fixed-instant file, change the display zone. The stored UTC instant must remain 17:00 even though its displayed wall time changes.
  3. For the floating file, read the classification and advice. The missing timezone is an unresolved meaning, not an automatic one-hour error.
  4. Ask which promise the organizer intended: the same instant for all attendees, or the same local clock reading wherever the person is. Do not choose a promise solely because it matches your current display.

Preserve identity as well as time.

If this were an existing invitation, changing its time in a personal copy would not establish that the organizer, room and other attendees received an update. Keep the original UID, source application and update history available for comparison. The two downloadable teaching files deliberately use different UIDs so they can be inspected independently; they are not a cancellation and replacement sequence.

After a source-side correction, compare the new export’s time representation and actual application display. A time that looks right on one device can still be stored under the wrong meaning. For a recurring meeting, repeat the check at more than one occurrence; this one-off pair does not test recurrence expansion.