Scheduling a Run of Recurring Meetings Without Landing on a Weekend
Setting up a recurring meeting sounds like the most solved problem in scheduling — every calendar app has a "repeat" button. But the moment your cadence is anything other than a clean weekly or monthly rule, the repeat button starts dropping meetings onto Saturdays, Sundays, and public holidays, and you're left dragging each one to the nearest working day by hand. A "every ten days" review, a sprint checkpoint every seven business days, a fortnightly-plus-a-bit steering cadence — these drift off the working week fast.
Why calendar-day recurrence drifts
The problem is that a fixed calendar-day interval takes no account of which days are workable. Add ten calendar days repeatedly and roughly every third or fourth occurrence lands on a weekend, because ten isn't a multiple of seven. Add a public holiday into the run and the drift compounds. Each meeting that falls on a non-working day either gets skipped, silently moved, or held on a day half the attendees aren't around — and the series loses its rhythm. What you actually want is a cadence measured in business days, so every occurrence is guaranteed to fall on a day people are working.
The Recurring Meeting Date Generator does exactly that. Give it a start date, how many occurrences you need, and the interval in business days, and it walks the series forward — skipping weekends and the holidays on your chosen calendar at every step — so the whole list lands on working days. The first occurrence is rolled forward to a working day if the start itself falls on a weekend, and each subsequent date is counted as business days from the one before it.
Generate the whole series, not just the next one
The real value is seeing the entire run at once. A single "next meeting" date tells you nothing about whether occurrence six collides with a holiday week, or whether the cadence quietly bunches two meetings into the same tight stretch after a long weekend. Laying out all the dates up front lets you spot those clashes before you send the invites — and lets you send a series people can actually plan leave and travel around, because the dates are fixed and visible rather than emerging one recurrence at a time.
A worked example
Suppose a project kicks off on Wednesday July 1 and you want ten checkpoints, each five business days apart, on a Monday-to-Friday week. Counting five business days at a time, the series lands on July 8, 15, 22, 29, and onward — every occurrence a weekday, none dragged onto a weekend, and any public holiday in the window automatically pushing the affected date to the next working day. Set the same cadence with a calendar-day "every 7 days" rule instead and you'd get a tidy run of Wednesdays — but a "every 5 days" calendar rule would have marched straight through the weekends. Business-day spacing is what keeps an irregular interval on the working week.
Pick an interval that survives the whole run
The interval is worth a moment's thought before you generate the series, because a business-day cadence and a calendar rhythm answer different questions. A weekly standup wants the same weekday every time — that's a calendar rule, "every Monday," and business-day spacing would actually work against it. But a great many recurring meetings aren't tied to a weekday at all: a review "roughly every two weeks," a checkpoint "about every ten working days," a cadence that just needs to be regular and never fall on a day off. Those are the ones a business-day interval serves well, because it holds the spacing steady in working time rather than in calendar time. A useful way to choose: if the meeting must recur on a named day, use a calendar rule; if it must recur after a consistent amount of work has passed, count it in business days. Getting that distinction right up front saves you from generating a tidy-looking series that's spaced correctly on paper but wrong for how the team actually works.
Match the calendar to the attendees
A meeting series is only as workable as the calendar it's counted on. If the group spans a team that observes different public holidays, or runs a six-day week, the default Monday-to-Friday, US-holiday assumption will put occurrences on days that are working for you and off for them. Set the workweek pattern and holiday country to match the people who actually have to attend, and add any company-wide shutdown as a custom closure so no meeting lands inside it. A cadence that's perfect on your calendar and broken on everyone else's isn't a schedule — it's a series of reschedules waiting to happen.
Run the Recurring Meeting Date Generator to turn a business-day cadence into a full list of concrete dates that never land on a weekend or holiday. Generate the series once, circulate the dates, and spend your time in the meetings instead of rescheduling them.