The DfE filtering and monitoring standard splits the work between leaders, the DSL and IT
The DfE filtering and monitoring standard has four parts: named roles, a review at least once every academic year, a filter that blocks harmful content without getting in the way of teaching, and monitoring that reports concerns quickly. Governors and proprietors hold overall responsibility, the DSL leads on safeguarding and IT support runs the systems. The DfE expects it to be in place already.

England: the DfE filtering and monitoring standard and Keeping children safe in education apply to schools and colleges in England. Wales, Scotland and Northern Ireland set their own guidance, which this guide does not cover.
The Department for Education's filtering and monitoring standard sets out how schools and colleges in England should put in place the appropriate filtering and monitoring systems that Keeping children safe in education (KCSIE) expects. It has four parts: assign roles and responsibilities, review the provision at least once every academic year, block harmful and inappropriate content without unreasonably affecting teaching and learning, and run monitoring that suits the setting's safeguarding needs. Governing bodies and proprietors hold overall strategic responsibility. A named member of the senior leadership team (SLT) and a named governor are responsible for the standard, the designated safeguarding lead (DSL) leads on safeguarding, and in-house or third-party IT support runs the systems. Each of the four parts on the DfE's filtering and monitoring page ends with the same line: "You should already be meeting this standard."
How the standard relates to KCSIE
The DfE's digital and technology standards page lists filtering and monitoring as one of six core standards that all schools and colleges should be working towards by 2030. The filtering and monitoring page itself gives no future date: it says the standard should already be met. The duty behind it comes from KCSIE, which is statutory guidance.
The current edition is Keeping children safe in education 2026. The KCSIE publication page records that the September 2026 version came into force on 1 September 2026, replacing the 2025 one. Schools and colleges in England must have regard to it.
Paragraph 173 says governing bodies and proprietors should ensure their school or college has appropriate filtering and monitoring systems in place, and that a review of their effectiveness is carried out at least once every academic year. The 2026 edition updates this wording to say who carries out that review (the SLT member responsible for filtering and monitoring, supported by the DSL and IT support) and what it includes: checks that filtering is working on all internet-connected devices in all relevant locations, with a record kept of those checks. Paragraph 175 points to the DfE standard for the detail, and paragraph 176 says schools can self-assess against it with the DfE's Plan technology for your school service.
KCSIE leaves what counts as "appropriate" to each school and college, informed in part by the Prevent duty risk assessment (paragraph 174). The judgement about risk stays with the school and its DSL.
Who owns which part
Governing bodies and proprietors name a member of the SLT and a governor to be responsible for the standard, and set out the roles of staff and third parties such as an IT provider. A setting may not have a full-time person for each role, but it must be clear who is responsible and possible to make prompt changes. Where job titles differ, the most relevant person takes the role.
- Governing body or proprietor: overall strategic responsibility, and the assurance that the standard is in place. They support the SLT to buy and set up systems that suit the school's risk profile.
- Senior leadership team: scoping the setting's needs, including its use of generative AI; buying the systems; documenting what is blocked or allowed and why; governance; reviewing effectiveness; overseeing reports. They also make sure staff understand their role, are trained, follow the procedures and act on reports.
- Designated safeguarding lead: checking relevant reports, responding to safeguarding concerns that filtering and monitoring identify, and giving governors assurance that the systems work and are reviewed regularly. KCSIE Annex B says the DSL's lead responsibility includes understanding the filtering and monitoring systems and processes in place, and that this should be explicit in the job description.
- IT support, in-house or third party: maintaining the systems, providing reports and completing actions after concerns or checks. They work with the SLT and DSL to buy systems, identify risk and carry out reviews and checks.
Day-to-day management needs both safeguarding and IT knowledge, so a change to the filter is never only a technical decision. KCSIE adds that all staff should get training at induction that includes the expectations, roles and responsibilities around filtering and monitoring (paragraph 153).
The review every academic year
The review runs at least once every academic year. It also runs when a safeguarding risk is identified, when working practice changes (remote access or bring your own device, for example), when new devices or generative AI tools arrive, after major software updates, and when the technical configuration of the network or devices changes. The SLT, the DSL and IT support carry it out, with the responsible governor involved, and it can sit inside a wider online safety review. The results and actions are recorded for anyone entitled to inspect them.
Of the things the review needs to understand, IT support will be asked about:
- what the filter currently blocks or allows;
- how the school or college uses technology, including any BYOD policy for students and staff;
- how and where generative AI products are used, on the web and inside applications;
- technical limits, such as whether the system can filter and monitor real-time, dynamic, personalised or AI-generated content;
- the approval process for temporary exceptions;
- what checks happen now and how the resulting actions are handled;
- set-up recommendations that keep the system working, including automatic updates.
The other items belong with the DSL and leaders: the students' risk profile (age, special educational needs and disabilities, English as an additional language), outside safeguarding influences, relevant incidents, digital resilience and what the RSHE and PSHE curriculum needs to reach. After any system or equipment change, the standard asks for assurance that filtering and monitoring still work on every school-managed device.
What the filter is expected to do
No filtering system can be 100% effective, the standard says, so the school needs to understand its coverage and limits. The technical requirements are specific:
- Blocklists from the Internet Watch Foundation (IWF) and the Counter-Terrorism Internet Referral Unit (CTIRU) are implemented, and no user in a school, college, multi-academy trust or local authority can disable, override or alter them, at any level, system administrators included. The provider should be an IWF member, signed up to CTIRU and updating the lists regularly.
- There is no single blanket profile. As a minimum, students and staff have separate profiles.
- The filter is active and up to date on school or college-managed devices (including those taken off site), on unmanaged devices under a BYOD scheme, and for guests on the school internet. Devices the school does not manage should be on a separate virtual network.
- Every internet feed is covered, including backup connections and portable wifi devices.
- Ways round the filter, such as VPNs, proxy services and encryption methods, are blocked. The UK Safer Internet Centre's appropriate filtering definitions, which the DfE page links, name DNS over HTTPS and ECH as examples, and ask providers to be clear about how they handle encrypted traffic.
- The logs identify, as a minimum, the device name or ID and IP address (and the individual where possible), the time and date, and the search term or content blocked.
- Safe search is on by default (or a child-friendly search engine is used) and locked into the browser, and users cannot install other browsers or unauthorised plugins.
App content on desktops and phones is often presented differently from web pages, so the standard says to ask the filtering provider whether it can filter apps, and to apply technical monitoring to devices that use them. Filtering logs hold personal data, so each school or college carries out its own data protection impact assessment (DPIA) and reviews the provider's privacy notice.
A temporary exception, for example so that IT administrators can run system updates, needs approval and documentation from the SLT member responsible, and the DSL assesses the safeguarding implications.
Checking that the filter works
Checks are part of the review process and are recorded. The standard sets no fixed frequency: it depends on the school's context, the risks the review found and other risk assessments, and checks should be made from both a safeguarding and an IT perspective. They confirm that the set-up has not changed or been switched off, across:
- every device the school or college manages, including laptops taken home, tablets and audio-visual equipment;
- every site, where buildings are on different premises;
- each user group, so that students, staff and guests get the content their profile allows.
The log records when the check took place, who did it, what was tested and what action followed. New devices and services are checked before they are handed out.
For a baseline test, the standard points to tools such as the one from South West Grid for Learning (SWGfL), TestFiltering, to check that the filter blocks, as a minimum, illegal child abuse material, unlawful terrorist content and adult content. KCSIE also mentions an SWGfL tool that checks whether a filtering provider is signed up to the relevant lists. TestFiltering's own page says its results are an indication, and that questions should go to the system administrator or the filtering provider. A clean result on one laptop says nothing about the others, so run it from each profile, site and device type, and log each run.
Changing filter settings during term
KCSIE warns governing bodies and proprietors that "over blocking" should not lead to unreasonable restrictions on what children can be taught (paragraph 163). The standard says the filter should not unreasonably affect teaching, learning or administration, or stop students learning to assess and manage risk themselves. A category switched on mid-morning for the student profile can take out a site a lesson depends on.
A safer order for any change:
- Write down the current setting, or export the policy if the product allows it, so you can put it back exactly.
- Apply the change to a test account in the right user group, or to a test device, first. Open the sites and apps that lessons rely on, and run the filter test again.
- Move it to the live groups at a time when someone can watch for reports, and tell staff how to report a problem.
- If teaching breaks, restore the recorded setting first and investigate afterwards. Where the change was made for a safeguarding reason, agree the rollback with the DSL before you make it. A fix that needs an exception goes through the SLT approval route above.
- Add the change, its reason and the test to the log, so the SLT's record of what is blocked or allowed and why stays current.
Staff should report restrictions they think are unreasonable, topics that could create unusual activity in the filtering logs, and misspellings that reach restricted material.
Monitoring watches and reports, it does not block
The standard calls filtering preventative and monitoring reactive. Monitoring looks at what users do on devices, and sometimes records it, but does not stop anyone seeing or doing anything. It can be manual, such as a teacher walking round looking at screens, or technical, with device software that raises alerts.
All staff in a room with students on devices are expected to do some in-person monitoring. Whether to add technical monitoring is decided through the review, based on student age, risk profile, how easy screens are to see, the number of devices and whether they go home. Mobile and app technology is the exception: where it is used, the standard says to apply a technical monitoring system, because the filter might not pick up app content.
A monitoring plan can combine device monitoring through device management software, in-person monitoring in the classroom, and network monitoring from logs of internet traffic and web access. As a minimum it includes weekly reports highlighting incidents, and immediate reports when an incident is classed as high risk. Technical monitoring should tell users the device is monitored, for example with a message at each sign-in. The monitoring should identify and alert on behaviours linked to the four areas of online risk set out in KCSIE: content, contact, conduct and commerce.
IT support that manages device monitoring makes sure it works on and off site, reports on student device activity, receives safeguarding training including online safety, and reports safeguarding concerns to the DSL. Monitoring procedures belong in the acceptable use policy, and a technical monitoring system needs its own DPIA.
The DSL is responsible for any safeguarding or child protection matter that monitoring identifies. What happens next is set by KCSIE and the school's own safeguarding policies, not by the IT team or the monitoring product.
Where generative AI fits
The DfE page notes that AI-generated content increasingly appears in apps and browsers, and asks schools and colleges to weigh the safeguarding implications in their review. Each should consider whether it needs a solution that can handle real-time, dynamic, personalised and AI-generated content. When a school introduces a specific generative AI product, the standard refers to the DfE's Generative AI: product safety standards. Those expect filtering to be built into learner-facing products, and full content moderation to stay in place when the product is used through an institutional account on any device, including BYOD and smartphones.
Common questions
- Do schools have to follow the DfE filtering and monitoring standard?
- KCSIE is statutory guidance that schools and colleges in England must have regard to. It says governing bodies and proprietors should ensure appropriate filtering and monitoring systems are in place and reviewed at least once every academic year, and points to the DfE standard for the detail. The DfE describes the standard as its recommended approach to meeting those expectations, and says schools and colleges should already be meeting it.
- How often should a school check its web filter?
- The provision is reviewed at least once every academic year, and again after events such as new devices, major software updates or network changes. The standard sets no fixed interval for checks: it bases the frequency on the school's context and the risks its review found. Every check is logged with the date, who did it, what was tested and what action followed.
- Does every school need a technical monitoring system?
- The standard expects all staff to do some in-person monitoring when students are on devices, and leaves additional technical monitoring to the risks the review identifies. Where students use mobile or app technology, it says to apply a technical monitoring system, because the filter might not pick up app content. The monitoring plan still needs weekly incident reports and immediate reports for high-risk incidents.
Sources
Every requirement, licence detail and figure in this guide comes from these pages, read on 20 November 2026. Guidance, licences and products change: check the source before you rely on one.
- Meeting digital and technology standards in schools and colleges: Filtering and monitoring: core standard, Updated 16 September 2026 (Department for Education)
- Meeting digital and technology standards in schools and colleges, Updated 16 September 2026 (Department for Education)
- Keeping children safe in education 2026: Statutory guidance for schools and colleges, September 2026, in force from 1 September 2026 (Department for Education)
- Keeping children safe in education, Updated 17 November 2026 (Department for Education)
- Generative AI: product safety standards, Updated 19 January 2026 (Department for Education)
- Appropriate Filtering (UK Safer Internet Centre)
- TestFiltering.com: Verify your Internet is Filtered (SWGfL)
Spotted something wrong or out of date? Tell us and we will correct it.