When to Stop Running Classes From a Spreadsheet
If you run classes, you may keep a whole term in a single file: several classes across a few evenings and a Saturday morning, six to eight places in each. There is a tab per class, a tab called Waiting List, and a tab of bank transfers pasted out of the account.
Then a parent emails to say her daughter is moving to the Wednesday group. Wednesday reads full, and whether that is true depends on whether the child who stopped coming in week one was ever taken off. Someone opens the waiting list, ordered by when each name was typed rather than by when each family asked. By the time the reply goes out, a second parent may have been told the same place is hers.
A registration spreadsheet stops working at the point where the file can no longer answer the questions people put to it: is that class full, who is next on the waiting list, who has paid and who turned up last week. Once a place is released and nobody is sure whose it is, or attendance can only be counted after the term has ended, the sheet has become a record of what happened rather than a system for running the next session.
When should you stop running classes from a spreadsheet?
Not at a particular number of students; plenty of organizations run three classes from a file for years. The threshold is behavioral, and four signals mark it.
The first is the second copy. When a coach keeps a paper attendance sheet, or the receptionist a notebook of who has settled up, the shared file has stopped being trusted, and what follows is reconciliation rather than administration.
The second is the delay before a confident answer. If is Thursday's beginners class full? cannot be answered while the caller is on the phone, the file is behind the organization rather than in front of it.
The third is the question nobody asks anymore — attendance across the term, or how many families came back — because finding out costs an afternoon.
The fourth is the double booking, which comes from two people editing a shared file minutes apart. The mechanics are those we set out in why double bookings keep happening, with the difference that a class runs weekly, so the error repeats.
What a registration spreadsheet stops being able to answer
It is worth writing the questions down, because a file answers the first and none of the rest.
How many places are left in Wednesday at five? Who is next in line for that class specifically? Has this family paid for this term, or is the payment on screen last term's? Which children were present last week, and which have missed three in a row?
A sheet can hold all of that. What it cannot do is keep the answers current while five people act on them independently. The gap is not storage but enforcement: nothing stops a ninth name being typed under a heading that says eight. Capacity that holds, rather than capacity written in a cell, is the first thing software for managing classes and registrations provides that a file cannot.
Waiting-list order and who gets a released place
A waiting-list tab grows one typed name at a time. Some appear twice, because a family will put a child down for two possible evenings. The order is the order of typing.
When a place comes free the usual process is: scan the tab, pick a plausible name, send an email, wait. Every week that place sits empty is a session you have already paid for, in pool time, room rental, or an instructor's hours, whether the spot is filled or not.
Worse, a family who has waited for weeks watches a place go to someone who asked later, and remembers it at renewal. A waiting list that works is ordered per class and timestamped when the family asks rather than when a name is typed. A released place goes to the top of it with an offer that expires — after forty-eight hours, say — and moves on by itself if it is not taken.
Late enrollments, transfers and drop-outs mid-term
Terms do not stay as they were sold. A family joins in week four and pays for seven sessions rather than eleven. A child moves up a level in week six and takes a place on a different night. Two families drop out after the first session and want a refund.
Each is a small piece of arithmetic and a change of state, done by hand in three places: the roster, the payment tab, and the attendance sheet the coach prints on Friday. The attendance sheet is what trips people up: any change made after Friday afternoon stays invisible for a week, so the coach marks a child absent who transferred out, and nobody at all for the child who joined.
What a term needs is one roster with a date on every change, so each week's attendance sheet shows who was enrolled that week, and a prorated fee worked out from the sessions remaining.
Attendance you cannot see until the term has ended
Paper attendance sheets are checked off, collected, and put in a folder. They are counted at the end of term, if at all, by which point everything useful in them has expired.
Go through that folder at the end of a term and you may find a class that ran well under capacity for weeks, or children who missed half their sessions with no follow-up. Both facts were there to see by mid-term.
Attendance marked at the session, on a phone, by the person taking the class, changes what is possible. Three consecutive absences raise a flag while a phone call still helps. A class averaging sixty percent can be merged or moved to a better slot for the spring. Make-up sessions are tracked against the child rather than settled at the poolside.
Payments and reminders that depend on someone remembering
Bank transfers arrive with memos like SWIM, JAKE, and the last name of a parent whose child is registered under a different one. Reconciling means matching a bank export against a roster by eye.
Chasing works the same way. No rule sends a reminder seven days before term; a person intends to, gets to it late, and sends it to the whole list because filtering out those who have paid takes longer than the apology afterward. A handful of unresolved payments adds up across a term, and the follow-up happens at the door in front of other parents.
Payment taken at registration removes most of this. A place is not held until it is paid for, reminders go out on a schedule rather than on a good intention, and reconciliation mostly disappears because payment and registration were one action. That is the ordinary behavior of taking bookings and payment online. Test a payment and a reminder yourself before the first family registers.
What running a term this way costs in hours
Keep a tally through one term, split four ways.
Enrollment covers inquiries, taking names, and building a roster for each class. Weekly upkeep covers transfers, absences, waiting-list emails, printing attendance sheets, and answering did you get my payment? Note it each week and multiply by the weeks in the term. Reconciliation and chasing come third. End-of-term tallies, refunds, and the mailing list for the next term come fourth. Add the four, and you have the hours one term costs before anyone stands by a pool.
Multiply by the terms in your year, and put your own hourly cost for admin time against it. Then look at how much of it is thinking. Often much of it turns out to be retyping something already held in the same file.
What a class or event system has to do instead
The requirement list is shorter than it looks.
Capacity is enforced at registration rather than checked afterward. Waiting lists are per class, ordered by when the family asked, with offers that expire. Attendance sheets exist per session, can be marked from a phone at the poolside, and roll up into a term view. Payment status lives against the person. Families can change a class and pay without sending an email. And a term can become the next term without being rebuilt.
That is the working definition of a class management system. Where the same organization runs workshops, open houses, or school-break camps, those are the same shape with a single date, and an event registration system holds them alongside each term's classes rather than in another file.
Moving a term's worth of registrations across without retyping
The objection is usually the same: there are dozens of children in that file and nobody is typing them in again.
Nobody has to. The existing file is the starting point. A tab per class can become a class with a capacity and a schedule, the columns of names and contact details the registrations inside it, and the waiting-list tab an ordered queue. You review what was built, correct the mapping where it has guessed wrongly, confirm the capacities, try a registration on a full class, and publish. The upload is a snapshot, and the original file is untouched at the end. That is the route in turning an enrollment spreadsheet into a booking system.
Do it in the gap between terms, when the roster is stable and nothing is mid-transfer, and keep the old file as an archive rather than a fallback: a fallback gets edited, and then there are two versions of the truth again.
What changes is smaller than a systems project sounds. Whoever answers the phone can say yes or no while the caller is still on the line. A released place goes to the family who waited longest. The coach's attendance sheet is right on Saturday morning because it was right on Friday night. And in week five, rather than at the end of term, you can see which class is emptying while there is still a term left to act.


