- Operational implementation support for Senior Manager Liability.
"This document section concerns the Protection of children codes of practice under the Online Safety Act (OSA)"
Senior Manager Liability decisions under the UK Online Safety Act should be written in operational language: who is in scope, what must happen, what evidence proves it, and when escalation is needed.
Use this guide to turn official requirements into scope, evidence, owner, and review decisions. This guidance is practical, source-linked, and should be validated against current legal and policy requirements before implementation.
Structured answer sets in this page tree.
Cited legal and guidance references.
This page helps you determine when UK Online Safety Act obligations apply, who owns each action, the required evidence, and the review path before escalation.
Senior Manager Liability is the part of the Act that can make a named senior manager personally relevant to enforcement for certain information offences. In practice, teams should confirm whether the service is in scope, which duty or notice applies, and whether the responsible manager has the authority and oversight to respond.
Start by deciding whether the service is in scope and which illegal-content, children-safety, age-assurance, user-empowerment, transparency, complaints, risk-assessment, or Ofcom enforcement duty is triggered. The answer should name the exact trigger, affected product or process, required action, owner, evidence, and escalation point.
Keep the Online Safety Act source, service-scope decision, user-to-user/search feature map, risk assessment, code-of-practice mapping, age-assurance evidence, and Ofcom-facing record together.
Ownership should sit with the team that can change service design, moderation, recommender systems, age assurance, reporting, complaints, terms, or transparency data, with legal and trust-safety review.
Evidence should show service categorisation, illegal-content risk assessment, children access assessment, children risk assessment, mitigation controls, age-assurance decisions, terms/complaints records, and Ofcom reporting readiness.
Most Online Safety Act mistakes happen at the boundary between user-to-user, search, pornography, category, child-access, illegal-content, and transparency duties.
Use this section before launching a user feature, recommender change, moderation change, age-assurance flow, complaint process, or transparency-reporting process.
Use an Online Safety Act workflow that captures service scope, user groups, risk assessment, code mapping, child-access status, mitigation owner, evidence, and Ofcom escalation path.
The output should be a service-scope memo, risk assessment, children access assessment, mitigation plan, age-assurance decision, complaint workflow, or transparency-report evidence pack.
Use this UK Online Safety Act guide to turn Senior Manager Liability into owners, evidence requests, review checkpoints, and reusable operating records inside Sorena.
Turn Senior Manager Liability into scoped questions, evidence fields, and review tasks.
Use Research Copilot to answer follow-up questions with cited source material.
Review scope, evidence, owners, and the next compliance actions with Sorena.
"This document section concerns the Protection of children codes of practice under the Online Safety Act (OSA)"
"The Online Safety Act 2023 (the Act) protects children and adults online."
"The Online Safety Act 2023 (the Act) is a new set of laws that protects children and adults online."
"Correspondence Implementation and enforcement of the Online Safety Act: letter from DSIT Secretary of State to Ofcom Published"
"Providers must use risk and evidence-based approaches to ensure there is no room for illegal content and activity on their platforms."