THE RECORD EVERYTHING
ELSE READS FROM.
Before a school can do anything interesting with its data, it has to agree what a student is: who they are, who is responsible for them, which year they are in, which class group, and which academic year the whole thing sits inside. Skoolarz administration is that agreement, made once.
ONE PROFILE, MANY RELATIONSHIPS.
A student is not a row in a list. They have guardians who may have other children in the school, a class group that changes each year, a bus route, a fee plan, a timetable and a history. Skoolarz models those relationships explicitly rather than flattening them into columns.
- Student and guardian profiles as separate, linked records — a parent with three children has one account and three links.
- Academic years and terms as first-class settings, so "this year" means the same thing to attendance, grading and finance.
- Class groups that carry their own schedule, roster and reports.
- Validation at the point of linking, so a mistyped guardian does not quietly become a second parent account.
WHAT THE REGISTRAR ACTUALLY GETS.
Bulk user import
Bring in students, parents, teachers and drivers from CSV, with a dry run first and a review queue for the rows that need a human decision.
Printable credentials
Generate account details for a whole cohort, or one student, as a printable handout — because not every family is reachable by email on day one.
Parent access invitations
Guardians set their own password through a tokenised link, so the office never has to hold or reset a family's credentials by hand.
Academic calendar
Years, terms and their boundaries defined once and respected everywhere — attendance rollups, grade windows and fee schedules all key off them.
Configurable school identity
Your logo on the login screen, dashboards, printed schedules and finance documents. It is your school; it should look like it.
Attributable changes
Who edited a record and when, retained as an audit trail. This protects the school far more than it protects us.
THE IMPORT IS EASY.
THE IDENTITY IS HARD.
Every school we onboard has the same mother recorded four different ways across four spreadsheets. Imported naively, she becomes four parent accounts, each seeing one child, none seeing the family.
So the importer reconciles against an identity key you choose — usually the national ID on the enrolment form — before it creates anything, and pushes ambiguous rows into a review queue instead of guessing.
A migration that produces zero exceptions has not solved the problem. It has hidden it.
RELATED, AND WORTH READING.
Parent portal
Where those guardian links become one login covering every child a family has in the school.
Explore the portalAttendance
The first module that depends entirely on getting class groups and the calendar right.
Explore attendanceSecurity & hosting
Where student records live, who can see them, and what happens if you leave.
Read the detail