Repeating dates

Recurring events: daily, weekly and monthly rules, with capacity, price and attendees kept per date.

In the paid plans Read the manual

A weekly class, a film that runs all month, a tour that leaves every Saturday. One event with many dates, not many events.

Making the dates

Describe the pattern once: repeats daily, weekly or monthly, every one or two weeks, on the days you choose, from a first date until one you set.

As you change the fields the dialog counts what it is about to make, so you can see that "every Friday until December" is fourteen nights before you commit to them.

The Recurring tab, counting the dates it is about to make.
The Recurring tab, counting the dates it is about to make.

The list is yours after that

The pattern makes the list; then you edit the list. Add a date by hand for the extra Sunday, move the one that clashes with a holiday, drop the one nobody wants.

The rule is not re-run behind you, so nothing you changed is quietly undone. Every row shows what has happened to it: edited, how many are booked, or cancelled.

Each date on its own terms

A date can hold a different number of people from the rest of the series, and start at a different time.

It can also carry its own price, which is how the night with the guest speaker costs more without becoming a separate event.

Calling one off

Removing a date that has bookings cancels it rather than deleting it, so the people on it are not lost. They are still there, still findable, still refundable, and a workflow can tell them what happened.

The rest of the series carries on selling. Change your mind and the date reopens.

How the series looks to a customer: passed and cancelled dates cannot be picked.
How the series looks to a customer: passed and cancelled dates cannot be picked.