Attendance, results, assignments, timetable and your own payslips. The paperwork side of teaching, made short.
Book a demoA teacher does not have an administration problem. They have a time problem. Attendance takes five minutes at the start of a lesson that is forty minutes long, and it takes those five minutes every single day.
Then results season arrives and the same marks are written three times: once in a register, once on a sheet handed to the office, once into whatever produces the report card. Each copy is a chance to introduce an error, and the error is found by a parent.
The staff portal is judged on one thing: whether a teacher finishes the administrative part of their day sooner than they did before. If it does not do that, nothing else about it matters, because it will not be used.
The daily work first, the periodic work after it.
Per class or per subject, marked in the lesson rather than written up later from memory.
Their own schedule, including changes, without checking a printed sheet in the staff room.
What goes home to families, entered once and delivered to the right people.
Marks entered once and used everywhere, so the report card cannot disagree with the mark sheet.
Set, collected and marked without a separate system or a pile of printouts.
Scheduled alongside the timetable, so a remote lesson is a lesson rather than a separate arrangement.
Requested and approved in the same place the timetable lives, so cover is arranged against what is actually happening.
Their own record, available to them, without asking the office for a copy.
Development recorded against the person rather than in a document nobody reopens.
Software demos always show attendance for a class that is present, sitting still, on a normal day. Teaching is not made of those days.
The lesson that is not in the timetable. A cover lesson, a merged class, a group taken outside. If attendance can only be marked against the scheduled slot, it will not be marked at all.
The late arrival. A student marked absent at the start walks in twenty minutes later. If correcting that means going to the office, the register stays wrong, and the absence letter goes home to a parent whose child was in the room.
Marks that change after submission. A remark, a missed script found, an arithmetic error caught at moderation. Locking results at submission is safe and useless. What is needed is a change that is allowed, visible, and attributable.
The teacher who covers three sections of the same subject. They want to enter marks once, in one view, not open the same screen three times with different filters.
A staff portal that shows too much is a data problem, not a feature.
A teacher sees the students they teach. Seeing the whole school is a deliberate choice you make for specific roles, not the default.
Whether a family has paid is not a teacher's business, and it is not on their screen. That separation is intentional.
Marks and attendance carry who entered them, which protects the teacher as much as the institution when a result is queried.
Payslips, leave balance and training history are visible to them without going through the office.
Attendance marked in a lesson is the same attendance a parent sees that afternoon and the same attendance a leadership report counts at the end of term. Nobody transcribes it in between, which is the only reliable way to make those three numbers agree.
The same holds for results. A mark entered once reaches the report card, the student portal and the family portal without a separate publishing step, and a correction reaches all three the same way.
The modules this portal reads from and writes to.
Not an administrator. A teacher, on their own phone, with a real class list. That is the honest test of whether this saves time.
Book a demo