Practical guide

THISANDFUTURE: Shift a Recurring Series Without Losing Exceptions

RANGE=THISANDFUTURE shifts the identified and later original recurrence instances by the same time difference. “Later” follows original RECURRENCE-ID values, and separately defined exceptions are not shifted by the range change. Audit identity, current time and duration in separate columns.

Readers inspecting recurrence exports and constructing a finite calendar schedule. · 7 minute read · Published

Choose the actual scope of the change

A single RECURRENCE-ID exception changes one original occurrence. Adding RANGE=THISANDFUTURE broadens that change to the identified occurrence and subsequent instances. It is not merely a label saying that the replacement start is later. [1]

RFC 5545 defines subsequent instances by their original RECURRENCE-ID values rather than their currently scheduled start times. It also says that subsequent instances defined in separate components are not impacted by the range parameter. [1]

This distinction matters when one later meeting was already moved to an earlier displayed date. Keep original identity, replacement start and replacement end separate before deciding which events a future range should alter.

Audit a range change beside a separate exception

On a narrow screen, swipe within this table to read the remaining columns.

Original four-meeting UTC series with two changes
Original identityCurrent startCurrent endReason
5 January 14:00Z5 January 14:00Z5 January 15:00ZBefore range:60 minutes
12 January 14:00Z12 January 16:00Z12 January 17:30ZRange:+2 hours,90 minutes
19 January 14:00Z10 January 16:00Z10 January 17:00ZSeparate exception:60 minutes
26 January 14:00Z26 January 16:00Z26 January 17:30ZLater original instance:range applies

The January 19 identity is displayed on January 10 because of its separate component. That component is retained without the range’s two-hour shift or 90-minute duration. The ordinary January 26 instance receives the range change.

The range instance itself moved from 14:00 to 16:00, so its delta is plus two hours. RFC 5545 applies that same difference to subsequent affected instances. If its duration changes, the affected subsequent instances receive the same changed duration. [1]

Identity before displayed order; complete values are in the adjacent worked table.
Identity before displayed order. Original explanatory diagram; use the complete table for every dated result.

Read one snapshot containing the master and both exceptions

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.

Download practice thisandfuture with separate exception (.ics)

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Recurrence Practice 1.0//EN
BEGIN:VEVENT
UID:practice-future-range-971dfa60@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART:20270105T140000Z
DTEND:20270105T150000Z
SUMMARY:Original four-meeting series
RRULE:FREQ=WEEKLY;COUNT=4
SEQUENCE:1
END:VEVENT
BEGIN:VEVENT
UID:practice-future-range-971dfa60@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART:20270112T160000Z
DTEND:20270112T173000Z
SUMMARY:Future range changed
SEQUENCE:1
RECURRENCE-ID;RANGE=THISANDFUTURE:20270112T140000Z
END:VEVENT
BEGIN:VEVENT
UID:practice-future-range-971dfa60@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART:20270110T160000Z
DTEND:20270110T170000Z
SUMMARY:Separate moved exception
SEQUENCE:1
RECURRENCE-ID:20270119T140000Z
END:VEVENT
END:VCALENDAR

All three components share the same UID. The range component retains the original January 12 14:00Z RECURRENCE-ID, and the single exception retains January 19 14:00Z. Their DTSTART values state the replacement times. These illustrative SEQUENCE=1 values are not evidence of a sent scheduling update or attendee notification. [2]

Do not use displayed order to choose future identities

The visible order is January 5, January 10, January 12 and January 26. The original identity order is January 5, January 12, January 19 and January 26. A rule that walks only the displayed list loses the fact that January 10 is the moved January 19 identity.

For each exported component, record UID, SEQUENCE, RECURRENCE-ID, DTSTART and the end or duration. Use the original identity to relate an exception to the master, then apply the documented range and separate-exception rules. A shared UID is expected for these related components; it is not sufficient evidence of accidental duplication. [3]

Recognize a future change that needs a different model

Suppose a master meets Mondays and Wednesdays, but only future Mondays should move to Tuesday. A broad THISANDFUTURE change shifts affected subsequent instances, including ordinary Wednesday instances; it does not filter the future by the weekday you intended to edit.

RFC 5545 discusses this complex pattern limitation and suggests truncating the original series and creating appropriate new recurring components for the changed future schedules. [1]

For a live calendar, use the service’s supported series editor and check the resulting split, identities and existing exceptions. This article explains a complete finite file snapshot, not a guaranteed synchronization protocol. Preserve a before-export and verify unaffected neighboring meetings before accepting the change.

Two complete range decisions

The January 19 meeting appears on January 10. Should its time be shifted because it is part of the later original series?

Its separate exception is retained without this range shift.

Later identities are determined from original RECURRENCE-ID values, but RFC 5545 separately excludes instances defined in separate components from the RANGE effect. This instance keeps its explicit January 10 16:00–17:00Z interval.

I want only future Mondays changed in a Monday/Wednesday series. Is THISANDFUTURE enough?

No. A broad future range is not a future-Monday-only filter.

The standard’s complex-pattern example calls for deliberately truncating and creating appropriate new recurring components. Verify the new schedules and preserved exceptions using the calendar’s supported workflow.

Sources and further reading

  1. RFC 5545 §3.8.4.4Rule scope and exact example interpretation.
  2. RFC 5545 §3.8.7.4Rule scope and exact example interpretation.
  3. RFC 5545 §3.8.4.7Rule scope and exact example interpretation.
  4. RFC 5545 §3.8.5.3Rule scope and exact example interpretation.