Many organizations schedule by ordinal weekday
Board meetings and maintenance windows are often defined as patterns like the second Wednesday rather than a fixed day number.
Repeating dates appear everywhere in operational work. Finance teams have review cycles, facilities teams have maintenance windows, managers have recurring one-to-ones, and individuals track renewals, compliance checks, billing events, or reporting deadlines. The rule behind those schedules can sound simple, but it is easy to misapply when months vary in length or when an event is defined by weekday rather than calendar day. This Recurring Date Calculator turns those rules into a concrete date list you can verify immediately.
The tool supports straightforward interval patterns such as every 7 days, every 2 weeks, every month, or every year. It also supports an nth-weekday mode for schedules like the second Tuesday of each month or the last Friday in the quarter. That is particularly useful when a rule is defined around business rhythm rather than a fixed numeric date. Instead of relying on memory or a separate spreadsheet formula, you can generate the series directly in the browser and inspect each occurrence.
The output focuses on clarity. It shows the first and last generated date, total number of occurrences, and a table of every occurrence with weekday labels. That makes the result appropriate for operational checks before you move the schedule into a project tool, calendar, or reminder system. Because it is client-side, it is also suitable for internal work where you may not want to push planning dates into a third-party service during the early drafting stage.
While this page is not a replacement for enterprise scheduling software, it solves the date-generation step cleanly and privately. It pairs well with the Date Calculator for one-off offsets and with the Cron Expression Generator when you need to move from human date planning into system automation. In short, it is the missing bridge between a scheduling rule and the concrete dates that rule actually creates.
fixed interval recurrence = start date + n × intervalmonthly yearly recurrence = UTC date shifted by month or year incrementsnth weekday recurrence = first weekday in month + (ordinal − 1) × 7 days, or search backward for last weekdayExample: if a compliance review starts on 2026-01-15 and repeats every month for six occurrences, the tool outputs the date series through June. If the rule is instead the second Tuesday of each month, the generator computes the actual weekday-based date in every target month and lists them in order.
You can repeat by days, weeks, months, years, or by nth weekday of a month such as the second Tuesday.
Yes. Monthly and yearly series are a good fit for subscriptions, renewals, and policy anniversaries.
It finds patterns like first Monday, third Thursday, or last Friday inside each target month.
No. It builds the occurrence list locally in your browser only.
Cron is better for system schedules and exact times. This tool is better for human-facing date patterns such as contracts, reviews, and reminders.
Board meetings and maintenance windows are often defined as patterns like the second Wednesday rather than a fixed day number.
A repeating rule tied to day 31 cannot appear in every month, which is why ordinal weekday patterns are often safer.
Once a pattern is defined, the full series can be reviewed instead of recalculated every period.
Monthly closes, quarterly reviews, and renewal reminders all rely on repeatable date rules.
Seeing the actual date list is easier to validate than reading only the recurrence rule itself.
This tool generates date sequences but does not automatically account for holidays, business-day shifts, or organization-specific rollover rules. Review each occurrence before using it for contractual or regulated deadlines.