School filtering and monitoring: roles, coverage and review

Understand the two different jobs

Filtering limits access to categories of online content or particular services. Monitoring helps identify activity that may require attention. Neither replaces supervision, relationships with pupils or a workable safeguarding process. A blocked request and a monitoring alert are also not the same evidence; the school needs to interpret each in context.

The DfE filtering and monitoring standard applies to schools and colleges in England and describes the recommended approach alongside statutory safeguarding guidance. It includes a review at least annually involving leadership, the designated safeguarding lead, IT support and the responsible governor. Other UK nations have their own education and safeguarding frameworks, so check the relevant local requirements rather than treating English guidance as UK-wide law.

Use this guide as a practical way to organise the service and its evidence. It does not provide a product assessment or a guarantee that a particular configuration will prevent every harmful experience.

Map the actual coverage

List the ways people access online services: managed classroom devices, staff laptops, guest Wi-Fi, personal devices, home use, backup broadband and specialist equipment. For each, record which filtering and monitoring controls apply and which do not. Include applications and generated content rather than assuming that a web-browser blocklist covers every interaction.

Ask providers to explain limitations in plain language. For example, a network-based control may not provide the same visibility when a device leaves the site. An installed agent may depend on a supported operating system and successful updates. The important question is whether the combined arrangement meets the school's assessed needs.

Bring the risk assessment back to the pupils using the technology. Age, communication needs, the curriculum and different learning settings can affect the response. A single default profile may need adjustment, but exceptions should be purposeful, authorised and recorded.

Separate technical and safeguarding decisions

IT support needs to keep systems working, investigate technical faults and provide appropriate evidence. The safeguarding lead needs a process for interpreting concerns and deciding what action is required for a pupil. Senior leaders need to make sure those responsibilities connect and that absence cover exists.

Agree who receives alerts, when they are monitored and how urgent concerns are escalated. Do not leave a system sending serious alerts to an unattended shared mailbox. Document what happens during staff absence, school holidays and any off-site use that the school supports.

Give staff a clear way to report both overblocking and underblocking. A teacher preparing a sensitive lesson should be able to request a review without bypassing the controls. Equally, an unexpected gap should be reported promptly without asking staff to reproduce harmful searches repeatedly.

Test safely and keep useful evidence

Use an agreed safe testing procedure with IT support and the safeguarding lead. Record the date, device type, user profile, connection and expected outcome. Test representative arrangements rather than one administrator laptop. Repeat relevant checks after a network, device-management or provider change.

When a test fails, record its practical significance, interim action, owner and resolution date. Avoid storing unnecessary harmful material or identifiable pupil information in general technical tickets. Safeguarding records should remain in the appropriate controlled process.

An evidence file can be concise: responsibilities, coverage map, review record, test results, significant exceptions and actions. It should help the school understand the service, not become a collection of supplier brochures that nobody can use during an incident.

Make privacy part of the design

Monitoring can involve sensitive information about pupils and staff. Involve the data protection lead when deciding what is collected, who can see it, how long it is retained and how people are informed. The DfE standard discusses privacy information and impact assessment for technical monitoring.

Limit access to people with a justified role. A general IT administrator should not automatically distribute monitoring reports widely, and a safeguarding reviewer should not have to use another person's account. Ask how exports, supplier access and account deletion are controlled.

Review outcomes, not just settings

At review time, consider whether alerts reach the right people, whether staff know the reporting route and whether recurring blocks are disrupting legitimate learning. Examine changes in device use, applications and pupil needs. A school that introduces new AI features or sends devices home may need to revisit its assumptions.

Connect actions to the wider cyber security plan and device management arrangements. The aim is an understood, maintained service with a proportionate human response, rather than a claim that installing software has completed safeguarding work.