Features · Student management
One record per student. Everyone in sync.
One record per student that everyone who needs it can see, and nobody else can.
- Enrol once: contact, batch, join date and history
- Batches drive attendance, fees and trainers
- Role-based access for admins, trainers and parents
The problem
What goes wrong without one
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.
Spreadsheet + forms + memory
- The same details in three places, disagreeing
- Batch changes never reach the old batch list
- Access is all or nothing for trainers
- The academy slows down when one person is on leave
With PartApp
- One record, updated once, everywhere
- Moving batch updates attendance, fees and trainer
- Each role sees exactly what it should
- The knowledge lives in the system, not a person
A phone number is updated in the WhatsApp group but not on the form. A student changes batch and the old list is never corrected. And either a trainer can see everything, including fee history and family contacts, or they see nothing and have to ask.
How it works
From admission form to a living record
- Enrol the student
Contact details, batch and join date, entered once.
- Allocate batches
One or more batches. Each sets the attendance list, fee and trainer.
- Access by role
Trainers see their batches, parents see their child, admins see the academy.
- History accumulates
Attendance, fees and changes build up on the same record over time.
What you get
How PartApp handles it
Enrolment that produces a record
A student is enrolled once and exists from then on. Later changes update the record rather than creating a second version of the truth somewhere else.
Batch allocation
Batches drive nearly everything: who is on the attendance list, what fee applies, which trainer is responsible. Moving a student updates those consequences.
Role-based access
Admins, trainers, students and parents each see what is appropriate. This is what makes it safe to give trainers an account at all.
Records that survive people leaving
Staff change. When the record is in the academy's system rather than someone's phone, a trainer leaving does not take the batch's history with them.
Why one record matters more than it sounds
Every other feature reads from the student record.
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 of them, which is exactly what does not happen when the same information lives in a spreadsheet, a form and someone's phone.
It is also what makes an academy transferable. An academy that lives in one person's head cannot easily add a branch, hand over administration or survive that person taking a holiday. An academy that lives in a system can.
Connected
How it fits with the rest of PartApp
Student management is the foundation. Batches decide attendance lists, fee structures attach to batches for fee collection, and parent accounts make parent communication possible. New students arrive from lead management.
Who it's for
Where it matters most
Many subjects and batches at once.
Students across multiple styles and levels.
Grown past what one person can hold in their head.
Common questions
Can trainers see everything about a student?
What happens to our records if a trainer leaves?
Can a student be in more than one batch?
A free, personal walkthrough with your own batches. 30-day free trial, no credit card.
