In development. This is on the roadmap and not available yet. The guide is here so it is ready the day it ships.
Event Management

Recurring Weekly Class Schedule

Define a class once and have it repeat on your weekly schedule, with bookings, capacity and waitlists per session.

4 min readUpdated 2026-07-29

Say you teach a Tuesday evening kirtan circle, a Wednesday morning yoga class, or a Thursday sound healing session that meets in the same room at the same hour every week. Building each of those as a separate event on your calendar means typing the same name, the same teacher, the same room, the same duration and the same price fifty-two times a year — once for every week the class runs. It also means your attendance history ends up split across fifty separate records that have no idea they belong to the same class, so you can never look in one place and see how a Tuesday evening has actually gone over a season. A recurring weekly schedule solves both problems at once by inverting the relationship: you describe the class once, place it on your weekly timetable, and every Tuesday, Wednesday or Thursday session is generated from that single definition rather than rebuilt from scratch.

One definition, many sessions

The class definition holds everything that stays the same from week to week: its name and description, who teaches it, where it happens, how long it runs, what it costs, and how many people fit in the room. The weekly schedule is the separate layer that says when — which day, which time, repeating week after week. Each individual session then carries what genuinely changes from one week to the next: who has booked, how many places remain, and who is currently on the waiting list for that particular date. Keeping these three things apart protects you from two different headaches. Edit the definition once — a new price, a corrected description, a different room — and every future session updates automatically, without you opening fifty separate entries by hand. And when something local goes wrong on a single date, your regular teacher is away or the room is double-booked, you can cancel or reassign that one session alone, while every other date on the timetable carries on exactly as scheduled.

Why capacity lives on the session, not the class

A weekly class does not really have one capacity — it has a capacity for each night it runs, because a room holds what it holds on that particular evening, regardless of how many people showed up the week before or will show up the week after. BrightStar treats capacity as a property of the individual session for exactly this reason: this Tuesday's count of places taken and places remaining is entirely separate from next Tuesday's, and neither one affects the other. This is also why check-in happens per session rather than per class as a whole. When someone arrives at your kirtan circle, they are checked in against that specific date, so your attendance record shows who came on which night — a real, dated history — rather than one blurred running total for 'the Tuesday class' in general.

What happens when a session fills

Once a given date reaches its capacity, anyone who books after that point joins that session's waitlist specifically — not a waitlist for the class in general. This distinction matters in practice. If your Tuesday kirtan circle is full but this Thursday's sound healing session, or even next Tuesday's circle, still has open places, a person waiting for this Tuesday is not quietly bumped into one of those other openings; they are waiting for this date, and only this date. Cancellations follow the same logic. If someone drops out of this Tuesday's session, the place that opens up goes to whoever is next on this Tuesday's waitlist — not to someone waiting on a different day entirely. Capacity, bookings and the waitlist all travel together with the session, never with the class as a general pool.

The schedule view is the page you will actually live in day to day, because a weekly timetable reads as a picture of your week rather than a list of fifty near-identical events to scroll through one by one. Build each class once, place it on the days it repeats, and let the schedule do the work of showing you what's happening Monday through Sunday at a glance, session by session, without you reconstructing the week from separate entries.

Changing or cancelling a single date without touching the rest

Because the class definition and its individual sessions are kept separate, you are never forced to choose between changing this one Tuesday and changing every Tuesday from now on. If your regular teacher is unavailable for a single date, someone else can cover that one session without touching the class record at all — the following week reverts to your usual teacher automatically, with nothing further to undo. If a date needs to be cancelled outright, for a holiday or a room conflict, cancelling it removes only that one occurrence from the timetable. Every other date keeps its own bookings, its own capacity, and its own waitlist exactly as they were before. Nothing about editing or cancelling a single session reaches backward into past dates or forward into future ones beyond the change you actually made.

Common questions

Can I run a weekly class on BrightStar without creating a new event every week?

Yes. BrightStar's recurring class schedule lets you define a class once — its name, teacher, location, duration, price and capacity — and place it on a weekly timetable. Each occurrence is generated from that single definition rather than built by hand.

Read more

This matters most once a class has been running a while: instead of hunting through dozens of similar-looking events to find last month's booking, you have one class record with a season's worth of sessions attached to it. Update the price or description once and it applies to every future date, while past sessions keep the details as they were on the night.

How does capacity work for a recurring class?

Capacity applies per session on BrightStar, not to the class as a whole, because a room holds a fixed number of people on any given night. Each date has its own count of places taken and places remaining.

Read more

This is why a class that's usually full doesn't automatically block a quieter week, and vice versa. A holiday Tuesday with fewer regulars showing up doesn't carry any extra headroom into the following week, and a fully booked night doesn't reduce the room's capacity for the next one — each date starts fresh with the same size room and its own count.

What happens when a class session is full?

Further bookings go to that session's waitlist. Because the waitlist belongs to the individual session rather than to the class, a cancellation on one date frees a place for whoever is waiting on that specific date.

Read more

In practice this means the waitlist behaves the way people expect a waiting list at a physical door to behave: it's tied to the specific night, not to the class as an abstract idea. Someone who couldn't get into Tuesday's circle isn't automatically considered for Thursday's session or next week's Tuesday — they're simply first in line if a spot opens on the date they actually asked for.

Can I change or cancel a single class session?

Yes. The class definition and the individual sessions are separate on BrightStar, so one date can be cancelled or covered by a different teacher without changing the class itself or disturbing any other date on the timetable.

Read more

This separation is what lets a single sick day, holiday, or scheduling conflict be handled as a one-off rather than a disruption to the whole term. You cover or cancel the affected date, the change is visible on that date alone, and every other session on the calendar — past, present or future — keeps its own bookings and waitlist untouched.

Does changing the class definition affect sessions that already happened?

No. Editing the class definition changes the class going forward, updating future sessions on the schedule, but it does not rewrite sessions that have already taken place.

Read more

Each past session keeps a record of what was true on the night it happened — who was booked, how many places were taken, who checked in — so a later change to the price, description or capacity in the class definition has no effect on that history. Only sessions still ahead on the timetable pick up the update.

Why does attendance get recorded per session instead of for the class as a whole?

Because check-in happens per session, attendance is recorded against the specific date someone actually attended rather than lumped into one running total for the class. This keeps your history of a weekly class organized by date instead of scattered or blurred together.

Read more

Without this, a weekly class that's been running for a year would leave you with a single combined attendance figure and no way to tell which nights were full and which were quiet. Recording check-in per session gives you a dated history: you can tell that this particular Tuesday had a certain number of people, distinct from every other week.

Ready to get started?

Create your first event on EveryEvent Rio de Janeiro — it’s free.