Attendance is taken at 8am,ready or not.
Your morning does not pause because a supplier is having a bad one. This page sets out exactly what we run, what we do when something breaks, and what your school is owed while we fix it — so you can judge us on the answer before you ever need it.
What we operate
The components a school depends on.
Each of these is monitored and each can fail independently. When one is degraded, affected schools are notified directly rather than being left to work it out.
School application
The workspace staff, teachers and guardians sign in to.
Platform API
Every read and write the applications make.
Authentication
Sign-in, sessions and password resets.
Notifications
Email and SMS delivery to families and staff.
File storage
Documents, report cards and uploads.
Scheduled jobs
Overnight processing, reminders and reports.
Every component above is monitored continuously. If you want the current position on any of them before you commit, ask us and you will have a straight answer the same day.
Our operating commitments
What you can hold us to.
Planned maintenance is scheduled around your term
Work that requires downtime happens outside teaching hours in the timezone your school is configured for, and is announced in advance rather than discovered.
Incidents are communicated, not hidden
If something is broken, affected schools are told what is affected, what is not, and what we are doing — while it is happening, not in a summary afterwards.
Your data survives our mistakes
Automated backups with a documented and rehearsed restore procedure. An outage should cost you time, never records.
Exam periods are treated as critical
We do not deploy anything non-essential during a school’s published examination window. Tell us your dates and they go on the calendar.
Something not working?
Tell us what you were doing and what happened. A problem reported during the school day is treated as a school day problem.