Practical guide

Move One Recurring Event: Keep Its Original RECURRENCE-ID

To move one occurrence, keep the series UID and use RECURRENCE-ID for its original scheduled start. Put the replacement start in DTSTART. The new date is not the identity of the occurrence you are replacing.

Calendar users checking event rules and practical date choices · 5 minute read · Published

Keep identity and current start separate

A series UID identifies the recurring component; RECURRENCE-ID identifies a particular original occurrence. Its value remains the original DTSTART for that occurrence even when the event moves. The exception’s DTSTART states where it now belongs. RFC 5545 explicitly illustrates a Friday occurrence moved to Thursday while retaining Friday as its recurrence identity. [1]

This is useful when an exported file shows two components sharing a UID. A master plus a single-occurrence exception is not automatically a duplicate. It may represent one schedule and one changed instance. Inspect RECURRENCE-ID before deleting either component. [2]

Map the original occurrence to its replacement

The fictional master meets on January 5, 12 and 19, 2027 from 14:00–15:00Z. Only the January 12 meeting moves to January 13 at 16:00–17:00Z. Its RECURRENCE-ID is still January 12 at 14:00Z; the January 5 and 19 instances remain unchanged.

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

Original three-occurrence UTC series with one moved meeting
Original identityCurrent scheduled startWhat changes
5 January 14:00Z5 January 14:00ZNothing
12 January 14:00Z13 January 16:00ZOne occurrence
19 January 14:00Z19 January 14:00ZNothing

The identity-to-start mapping is the central check. A second independent UID describes another event rather than clearly identifying the replaced occurrence. Whether a particular import route actually applies the exception needs an application-specific test.

Inspect the master and exception together

This is one complete fictional calendar object with two VEVENT components. The exception has no RRULE: it changes one occurrence. Both timestamps are illustrative. The file is a single snapshot for reading and isolated testing, not a tested scheduling update sent to attendees.

Download practice move one occurrence (.ics)

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Fictional Examples 1.0//EN
BEGIN:VEVENT
UID:practice-moved-occurrence-6d53c1be@daymooncalendar.com
DTSTAMP:20261108T000000Z
DTSTART:20270105T140000Z
DTEND:20270105T150000Z
SUMMARY:Practice - Original weekly practice
RRULE:FREQ=WEEKLY;COUNT=3
END:VEVENT
BEGIN:VEVENT
UID:practice-moved-occurrence-6d53c1be@daymooncalendar.com
DTSTAMP:20261108T000000Z
RECURRENCE-ID:20270112T140000Z
DTSTART:20270113T160000Z
DTEND:20270113T170000Z
SUMMARY:Practice - Moved occurrence
END:VEVENT
END:VCALENDAR

Read the exception’s three fields together: the same UID, original January 12 RECURRENCE-ID and new January 13 DTSTART. The displayed end also changes to January 13 at 17:00Z. Leaving the original January 12 DTEND behind would describe the replacement interval incorrectly.

Keep the changed occurrence’s type and scope correct

RECURRENCE-ID must match the recurring start’s value type. For an all-day series, use RECURRENCE-ID;VALUE=DATE with the original date. A DATE is not replaced by a midnight UTC timestamp. For a named-zone series, preserve the relevant local-time representation and zone reference; these UTC specimens deliberately avoid a missing zone definition. [1]

RANGE=THISANDFUTURE is a different scope. Under the standard it shifts the identified and subsequent occurrences by the same time difference, subject to its stated exception rules. It does not mean “only this event.” Do not add RANGE just because the replacement is later than the original time.

A complex pattern may need a deliberate split into future series instead of a broad range change. That task is outside this single-occurrence example; avoid editing every future event when only one meeting changed.

Use the supported editor for a real shared calendar

Save an original export and note the intended original occurrence. In the app’s supported event editor, choose the option explicitly scoped to that occurrence. Re-export if available and compare the identity, new start/end and unaffected neighboring dates. A file import, server sync and attendee scheduling message can have different update behavior.

The UID/RECURRENCE-ID fields explain identity; they do not by themselves prove that a second import overwrites existing events or notifies guests. The existing duplicate-import guide covers that separate workflow. Keep shared-calendar revisions and permissions within the actual service’s documented controls.

Two complete decisions

The meeting moved to January 13. Should RECURRENCE-ID become January 13 too?

No. Keep January 12 at 14:00Z as the original occurrence identity.

DTSTART becomes January 13 at 16:00Z. RECURRENCE-ID continues to identify which generated January 12 instance is changed. Using the new date as the identity no longer points at the original instance in this master series.

Two components have one UID. Can I delete the second as a duplicate?

Check for a matching RECURRENCE-ID first.

In this file the second component is the single January 12 exception. Removing it loses the moved-start information and leaves only the master’s original weekly pattern. A same-UID component is not enough evidence of an accidental duplicate.

Check both neighbors as well as the moved date

The expected final starts are January 5 at 14:00Z, January 13 at 16:00Z and January 19 at 14:00Z. Compare the actual application result with that mapping in a test calendar. If the original January 12 and the replacement both appear, retain the source files and diagnose import support or identity handling before repeatedly importing or deleting the full series.

Sources and further reading

  1. RFC 5545 §3.8.4.4 — RECURRENCE-IDOriginal identity, matching type and single versus THISANDFUTURE scope.
  2. RFC 5545 §3.8.4.7 — UIDPersistent series identity and correlation with individual recurrence instances.
  3. RFC 5545 §3.8.5.3 — Recurrence setMatching DTSTART, generated instances and exception duration.