On November 10, 2026, the UK Department for Education (DfE) opened a public consultation on a proposed product certification scheme to assure the safety of education technology and artificial intelligence products used in schools and other education settings across England. The consultation, which closes on February 4, 2027, sets out a risk-based framework that would require certain EdTech products to undergo independent assessment against defined safety criteria before being sold to schools. If adopted, the scheme could take at least 18 months to establish, with a transition period for suppliers and settings to adapt.

In Brief

  • The DfE proposes a government-backed product certification scheme covering four EdTech categories: filtering products, high-risk data processing tools, student-facing generative AI tools, and student-facing personalised learning tools
  • Certification would focus on safety — data protection, harmful content exposure, and risks to children’s cognitive, social and emotional development — not educational efficacy
  • The scheme would use UKAS-accredited Conformity Assessment Bodies to independently assess products against minimum safety criteria
  • Low-risk products such as general office software, static content repositories, and staff-facing tools would be excluded
  • The DfE’s Technology in Schools Survey 2025 found that 50% of school leaders cited safeguarding and data concerns as a barrier to technology adoption
  • The consultation closes on February 4, 2027, with results expected in Spring 2027
  • The proposal could influence EdTech regulation in other markets, including the EU, Australia, and developing education systems

Why the DfE Is Proposing Certification Now

The consultation document, published on GOV.UK, identifies three categories of risk that current safety standards do not adequately address: unlawful use of children’s personal data, exposure to harmful content, and harm to children’s cognitive, social and emotional development from product design choices.

The DfE notes that schools are currently expected to assess technical safety risks with limited information from suppliers and without independent assurance. According to the Technology in Schools Survey 2025, half of school leaders said safeguarding and data concerns were a barrier to increasing technology uptake. The DfE argues that this uncertainty affects both schools and suppliers — schools cannot make informed purchasing decisions, and suppliers face a fragmented route to market with no clear way to demonstrate that their products meet safety expectations.

Existing regulations already apply to EdTech. The Online Safety Act covers certain services, UK GDPR and the Data Protection Act 2018 govern data processing, and the ICO’s Age Appropriate Design Code sets standards for online services likely to be used by children. The DfE has also published its own generative AI product safety standards for suppliers. But there is currently no mechanism to independently verify whether products actually meet these standards.

The Four Product Categories in Scope

The proposal takes a risk-based approach, focusing on products where the likelihood of harm is highest. Four categories fall within the proposed scheme:

1. Filtering Products

Schools are legally required to have filtering systems in place under the statutory guidance Keeping Children Safe in Education. The DfE argues that filtering solutions are critical to online safety but that schools struggle to evaluate whether products meet the required standards, particularly as AI-generated material creates new challenges for content moderation.

2. EdTech Conducting High-Risk Data Processing

Any EdTech product conducting high-risk data processing of children’s data would be in scope. The proposal draws on UK GDPR Article 35 guidance on Data Protection Impact Assessments to define “high-risk.” Products likely to fall within this category include AI tutoring tools, personalised learning systems, behaviour and safeguarding systems, SEND platforms, wellbeing and mental health platforms, and Management Information Systems that process special category data.

3. Student-Facing Generative AI Tools

The DfE specifically calls out generative AI chatbots, tutoring tools, and content-generation tools designed for use by children. Because generative AI outputs are dynamic and unpredictable, existing filtering and monitoring arrangements may not provide sufficient protection. Certification would apply to the product — the app, chatbot, or tutoring tool — rather than the underlying AI model or API. This means the product supplier is responsible for certification, even when using a third-party model.

Notably, the DfE proposes exempting teacher-created AI agents or custom wrappers used within a single education setting. Schools would remain responsible for ensuring locally created tools are safe and lawful.

4. Student-Facing Personalised Learning Tools

Tools that use AI or other technology to tailor content, pace, difficulty, or sequencing based on a child’s data are in scope. The DfE’s concern is that design features may expose children to inappropriate learning pathways, make inaccurate assumptions through profiling, or use engagement patterns that encourage use beyond the point of educational benefit.

What Is Explicitly Excluded

The proposal excludes several product types as low-risk:

  • General office and communication tools (email, word processors) that do not conduct high-risk processing of children’s data
  • Static content without personalisation (PDF textbooks, content repositories)
  • Hardware and infrastructure (computers, tablets, interactive whiteboards, projectors)
  • Staff-facing products, including generative AI tools and administrative systems that do not process children’s data at high risk

This exclusion list is important for EdTech suppliers. It means that a tool like Google Docs, used for writing essays, would not require certification. But an AI tutoring tool that adapts to a student’s performance and processes their behavioural data would. The line is drawn at risk, not at whether a product uses AI.

How Certification Would Work in Practice

The proposed scheme follows a three-tier model:

  1. UKAS accredits Conformity Assessment Bodies (CABs) — The United Kingdom Accreditation Service would accredit independent organisations to assess products.
  2. CABs certify products — Suppliers would submit their products to an accredited CAB, which would assess them against the scheme’s safety criteria.
  3. Settings select certified products — Schools and education settings would be expected to purchase or use products that have been certified.

The DfE is consulting on whether certification should be mandatory or strongly encouraged through procurement guidance. The consultation also asks about recertification frequency, surveillance requirements, and compliance auditing. The minimum safety criteria would cover data protection compliance, content safety, and design features that could affect children’s wellbeing.

The DfE is careful to note that certification would not assess educational efficacy — only safety. The exception is where a product’s lack of effectiveness could directly put children at risk. The DfE says it will continue supporting schools with evidence about what works through its EdTech Testbeds programme with the Education Endowment Foundation.

Why This Matters Beyond the UK

The UK is not the first country to consider EdTech safety regulation, but its approach is among the most structured. The EU’s AI Act classifies some AI systems in education as high-risk, requiring conformity assessment before deployment. Australia has been developing its own framework through the eSafety Commissioner. What makes the UK proposal distinctive is its product-level certification focus — assessing specific products rather than general regulatory compliance.

For EdTech suppliers operating globally, this creates a patchwork of requirements. A product certified in the UK may still need separate assessment for the EU market. A product that passes the EU’s AI Act conformity assessment may not automatically meet UK certification criteria. For suppliers in developing markets, the cost of multiple certifications could become a barrier to entry.

What This Means for Pakistan and Developing EdTech Markets

Pakistan’s EdTech sector is at a different stage of maturity, but the direction of travel is clear. As covered in our analysis of Pakistan’s first Chromebook assembly line, the country is making significant investments in getting devices into schools. The federal and provincial governments have launched digital literacy initiatives, and private EdTech platforms are growing. But Pakistan does not yet have a product safety certification framework for EdTech.

The UK proposal offers a useful template for countries considering similar regulation. Three elements are particularly relevant:

Risk-based scoping. Rather than regulating all EdTech, the UK scheme targets products where harm is most likely. This is a pragmatic approach for countries with limited regulatory capacity. Pakistan could begin by requiring safety assessments for student-facing AI tools and products that process sensitive children’s data, while leaving lower-risk categories unregulated initially.

Independent assessment. The UK model uses accredited third parties rather than government inspectors. This reduces the burden on regulators and creates a market for assessment services. Pakistan’s Higher Education Commission and the Pakistan Software Houses Association (P@SHA) could collaborate on a similar accreditation model.

Supplier responsibility. The UK proposal places the certification burden on suppliers, not schools. This is the right approach for markets where schools lack the technical expertise to evaluate AI safety. For STEAM education platforms operating in Pakistan, this means the platform provider — not the school — would be responsible for demonstrating that student data is protected and that AI features are safe for children.

Product Builder’s Perspective

For EdTech product teams, the UK proposal signals a shift from voluntary safety standards to assessable requirements. Three implications stand out:

Safety by design becomes a market requirement. Products that cannot demonstrate data protection compliance, content safety, and developmentally appropriate design will face a barrier to the UK education market. This is not unlike what happened with GDPR — companies that treated privacy as an afterthought faced expensive remediation. EdTech teams should treat safety as a first-class product requirement, not a compliance checklist item.

The certification boundary matters. The DfE’s decision to certify the product rather than the underlying AI model is significant. If you build an AI tutoring tool using OpenAI’s API, you — not OpenAI — are responsible for certification. This means product teams need to understand how their model integration affects safety outcomes. The agentic robotics debate about whether general-purpose models are safe enough for physical robots has a parallel here: are general-purpose AI models safe enough for children, and who is responsible when they are not?

Cost and timeline. The DfE estimates at least 18 months to establish the scheme before products can be certified. For early-stage EdTech companies, this is a window to prepare. Products that are already designed with safety in mind will find certification straightforward. Products that need retrofitting will find it expensive. For teams building AI coding tools or educational platforms, the lesson is the same: building safety into the architecture is cheaper than adding it later.

What to Watch Next

  • Consultation responses (February 2027). The DfE will publish responses in Spring 2027. Watch for pushback from EdTech suppliers on cost and scope, and for whether the four product categories change.
  • Mandatory vs. voluntary. The consultation asks whether certification should be required by law or encouraged through procurement. A mandatory scheme would have more market impact but face more supplier resistance.
  • International alignment. Whether the UK scheme aligns with the EU AI Act’s high-risk education categories will determine whether suppliers can use a single assessment for both markets.
  • Pakistan and similar markets. Watch for whether Pakistan’s Ministry of Federal Education and Professional Training, or regulators in other developing markets, reference the UK framework when designing their own EdTech safety standards.

Conclusion

The UK’s proposed EdTech and AI safety certification scheme is a serious attempt to solve a real problem: schools cannot independently verify that the technology they buy is safe for children. The risk-based approach is reasonable, the four product categories are well-targeted, and the use of independent assessment bodies should keep the scheme credible without making it a government monopoly. The key question is whether certification becomes mandatory — and if it does, whether smaller EdTech suppliers can afford to comply.

For product builders in EdTech, the message is clear: safety is becoming a market access requirement, not a differentiator. The teams that build safety into their product architecture now will be the ones who navigate certification smoothly when it arrives.

What would a safety certification framework for EdTech look like in your market? That is a question worth thinking about before regulation arrives at your door.

Sources