FitWay supports class capacity, waitlists, cancellation cutoffs, no-show rules, recurring bookings, credit restoration and instructor substitutions. Those capabilities belong together because a change to one booking can affect several people and records.
A cancellation may release a place, affect a member’s credit and create an opportunity for someone waiting. Treating it only as a calendar change leaves the rest of the operating decision unresolved.
Begin with the rule the member understands
State when a cancellation is permitted, when a credit is restored and how a no-show is treated. Members should be able to understand the consequences before reserving a place.
The rule should also be practical for the gym to administer. A policy that staff routinely override needs review, even if the software can represent it precisely.
We have confirmed support for these controls in FitWay. We have not supplied one universal cutoff time, fee or credit policy. Each operator needs to define and test its own arrangement.
Walk through a cancellation before the cutoff
In an illustrative test, a member cancels while still within the gym’s permitted window. Check the booking record, available class capacity and the member’s credit position.
If a waitlist exists, demonstrate how that released place is handled in the actual setup. Do not assume automatic promotion, a particular order or a specific notification channel merely because a product supports a waitlist.
The useful result is a sequence everyone can explain: what happened to the booking, what happened to the place and what happened to the credit.
Then test the same action after the cutoff
Repeat the scenario after the configured deadline. Ask what the member sees, what staff can change and how any exception is recorded.
This is where policy clarity becomes operationally important. If one staff member restores a credit and another refuses under the same circumstances, the disagreement is partly about how the business applies its rules.
Use the software demonstration to make that decision explicit rather than leave it for the first disputed booking.
Recurring bookings need individual-session checks
A recurring booking creates a sequence of commitments. Staff need to understand how a change affects one occurrence compared with the series.
Test a single-session cancellation, a wider change to the series and an instructor substitution. Confirm the effects in your configuration rather than infer them from the recurring-booking label.
An instructor substitution is also a communication issue: the booking record and the member’s expectation should remain aligned. The supported workflow should be demonstrated without inventing a universal messaging behaviour.
Separate filling places from protecting them
At Coreo, targeted pre-class invitations help make open places visible to selected members. Capacity and booking controls serve a different purpose: keeping commitments and entitlements clear once people act.
Both are useful. Sending invitations cannot compensate for uncertain cancellation rules, and a precise booking ledger alone does not tell interested members that a space exists.
Review the exceptions that consume staff time
Keep a simple record of the reasons staff intervene: disputed no-shows, unclear credit restoration or confusion about recurring changes. This can be a manual operating log; it is not a claim of a built-in FitWay exception dashboard.
Use those cases to improve the policy explanation and staff training. The aim is a booking process the member, coach and administrator understand in the same way.
Booking questions
Does waitlist support always mean automatic promotion?
No specific promotion behaviour has been established here. Demonstrate the exact workflow for your setup.
Are late cancellations and no-shows the same event?
They can have different meanings and rules. Define each and confirm how the system represents it.
Related workflows: FitWay CRM and targeted class invitations.
Want to test this against your gym’s workflow?
Book a FitWay demo →