Student Radar
Back to Office

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

Office / Policies & Returns

School policy register, review dates and signatures

Student Radar helps school leaders maintain policy owners, review dates, versioned files and required staff signatures. Connected tasks support the next review or return preparation; website publication requires its own authorised workflow.

School staff decide applicability, approval and publication. A saved review date, signature count or completed task is not legal compliance or proof that a statutory return was submitted.

The fictional register keeps owner, review date, file state and one of two required signatures distinct. Fictional example.

Check context, record the decision, review the result

Keep policy ownership, review dates, versions and staff sign-off together.

Review the policy register, maintain the agreed next review, connect versioned documents and required signatures, and make any website-publication decision separately.

  1. 01

    Give the policy an owner and explicit review date

    Register details separate applicability, review cycle and next review from file contents and approval.

  2. 02

    Return to the retained register revision

    The fictional revised title and review date are retained without implying a new file or approval.

  3. 03

    Choose the specific file or lifecycle action

    The actual More actions menu exposes available version/PDF/archive controls for the fictional policy.

Policies & Returns

Give the policy an owner and explicit review date

Register details separate applicability, review cycle and next review from file contents and approval.

Register details separate applicability, review cycle and next review from file contents and approval. Fictional example.

Policies & Returns

Return to the retained register revision

The fictional revised title and review date are retained without implying a new file or approval.

The fictional revised title and review date are retained without implying a new file or approval. Fictional example.

Policies & Returns

Choose the specific file or lifecycle action

The actual More actions menu exposes available version/PDF/archive controls for the fictional policy.

The actual More actions menu exposes available version/PDF/archive controls for the fictional policy. Fictional example.

Policies & Returns

Coordinate the next step without claiming a return was filed

Tasks support work and due dates; the empty fictional list is not a statutory-return submission tracker.

Tasks support work and due dates; the empty fictional list is not a statutory-return submission tracker. Fictional example.

Policies & Returns

Keep document records distinct from register entries

The Documents section retains its separate file/version workflow; no documents have been listed in this fictional example.

The Documents section retains its separate file/version workflow; no documents have been listed in this fictional example. Fictional example.

Policies & Returns

Review the saved policy on a phone

The policy row stacks its owner, date, status and actions at phone width.

The policy row stacks its owner, date, status and actions at phone width. Fictional example.

A clear record for the responsible team

School staff decide applicability, approval and publication. A saved review date, signature count or completed task is not legal compliance or proof that a statutory return was submitted.

A register that explains what needs attention

Review dates, flags, applicability, file state and sign-off progress expose different questions rather than one misleading complete status.

A current version with its actual required audience

Version history and role/named-person sign-off keep the file being read distinct from old attestations or unrelated signers.

Deliberate sharing and follow-up

Audience checks, a separate website-publication workflow and connected tasks preserve who must act without treating a task as external filing.

Questions about Policies & Returns

Can policies retain their current file version and required signatures?

Yes. The register connects policies to versioned documents and required staff signatures, keeping the policy owner and review date visible.

Can we give policy reviews and return preparation owned tasks?

Yes. Use connected tasks for the next review or return preparation. Publishing a policy to the website remains a separate decision.

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

The office keeps the connections working.

Accounts, access and shared resources underpin the school day. Keep those foundations close to the people and work they support.

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. Family communication + Office

    Keep family access tied to the right pupil

    Maintain parent invitations and parent-pupil links in account connections so family access follows the school’s current records.

    Explore family communication
  2. Staff and cover + Office

    Keep class access current as staffing changes

    Staff administration records roles and class access from arrival to deactivation. Cover planning gives office teams a clear place to coordinate the staffing response.

    Explore staff and cover
  3. SEND + Office

    Make room for the support that is planned

    Resource booking gives staff a shared view of room availability. Intervention planning brings pupils, staff, rooms and sessions together when arranging support.

    Explore SEND

Agree the next step with the responsible staff

Review the policy register, maintain the agreed next review, connect versioned documents and required signatures, and make any website-publication decision separately. School staff decide applicability, approval and publication. A saved review date, signature count or completed task is not legal compliance or proof that a statutory return was submitted.