Occurrences winding through week-years with visible exception shiftsLive current inputs
Date & Time
Week Number Recurring Date Calculator
Generate a stable ISO-week recurrence series with an explicit weekday, interval, blackout rule, and controlled exception shift while preserving the intended cadence across 52- and 53-week years.
Last adjusted occurrence—
First-to-last calendar span—
Nominal cadence—
Shifted occurrences—
Adjusted weekday drift—
First notice deadline—
ISO week-year seams crossed—
Cadence status—
ISO recurrence spiral
Occurrences winding through week-years with visible exception shifts
Nominal occurrences advance around concentric week rings. Shifted exceptions leave the nominal rail on a short colored spoke, making cadence drift and week-year seams immediately visible.
Recurrence exception register
Nominal dates, adjusted dates, notices, and cadence deltas
Audit every generated occurrence rather than trusting only the final date.
| Occurrence | Nominal ISO date | Adjusted ISO date | Notice deadline | Shift applied | Gap from prior | Week-year |
|---|
Recurrence setup
Protect the anchor before modeling exceptions
- Choose an actual ISO week-year, week number, and weekday.
- Enter the interval in whole ISO weeks.
- Set the number of occurrences to publish.
- Describe one repeating blackout pattern only if it is real.
- Apply notice lead to the adjusted operating date.
Anchor logic
An exception should not silently reset the cadence
If a shifted occurrence becomes the next anchor, a two-day exception can permanently move every future date. This model always returns to the original ISO-week rail.
Because the recurrence is date-based, a 53-week ISO year is handled naturally. Week labels are derived after date arithmetic rather than incremented by a fixed 52-week assumption.
Calculation method
Advance from the original anchor, then apply exceptions locally
Every nominal date equals the original anchor plus an integer number of interval weeks. A blackout shift changes only that occurrence; it does not become the anchor for the next recurrence.
Detailed calculation process and general formulas
n_i = d_0 + (i - 1) * 7Ix_i = 1[k > 0 and i mod k = 0]a_i = n_i + x_i*Snotice_i = a_i - Lgap_i = a_i - a_(i-1)Symbols, meanings, and units
- I
- nominal recurrence intervalweeks
- k
- frequency of blackout exceptionsoccurrences
- S
- date shift applied to an exceptiondays
- L
- required notice lead before an adjusted datedays
- a_i
- adjusted date for occurrence icalendar date
Cadence integrity
Separate nominal rhythm from operating exceptions
The spiral exposes four aspects of a recurring date policy.
Published horizon
—The adjusted date of the final generated occurrence.
Exception count
—Occurrences moved away from the nominal weekly rail.
Weekday consequence
—How far adjusted exceptions move from the chosen weekday.
Notice opening
—The earliest deadline for notifying participants.
Decision takeaway: Keep the nominal cadence immutable and document exceptions as exceptions.
Recurrence controls
Check the series before publishing it
- Confirm the starting ISO week exists.
- Review every shifted date for weekends or holidays.
- Do not let a shifted date reset future occurrences.
- Publish the week-year with week numbers around year-end.
Recurrence evidence
Records for a stable recurring policy
- Approved anchor date
- Recurrence policy
- Blackout calendar
- Participant notice requirement
- Prior exception log
Practical applications
Decisions this calculator is designed to support
Triweekly governance meeting
A committee meets every three ISO weeks, but every fourth occurrence shifts two days for a standing blackout.
What the result clarifies: The spiral shows the shift without allowing it to drift the following meetings.
Recurring maintenance window
A maintenance notice must be sent seven days before each adjusted operating date.
What the result clarifies: The register provides both nominal and notice dates across the new year.
Worked example
Current-input substitution and reconciliation
Model limitations
The model supports one repeating exception pattern and a fixed day shift. It does not resolve holidays, local time zones, irregular exception lists, recurrence rules such as last business day, or legal notice requirements.
Week Number Recurring Date Calculator FAQ
Does a shifted occurrence change the next occurrence?
No. Every nominal date is generated from the original anchor and interval.
Can the shift be negative?
Yes. A negative value moves the exception earlier while preserving later nominal dates.
How are week 53 years handled?
The model advances real dates and derives ISO labels afterward, so week 53 appears when applicable.
Why show notice deadlines separately?
Operational communication may need to begin before the adjusted event date.