A one-off event is a project. You plan it, you run it, it's over, you feel good.
A recurring event is something else entirely. It never finishes. Every single week it needs a small amount of attention from a specific person, forever, and the failure mode isn't drama. It's slow erosion. Attendance drifts. Reminders get skipped. One week nobody unlocks the hall.
Most clubs run recurring events on memory and goodwill. Here's a system that survives one organizer being ill.
The problem with "same time as always"
"Same time as always" isn't a schedule, it's an oral tradition. It works perfectly for the eight people who've been coming for years and fails completely for the person who joined last month.
Every recurring event needs an answer to four questions that a newcomer can find without asking anyone:
- When is it, including the next actual date?
- Where is it, precisely enough to arrive at?
- Who's coming this time?
- What do I need to bring or know?
If the only place those answers exist is in someone's head or in a chat message from March, the event is more fragile than it looks.
Set it up once, not fifty-two times
The first rule: never create next week's session manually. If a human has to remember to post it, one week a human will forget, and the drop-off from a missed session is much bigger than it should be.
Set the event up as genuinely recurring, with the real pattern. Every Tuesday, first Monday of the month, every other Thursday during term. Then the schedule exists whether or not anyone thought about it, and members can look further ahead than one week.
The side benefit is that the event stops being an announcement and becomes a place. Same address, same page, week after week, with the details already on it.
Make an RSVP mean something
An RSVP is only useful if it changes a decision. Before you ask people to respond, know what you'll do with the answer:
- Under eight, we cancel and use the hall for something else
- Over twenty, we split into two groups and need a second coach
- Exactly this list of people, so I know how much food to buy
If the number doesn't change anything, don't ask for it. You'll train people to ignore RSVPs, and then the one time it matters, they'll ignore that too.
When it does matter, keep the options honest. Going, maybe, and not going is enough. "Maybe" isn't a failure of the system. For a Tuesday evening in a volunteer club, "maybe" is the truth, and it's more useful than a forced yes that doesn't show up.
The reminder ladder
Reminders fail in two directions. Too few and people forget. Too many and people mute the whole thing, which is worse, because now they miss the cancellation too.
A ladder that works for most weekly events:
- A week ahead: only for people who haven't responded, and only if you need numbers to plan.
- The day before: to everyone who said they're coming, with the practical details of time, place and what to bring.
- The morning of, if and only if something has changed.
Notice what's missing: a reminder to everyone every day. Silence is a feature. If your members trust that a notification from the club means something actually happened, they'll keep reading them.
Handle the exceptions in the open
Recurring events break constantly. Easter, a double-booked hall, a coach on holiday, a heatwave. The temptation is to fix each exception in a chat message, because it's quick.
Do it on the event instead. Cancel that specific occurrence, or move it, and let the change carry its own explanation. The rule is simple: if a change is only in a chat message, it didn't happen. Someone will arrive at a locked door and they'll be right to be annoyed.
Track who shows up, without being weird about it
There's a real difference between who said they were coming and who actually came, and after a few months that difference tells you things worth knowing. Which sessions are dying. Which ones have a waiting list you hadn't noticed. Whether the new Thursday slot was a good idea.
Keep it light. You're not running a performance review on volunteers. You're checking whether the schedule still matches how people actually live, and adjusting once a term instead of guessing.
Write down the handover while it's boring
The best time to write down how an event runs is a normal week when nothing is going wrong. Nobody ever does this, which is why handovers happen by panicked phone call.
One page, on the event or in the group's files: who has the keys, what time the hall opens, the caretaker's number, where the equipment lives, what to do if fewer than eight people come, who to tell if you cancel. Ten minutes now, and the event survives you being unavailable.
The checklist
For each recurring thing your community runs:
- It exists as a real recurring schedule, not a weekly manual post
- Time, place and practical details live on the event, not in chat history
- RSVPs are asked for only where the number changes a decision
- Reminders follow a ladder, not a habit
- Cancellations and moves are made on the event itself
- There's one page telling someone else how to run it
None of this is exciting. That's rather the point: a recurring event should be the least interesting thing in your week.
Pick the one recurring thing that costs you the most attention and set it up properly once. If you want somewhere to do that, start a space for free and put next Tuesday in it.