Student Radar
Back to Lead

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

Lead / Inspection Readiness

School inspection readiness and evidence coordination

Student Radar helps leaders connect self-evaluation, improvement priorities and cited evidence in the Inspection Hub. Purposeful pupil reviews and owned inspection-day requests support preparation without predicting an inspection result or grading the school.

Leaders judge readiness and choose the response. Cited evidence, a completed request or an empty queue does not predict an inspection result or prove school improvement.

The fictional overview separates recorded judgements, cited evidence and the areas still needing an evidence check. Fictional example.

Review evidence, agree responsibility, retain the outcome

Connect inspection enquiries to reviewed evidence and owned work.

Bring self-evaluation, priority attention flags and cited evidence together, then coordinate purposeful pupil samples and inspection-day requests with owners, due times and outcomes.

  1. 01

    Trace the evidence cited by an evaluation

    The evidence index links the retained fictional discussion review to its applicable evaluation area.

  2. 02

    Give requests an owner and due time

    Inspection day lists operational work without implying an external submission or automatic pack.

  3. 03

    Record the next update against the actual request

    The work editor keeps request, source context, owner, school-time deadline and outcome together.

Inspection Readiness

Trace the evidence cited by an evaluation

The evidence index links the retained fictional discussion review to its applicable evaluation area.

The evidence index links the retained fictional discussion review to its applicable evaluation area. Fictional example.

Inspection Readiness

Give requests an owner and due time

Inspection day lists operational work without implying an external submission or automatic pack.

Inspection day lists operational work without implying an external submission or automatic pack. Fictional example.

Inspection Readiness

Record the next update against the actual request

The work editor keeps request, source context, owner, school-time deadline and outcome together.

The work editor keeps request, source context, owner, school-time deadline and outcome together. Fictional example.

Inspection Readiness

Retain what was checked without overstating completion

The reopened fictional request keeps its update while remaining To do; supplying records and completing review are distinct.

The reopened fictional request keeps its update while remaining To do; supplying records and completing review are distinct. Fictional example.

Inspection Readiness

Choose a purposeful pupil enquiry

An empty sampling list offers a deliberate review rather than implying every pupil has been checked.

An empty sampling list offers a deliberate review rather than implying every pupil has been checked. Fictional example.

Inspection Readiness

Coordinate the same enquiry on a phone

The Pupil sampling section retains its work filter and explicit empty state at phone width.

The Pupil sampling section retains its work filter and explicit empty state at phone width. Fictional example.

A leadership account with a clear next action

Leaders judge readiness and choose the response. Cited evidence, a completed request or an empty queue does not predict an inspection result or prove school improvement.

Evidence gaps with a concrete next check

Area context and cited sources help leaders decide what needs review without treating restricted records as absent.

Purposeful enquiries with responsibility

Pupil reviews and inspection requests have an owner, school-time deadline and recorded account of what happened.

Preparation coordinated through original records

Source links and owned work connect the response while specialist facts remain in their own authorised workflows.

Questions about Inspection Readiness

Can we trace inspection preparation back to cited evidence?

Yes. The hub brings evaluation areas and an evidence index together so leaders can inspect the cited sources they are permitted to open.

Can inspection-day requests have owners and due times?

Yes. Log requests, assign ownership and due times, and record the actual response or outcome.

The value of a connected school

School priorities with the evidence underneath.

Connected reporting gives leaders a route from the whole-school picture to a question, a named action and its review.

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. Attendance + Lead

    Follow the cohort behind the headline

    Move from school attendance into year groups, pupil groups and sessions. Use the detail to focus the leadership conversation and decide what needs investigating.

    Explore attendance
  2. SEND + Lead

    Review provision, delivery and the evidence of progress

    Bring SEND reporting into the improvement cycle so leaders can review provision and costs alongside recorded outcomes and the gaps still needing attention.

    Explore SEND
  3. Safeguarding + Lead

    Keep oversight appropriate to the audience

    Use safeguarding assurance and aggregated evidence for leadership oversight, while case detail stays within authorised safeguarding workflows.

    Explore safeguarding

Walk through the next review with your leadership team

Bring self-evaluation, priority attention flags and cited evidence together, then coordinate purposeful pupil samples and inspection-day requests with owners, due times and outcomes. Leaders judge readiness and choose the response. Cited evidence, a completed request or an empty queue does not predict an inspection result or prove school improvement.