Calendar Event Rules: Dates, Recurrence and Availability
Choose among twenty complete guides by your reader problem: date selection, recurrence boundaries, added or excluded dates, selector combinations, individual or future changes, clock time and transitions, availability and task fields.
Start with the intended schedule, then compare its concrete dates with the exported rule. Complete fictional files help explain the standard; your calendar’s import, editor and availability behavior still need their own checks.
Month positions and annual reminders
Choose an exact date, month-end weekday, monthly ordinal or explicit leap-birthday reminder policy.
A monthly event on the 31st skips months without that date. It does not automatically move to February 28 or April 30. Choose an exact-day rule or an explicit month-end rule, then inspect the generated dates before replacing an existing calendar.
A last-weekday recurrence knows the selected weekdays, not your holiday calendar. Excluding a closure removes an event; it does not automatically move it to the previous open day. Separate the weekly rule from your organization’s dated closure and replacement policy.
The second Tuesday of every month is a calendar-month rule, not an every-four-weeks rule. Use an ordinal weekday selector, start on a matching date and check a month where the 28-day rhythm diverges from the calendar.
An exact February 29 yearly event appears only in years with that date. A yearly reminder on February’s final day or on March 1 is a separate chosen policy. Make that choice explicit without changing the recorded birth date.
Alternating weeks and series endings
Inspect week boundaries, counted occurrences and inclusive cutoffs before extending a schedule.
“Every other week” needs an anchor and a week boundary. For a series on both Tuesday and Sunday, changing WKST from Monday to Sunday can change the Sunday dates even when INTERVAL and DTSTART stay the same.
Use COUNT for a chosen number of generated occurrences or UNTIL for an inclusive cutoff. DTSTART counts first. Excluding an occurrence does not top up COUNT, and a cutoff between scheduled starts does not create a final event.
Change one occurrence or the future series
Identify original occurrences before moving one meeting or shifting affected future instances.
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.
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.
Clock time and availability
Choose clock-time anchors, nominal or exact durations, and busy-time transparency separately.
An all-day date and a busy-time block are separate choices. TRANSPARENT keeps an event out of busy-time searches; OPAQUE is the default. Choose availability according to whether the event consumes your time, then verify the result in your actual calendar.
Under RFC 5545, floating time represents the same local clock reading wherever it is interpreted. It does not represent one worldwide meeting instant. Compare three complete original files, then check whether your actual calendar preserves the intended meaning.
A weekly series anchored to UTC can change its local clock reading when the viewer’s offset changes. A series anchored to a named local zone can keep that zone’s clock time while changing its UTC time. Check the intended anchor and the full recurrence before shifting the series.
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.
Add and exclude specific dates
Reconstruct the final set without losing its original anchor.
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.
Combine and rank recurrence selectors
Compare calendar intervals, candidate positions, weekday intersections, time combinations and week numbering.
A daily interval advances by calendar days before a weekday filter removes candidates. It does not count only the weekdays that survive. Compare every three calendar days with every third included weekday, and state whether your policy includes holidays or other closures.
BYSETPOS chooses positions from the combined candidate set for each frequency interval. BYDAY=TU,TH;BYSETPOS=2 selects one second candidate per month, while BYDAY=2TU,2TH selects the second Tuesday and second Thursday separately.
When BYDAY and BYMONTHDAY both limit a monthly recurrence, a date must satisfy both filters. A Friday-the-13th rule selects only dates that are Friday and the 13th, with long gaps possible between occurrences. It does not combine every Friday with every monthly 13th.
BYHOUR and BYMINUTE are independent selectors. With DAILY frequency, hours 9 and 17 and minutes 0 and 30 create four daily starts, not just 9:00 and 17:30. Use separate finite series or explicit dates when the intended time slots are paired.
BYDAY=20MO counts the twentieth Monday within the year when no month or week-number selector is present. BYWEEKNO=20;BYDAY=MO selects Monday in week 20 under its week rules. These dates differ in 2026 even though they happen to agree in 2027 and 2028.
Task due dates and completion
Distinguish an action item’s expected due boundary, percent complete, actual UTC finish and revision metadata from an event interval or reminder.
Keep a task’s expected due boundary separate from progress, its actual UTC finish and revision metadata. Compare three complete fictional VTODO files and check a date deadline before treating it as an end-of-day promise.
Clock gaps and repeated times
Use the verified recurrence correction to distinguish a nominal local start from its selected instant. Compare two complete finite fictional schedules through forward and backward clock transitions.
A weekly local start can fall in a clock gap or a repeated interval. Use verified RFC 5545 erratum 4271 to interpret the instant, then compare two complete fictional COUNT=3 schedules.