One page for a stack that keeps changing
The mix of systems behind your school will not be the same in three years. New sources are added through settings, not procurement, and an integration built because one school asked for it ships to every school. You are not buying this year's configuration.
See the week as a picture, not a pile of logs
Wiring shows where each item entered, what kind of update it was, and which classes it reached — ribbon width is the count. Quiet sources and unanswered questions sit beside the figure, so a head can act without opening seven tabs. The same numbers are also a table: the diagram is an enhancement, never a trap.
Find, explain, flag. Not act
StudyBot is a command centre, not an agent loose in your school. It answers questions over your own data, makes the numbers readable, and raises what deserves attention. It does not take action on your behalf. No head of school wants software mailing six hundred families unsupervised.
Answers cite your pages, or refuse to guess
Every answer comes from your school's own published content and names the page it came from. When your pages do not cover the question, it is handed to the office rather than improvised. The questions nobody could answer become a list of pages worth writing.
Nothing leaves without a person signing it
Anything going out to families waits for a staff member to approve it. Each category of sharing is configurable and there is no route that bypasses human review. This is the part that lets a safeguarding lead put their name to the decision.