Student Radar

What happened, what might explain it, and what next

School Behaviour Tracking System

Connect behaviour recording, pattern analysis, functional understanding, support planning, response, and review. Staff see the context they need while professional judgement stays in charge of every response.

One platform. Everything included.

Share context and move from signal to action without buying separate modules.

£4.25 per pupil/year, £250 minimum/year, excluding VAT

Student Radar Demo School behaviour analytics showing populated incident, suspension, exclusion, and risk measures
See current incidents, suspensions, exclusions, risk, trends, and hotspots before opening the context behind them.
  1. 01Leadership dashboards that show what is changing
  2. 02Structured tools for understanding behaviour and planning support
  3. 03Connected response and review without losing pupil context

The strongest fit

Best fit

Schools that want consistent behaviour practice across recording, analysis, support, response, and review without reducing pupils to incident counts.

A clear boundary

Where this is not the right tool

  • 01Automating sanctions or replacing professional judgement about a pupil
  • 02Treating behaviour frequency alone as an explanation of need

Product evidence

See the workflow behind the promise

A closer look at the connected workflows behind this solution. The demo school uses realistic, privacy-safe information so buyers can inspect the product without exposing a real pupil record.

Student Radar Demo School ABC Observation Register showing completed pupil observations
Start with completed observations grouped around the pupil, then move into history and cautious pattern support.
Student Radar Demo School detention register showing a populated session and attendance outcome
Coordinate a staffed response with the session, assigned pupils, attendance outcome, and next action together.

Connected school work

Built for the way schools actually work

Schools searching for “school behaviour tracking system” usually need clarity, prioritisation, and a way to move from insight to action without adding another spreadsheet.

Operational outcomes this workflow is designed to support

  1. 01

    A more consistent route from an incident or pattern to proportionate support

  2. 02

    Better visibility of where, when, and for whom behaviour is changing

  3. 03

    A connected record of observations, plans, responses, and review

Product intent only; these are not presented as verified customer outcome claims.

What this is designed for

Analytics can be explored by time, place, group, and incident type

ABC, QABF, support plans, and report cards sit in one support workflow

On-call, detention, exclusion, and agreed automation routes remain staff-controlled

How it works in practice

01

See the pattern behind the incidents

Explore changes by time, place, group, and incident type, then move into the relevant pupil and practice context.

  • Trend and hotspot views
  • Cohort and equity context
  • Direct drill-down to pupils and records
02

Build support around understanding

Use structured observations and assessment tools to support professional enquiry, then keep the resulting plan visible to the staff delivering it.

  • ABC observations and QABF
  • Behaviour support plans
  • Report cards and review evidence
03

Coordinate response and follow-through

Manage agreed school responses from a shared record while keeping decisions, permissions, and accountability with staff.

  • On-call, detention, and exclusion workflows
  • School-defined prompts and routing
  • Owned actions and review points

Workflow differences worth reviewing

Use these product capability descriptions as a procurement checklist against the tools and processes you already use.

Compared with an incident log

  • Connects patterns to observations, plans, responses, and review
  • Shows context beyond the number of incidents
  • Keeps positive recognition and support visible alongside accountability

Compared with disconnected behaviour tools

  • Uses one pupil and action context across analytics and support
  • Reduces repeated entry between logs, plans, and report cards
  • Keeps school-defined responses consistent without automating judgement

Next step

See how the connected workflow fits your school

We can walk through the route your team would use from the first signal through to action and review.

In their words

A practitioner view of the platform

Built from the point of view of school leaders and teachers, not IT departments. It takes what would normally be an hour of spreadsheet work and makes it available in seconds. It reduces workload rather than adding to it.
Jon Gibson
Director, Backdrop Education Services

The practical questions

FAQs

01

Can we see behaviour hotspots and trends?

Yes. Behaviour Analytics is designed for leadership visibility, including hotspot views and changes over time.

02

Is there a consistent intervention approach?

Yes. Behaviour Playbooks provides a structured, evidence-led framework to keep support consistent across staff.

03

Does this support positive behaviour approaches?

Yes. Tools like Points are designed to be positive-first and practical for real classrooms.

04

Can staff record ABC observations or functional assessment?

Yes. Behaviour support includes structured ABC observations, QABF, support plans, and report cards so enquiry, planning, and review stay connected.

05

Does the system automate sanctions?

No. Schools can define prompts and routing rules, but staff retain control of decisions, responses, and professional judgement.

06

Can behaviour be reviewed alongside attendance, SEND, and safeguarding?

Relevant authorised context can be viewed through connected pupil workflows. Sensitive detail remains controlled by role and purpose.