A one-off event is a project. A recurring event is a process, and processes break differently. The first edition of a weekly class takes an afternoon to set up. The fortieth should take thirty seconds — but with most tools it still takes the afternoon, because every edition is a fresh event with a fresh page, fresh tickets and a fresh guest list that knows nothing about the last one.

This guide covers the four things that turn recurring events from a chore into a system: series, templates, memberships and automations. It is written for anyone running recurring events — classes, meetups, clubs, run groups, workshops — and for membership organisations whose events are part of what members pay for.

1. Series: one event, many editions

An event series groups editions together and applies a recurrence rule — every Tuesday, the first Thursday of the month — so the next edition is created for you and inherits the last one's settings. Edit the series and every future edition follows; edit one edition and only that one changes.

The less obvious benefit is continuity of data. When all the editions belong to one series, you can see who comes every week, who came three times and stopped, and which editions sold out. That is the information you need to decide whether to add a second weekly slot.

2. Templates: for events that repeat but not on a schedule

Not everything recurs on a fixed rhythm. A quarterly workshop, a pop-up dinner or a launch party happens whenever it happens, but the setup is the same each time. Event templates save the format, capacity, visibility, tickets and defaults so the next one starts from a known-good setup rather than from memory. If your registration form uses conditional questions, the template keeps those too — see our conditional registration form examples for patterns worth saving.

3. Memberships: pay once, come often

For regulars, buying a ticket every week is friction. Memberships let you sell a plan — one-time, monthly or yearly — that unlocks:

• Member pricing on tickets, or free entry.
• Member-only registration for events that are part of the membership.
• A managed roster, with public join pages and auto-renewal, so you are not reconciling a spreadsheet against payments.

Membership also works as an access rule on registration: an event can be limited to members, or members can register before everyone else. Combined with approval gates, it covers most "members and invited guests" formats. The registration and RSVP page covers those gates.

4. Audience: people who follow you, not just one event

For a recurring programme, the audience is the asset. An organiser profile with followers means your next event reaches people who already opted in, rather than depending on a marketplace to surface it. Between events, community features — announcements, polls, discussion boards, chat — keep people engaged, and email and SMS handle the "this week's session" reminder.

Every attendee lands in your attendee CRM with their history across editions, so you can segment regulars from first-timers and treat them differently.

5. Automations: the jobs you do every single week

List the things you do manually for each edition. It usually looks like: send a reminder the day before, send a thank-you afterwards, nudge people who registered but did not show up, welcome first-timers, and tell the waitlist when a spot opens. Each of those is a trigger and an action, which is exactly what event automations are for: a registration submitted, an event starting soon, an attendee checked in or marked a no-show — each can kick off emails, SMS or tags, with run history so you can see what fired.

Waitlist promotion in particular should never be manual for a recurring event. With a capacity limit and an auto-promoting waitlist, a cancellation on Monday fills itself before Tuesday's class.

A setup that runs itself

Put together, a weekly class looks like this:

1. A series with a weekly recurrence and a capacity limit.
2. A short registration form with one conditional question (first time? show "anything we should know?").
3. A monthly membership that makes each class free for members, with drop-in tickets for everyone else.
4. Automations for the day-before reminder, the first-timer welcome and the post-class thank-you.
5. An organiser profile, so followers hear about new series and one-off specials.

After the first afternoon of setup, the weekly work is showing up and teaching the class.

Where to go next

If you run a community rather than a class, community event platform is the better starting point; creators selling to their own audience should read events for creators; and if your events raise money, see nonprofit and fundraising events. Choosing a platform in the first place? Our buyer's guide covers the five questions to ask.