Practical guide
RDATE and EXDATE: Add, Remove and Deduplicate Recurring Dates
Build a recurring event’s final date list by combining its rule dates and RDATE additions, deduplicating them, then removing EXDATE values. An excluded date does not return because it also appears in RDATE, and an excluded first start still supplies the original series anchor.
Reconstruct the set before editing the calendar
A calendar export can contain one recurring event with three different lists of dates. RRULE generates its regular pattern. RDATE adds specifically named starts. EXDATE excludes specifically named starts. Read them together rather than interpreting each property as another independent meeting. [1]
The final inclusion set is the union of DTSTART, the rule’s generated starts and the RDATE starts. Duplicate starts become one occurrence. EXDATE is applied to that union and takes precedence over both the rule and explicit additions. [2]
This is useful when a makeup date disappears, an extra date looks duplicated in the file, or the first displayed occurrence is later than DTSTART. It does not establish how a second import updates an existing calendar. That separate workflow belongs in the import guide.
Work through an addition that is also excluded
On a narrow screen, swipe within this table to read the remaining columns.
| Input stage | Starts at 14:00Z | What this stage changes |
|---|---|---|
| DTSTART and COUNT=4 weekly rule | 5, 12, 19, 26 January 2027 | Four generated starts |
| RDATE additions | 12 January; 2 February | 12 January already exists |
| Deduplicated union | 5, 12, 19, 26 January; 2 February | Five distinct starts |
| EXDATE removals | 5 and 12 January | Both removed from union |
| Final event set | 19, 26 January; 2 February | Three distinct starts |
The January 12 RDATE does not defeat the January 12 EXDATE. Exclusions win after all inclusions are collected. February 2 survives even though the four-occurrence RRULE ended in January: it was explicitly added, rather than generated by an extended count. [2]
COUNT has not been changed to three. Its original four rule starts were generated first; the union and subtraction explain the final three visible occurrences. A remaining-occurrence target is a scheduling policy that must be expressed deliberately.
Inspect one complete file with all three properties
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 rdate exdate set audit (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Recurrence Practice 1.0//EN
BEGIN:VEVENT
UID:15e1956b8c0703633f2153cc@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART:20270105T140000Z
DTEND:20270105T150000Z
SUMMARY:Fictional date-set audit
RRULE:FREQ=WEEKLY;COUNT=4
RDATE:20270112T140000Z,20270202T140000Z
EXDATE:20270105T140000Z,20270112T140000Z
END:VEVENT
END:VCALENDAREvery date property in this specimen uses a UTC DATE-TIME. Compare full instants, not just printed day numbers. An all-day DATE series needs corresponding DATE-valued additions and exclusions; do not turn a date into midnight UTC to make the fields look uniform. [3]
Keep an excluded first start as the original anchor
EXDATE may remove DTSTART from the visible recurrence set, but RFC 5545 says the original DTSTART value must still be maintained because other properties, including RECURRENCE-ID, depend on it. [2]
In this specimen the first visible meeting is January 19. Changing DTSTART to January 19 while retaining COUNT=4 is a different schedule: its four generated weekly starts would be January 19 and 26, then February 2 and 9. It is not a harmless way to hide the already excluded January 5 event.
When auditing an export, keep separate columns for the original anchor, generated starts and final visible starts. If you want to start a new series rather than retain the old identity, make that change intentionally in the supported calendar editor.
Use a repeatable audit instead of repeated imports
Save the original file. Identify the UID and master component; locate its DTSTART and single RRULE. Enumerate the finite rule starts, copy each RDATE into the inclusion list, collapse exact duplicate starts, then remove all EXDATE starts. Finally inspect separate RECURRENCE-ID components, which can change an individual occurrence’s current time.
If the file uses a named zone, keep the value type and zone representation while comparing starts. This article’s UTC example deliberately avoids offset ambiguity. If the app shows a different final set, retain both the original and exported result so you can distinguish a source-file rule from an import or display problem.
Two complete date-set decisions
RDATE and EXDATE both name January 12. Should the makeup inclusion restore that date?
No. EXDATE removes it from the combined inclusion set.
January 12 is generated by RRULE and included again by RDATE, but duplicate inclusion supplies only one candidate. EXDATE then removes that candidate. Choose a genuinely different confirmed makeup start if one is needed.
Only January 19, January 26 and February 2 appear. Should I replace DTSTART with January 19?
Keep the original January 5 anchor unless you intend a different series.
The first visible occurrence is not necessarily the original DTSTART. Moving the anchor changes the counted rule sequence, while the original DTSTART remains important for recurrence identity even when it is excluded.
Sources and further reading
- RFC 5545 §3.8.5.3Rule scope and exact example interpretation.
- RFC 5545 §3.8.5.1Rule scope and exact example interpretation.
- RFC 5545 §3.8.5.2Rule scope and exact example interpretation.