School management software built by people who run a school platform

What school software gets wrong, and why

Most school management systems are designed by people who have never stood in front of a class at nine in the morning with twenty children waiting. The result is software that is technically complete and practically unusable, and the symptom is always the same. Teachers fill in the records at the end of the day from memory, or a fortnight later before an inspection, and the data becomes a work of fiction that management then uses to make decisions.

The single most important requirement in a school system is that recording something takes seconds. Not a minute. Seconds. If entering a lesson record requires opening a menu, selecting a class, finding a student, choosing a subject and typing into three fields, it will not happen reliably. On our own platform a teacher can log a recitation in around five seconds, and that number is not a marketing figure, it is the design constraint the whole interface was built around.

The second thing generic systems miss is that parents will not log into a portal regularly. They intend to, and they do not. Information has to travel to parents rather than waiting for them, which means notifications by email, message and mobile alert, sent automatically when something matters, with the school controlling exactly what goes out and when.

The third is that school leadership needs answers rather than screens. How many lessons were missed this month. Which classes are behind on the curriculum. Which children have attendance patterns worth investigating. Which staff have incomplete records. Those questions should be answered on one page, not assembled by an administrator on a Friday afternoon.

The modules a school system usually needs

Requirements vary between schools, madrasas, academies and tuition providers, but a recognisable core appears almost every time. Student and family records with contact details and relationships. Classes and groups, which are rarely as simple as one child in one class. Staff accounts with permissions that reflect real responsibility. Attendance, with the ability to record quickly and to alert parents automatically.

Then comes the academic side. Lesson and progress records, homework, subjects and curriculum completion, assessments and remarks. Around that sits the operational layer, meaning calendars and holidays, events, communication with families, document storage and the reports that governors, funders or inspectors expect. Where an organisation runs several sites, a level of oversight above the individual school becomes necessary so that standards can be compared and supported.

Permissions and privacy in an education setting

School data is sensitive and the permission model deserves more attention than in almost any other kind of business system. A teacher should see their own classes. A head of department should see their subject across classes. Administration should see the operational picture. A parent should see their own children and absolutely nothing else, including the names of other children in a shared list.

We enforce those boundaries at the database query level rather than by hiding elements in the interface, and we record who accessed and changed what. Schools also need sensible handling of the awkward realities, such as separated parents with different access rights, students who move between classes mid year, and staff who leave and whose accounts must be closed cleanly without deleting the records they created.

Mobile applications for teachers and families

A school system that only works on a desktop computer in the office will not be used by teachers who move between rooms or by parents who check their phone in the evening. We build native Android applications in Kotlin and native iOS applications in SwiftUI, connected to the same backend through a REST API so the rules stay consistent across web and mobile.

Push notifications matter enormously here, because they are how attendance alerts, homework reminders and school announcements actually reach families. We build that infrastructure with Firebase Cloud Messaging and give the school control over what is sent, so parents receive what is genuinely useful rather than a stream that gets muted within a week.