One student record, not five copies of one

Admission to alumni on a single record, with the family, documents and history attached. Every other module reads from it rather than keeping its own version.

Book a demo

What this usually looks like today

A family enrols. Their details get typed into the admission register, again into the fee system, again into the attendance sheet, and a fourth time when the ID card is made. Each copy is now free to drift.

Six months later somebody updates a phone number in one place. The office calls the old one. A sibling joins and the address is entered differently, so the two children are no longer visibly related.

When the student record is the single record, none of that happens. Update the number once and every module that needs it has it.

What it handles

Grouped by the job it does rather than listed as one long set of features.

Admission and enrolment

Enquiry through to enrolled student without re-entering anything, including the family details captured at the front desk.

Family and guardians

Parents and guardians linked to every child they are responsible for, so siblings are visibly one family.

Documents on file

Birth certificates, previous transcripts, medical notes and photographs stored against the student rather than in a cabinet.

ID cards and certificates

Built from a template against the same record, so a reprint does not need the details typing again.

Promotion and transfer

Move a student up a year, between sections or between campuses, with the history following them.

Complete academic history

Classes attended, results achieved and fees paid, in one place, years after the fact.

Withdrawal and leavers

A structured exit that closes the fee position and stops the student appearing on live registers.

Search that finds people

By name, roll number, family, class or admission year, without knowing exactly how it was typed.

Enrolment reporting

Headcount by class, section, gender or campus, current rather than as of the last export.

The cases most systems get wrong

The sibling nobody linked. Two children, two admission forms, two slightly different spellings of the same address. Nobody knows they are one family, so the sibling discount is never applied and the office phones twice.

The student who left and came back. Rejoining in a later year creates a second record, and the earlier history is stranded on the first. Their transcript is now in two halves.

The name spelled three ways. One spelling on the register, another on the certificate, a third on the fee voucher. At transcript time somebody has to decide which is correct.

The guardian who is not a parent. An uncle, an elder sibling, a sponsor. Systems that assume "father and mother" force the office into workarounds that break the contact list.

These are the cases worth testing in a demo. Bring the messiest one you have.

Who touches it, and what they see

The same records, presented differently depending on the job.

The front office

Creates and maintains the record, handles admissions, prints documents and answers the questions families ask.

Teaching staff

See the students in their own classes - who they are, who to contact, what they need - not the whole institution.

Families

See and correct their own details, which is how a contact list stays current without the office chasing.

Sensitive fields

Identity documents and contact details can be withheld from roles that have no reason to see them.

What it shares records with

The student record is what every other module is about. An admission creates the fee position, puts the student on the attendance register and adds them to the examination roll, all from the one entry at the front desk.

Transport assigns them a route. The library issues against their name. Results attach to their history. A withdrawal closes all of it at once rather than leaving them live in three registers nobody remembers to check.

That is what makes the difference between a student database and a student information system: the record is the institution's spine, not one more list.

An institution that fixed admissions first

What changed when enquiries stopped living in a paper register.

School · 500 students · PK

Admissions enquiries that stop falling through

Walk-in and phone enquiries moved from a paper register to a tracked list that turns into an admission.

Tracked
Every enquiry
No re-entry
Enquiry to admission
Read the full story

Questions we get asked

Can we import the student records we already have?
Yes, from spreadsheets or your current system during setup. We check the import with you before go live, because a silent mismatch in a class list or an opening fee balance is far more expensive to unpick in month three.
How are siblings handled?
Children are linked to the same family, so the office sees them as one household rather than as unrelated records that happen to share an address. That is what makes sibling concessions and single family payments possible.
What if a student leaves and rejoins later?
They keep the same record rather than gaining a second one, so their earlier results and history are still attached. A transcript covers the whole time they were with you.
Can the guardian be somebody other than a parent?
Yes. Guardians are recorded by their relationship to the child rather than assumed to be a mother and father, which matters more often than most systems allow for.
Who can see a student's personal details?
Teaching staff see the students in their own classes rather than the whole institution, and sensitive fields such as identity documents can be withheld from roles that have no reason to see them.
Can families update their own details?
Yes, through the family portal. That is how a contact list stays current without the office chasing everybody once a year.

Bring your messiest record

The duplicated sibling, the returning student, the name spelled three ways. We would rather show you that than a clean demo record.

Book a demo