How to track group sessions, bootcamps, and classes
5 min read
Group sessions are where most tracking systems quietly fail. The maths is unforgiving: a twelve-person bootcamp run three times a week is thirty-six individual records a week if you track people properly, and nobody sustains that by hand. So the record degrades into a class headcount, and the moment you need to know whether a specific person actually attended — or paid — the answer is not there.
The two failure modes
Aggregate-only: the class is one entry with a number attached. Cheap to log, useless for billing, retention, or answering "how many sessions do I have left?"
Fully manual: every participant logged individually. Accurate in theory, abandoned in practice, usually within a month.
One action to log, many records produced. The cost should scale with the number of classes you run, not the number of people in them.
What a group record should hold
The group entry is the delivery unit. The participant entries are the business units. Both need to exist, and the participant entries need to carry everything a one-to-one session would.
Attendance per person, not just a headcount. The regular who has missed three weeks is the one about to stop paying.
Payment state per person. Group members frequently pay on different terms — some monthly, some per class, some on a block.
Group sessions counted in each participant’s total session history, so their record is complete regardless of how the session was delivered.
Recurring series
Nearly all group work repeats. Setting up each week by hand is the second-biggest reason group tracking gets abandoned, after per-participant entry. A recurring series should populate the calendar forward, with each occurrence still independently editable — because the exceptions are the whole point. Someone misses a week, a class gets cancelled for a bank holiday, one participant drops out halfway through the block.
A recurrence model that cannot handle a single-occurrence exception will be worked around, and the workaround is always some form of manual duplication.
Mixed practices
Most group-running practices are not purely group. A trainer runs three bootcamps and eight one-to-one clients; a physio runs a rehab class alongside a normal caseload. The important property is that both kinds of session land in the same client history. If a participant’s record only shows their one-to-one sessions and their class attendance lives somewhere else, you are back to reconciling two systems.
A practical setup
Add every participant as a normal client first. Group membership is a property of the session, not a separate kind of person.
Create the group session and attach the participants.
If it repeats, set the recurrence once and let the series fill the calendar forward.
Log each occurrence as it happens, marking anyone absent at the same moment. Absences recorded later are absences recorded wrongly.
Set payment terms per participant, not per group, so the person paying monthly and the person paying per class are both correct.
Done this way, a weekly twelve-person class costs one action per week and produces twelve maintained records — which is the only version of group tracking that is still running six months later.
Blockday logs a group session once and tracks attendance and payment per participant.
