Most academies do not have a student database. They have a spreadsheet, a WhatsApp group, a stack of admission forms, and one person who remembers the rest.
What goes wrong without one
Information gets duplicated and then disagrees with itself. A phone number is updated in the WhatsApp group but not on the form. A student changes batch and the old batch list is never corrected. When the person who remembers everything is on leave, the academy slows down.
It also makes access all-or-nothing. Either a trainer can see everything including fee history and family contact details, or they can see nothing and have to ask.
How PartApp handles it
Enrolment that produces a record
A student is enrolled once and exists from then on: contact details, batch, join date and history in one place. Later changes update the record rather than creating a second version of the truth somewhere else.
Batch allocation
Students belong to batches, and batches drive nearly everything else — who is on the attendance list, what fee applies, which trainer is responsible. Moving a student between batches updates those consequences rather than requiring you to remember them.
Role-based access
Admins, trainers, students and parents each see what is appropriate to them. A trainer sees their batches and can mark attendance. A parent sees their own child. An admin sees the academy. This is what makes it safe to give trainers an account at all, and it is the difference between a shared spreadsheet and a system.
Records that survive people leaving
Staff change. When the record is in the academy's system rather than in someone's phone, a trainer leaving does not take the batch's history with them.
What it connects to
Student management is the foundation the rest sits on. Batches determine attendance lists, fee structures attach to batches for fee collection, and parent accounts are what make parent communication possible.
Who this matters most for
- Coaching institutes managing many subjects and batches at once
- Dance academies with students across multiple styles and levels
- Tuition centres that have grown past what one person can hold in their head
Why one record matters more than it sounds
The argument for a single student record is not tidiness. It is that every other feature reads from it. If a student's batch is wrong, their attendance list is wrong, their invoice is wrong, and their parent gets the wrong notifications. Fixing the record in one place fixes all three, which is precisely what does not happen when the same information lives in a spreadsheet, a form and someone's phone.
This is also what makes an academy transferable. An academy where the knowledge lives in one person's head cannot easily add a branch, hand over administration, or survive that person taking a holiday. An academy where it lives in a system can.
Common questions
- Can trainers see everything about a student?
- No. Access is role-based: trainers see the batches they teach and can mark attendance, parents see their own child, and admins see the academy. That is what makes it safe to give trainers their own account.
- What happens to our records if a trainer leaves?
- The records belong to the academy, not to the person who entered them. A trainer leaving does not take the batch history, contact details or attendance record with them.
- Can a student be in more than one batch?
- Yes. Students commonly attend more than one batch, for example a second style or level, and attendance and fees follow each batch correctly.