Practical guide
Every Other Week: Start Dates, Selected Days and Week Boundaries
“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.
Define alternating weeks before choosing days
FREQ=WEEKLY;INTERVAL=2 repeats across alternating weekly intervals. DTSTART supplies the starting anchor; BYDAY selects days within those intervals. WKST supplies the beginning of a week. RFC 5545 defaults WKST to Monday and explains why it matters with intervals above one and multiple selected weekdays. [1]
For one Tuesday every two weeks, a January 5 start naturally leads to January 19 and February 2. A Tuesday-and-Sunday series requires another choice: does Sunday January 10 belong to the active week that began Monday January 4, or does it begin a different Sunday-first week? Write that choice before comparing dates.
Map the first two active weeks
With Monday-first weeks, January 5 is in the January 4–10 interval. Its Tuesday and Sunday are January 5 and 10. The next active interval is January 18–24, giving January 19 and 24.
With Sunday-first weeks, January 5 is in the January 3–9 interval. Sunday January 3 is before DTSTART and is not an additional earlier event. The next active interval is January 17–23, giving Sunday January 17 and Tuesday January 19. The following active Sunday is January 31.
Compare the first four occurrences
On a narrow screen, swipe within the table to read the remaining columns.
| Occurrence | WKST=MO | WKST=SU |
|---|---|---|
| 1 | Tuesday 5 January | Tuesday 5 January |
| 2 | Sunday 10 January | Sunday 17 January |
| 3 | Tuesday 19 January | Tuesday 19 January |
| 4 | Sunday 24 January | Sunday 31 January |
COUNT=4 counts occurrences, not four active weeks. Two selected weekdays can consume more than one occurrence in a weekly interval. A screen preview showing only Tuesdays can miss the differing Sundays entirely.
Inspect both week-boundary files
The two complete all-day files differ in their chosen WKST policy and example UID/summary. Their DTSTART, count and selected weekdays are the same. Gregorian date arithmetic and a recurrence library were used to compare the stated dates; no application import was performed.
Download practice alternate weeks monday (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Fictional Examples 1.0//EN
BEGIN:VEVENT
UID:a8d58ed1aad051cc1cbd3e09@daymooncalendar.com
DTSTAMP:20261108T000000Z
DTSTART;VALUE=DATE:20270105
SUMMARY:Practice - Alternating Monday weeks
RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=4;BYDAY=TU,SU;WKST=MO
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDARDownload practice alternate weeks sunday (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Fictional Examples 1.0//EN
BEGIN:VEVENT
UID:c60f9d6894788fd4f819d79e@daymooncalendar.com
DTSTAMP:20261108T000000Z
DTSTART;VALUE=DATE:20270105
SUMMARY:Practice - Alternating Sunday weeks
RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=4;BYDAY=TU,SU;WKST=SU
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDARKeep display preferences separate from recurrence rules
A calendar’s displayed first column may be a visual preference. Inspect the actual RRULE before assuming that preference rewrites WKST. These are separate things to check, and the standard does not promise how an app maps its editor labels onto exported files.
Changing DTSTART can also change the anchor. A new series starting January 12 on the opposite Tuesday belongs to a different alternating-week rhythm. Do not move the entire series start just to repair a single event; a single-occurrence exception preserves that narrower intent.
The relevant RFC examples demonstrate a Tuesday/Sunday schedule whose result changes with WKST. The example here uses new 2027 dates and DATE values to isolate the week-boundary problem from daylight-saving and timed-event issues. [2]
Two complete decisions
My Tuesdays match, but Sunday January 10 is missing. Could WKST explain it?
Yes, if your rule uses Sunday-first alternating weeks in this example.
With WKST=SU, the active intervals are January 3–9, January 17–23 and January 31–February 6. January 10 begins an inactive interval. Compare the full rule and both selected weekdays before adding an independent Sunday event.
I need four active weeks with both Tuesday and Sunday. Is COUNT=4 enough?
No. COUNT counts event occurrences, not active intervals.
In this example the initial Sunday-first interval contributes only Tuesday after DTSTART. Enumerate the desired date range and all selected dates first; do not multiply weeks by two without checking the truncated initial interval. Use a verified cutoff or count appropriate to the actual list.
Test a boundary before applying a long schedule
Inspect the first selected day, the first Sunday, an inactive week and the final occurrence. If your actual app exports a different WKST or changes the series start, compare those fields with the intended date list. For clock-time movement around a seasonal offset change, consult the existing DST guide; the weekly partition itself does not explain that separate problem.
Sources and further reading
- RFC 5545 §3.3.10 — Recurrence valueFrequency, intervals, ordinal weekdays, set positions, count/cutoff and invalid generated dates.
- RFC 5545 §3.8.5.3 — Recurrence setDTSTART synchronization, inclusion/exclusion precedence and documented examples.