Theoperatingsystemfor schools.
Admissions, academics, attendance, finance and communication on one secure platform — where every record connects, every change is traceable, and every school configures it their own way.
Nursery → University
One platform, every stage
Role-based access
Down to the individual permission
Immutable audit
Every change, attributable
Built for every kind of institution
Nursery schools
Primary schools
Secondary schools
International schools
Vocational institutes
Colleges
School groups
Multi-campus networks
Built for a Monday morning, not for a demo.
Dense enough for an administrator who lives in it all day, and legible on the phone a teacher is holding at the classroom door. What leads is what needs attention — not a wall of counters.
Greenhill
Overview
Students
Attendance
Assessments
Fees
Messages
Term 2 · Week 6
Today at Greenhill
Students enrolled
1248
Attendance today
94.2%
Staff on duty
86
Fees collected
78%
Attendance, last 14 days
School-wide, all year groups
Needs attention
Raised by your school's own rules
Amara O.S3 Blue
Attendance below 80% for 3 weeks
Daniel K.S2 Gold
Maths average down 14 points
Grace N.S4 Blue
Fees outstanding past second reminder
Illustrative interface with sample data for one school.
Not a bundle of modules. One system, on five pillars.
Most school software grows by bolting on another module. Schoolspine starts from the platform layer — identity, tenancy, permissions and audit — so every module inherits the same security and the same configurability instead of reinventing them.
Platform
The foundation everything else stands on. Identity, tenancy and permissions are not features bolted on later — they are the first thing built.
- Multi-tenant isolation
- Roles, permissions & claims
- Immutable audit
- Notifications & storage
School operations
The daily work of running a school: who is enrolled, who turned up, what they were taught and how they did.
- Students & guardians
- Staff & departments
- Attendance & timetable
- Assessments & results
Business
Fees, invoices and collection, with the financial trail a bursar can defend in a board meeting.
- Fee structures
- Invoices & receipts
- Payment providers
- Arrears & reconciliation
Administration
A school configures its own rules — grading, terms, approvals, branding — without waiting on an engineer.
- School settings
- Custom roles
- Branding & domains
- Approval workflows
Intelligence
On the roadmapMoving from “here are your reports” to “here is what needs attention”, with the evidence behind every flag.
- Early-warning signals
- Intervention tracking
- School health
- Explainable insights
Most school software stores what happened. This one tells you what to do about it.
Any system can hold a register and print a report card. The difference is what happens between the record and the decision — and that is a loop, not a module you can bolt on later.
01
One record
A student is one record, not six systems.
Academics, attendance, finance, guardians, communication and documents describe the same child. That connection is what makes everything below possible — and it is the thing a bundle of modules can never retrofit.
02
Signals
The system tells you what needs attention.
Chronic absence, a grade trending down, arrears building, a class whose attendance broke pattern. Not another report to go and read — a short list of what changed, surfaced to the person who can act.
03
Your rules
You define what counts as a problem.
Three absences or five. Arrears at one term or two. A drop of ten points or twenty. Schools differ, so the thresholds, the approvals and the escalations are configuration rather than our opinion in code.
04
Intervention
And what the school did about it.
Flagged, assigned, acted on, parent contacted, followed up, resolved. Six weeks later leadership can answer the question that actually matters: did it help?
05
Accountability
Every change has a name against it.
Who changed this mark from 62 to 74. Who approved this fee waiver. Who published these results. Not a server log an engineer retrieves — a record school leadership can read.
A school that has run on Schoolspine for two years does not just have cleaner records. It has evidence of what it tried, and what worked.
A child is not six spreadsheets.
In most schools a student's attendance lives in one system, their fees in another and their results in a third — so nobody can see that the child falling behind is the same child whose fees lapsed in March. Schoolspine keeps one record and lets every workflow write to it.
See how the record connectsAcademics
Classes, subjects, assessments and published results.
Attendance
Daily registers, patterns and chronic absence.
Finance
Invoices, payments, arrears and receipts.
Guardians
Who to call first, and who may see what.
Communication
Every message sent about this student.
Documents
Admission papers, reports, certificates.
A school hands us its children's records. That deserves proof, not assurances.
Four commitments hold up everything else. They are architectural, which means they are the same on the day a school signs up and the day it has ten thousand students.
One school never sees another
Tenant isolation is enforced in the data layer, not in the interface. A query that forgets its tenant does not run.
Permission, not appearance
Hiding a button is not security. Every request is authorised on the server against the permissions that user actually holds.
Every change is attributable
Who changed this mark from 62 to 74, and when? Leadership can answer that without opening a server log.
Your rules, not ours
Grading, terms, attendance thresholds, approval chains and roles are configuration — not a change request to our engineers.
The same system. Five different mornings.
A bursar and a parent do not need the same dashboard, and a parent must not be able to reach another family's child. Role decides what a person sees; ownership decides which records that applies to.
What needs attention today — attendance dips, unresolved cases, collection against target.
See it with your school's own data.
We will walk you through Schoolspine against a real workflow from your school — an admission, a term's results, a fee cycle — and answer the hard questions about migration and security.