See who may need support and why.

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.

OverviewFictional school
Pupils in view36
Review priority4
Active support18
Pupils to review View pupils
AJ
Alex JordanYear 5 · Willow
High priority
ST
Sam TaylorYear 3 · Oak
Elevated
RC
Riley CarterYear 6 · Maple
High priority

Bring pupil information and support plans together.

Schools hold valuable information about their pupils. The challenge is seeing how it connects — and knowing what needs attention first.

One whole-school view

See attendance, behaviour and wider needs together — without piecing together multiple spreadsheets before every meeting.

Current and historical context

Understand current and historical circumstances, from safeguarding involvement to significant life events, with reasons visible to authorised staff.

Earlier conversations

Spot patterns and changes that deserve a closer look, then make informed decisions using professional judgement.

Support that gets followed up

Record the support agreed, who's responsible, when to review it and what difference it made.

From first concern to review.

See how school teams move from identifying a concern to reviewing the support they agreed.

ILLUSTRATIVE WORKFLOW01 / 04
Review priority4for staff attention
Attendance
Behaviour
Context

Start with the whole-school picture.

One view brings the signals together so leaders can focus their professional attention where it may be needed.

Try this in the demo

Follow one pupil’s support journey.

Follow Alex Jordan, a fictional Year 5 pupil, from an attendance concern to a review of the support agreed.

AJAlex JordanYear 5 · Willow · Fictional exampleFICTIONAL EXAMPLE
01 — NOTICE

A change worth noticing.

Alex’s attendance fell by 3.3 percentage points. The team checks what changed before deciding how to help.

Earlier attendance79.7%
→
Current attendance76.4%
Information prompts a conversation. It does not decide the answer.Open Alex’s profile
All pupils and figures are fictional. Contextual indicators are illustrative and should never be used as automatic safeguarding decisions.

Support pupils.
Protect their information.

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 approach
♢
Human decisions, alwaysIndicators prompt professional review. They are not automatic safeguarding decisions.
▣
Information on a need-to-know basisRole-based access and protected contextual records are required for a live school deployment.
↻
Clear ownership and accountabilityReview dates, named leads and an audit trail form part of the production plan.
◎
Prototype with fictional pupilsThe interactive demonstration contains no genuine pupil or safeguarding records.

Frequently asked questions

We're building Pupil Support around real school workflows. These answers explain what's available in the demonstration and what a live service would require.

Does Pupil Support replace school safeguarding systems?

No. It is intended to support joined-up review and intervention tracking, not replace safeguarding recording, statutory processes or professional decision-making.

Does it connect directly to Arbor?

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.

Can I upload real pupil information to the demo?

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.

How does the Vulnerability Indicator work?

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.

Can schools track whether support is working?

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.

Talk to us about your school.

Want to discuss how Pupil Support could fit your school’s workflow? Request a conversation.

Explore the interactive demo
REQUEST A CONVERSATION

Tell us about your school.

Business contact details only. Not for safeguarding referrals.

Checking whether the enquiry service is connected…

Contact details will only be submitted when the secure email service has been configured by the site owner. No real pupil information.