When a local time occurs twice

The clock label repeats; the instant does not

When clocks move backward, part of the local day happens twice. In New York on 1 November 2026, 01:30 occurs first at UTC−04:00 and again at UTC−05:00. Both displays say 01:30 on the same date, but the corresponding instants are one hour apart.

Choose the occurrence you intend

The earlier choice refers to the first pass through the repeated interval. The later choice refers to the second. Neither choice is automatically more appropriate for a meeting. Ask which occurrence the organizer means, then select the matching offset. If the invitation gives a UTC time or an explicit numeric offset, use it to distinguish the two.

An ordinary 01:30 entry on a different date may have just one match. Keep the date and IANA identifier attached to the question. The repeated interval differs between zones, and some places do not have a change at all on the selected day.

Check the meeting’s end across the transition

Duration measures elapsed minutes. A ninety-minute event starting at the earlier New York 01:30 spans the clock rollback. The wall-clock labels may look surprising because the hour repeats inside the event. Read the end time and offset in the result rather than adding ninety to an isolated clock label.

A weekly series needs per-date resolution

Most occurrences of a weekly local-time instruction may be ordinary. The one landing in the repeated hour still needs an explicit decision. In the twelve-date preview, identify the affected row, choose earlier or later, and confirm what the other cities show. Unresolved ambiguity should keep the calendar download unavailable.

Carry the choice into the calendar file

A resolved UTC timestamp preserves the chosen instant. After importing, a calendar may display the event in another zone or in its own local zone. Compare the date, offset, and corresponding UTC instant if the hour looks unexpected. A screenshot containing only “01:30” is insufficient evidence of which occurrence was imported.