{"resourceId":"dfe-product-safety-standards","versions":[{"version":"legacy/2026-08-29/dfe-product-safety-standards","resource":{"id":"dfe-product-safety-standards","title":"Education safety standards turn broad AI principles into product requirements","organization":"UK Department for Education","sector":"Education technology procurement","geography":"United Kingdom","publishedAt":"January 19, 2026","sourceName":"Generative AI: product safety standards","sourceLabel":"Department for Education standards","sourceUrl":"https://www.gov.uk/government/publications/generative-ai-product-safety-standards/generative-ai-product-safety-standards","evidenceClass":"standards-guidance","outcomeClass":"emerging","topics":["infrastructure","data-security","governance-procurement","accessibility-workforce","operating-model"],"finding":"The Department for Education published a supplier-oriented baseline covering stated purpose, learner population, evidence claims, safeguarding, access control, testing, patching, privacy, and equality duties for generative AI products.","sledRelevance":"Districts and higher-education buyers can translate the standards into solicitation questions, acceptance criteria, contract schedules, and renewal evidence instead of relying on generic responsible-AI promises.","evidence":"The standards require clear intended use cases and target demographics, including age and special educational needs; robust and transparent evidence for impact claims; protections against harmful content and jailbreaks; permission levels; testing before releases; authentication; lawful and transparent personal-data handling; and attention to public-sector equality duties.","architectureImplications":"Require identity integration, role-based permissions, filtering, monitoring, version testing, patch management, administrative controls, data-flow documentation, and an exit route compatible with existing school security standards.","governanceImplications":"Embed the standard in market research, product scoring, contract clauses, acceptance testing, incident obligations, change notification, accessibility review, and periodic renewal decisions.","securityPrivacyImplications":"Demand explicit data handling, lawful basis, authentication, least privilege, jailbreak resistance, pre-release safety tests, rapid security updates, and transparent handling of learner and teacher data.","caveats":"This is normative guidance, not an evaluation of products or evidence that suppliers currently meet the requirements; several assurances depend on upstream providers and buyer verification."}},{"version":"enrichment/2026-09-05T02:33:27.019Z/dfe-product-safety-standards","resource":{"id":"dfe-product-safety-standards","title":"Education safety standards turn broad AI principles into product requirements","organization":"UK Department for Education","sector":"Education technology procurement","geography":"United Kingdom","publishedAt":"January 19, 2026","publicationDate":"2026-01-19","eventDate":null,"sourceName":"Generative AI: product safety standards","sourceLabel":"Department for Education standards","sourceUrl":"https://www.gov.uk/government/publications/generative-ai-product-safety-standards/generative-ai-product-safety-standards","evidenceClass":"standards-guidance","outcomeClass":"emerging","topics":["infrastructure","data-security","governance-procurement","accessibility-workforce","operating-model"],"finding":"The Department for Education published a supplier-oriented baseline covering stated purpose, learner population, evidence claims, safeguarding, access control, testing, patching, privacy, and equality duties for generative AI products.","sledRelevance":"Districts and higher-education buyers can translate the standards into solicitation questions, acceptance criteria, contract schedules, and renewal evidence instead of relying on generic responsible-AI promises.","evidence":"The standards require clear intended use cases and target demographics, including age and special educational needs; robust and transparent evidence for impact claims; protections against harmful content and jailbreaks; permission levels; testing before releases; authentication; lawful and transparent personal-data handling; and attention to public-sector equality duties.","architectureImplications":"Require identity integration, role-based permissions, filtering, monitoring, version testing, patch management, administrative controls, data-flow documentation, and an exit route compatible with existing school security standards.","governanceImplications":"Embed the standard in market research, product scoring, contract clauses, acceptance testing, incident obligations, change notification, accessibility review, and periodic renewal decisions.","securityPrivacyImplications":"Demand explicit data handling, lawful basis, authentication, least privilege, jailbreak resistance, pre-release safety tests, rapid security updates, and transparent handling of learner and teacher data.","caveats":"This is normative guidance, not an evaluation of products or evidence that suppliers currently meet the requirements; several assurances depend on upstream providers and buyer verification.","streamIds":["k12","student-success","campus-operations"],"roles":{"sales":"Interpretation — Customer problem: education buyers need testable product requirements rather than broad AI safety promises. Stakeholders: procurement, curriculum, safeguarding, accessibility, privacy, IT, and representatives of the intended learners. Discovery: what is the stated purpose; which ages and special educational needs are included; what supports impact claims; and which assurances depend on upstream providers? Value hypothesis: explicit requirements may improve product comparison and expose unmet safeguards before commitment. Potential engagement: convert the baseline into use-specific evaluation questions and contract evidence schedules. Unsupported claims: the UK standards are normative guidance, not product certification or demonstrated educational outcomes. U.S. buyers must adapt legal and equality obligations locally rather than treat this record as a compliance determination.","engineering":"Interpretation — Fit: assess a defined education AI product against its intended population and tasks. Architecture and integration: verify identity, role permissions, filtering, monitoring, administrative controls, data flows, patching, release testing, and an exit route compatible with existing systems. Prerequisites: supplier documentation, target-user requirements, safety test cases, and visibility into upstream dependencies. Constraints: buyer assurance may be limited by what suppliers and their model providers disclose; controls must match actual learner access. Security: exercise harmful-content and jailbreak resistance, authentication, least privilege, and teacher/learner data handling. Proposed proof: run population-relevant accessibility and safety scenarios, verify model-change behavior and patch responsibilities, and record which requirements are demonstrated, unsupported, or awaiting remediation.","delivery":"Interpretation — Work: embed the requirements in product scoring, contract schedules, acceptance tests, incident duties, change notices, and renewal reviews. Dependencies: supplier evidence, procurement/legal support, safeguarding and accessibility expertise, and upstream-provider cooperation. Ownership: procurement tracks commitments; the education service owner accepts intended use; IT/privacy/safeguarding leads own controls and exceptions. Skills and adoption: train administrators and educators on approved use, permissions, incident reporting, and limitations for the target population. Governance checkpoints: selection, pre-use acceptance, material release, and renewal. Proposed acceptance: agreed requirements have traceable evidence, intended-user accessibility/safety tests pass, and unresolved gaps have explicit owners and decisions. Risks include treating vendor statements as verification and carrying UK-specific duties into local policy without qualified review."},"retrievedAt":null,"enrichedAt":"2026-09-05T02:33:27.019Z","enrichmentBasis":"archived evidence"}}]}