Student Radar

Record, triage, act, review

School Safeguarding Dashboard for DSL Teams

Student Radar Safeguard gives DSL teams reporting, triage, case workspaces, chronologies, actions, role-based access, and auditability alongside wider whole-child context.

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 safeguarding workflow for reporting and triage
Give staff a clear reporting route and DSLs a controlled place to triage what happens next.
  1. 01Simple reporting for staff, clear triage for DSLs
  2. 02Case workspaces with chronology so nothing is missed
  3. 03Role-based access and audit logs for sensitive information

The strongest fit

Best fit

DSL teams that need a controlled safeguarding workflow and want authorised staff to see relevant attendance, behaviour, SEND, health, and pastoral context.

A clear boundary

Where this is not the right tool

  • 01Replacing professional safeguarding judgement or statutory referrals
  • 02Giving every staff role unrestricted access to sensitive case detail

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.

DSL action board showing safeguarding work and ownership
Keep safeguarding actions, owners, and priorities visible to the authorised team.
Safeguarding chronology showing a connected sequence of records and actions
Review the sequence around a pupil without rebuilding the story from separate systems.

Connected school work

Built for the way schools actually work

Schools searching for “school safeguarding dashboard” 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 clearer route from concern to triage, action, and review

  2. 02

    Less fragmented case context for authorised safeguarding staff

  3. 03

    Visible ownership and follow-through across the DSL team

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

What this is designed for

Staff reporting and DSL casework are distinct, controlled workflows

Chronology, actions, and multi-agency work stay connected

Role-aware permissions protect sensitive detail

How it works in practice

01

Report and triage with clarity

Staff get a direct route for recording a concern, while DSLs retain control of triage, sensitivity, and the appropriate response.

  • Guided concern reporting
  • DSL-owned triage and case routing
  • Controlled visibility for sensitive records
02

Keep the chronology and actions together

Bring events, professional notes, actions, documents, and decisions into one authorised case history.

  • Connected chronology
  • Owned actions and due dates
  • Clear audit history
03

Work across agencies without losing accountability

Record meetings, contacts, referrals, and agreed next steps while the DSL and school procedures remain in charge.

  • Multi-agency contacts and meetings
  • On-call and alert routes
  • Assurance and leadership reporting

Workflow differences worth reviewing

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

Compared with email and shared documents

  • Keeps the chronology, ownership, and current action together
  • Restricts detail through role-aware access rather than broad distribution
  • Makes overdue and unresolved safeguarding work visible

Compared with an isolated safeguarding log

  • Connects authorised whole-child context without copying sensitive records
  • Moves from reporting into triage, casework, and review
  • Supports leadership assurance while preserving case-level controls

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

How does Student Radar support safeguarding workflows?

Safeguard brings reporting, triage, and case management into one place, with clear chronologies and role-based access.

02

Can staff log concerns quickly?

Yes. The reporting flow is designed to reduce friction and doubt, so staff can log concerns with confidence.

03

Does it support audit trails?

Yes. Role-based access and audit logs help protect sensitive detail and maintain accountability.

04

Can safeguarding staff see relevant wider pupil context?

Authorised staff can follow governed routes to relevant attendance, behaviour, SEND, health, and pastoral context. Access remains role- and purpose-aware rather than opening every record to everyone.

05

Does Student Radar replace the DSL or local procedures?

No. Student Radar supports recording, triage, coordination, and assurance. The DSL, school policy, statutory guidance, and professional judgement remain authoritative.

06

Can it support multi-agency working?

Yes. DSL teams can keep contacts, meetings, referrals, agreed actions, and review points connected to the safeguarding record.