Practical guide
Every Three Calendar Days Is Not Every Third Weekday
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.
Say which days the counter advances through
“Every three days, weekdays only” can describe two different policies. One advances three calendar days at a time and drops candidates on Saturday or Sunday. The other counts only included Monday–Friday dates and selects every third one. These instructions need not produce the same schedule.
With FREQ=DAILY;INTERVAL=3;BYDAY=MO,TU,WE,TH,FR, INTERVAL is measured in days under DAILY frequency. BYDAY limits the candidates to the listed weekdays. It does not change the interval into a business-day counter. [1]
Use the distinction for recurring reminders or maintenance scheduling. For a contractual or legal business-day deadline, identify the controlling calendar and holiday policy separately; a weekday-only recurrence cannot establish those rules.
Trace the calendar-day candidates first
On a narrow screen, swipe within this table to read the remaining columns.
| Calendar candidate | Weekday | Keep under Monday–Friday filter? |
|---|---|---|
| 9 November | Monday | Yes: occurrence 1 |
| 12 November | Thursday | Yes: occurrence 2 |
| 15 November | Sunday | No |
| 18 November | Wednesday | Yes: occurrence 3 |
| 21 November | Saturday | No |
| 24 November | Tuesday | Yes: occurrence 4 |
| 27 November | Friday | Yes: occurrence 5 |
| 30 November | Monday | Yes: occurrence 6 |
The two weekend candidates disappear. The interval keeps advancing along the original three-calendar-day rhythm; it does not restart a three-day count after the last retained weekday. COUNT=6 stops after the six retained rule occurrences in this example.
Compare a counter that includes weekdays only
On a narrow screen, swipe within this table to read the remaining columns.
| Occurrence | Three calendar days, then filter | Every third included weekday |
|---|---|---|
| 1 | 9 November | 9 November |
| 2 | 12 November | 12 November |
| 3 | 18 November | 17 November |
| 4 | 24 November | 20 November |
| 5 | 27 November | 25 November |
| 6 | 30 November | 30 November |
For the included-weekday column, November 9 is included day 1. Select included-day positions 1, 4, 7, 10, 13 and 16. Weekends never advance that counter. There are no holidays or employer closures in this fictional policy.
The first two dates agree, and the sixth agrees again. Checking only the initial date or a single later match would conceal the different rules. Check the first divergence and at least one weekend crossing.
Inspect the rule and an explicit alternative date list
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 three calendar days filtered (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Recurrence Practice 1.0//EN
BEGIN:VEVENT
UID:c8c7b8b7387ef5b19b6d31cd@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART;VALUE=DATE:20261109
SUMMARY:Filtered calendar rhythm
TRANSP:TRANSPARENT
RRULE:FREQ=DAILY;INTERVAL=3;COUNT=6;BYDAY=MO,TU,WE,TH,FR
END:VEVENT
END:VCALENDARDownload practice every third weekday explicit (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Recurrence Practice 1.0//EN
BEGIN:VEVENT
UID:92a85a2803ec0bcdc3c4b72a@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART;VALUE=DATE:20261109
SUMMARY:Explicit included-weekday dates
TRANSP:TRANSPARENT
RDATE;VALUE=DATE:20261112,20261117,20261120,20261125,20261130
END:VEVENT
END:VCALENDARThe explicit DATE list records this finite six-date decision. It is not an unlimited holiday-aware algorithm. Both files are transparent all-day practice entries; a DATE start without an end has a one-day duration under RFC 5545. [2]
Choose the counter before choosing the file
Write the operational instruction in plain language: what is day 1, which dates increment the counter, what happens on a closure, and when should the series end? For a finite confirmed schedule, an explicit date list can communicate the result without pretending that a generic RRULE knows your organization’s exceptions.
If a closure removes a selected occurrence, decide whether that merely cancels the entry or causes all future selections to be recalculated. An EXDATE can express cancellation; it does not automatically rebuild an included-business-day count. Preserve the original schedule and verify the newly calculated list against the approved policy.
Two complete interval decisions
The November 15 candidate is a Sunday. Does the three-day rhythm restart from November 12?
No. The next calendar candidate is November 18.
The candidates are November 9, 12, 15 and 18. Filtering November 15 removes that candidate, without changing the original three-calendar-day spacing.
The first two dates match both policies. Is the calendar-day rule equivalent?
No. Their third occurrences differ: November 18 versus November 17.
Count included weekdays explicitly: November 9 is position 1, November 12 position 4 and November 17 position 7. The calendar interval instead advances through weekends before applying its weekday filter.
Sources and further reading
- RFC 5545 §3.3.10Rule scope and exact example interpretation.
- RFC 5545 §3.6.1Rule scope and exact example interpretation.
- RFC 5545 §3.8.5.3Rule scope and exact example interpretation.