Date & Time
Recurring Event Recurring Date Calculator
Generate a recurrence-of-recurrence calendar with a weekly interval, declared weekday, blackout shifts, periodic review markers, minimum-gap protection, and a fixed planning horizon.
Recurrence calendar lattice
Biweekly date lattice with shifts, reviews, and horizon boundary
Dates occupy a seven-column calendar lattice; shifted dates keep their nominal anchor, review markers remain distinct, and the horizon boundary cuts the series visibly.
Rule expansion ledger
Nominal and adjusted date generated by every recurrence
Inspect index, nominal day, weekday, blackout shift, adjusted day, gap from prior date, review marker, and horizon status.
| Index | Nominal day | Weekday | Shift | Adjusted day | Gap | Review marker | Horizon status |
|---|
Recurrence-rule setup
Write the base rule before adding exceptions
- Choose occurrence count and interval weeks.
- State the declared weekday.
- Set the first relative calendar day.
- Apply a transparent blackout-shift cadence.
- Add review markers, minimum gap, and horizon.
Rule-expansion logic
Exceptions should remain traceable to nominal dates
A shifted occurrence keeps its nominal anchor in the ledger so the exception does not silently redefine future cadence.
Minimum-gap testing uses adjusted dates because those are the dates that consume operational capacity.
Calculation method
Expand the recurrence rule, apply exceptions, then validate spacing and horizon
Nominal dates are generated at a fixed weekly interval. Selected dates shift by a declared number of days; adjusted gaps and horizon inclusion are then tested in chronological order.
Detailed calculation process and general formulas
G=7wd_i=d₁+(i−1)Gd'_i=d_i+s·1(i mod b=0)gap_i=d'_i−d'_{i−1}inside_i=1(d'_i≤H)Symbols, meanings, and units
- w
- weeks between nominal datesweeks
- G
- nominal date gapdays
- s
- blackout shiftdays
- b
- blackout-shift cadenceoccurrences
- H
- planning horizonrelative day
Pattern integrity
See when exceptions distort an otherwise stable recurrence
The lattice distinguishes base cadence, shifted dates, review markers, spacing breaches, and horizon exclusion.
Base rhythm
—Days between nominal dates.
Exception count
—Occurrences moved by the blackout rule.
Spacing defects
—Adjusted gaps below the accepted minimum.
Horizon coverage
—Generated dates still inside the planning window.
Decision takeaway: Keep the nominal recurrence stable and record exceptions explicitly; otherwise each shift can unintentionally drift the entire series.
Rule checks
Validate what the recurrence grammar omits
- Real blackout dates are not usually periodic.
- A shift can change the weekday.
- Review markers may require additional time.
- Some systems skip rather than shift exceptions.
Recurrence evidence
Artifacts needed for a durable rule
- Published recurrence specification
- Exception and blackout calendar
- Minimum-spacing policy
- Review cadence
- Horizon approval date
Practical applications
Decisions this calculator is designed to support
Biweekly governance review
A committee meets every two weeks, shifts selected blackout occurrences, and flags every third date for a deeper review.
What the result clarifies: The lattice shows whether the exceptions preserve minimum spacing.
Recurring maintenance inspection
A maintenance series is generated six months ahead with periodic exception shifts.
What the result clarifies: Nominal anchors prevent one exception from drifting all later inspections.
Worked example
Current-input substitution and reconciliation
Model limitations
This relative-day generator does not resolve real calendar months, daylight saving, jurisdiction holidays, nth-weekday grammar, duplicate-date merging, or resource availability. Periodic blackouts are a planning proxy.
Recurring Event Recurring Date Calculator FAQ
Does a shifted date change later nominal dates?
No. Later dates continue from the original recurrence rule.
Why test adjusted gaps?
Adjusted dates determine actual operational spacing.
What is a review marker?
A label on every entered nth occurrence; it does not move the date.
Are dates beyond the horizon deleted?
No. They remain in the ledger and are marked outside.