Attendance and behaviour
Persistent or severe absence, and recorded internal suspensions.
Bring attendance and behaviour together with SEND, language needs, disadvantage and family circumstances. Use the Vulnerability Indicator (VIS) to see what’s changed, understand what’s behind the score and agree the next step.
The demo uses fictional pupil records.
Two pupils with similar attendance may need very different support. The VIS brings the relevant context into one view so staff can decide what to look at first.
Persistent or severe absence, and recorded internal suspensions.
SEND support, education, health and care plans, and English language proficiency.
Pupil Premium and free school meal eligibility.
Young caring responsibilities, homelessness and emergency housing.
Support already in place, such as Place2Be, CAMHS or a mental health support team.
Reading age, oracy and early language development sit alongside the VIS as unscored learning information.
The score helps staff decide where to look. Staff review the context and agree what support is appropriate.
Follow Alex’s fictional caseCompare attendance, persistent absence, suspensions and inclusion by school and term. Explore SEND progress, EHCP requests and IQM specialisms alongside the leadership scorecard.
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.
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 walkthrough.
Explore the interactive demoBusiness contact details only. Not for safeguarding referrals.
Checking whether walkthrough requests are available…