Student Radar
Log in
Back to Core

Everything included: £4.25 per pupil/year before volume discounts of 5% to 20%, £250 minimum/year, excluding VAT. See pricing

Core / School Automation

Rules start switched off, and act only on the version someone approved

Adopt a rule from a template, preview who it would affect, get independent approval where it is required, and switch on that exact version.

Request a demoWatch a product example

Signals and suggested routes support professional enquiry. Staff decide what the evidence means and what should happen next.

School Automation in action. Adopt a rule from a template, preview who it would affect, get independent approval where it is required, and switch on that exact version.

Limits made explicit

What it deliberately does not do

01

Nothing acts until a person switches on the exact version they checked. The preview counts current matches and action targets, with unknown and stale data counted separately, so missing information is never read as a match or a non-match.

02

Safeguarding rules and rules that message families need approval from a second person, and the author cannot approve their own rule. Editing an approved rule creates a new draft that needs approving again.

03

Switching a rule on applies it to new events. Acting on pupils who already match is a separate choice, confirmed by typing it out.

04

What a rule creates, such as a task or a review suggestion, is a prompt for staff to look more closely. It is not a decision about a pupil, and a completed task does not show that things have improved.

Evidence in context

Shadow mode, limits and a record of each run

Rules only take action when automation is switched on for the school and shadow mode is off. In shadow mode, rules are checked and the results recorded, but nothing is done. Behaviour rules and recurring report schedules keep their own workflows.

  • Daily limits on actions and messages
  • Activity lists each run and what happened to each action
  • Needs attention lists missing owners, stale data, failed actions and approval requests

Related help guides

See how to carry out these tasks in Student Radar, with step-by-step product help for the people using them.

The value of a connected school

See the pattern. Bring the context.

A change in attendance or behaviour is the start of a conversation. The connected pupil record helps staff ask a better next question.

Core

Context for the next step

Student Radar

Follow a connection to see what it makes possible

Relevant context, with access set by each staff member’s role and responsibilities. Staff decide the response.

  1. SEND + Core

    Check whether support is reaching the pupil

    Put attendance and behaviour alongside plans, provision and review evidence. Staff can investigate missed support before deciding what needs to change.

    Explore SEND

  2. Health + Core

    Bring health needs into the attendance conversation

    Authorised staff can check relevant medical needs and care plans when following up absence, then agree practical support with the family.

    Explore health

  3. Family communication + Core

    Keep the family conversation with the follow-up

    Read the contact history around a pupil before reaching out. Record the next action so another colleague can pick up the conversation with context.

    Explore family communication

Ask to see School Automation in the Demo School

The templates, and how preview, approval and activation work.

Request a demoWatch a product example