One whole-school view
See attendance, behaviour and wider needs together — without piecing together multiple spreadsheets before every meeting.
Bring attendance, behaviour and wider context together. See which pupils need a closer look, agree support and review what changed.
The demo uses fictional pupil records.
Schools hold valuable information about their pupils. The challenge is seeing how it connects — and knowing what needs attention first.
See attendance, behaviour and wider needs together — without piecing together multiple spreadsheets before every meeting.
Understand current and historical circumstances, from safeguarding involvement to significant life events, with reasons visible to authorised staff.
Spot patterns and changes that deserve a closer look, then make informed decisions using professional judgement.
Record the support agreed, who's responsible, when to review it and what difference it made.
See how school teams move from identifying a concern to reviewing the support they agreed.
One view brings the signals together so leaders can focus their professional attention where it may be needed.
Follow Alex Jordan, a fictional Year 5 pupil, from an attendance concern to a review of the support agreed.
Alex’s attendance fell by 3.3 percentage points. The team checks what changed before deciding how to help.
Pupil information is sensitive. The production platform must be designed around school-controlled access, clear accountability and data protection — not just an attractive dashboard.
See the demo's privacy approachWe're building Pupil Support around real school workflows. These answers explain what's available in the demonstration and what a live service would require.
No. It is intended to support joined-up review and intervention tracking, not replace safeguarding recording, statutory processes or professional decision-making.
The intended live service would use school-approved, read-only integration, subject to available data and permissions. The current demo uses synthetic information only and does not connect to Arbor.
No. The demo is not an approved production environment and must not be used for identifiable pupil or safeguarding information. It includes a synthetic sample-data workflow instead.
The demo uses clearly labelled illustrative criteria to group pupils by priority for staff review. The final rules, weights and thresholds must be validated with school leaders before any production use.
Yes, the demo shows how to create support actions, assign owners, set review dates and record outcomes. A production system would retain these in a secure school-specific database.
Want to discuss how Pupil Support could fit your school’s workflow? Request a conversation.
Explore the interactive demoBusiness contact details only. Not for safeguarding referrals.