The three tools every training centre rebuilds in spreadsheets
The spreadsheet is not the problem. The problem is the moment there are two of them and nobody knows which is current.
Training centres are one of the clearest cases of software being replaced by determination. Every one we have worked with runs the same three things in spreadsheets, and every one hits the same wall at roughly the same size.
The three, in the order they break
1. Enrolment
It starts as a sheet of names and turns into the system of record for money. Who paid, who paid half, who was promised a discount by someone who has since left. It works until two people edit it in the same afternoon, and then it quietly stops being true while continuing to look authoritative.
2. Attendance
Usually a printed sheet, later typed in. The typing is the failure point, because it happens days later from memory, and the resulting data is exactly wrong enough to be useless for the one question worth asking: which students are about to drop out.
3. Certificates
A template document, filled in by hand, one file per graduate. This is the one that produces the awkward phone call two years later when someone needs proof they completed a course and nobody can find the file, or worse, finds three versions with different dates.
Why a spreadsheet is genuinely the right first answer
It costs nothing, everyone can already use it, and it can be changed in the middle of a working day. Any advice that starts with buying enterprise software before you have fifty students is advice from someone who has not run a training business.
The question is not whether to start in a spreadsheet. It is knowing the specific moment it turns from an asset into a liability. There is one reliable signal: the day someone asks which copy is the current one.
What replacing it actually needs
Far less than most vendors will sell you. A working system for a training centre of this size needs four things, and a full learning-management platform is not one of them:
- One record per student that the whole team reads from, rather than a file each.
- Attendance captured at the session, on a phone, by whoever is in the room.
- Payments visible against the student, without becoming accounting software.
- Certificates generated from the record, so they cannot disagree with it.
That is a week of work, not a quarter. The reason it usually turns into a quarter is scope: someone asks for a mobile app, a parent portal and an integration nobody has needed yet, and the useful version dies waiting for the complete one.
Build the thing that removes the current pain. The roadmap can wait until something is actually running.
The pattern is not specific to training
Clinics do it with appointments, gyms with memberships, agencies with client reporting. Same shape every time: a spreadsheet that quietly became infrastructure and now cannot be changed without someone's afternoon disappearing. Research on large technology projects consistently finds that overruns come from scope and unclear ownership rather than from technical difficulty, a theme running through McKinsey Digital's published work on delivery.
It also explains why we quote in days. A system scoped to one week has to be about the actual bottleneck, because there is no room in a week for anything decorative.
If you run a training business
Ask the three questions in order. Can any two people tell you the same current enrolment number? Do you know today which students missed the last two sessions? Could you produce a certificate for someone who graduated in 2024 in under a minute? Every no is a week of somebody's time you are already paying for.
For a working example of the shape of a hybrid training operation, UCourses runs live sessions alongside online material, which is exactly the model that makes attendance data worth having rather than a formality.
Describe it. We build it.
Seven or twelve days, pay on delivery, a year of maintenance included. Bring the problem, not a spec.
Book a meetingRead next
A slow site is a revenue problem, not a design opinion
Load time is treated as a developer preference and argued about accordingly. It is a commercial number: it decides how much of the traffic you already paid for ever sees your offer.
Read