For schools
SentinelXR Class
Lesson planning, parental reporting and a safeguarding record that holds up to inspection. Every Orin flag routes to a named adult with its reasoning attached, and nothing is ever raised anonymously.
Heads · DSLs · teachers · parents
Flags go to a person
Every concern routes to the designated safeguarding lead by name, with the reasoning and the records it drew on. No shared inbox, no anonymous alert.
A record built for inspection
Chronologies assemble themselves from what already happened. Nothing has to be written twice, and nothing can be quietly edited.
Planning that survives a cover lesson
Schemes of work, differentiation and resources attached to the lesson rather than a teacher’s drive. A cover teacher opens the same thing.
Parents see the same record
Attendance, progress and behaviour in plain language, in the family’s language, without a separate portal login for every child.
The limits, on purpose
Widen Orin for under-18s
The narrower behaviour is architectural. A teacher cannot loosen it, and neither can a head — it is not a permission.
Raise a concern anonymously
Every flag carries the reasoning and the records behind it, and lands with a named DSL. An alert nobody owns is an alert nobody acts on.
Edit a chronology after the fact
Records append; they do not rewrite. The version an inspector reads is the version that happened.
Orin in Class
The same intelligence runs in all four products, and the same rule holds everywhere: it observes and proposes, then stands back. It cannot change a grade, a record or an enrolment.
Two pupils in Year 9 have a pattern worth a look: attendance falling on the same weekday, both since half term.
Based on registration data only. No assessment or behaviour records were used to raise this.
Class is deployed per school or per trust, with safeguarding roles mapped before any data is loaded.