Every feature, by role

Isolated by design

Every school's data is isolated at the database level, with access rules held in the database itself rather than only in application code.

Every change tracked

Every change is tracked: who, what and when, ready for a subject access request.

No ticket to IT

Add a new member of staff with an email invite. No ticket to IT required.

A setup checklist for a new school

Subjects, faculties, houses, rooms, staff, rosters and the timetable, in the order that actually works.

Roles that match how a school is organised

School admin, depute head, principal teacher, pastoral, teacher and support assistant, plus pupil and parent, each seeing only their own remit.

Remits by subject, house or year group

A teacher can hold a principal teacher remit for one subject, or a depute a remit over two year groups, without a second account.

Import your whole school from a spreadsheet

Pupils, staff and timetable data, checked and staged before anything is committed.

An import that will not quietly lose rows

A failed batch is retried row by row and the offending records are reported, rather than counted as skipped and forgotten.

Catch a bad record before it causes a problem

Missing or malformed pupil numbers and dates of birth, duplicates and gaps, flagged automatically.

Staff, pupil and parent accounts in one place

Invite, activate, deactivate and reset in bulk, without a separate process per user type.

Pupil photos and files kept private

Photos and homework attachments are served through short-lived authorised links, so a copied URL is inert.

Deletes that refuse rather than cascade

Removing a class, period or session stops if attendance exists behind it, and tells you how many marks are at stake.

Locks itself on a shared machine

An idle session locks, which matters on a classroom computer that anyone can walk up to.

Training built into the system

Twenty guided walkthroughs cover the pages staff actually use, and the real pages can run the same tour, so a new starter is not waiting for an in-service day.

Built to WCAG 2.2 AA

Keyboard operable, screen-reader labelled, contrast checked, and never using colour as the only signal.

Light and dark, and reduced motion

Follows the device's own preferences, including for users who have asked for less animation.

An internal phonebook that stays current

Room extensions and staff contacts, built from the rooms your timetable already uses.

In-app notifications, not another inbox

Approvals, referrals and record changes reach people inside the system they are already working in.

Search that respects permissions

One search across pupils, staff, classes and rooms, returning only what the person searching is allowed to see.

Built for more than one school

Multi-tenant from the start, with platform-level administration and cross-school audit for whoever runs the estate.

Hosted in the UK

Data stays in a UK region, isolated per school at the database level.