Running a recurring event without the weekly admin

The single most reliable thing you can put into a paid community is a recurring live event. Same time every week, something happens, people show up. It beats content, it beats a feed, and it is the reason a lot of memberships renew.

It is also the thing hosts quietly stop doing, and the reason is almost never that the calls went badly. It is that each one costs forty minutes of admin — creating the event, chasing RSVPs, sending the reminder, posting the link, remembering who is on the waitlist — and forty minutes a week for a year is a job.

Here is how to set it up so that it costs you nothing after the first time.

Create it once, as a series

Set the pattern and an end condition: never, a specific date, or after N occurrences. Set the timezone explicitly — this matters more than it sounds if you have members abroad, and your timezone is not the same claim as the community's.

Pick online or in person, and decide whether the location is hidden. Klaas withholds the location and the joining link from anyone not entitled to attend, showing "(Location visible to attendees)" instead. That is not just for paid events: a public Zoom link in a public event page is how you get an uninvited guest, and it happens to somebody in this industry roughly every week.

Understand the RSVP scope, because your members will use it wrong

When a member RSVPs to one occurrence of a series, they choose the scope:

• This event — just this week.
• This and following — from here on.
• All events — the whole series.

This is the setting that saves you the weekly chase. A member who picks "all events" is now on every occurrence, in their calendar, receiving every reminder, without ever thinking about it again.

So say so. In the event description, one line: "Tip: choose 'All events' when you RSVP and you'll never have to think about this again." Almost nobody notices a scope selector unaided. The default behaviour of the average member is to RSVP to the one in front of them, and then wonder in three weeks why they stopped getting reminders.

Capacity and the waitlist

Set a maximum if the format needs one — a critique session with twelve people is a different product from one with sixty.

With a waitlist enabled, a full event offers Join waitlist. Without one, it says Sold out. Both are honest; pick deliberately. "Sold out" creates scarcity and turns away a member who would have come. A waitlist captures them, and promotions happen automatically when somebody drops, which is the whole reason to have one — a waitlist that requires you to notice a cancellation is a to-do list.

You can also hide the RSVP count, the maximum capacity, or both. This is worth thinking about rather than defaulting. A visible "23 going" is powerful social proof once you have 23 people. A visible "2 going" on a Tuesday is a reason for the third person not to come. Hide the count until your events are reliably full, then show it.

The calendar files are the retention mechanism

Once a member is attending, they get links to add the event to Google, Outlook and Yahoo calendars, plus a downloadable .ics file for everything else.

I would put this above every other item on this page. An RSVP on a website is an intention. An event in someone's calendar is a commitment that will interrupt them at the right moment with a notification you did not have to send. The gap in attendance between the two is enormous.

Which means the most valuable sentence in your event description is a request to add it to their calendar. Not a feature announcement — an instruction.

Reminders, and the setting that overrides you

Klaas sends reminders and RSVP confirmations automatically on a schedule. You do not send them.

One thing to be aware of, because it will look like a bug: members can turn event reminders off in their own notification preferences, and that preference is real — it genuinely gates the send. So "I never got the reminder" is sometimes a member who switched them off, and the honest answer is to check rather than assume the system failed. This is the correct behaviour and we would not change it, but it means reminders are a floor, not a guarantee.

The practical consequence: the calendar entry is the only channel you control end to end. Reminders are best-effort. Push the calendar link.

Ticketing, if you charge

An event can be free, restricted to paid members or specific plans, gated to a segment, or sold as a one-time fee — a ticket, without a subscription.

One behaviour worth knowing so you do not panic: if you set an event to require a ticket but have not yet configured a price, the event honestly says "Ticket required — not on sale yet" rather than showing a broken buy button. That is the system telling you it is half-configured, not a failure. Set the price and it resolves.

You can also point an event at an external registration URL, which bypasses RSVP entirely. Useful when the event genuinely lives on someone else's platform. Be aware that you lose everything above — no attendee list, no automatic reminders, no calendar files, no waitlist. It is an escape hatch, not a strategy.

Cancelling one week

Real life happens. You can cancel a single occurrence without touching the series, and it is worth knowing this exists before the morning you need it. The alternative — deleting and rebuilding a series — loses every RSVP you had.

After the event

Two things you can do inside the admin that most hosts do not:

• Mark attendance. Who actually came, versus who said they would. Over a few months this is the most useful engagement signal in your community, and far more honest than post counts.
• Export the RSVP list. A real export, not a screenshot. Useful for follow-up mail, and for noticing that the same eleven people come to everything, which is a fact you should probably act on.

A workable weekly setup

1. Create the series once with an explicit timezone, recurrence, and no end date.
2. Enable a waitlist. Hide the RSVP count for now.
3. Write the description with two lines in it: "RSVP with 'All events' so you don't have to think about it" and "Add it to your calendar — that's what actually reminds you."
4. Set access — free, plan-gated, or ticketed.
5. Never touch it again.

Then spend the forty minutes you got back on the event itself, which is the part your members are paying for.