Class scheduling and registration lifecycle
This article explains how class sessions are scheduled and how student registrations move through each status from enrollment to session closure. Understanding these concepts helps you configure sessions, manage capacity, and troubleshoot registration issues.
Before you begin
- Ensure the classes module is enabled for your organization.
- Confirm that you have at least one class defined with sessions scheduled.
Session scheduling
A session is a scheduled occurrence of a class at a specific date and time. When you create sessions for a class, you can create:
- Single sessions β One session at a specific date and time
- Recurring sessions β Multiple sessions created from a recurrence pattern
Recurring sessions support daily, weekly, and monthly patterns. You can define the recurrence by end date or by a fixed number of occurrences. You can also select specific weekdays for weekly recurrences.
Each session includes:
- Date and time β Start time and duration (or end time)
- Instructor β One or more instructors; each can be designated as primary or secondary
- Room β Optional room assignment for utilization tracking
- Capacity β Total and web-specific capacity limits
Session status lifecycle
Session status reflects the current state of the session relative to the current time. Status transitions happen automatically:
| Status | When it applies |
|---|---|
| Upcoming | The session's start time is in the future |
| In Progress | The session has started but has not yet ended |
| Completed | The session's end time has passed |
| Cancelled | An admin cancelled the session explicitly |
The Cancelled status is the only status set by an admin action. All other statuses transition automatically based on time.
Capacity model
Two capacity limits apply to each session:
- Total capacity β The absolute maximum number of students. Admin (front-desk) bookings count against this limit.
- Web capacity β A lower limit applied only to self-service bookings from the Webstore and mobile app. When web capacity is reached, self-service bookings stop, but front-desk staff can still register students up to total capacity.
When a session reaches its applicable capacity limit and a student attempts to register, they are automatically added to the waitlist.
Registration pathways
Students can register for class sessions through three pathways:
- Standard registration β The student is registered immediately and receives Registered status. This is the default pathway.
- Enrollment pathway β The student receives Enrolled status and waits for admin approval before being confirmed on the roster. This pathway is configured per class.
- Waitlist β The student is added to the waitlist when the session is full and receives Waitlisted status. They move to Registered when a spot opens.
Registration status lifecycle
The following diagram shows the valid status transitions for a registration:
Enrolled (8)
βββ β Registered (0) [approved by admin]
βββ β Waitlisted (4) [approved but session full]
βββ β Cancelled (1) [admin or student cancels]
βββ β Rejected (9) [admin rejects enrollment]
Registered (0)
βββ β Signed In (3) [student attends]
βββ β Cancelled (1) [student or admin cancels]
βββ β No Show (2) [admin marks absent]
βββ β Class Cancelled (6) [session is cancelled]
Waitlisted (4)
βββ β Registered (0) [spot opens, guest promoted]
βββ β Cancelled (1) [student or admin cancels]
Signed In (3)
βββ β Registered (0) [admin undoes sign-in]
βββ β Closed (7) [session closes]
Closed (7) β Terminal β no further transitions
Cancelled (1) β Terminal β no further transitions
No Show (2) β Terminal β no further transitions
Class Cancelled (6) β Terminal β no further transitions
Rejected (9) β Terminal β no further transitions
Waitlist mechanics
When a session is full and a student registers, they are added to the waitlist in FIFO (first-in, first-out) order based on the time they joined.
When a spot opens (due to a cancellation or capacity increase), the system promotes the next student in line:
- Automatic promotion β The student is moved directly to Registered status.
- Confirmation-required promotion β When the waitlist confirmation setting is enabled, the student receives a notification and must confirm before being added to the roster.
After promotion, if the auto sign-in window is currently active, the newly promoted student is automatically signed in.
Cancellation and no-show fee mechanics
Cancellation fees and no-show fees are assessed based on a fee hierarchy:
- Session-level fee (if configured)
- Class-level fee (if configured)
- Organization-level flat fee
- Organization-level percentage fee
Fees are assessed when a student cancels a Registered registration within the configured fee window, or when a student is marked as no-show. ClassPass, GymPass, FitReserve, and BILT bookings are always exempt from cancellation and no-show fees.
Students with an enrollment-pathway or waitlisted registration are not charged cancellation fees.
Sign-in methods
Students can be signed in to a session through the following methods:
- Manual sign-in β Front-desk staff marks the student as signed in from the roster view.
- Regular auto sign-in β When enabled, the system automatically signs in registered students within a configurable time window before or after the session start time. The window is defined by the start offset and end offset settings.
- Virtual class auto sign-in β For virtual sessions, registered students are automatically signed in 15 minutes after the session's scheduled end time.
- Kiosk sign-in β Students scan a barcode, RFID card, or QR code at the fitness kiosk to sign themselves in.
Note: Regular auto sign-in (configurable time window around session start) and virtual class auto sign-in (fixed 15-minute delay after session end) are separate mechanisms with different configuration. Do not confuse the two.
Session closure
After a session completes, the system closes registrations:
- Students with Signed In status transition to Closed.
- Students with Registered status (who did not sign in) may be transitioned to No Show with fee assessment, depending on your configuration.