Timetable, assignments, results, attendance and notices. One place, on the device they already carry.
Book a demoStudents do not choose school software, so a student portal is usually the least examined part of a purchase. It is also the part with the largest number of users, and the one that decides whether the family portal gets used at all.
The test is not whether the portal has features. It is whether a student opens it without being told to. That happens only when it answers questions they actually have: what is due tomorrow, what room, what did I get, am I short on attendance.
A portal that requires a laptop, a login they have forgotten and three clicks to reach the timetable will be abandoned in the first fortnight, and the institution will conclude that students are not interested. They are. The portal was.
Ordered by how often a student actually opens it.
Today and this week, including changes, without asking somebody.
What is set, what is due, and what has been submitted.
Marks as they are released, alongside the datesheet they relate to.
Their own record, so a shortfall is visible early rather than at the point it becomes a problem.
Joined from the same timetable that shows the in-person lessons.
What is borrowed, what is due back, and what is available.
What was announced, still there next week rather than gone with the assembly.
Route, stop and residential information where those apply.
What is outstanding, for older students who handle their own payments.
Student portals fail in ways that are obvious the moment a real student uses one, and invisible in a demo.
The forgotten password on results day. The one day the portal matters most is the day the most people cannot get in. If a reset needs an office visit, the office spends results day doing password resets.
The timetable that is right on paper and wrong today. A cover lesson or a room change that reaches the staff room but not the student portal teaches students that the portal cannot be trusted. After that they stop checking it, and no amount of feature work brings them back.
The assignment due at midnight. Submission at 23:58 from a phone on a weak connection is the realistic case, not the exception. A portal that only works well on a laptop on a good connection has designed for the wrong student.
The student who is short on attendance and does not know. By the time a letter goes home it is usually too late to fix. Showing the student their own figure early is the cheapest intervention available.
A student portal is the easiest place to leak something by accident.
A student sees themselves. Not classmates, not another year group, not a list.
Staff records, payroll and internal notes are not part of the student portal in any form.
Some institutions show fee status to older students and hide it from younger ones. That is configurable rather than fixed.
Communication runs between a student and the institution, not as an open channel between students.
Everything a student sees is the same record the teacher entered and the same record the family sees. There is no separate student-facing copy that has to be published, which is what removes the usual lag between a mark being entered and a student being able to see it.
For families with more than one child, the family portal reads these same records and adds switching between children, rather than being a different system with its own version of the truth.
The modules this portal reads from and writes to.
Give a real student the portal on their own phone and watch what they open first. That tells you more than a feature list will.
Book a demo