Student records and admissions, in one continuous record.
In most schools a student exists in several places at once. The admission form is in a file cabinet, the contact number is in a class register, the transfer certificate is in a folder on somebody’s desktop, and the mark record is in a different register again. Nothing is wrong with any one of those, but together they mean a simple question — who is this child, who do we call, what have they done here — takes four people and twenty minutes to answer.
- Complete student profiles with guardian and contact details
- Admission workflow from enquiry to enrolled
- Document upload against each student
- Import an entire school from a spreadsheet in minutes
- Search and filter across the whole student body
One profile that follows the student the whole way
A student record in e-SchoolBase starts at enquiry and stays with the same person until they leave. Guardian names and contact numbers, address, date of birth, admission number, class and section history, and uploaded documents all hang off that one record. When a class teacher needs a parent’s number during the school day they open the student, not a register. When the office needs to reissue a document at the end of the year, the original is already attached where it was uploaded.
Admissions as a sequence, not a stack of forms
The admission workflow moves an applicant through the stages your office already uses — enquiry received, form submitted, documents verified, admitted, enrolled into a class and section. Because each stage is recorded against the applicant, the pipeline itself becomes visible: how many enquiries are outstanding, which applications are waiting on a document, which admitted students have not yet been allocated a section. That visibility is usually the thing schools lose when admissions season gets busy.
Bring the school you already have, from the spreadsheet you already have
Nobody should retype a school. Student data imports from a spreadsheet: you map your columns to the fields once, review exactly what will be created before anything is written, and confirm. A school of any size can be set up in minutes rather than keyed in one record at a time, and the same import path is there later when a new intake arrives as a list rather than as individual forms.
Finding one student among two thousand
Search and filtering run across the whole student body rather than class by class. You can find a single child by name or admission number, or narrow to a group — a section, an intake year, students missing a particular document — and act on the result. The point is not the search box itself; it is that the office stops keeping a private parallel spreadsheet just to answer questions the main system could not.
About students & admissions.
The modules this one leans on.
- Structure
Classes & Sections
Define your school once — classes, sections, capacities and class teachers — and the rest of the system follows that structure for the whole session.
Learn more → - People
Staff
Teaching and non-teaching staff records, with the roles and permissions that decide what each person sees when they log in.
Learn more → - Paperwork
Reports
The documents schools are asked for again and again, generated on demand instead of assembled by hand the night before.
Learn more →
See all eight modules on the platform overview.
Spend less time on administration. More on students.
Start with one class and see how the session works end to end — admissions through marksheets — before you commit to anything.