OpsWise School Assurance · AI Decision Centre

Choose AI with evidence.

Start with the job you need to do, who will use the AI and what information is involved. Then compare capability, safeguarding, privacy, security and school controls.

Designed for UK school staff, leaders, DPOs, DSLs and IT teams. Results support a decision; they do not certify or approve a product.

Evidence baseline: September 2026 · Supplier terms and features can change; verify before procurement or deployment.
AI ASSURANCE VIEWDecision support

From purpose to approval.

Compare tools in context, expose evidence gaps and record what still needs checking.

01Purposedefine the school need
02Protectcheck people and data
03Assureverify and record
23 core toolsGeneral tools + tools for education
5 decision promptsPurpose, users, data, platform, priority
DfE · ICO · NCSCControls translated into school questions
Evidence, not endorsementLocal review remains essential
A route designed for schools

Start with the need, not the product name.

The same AI tool can be reasonable for one use and inappropriate for another. The Decision Centre separates capability from assurance so staff can explore options without confusing a shortlist with approval.

01

Find the right category

Teacher productivity, research, tutoring, assessment, feedback, creative work and more.

02

See the controls

Privacy, administration, learner safeguards and evidence depth stay visible alongside capability.

03

Know what remains

Supplier evidence supports a decision but does not replace the school's contract, DPIA or safeguarding review.

Guided decision

Build a practical shortlist.

Five questions narrow the landscape. The result is a fit model, not an approval or compliance score.

01
Tell us about the intended useNo school or personal details are collected by this local comparison.
5 What matters most?
Tool library

Compare the right tools for the right job.

Core products are assessed by purpose, audience, admin controls, privacy evidence and learner-facing safeguards.

Assurance checks

What should be verified before approval.

Practical questions shaped around DfE product safety, ICO data protection expectations and NCSC security principles.

01

Purpose & users

Defined educational purpose, target age, staff/pupil roles and whether the tool is genuinely needed.

02

Filtering & monitoring

Age-appropriate filtering, learner supervision, reporting, moderation and escalation routes.

03

Privacy & UK GDPR

Lawful basis, processor status, DPA, subprocessors, retention, deletion, transfers, transparency and DPIA triage.

04

Security

MFA/SSO, least privilege, admin roles, encryption, logging, patching, incident response and AI-specific attack risks.

05

Learner development

Overreliance, manipulation, wellbeing, cognitive development, human help and avoiding inappropriate dependency.

06

Governance & evidence

Approved use register, owner, staff training, acceptable use, evidence links, review date and change monitoring.

Important: “GDPR compliant”, “student safe” and similar vendor claims are not enough on their own. Assess the exact service, contract, configuration, purpose and data flow the school intends to use.
Emerging tools

Worth watching, but not yet core recommendations.

Tools move into the core matrix when there is enough school-relevant evidence to assess them responsibly.

From comparison to assurance

Turn the shortlist into an AI register approved by your school.

OpsWise can review the exact tenant, DPA, data flow, safeguarding controls and intended use; document the decision; and produce a dated AI Assurance record for SLT, governors and the DPO.