Everything a school runs on. Nothing it has to stitch together.
Most schools operate four or five disconnected tools and reconcile them by hand. Schoolspine holds the whole operation on one record set, so the register, the invoice and the report card are describing the same child.
5
Product pillars
20+
Operational modules
1
Student record
The people a school is responsible for
Every person the school holds a duty of care or a contract with, on one record each — and linked to each other where the relationships actually matter.
Students
Admission through graduation on a single profile: enrolment, class history, attendance, results, fees, documents and guardians.
Guardians
One guardian to many children, one child to many guardians, with relationship and primary-contact recorded. Portal access is optional — a guardian exists in the records whether or not they ever sign in.
Staff & teachers
Employment records, departments, subject and class assignments, and the permissions that follow from the role.
Classes & departments
Streams, sections, subject allocation and the teaching assignments that decide who is responsible for whom.
The academic year, start to finish
Years, terms, registers, timetables, assessments and published results — configured to how your school actually grades and promotes, not to a model we chose.
Attendance
Daily and per-period registers designed to be fast: a teacher marks a full class in seconds, not clicks. Patterns and chronic absence surface automatically.
Timetable
Class, teacher and room timetables with conflict detection, so a double-booked teacher is caught when it is built rather than on Monday morning.
Assessments
Continuous assessment, exams and marks entry built for bulk work — a teacher entering a class set should never fight the interface.
Results & report cards
Your grading scale, your weighting, your comment structure, your branding. Publication is a deliberate, permissioned, audited act.
Money, with a trail you can defend
Fee structures, invoices, payments and arrears — where every figure can be traced to who entered it and when.
Fees & invoicing
Fee structures per class, term or category. Assign, invoice, and track what is outstanding against each student and each family.
Payments & receipts
Record payments, issue receipts, and reconcile. Financial writes are never optimistic — the interface confirms only what the server has committed.
Financial reporting
Collection against expectation, arrears by class or family, and the term-on-term picture a board asks for.
Payment providers
PlannedA provider-agnostic payment layer, so mobile money and card rails can be added without reworking the finance module.
Talking to families, on the record
Communication that is attached to the student record, so a conversation about a child is part of that child’s history rather than lost in someone’s phone.
Messaging
Direct and group messages to guardians and staff, with delivery status and a permanent record against the recipient.
Announcements
School-wide or targeted notices, scheduled or immediate, with a defined audience rather than a broadcast to everyone.
Documents
Admission papers, certificates and reports stored against the student, staff member or school, with permissions on who may open them.
The layer that makes the rest safe
Identity, tenancy, permissions and audit are not an admin screen bolted on at the end. They are the first thing built, and every module inherits them.
Roles & permissions
Capability-based permissions, plus custom roles a school defines for itself — Examination Officer, Registrar, Librarian — without asking us for a code change.
Audit
Who changed this mark, approved this waiver, published these results, or granted this permission. Append-oriented and readable by leadership, not just engineers.
School settings
Grading, terms, attendance rules, finance settings, notification channels, branding and document templates — configuration, not a support ticket.
Users & access
Invitations, account status, session control and the security policies your school chooses to enforce.
One platform. Configured to how you actually operate.
A nursery and a college run on the same foundation but almost nothing else in common. Every difference below is configuration rather than a separate product.
Nursery & primary
Fewer systems, less admin, more time with the children.
Smaller schools carry the same obligations as large ones with a fraction of the office staff. The work that has to disappear is duplicate data entry and chasing fees by hand.
- A register a class teacher completes in under a minute
- Guardian contacts that are correct when it matters
- Fee collection without a parallel spreadsheet
- Report cards that assemble themselves
Secondary schools
Streams, subject teachers and exams that actually reconcile.
Once students take different subject combinations across streams, spreadsheets stop coping. Marks arrive from a dozen teachers and have to become one defensible result.
- Per-period attendance across streams
- Bulk marks entry built for a full class set
- Grading and weighting configured to your policy
- Result approval before anything is published
International schools
Multiple curricula, multiple currencies, higher expectations.
Parents paying international fees expect a portal that works, communication that arrives, and records that stand up to scrutiny from a board or an inspection.
- Configurable grading for more than one curriculum
- Currency and locale settings per school
- Guardian portal access and communication history
- A complete audit trail on every record
School groups
Several schools, one standard, no shared database.
A group needs comparability across campuses without one school ever being able to see another’s records. Each school is a separate tenant; the group sees across them by design, not by accident.
- A separate, isolated tenant per school
- Its own branding and domain for each campus
- Consistent roles and policies across the group
- Comparable reporting between schools
Colleges & vocational
Intakes, cohorts and programmes rather than year groups.
Post-secondary institutions admit continuously, run programmes of different lengths, and carry finance arrangements that a school timetable model was never designed for.
- Academic structures configured to your programmes
- Continuous admissions rather than one annual intake
- Flexible fee structures and instalments
- Records that follow a student across cohorts
Walk through it with your own workflow.
Bring a real process from your school — an admission, a term's results, a fee cycle — and we will show you exactly how it runs.