Ask an operator what their booking system does and you will hear about the timetable. Ask what frustrates them about it and you will hear about no-shows, waitlists that never clear, and a class that looked full but ran with six people in it.
Those are not calendar problems. They are capacity problems, and a system designed as a diary handles them badly.
Booked is not the same as attended
The gap between the two is where the cost sits. A no-show occupies a place that somebody on the waitlist would have taken, so one absent member can cost you two: the one who did not come, and the one who was turned away.
Most systems record the booking well and the attendance poorly, if at all — often because marking attendance is a job for an instructor who is busy running the class. If capture takes more than a moment at the door, it will not happen reliably, and without it the whole picture is guesswork.
The waitlist is the useful part
A waitlist is usually treated as a courtesy. Handled properly it is the mechanism that recovers the capacity a no-show would waste:
- Release places automatically when someone cancels, without anyone intervening.
- Give the next person a real window to accept, then move on. A place offered overnight to somebody asleep helps nobody.
- Stop offering once the class has started, which sounds obvious and is frequently wrong in practice.
Get that loop right and utilisation improves without adding a single class.
Cancellation windows are a design decision
Every operator sets a window — cancel more than n hours ahead and the place is released cleanly. The number matters less than two things around it:
Reminding at the right moment. A prompt that arrives before the window closes converts a no-show into a released place. One that arrives after it does not.
Making the consequence visible and fair. If there is a penalty, people should know the rule before they break it, and be able to see their own record. Rules enforced invisibly feel arbitrary and cost you goodwill for very little gain.
What to measure
Timetable software reports on bookings. Capacity management needs:
- Attendance against capacity, by class, instructor and time slot.
- No-show rate, by class and by member.
- Waitlist conversion — how often a released place was actually taken.
- Repeat attendance, which is the difference between a popular class and a class a few people book habitually and skip.
Those four together answer the question that actually matters: which classes are worth running, at what time, with whom.
The connection to retention
There is a link operators often miss. Booking and not attending is one of the earliest signals that a member is drifting — stronger than simply not booking, because it shows intent that did not survive contact with the day.
That only surfaces if bookings and attendance live on the same record. When they sit in separate systems, the signal is invisible until it becomes a cancellation.
We built The Performance Centre with availability, attendance and progress on one record for exactly that reason.
If your timetable is full and your classes are not, get in touch, or read more about software for health and fitness.