Student Radar

Messages out. Responses and consent back

School Parent Communication Platform

Connect messages, contact history, parent evenings, consent, trips, and enrichment to the pupil and the school workflow they belong to. Staff stay in control of what goes out, and families get a route to respond.

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 family messaging workflow connected to pupil context
Keep outbound communication, replies, and contact history close to the reason for contact.
  1. 01Messages and contact history stay connected to the pupil and purpose
  2. 02Parent evenings, consent, trips, and enrichment use dedicated workflows
  3. 03Staff review, send, and remain accountable for every communication

The strongest fit

Best fit

Schools that want family communication connected to pupil support and operational workflows rather than separated into broadcast messages and disconnected forms.

A clear boundary

Where this is not the right tool

  • 01Sending autonomous messages or making decisions on behalf of school staff
  • 02Replacing safeguarding procedures for urgent or sensitive family contact

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.

Parent evening booking and follow-up workflow
Coordinate invitations, appointments, attendance, notes, and follow-up in one journey.
School consent and trip communication workflow
Connect family responses to the trip, pupil context, and staff action they affect.

Connected school work

Built for the way schools actually work

Schools searching for “school parent communication platform” 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

    Clearer contact history across the staff supporting a pupil

  2. 02

    Less repeated chasing between messages, forms, consent, and operational lists

  3. 03

    More consistent family journeys from invitation to response and follow-up

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

What this is designed for

Messaging and communication logs use shared pupil and family context

Parent evenings connect booking, attendance, notes, and follow-up

Consent and trip responses feed the governed operational workflow

How it works in practice

01

Communicate from the right context

Start with the pupil, group, event, plan, or action that prompted the communication, then keep the resulting history connected.

  • Targeted and group messaging
  • Pupil communication history
  • Staff-reviewed content and recipients
02

Give families a clear route to respond

Use dedicated journeys for appointments, consent, and participation instead of asking families to piece together email, paper, and separate forms.

  • Parent evening booking
  • Consent and response tracking
  • Trips and enrichment participation
03

Turn the response into follow-through

Keep non-response, changed information, agreed actions, and next contact visible to the staff responsible for the workflow.

  • Visible response status
  • Owned follow-up actions
  • A connected record around the pupil or event

Workflow differences worth reviewing

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

Compared with broadcast-only messaging

  • Keeps contact tied to the pupil, event, or support workflow
  • Connects replies and non-response to staff follow-up
  • Supports appointments, consent, and participation as well as messages

Compared with separate forms and booking tools

  • Uses shared pupil, family, event, and staff context
  • Reduces repeated list matching and manual reconciliation
  • Keeps each specialist workflow and its approvals intact

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 staff see a pupil communication history?

Authorised staff can review relevant messages, calls, replies, and attempted contact around the pupil so the next conversation starts with context.

02

Does it support parent evening booking?

Yes. Parent Evening connects invitations, appointment booking, attendance, notes, and follow-up in one workflow.

03

Can families provide trip consent?

Yes. Consent responses connect to the trip and pupil workflow so staff can see participation status and follow-up without rebuilding lists.

04

Does Student Radar send messages autonomously?

No. The platform helps staff prepare, target, send, and follow up communication. School staff remain responsible for the content, recipients, timing, and every decision.

05

Can communication connect to SEND, safeguarding, or pastoral work?

Relevant communication can remain connected to the authorised pupil workflow and purpose. Sensitive records and specialist access controls remain governed separately.