Recurring and multi-date events

A recurring event on Cloomba is one event with many sessions — a weekly class, a monthly meetup, a course that runs for eight weeks. It has one page, one guest list, one comment thread and one media wall, no matter how many times it meets.

Setting it up

Create your event as normal. In the When section, switch Does not repeat to Repeats, and describe the pattern:

How often — daily, weekly, or monthly.
Every — every week, every 2 weeks, every 3 months, and so on.
On days — for weekly events, tick the days it runs. A class on Tuesdays and Thursdays is one event, not two.
Ends — After a number of sessions (an eight-week course), On a date, or Never for an open-ended series that keeps rolling forward.

The dates appear underneath as you set the pattern, so you can check them before you publish.

The schedule

Once published, your event gets a Schedule tab listing every session. View it as a week, a month, a day, or a plain list.

Open any session to make changes to that session alone:

Move it to a different time — one week's class runs late, the rest are unaffected.
Cancel it — a holiday, a room clash. Guests see it as cancelled; the rest of the series carries on.
Assign an instructor — pick from your event's speakers, either for that session only or for it and everything after it.

Individually edited sessions are protected. If you later change the recurrence pattern, Cloomba reflows the future sessions but leaves your hand-edits and past sessions alone.

How guests sign up

Guests choose how much they are committing to, from the session they are looking at:

This lesson — a drop-in. They can do this for several sessions separately.
This and all following lessons — they join from here to the end.
The entire course — the whole series in one go.

Which options appear depends on the series: an open-ended free series offers "this lesson" or ongoing, while an open-ended paid series is sold one lesson at a time.

Each session shows how many spots are left, and fills up independently.

Charging for it

You can price a recurring event per lesson, per course, or both — they are set independently, so a drop-in can cost more than the same session bought as part of a pass.

Payment works as it does everywhere on Cloomba: by card, or off-platform if you take cash or bank transfer and mark people as paid yourself.

Running the sessions

Check-in is per session. Open a session and you get its own roster — mark people attended or no-show, and add or remove someone on the spot. There is also a grid view of everyone against every session, so you can see attendance across the whole course at a glance.

When not to use it

A recurring event is right when the sessions are the same event, meeting repeatedly — same format, same audience, one shared guest list.

If each edition is really its own event, with its own guest list, its own cover and its own turnout to measure, keep them separate and clone the previous one to make the next. Group them with a calendar so followers get notified each time you add one.

Setting one up on mobile

The recurrence pattern is set on the web. In the iOS and Android apps you can see the schedule, sign up for lessons, and check guests in session by session — but to create or reshape the pattern itself, use the web app.