Practical guide
P1D, PT24H and DTEND: Recurring Event Duration Across DST
P1D is a nominal calendar-day duration, while PT24H is twenty-four elapsed hours. For recurring events, DTEND preserves the master’s exact elapsed duration. Across New York’s November 2026 clock change, these choices produce different ends even when the first event looks similar.
Decide whether the end follows the local day or elapsed time
An event lasting “one day” can mean ending at the same local clock reading tomorrow or ending twenty-four elapsed hours after it starts. When the clock changes, those instructions can differ. A recurring event with a DTEND also carries a specific exact duration from its master instance.
RFC 5545 distinguishes nominal durations expressed in days or weeks from accurate durations expressed in hours, minutes and seconds. It also says recurring events with DTEND use the same exact duration for every generated instance, while DURATION supplies the same nominal duration. [1] [2]
Use one end mechanism in a VEVENT: DTEND and DURATION must not appear together. Choose the one that represents the actual activity instead of supplying both and expecting the calendar to decide. [3]
Establish the specific 2026 clock change
The example starts at 12:00 in America/New_York on Saturday October 31 2026 and repeats the following Saturday. NIST confirms that U.S. daylight saving time ends on November 1 2026 at 02:00 local time, when the clock repeats the 01:00 hour. [5]
October 31 noon uses UTC−04:00, so it is 16:00Z. November 1 noon uses UTC−05:00, so it is 17:00Z. The interval between those two noons is twenty-five elapsed hours. Neither start is inside a nonexistent or repeated early-morning time.
NIST describes national rules and exceptions; the worked example specifically uses New York. Do not apply its offsets to a location that does not observe that transition.
Compare the first event and the following week
On a narrow screen, swipe within this table to read the remaining columns.
| Start at local noon | DURATION:P1D end | DURATION:PT24H end | DTEND master duration:25 hours |
|---|---|---|---|
| 31 October 2026 | 1 November 12:00;25 elapsed hours | 1 November 11:00;24 elapsed hours | 1 November 12:00 |
| 7 November 2026 | 8 November 12:00;24 elapsed hours | 8 November 12:00;24 elapsed hours | 8 November 13:00 |
P1D advances one nominal calendar day, preserving the noon reading here; its actual elapsed length changes from 25 to 24 hours. PT24H always advances twenty-four elapsed hours, ending at 11:00 on the transition Sunday.
The DTEND master ends November 1 at 12:00, so its exact duration is 25 hours. The next generated Saturday start therefore ends Sunday November 8 at 13:00, even though that weekend has no clock change. A recurring DTEND is not automatically a daily noon-to-noon policy. [2]
Inspect three finite files with their zone definition
These are complete fictional calendar files for inspection and isolated practice. Identifiers and timestamps belong to the examples. No invitations or alarms are present. Keep your original export and use a separate test calendar before changing a live schedule; particular calendar-app import behavior has not been tested here.
Each file includes a VTIMEZONE with the March 8 and November 1 2026 transitions. It covers these finite October/November examples and is not a zone definition for indefinite future recurrence. RFC 5545 requires referenced zone information valid for all recurring instances. [4]
Download practice new york nominal p1d (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Recurrence Practice 1.0//EN
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:DAYLIGHT
DTSTART:20260308T020000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20261101T020000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:0bd1632165fb651b8a30f5ca@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART;TZID=America/New_York:20261031T120000
SUMMARY:Nominal one-day practice
RRULE:FREQ=WEEKLY;COUNT=2
DURATION:P1D
END:VEVENT
END:VCALENDARDownload practice new york accurate pt 24h (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Recurrence Practice 1.0//EN
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:DAYLIGHT
DTSTART:20260308T020000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20261101T020000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:09efa4cd3a47987c74e33c13@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART;TZID=America/New_York:20261031T120000
SUMMARY:Accurate 24-hour practice
RRULE:FREQ=WEEKLY;COUNT=2
DURATION:PT24H
END:VEVENT
END:VCALENDARDownload practice new york dtend exact duration (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Recurrence Practice 1.0//EN
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:DAYLIGHT
DTSTART:20260308T020000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20261101T020000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:3722ee33736c0423dca6f6cc@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART;TZID=America/New_York:20261031T120000
SUMMARY:Master exact-duration practice
RRULE:FREQ=WEEKLY;COUNT=2
DTEND;TZID=America/New_York:20261101T120000
END:VEVENT
END:VCALENDARVerify ends by converting to UTC
Read DTSTART, the named zone and the chosen end mechanism. For a DTEND master, convert both endpoints using their own dated offsets, subtract in UTC, then apply that exact elapsed duration to each generated start. For a nominal P1D, advance the local date and determine the new endpoint’s offset.
The examples were checked with explicit UTC-offset arithmetic, Python ZoneInfo and an independently parsed finite VTIMEZONE. The available tzdata package is 2026.3, using IANA 2026c. These computation checks establish the listed examples; they do not prove every application imports or displays the files identically.
If a real booking depends on local checkout rules, operating hours or a contractual definition of a day, obtain that policy before choosing the event duration. Inspect an ordinary week as well as the transition week; a single matching first end can hide the wrong recurring policy.
Two complete duration decisions
The first DTEND and P1D files both end at noon November 1. Are they equivalent recurring policies?
No. On November 8 the DTEND series ends at 13:00, while P1D ends at 12:00.
The DTEND master fixes 25 elapsed hours for later instances. P1D preserves a nominal day, which is 24 elapsed hours the following weekend. Agreement on the master instance is insufficient.
Why does PT24H end at 11:00 on November 1 rather than noon?
The clock-change weekend contains an extra elapsed hour between local noons.
October 31 noon is 16:00Z. Adding 24 hours gives November 1 16:00Z, which is 11:00 at UTC−05:00. Noon there is 17:00Z, twenty-five hours after the start.
Sources and further reading
- RFC 5545 §3.3.6Rule scope and exact example interpretation.
- RFC 5545 §3.8.5.3Rule scope and exact example interpretation.
- RFC 5545 §3.6.1Rule scope and exact example interpretation.
- RFC 5545 §3.6.5Rule scope and exact example interpretation.
- NIST — Daylight Saving Time RulesRule scope and exact example interpretation.