Deadlines and Compliance Calendar 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.
Track the Online Safety Act milestones that have already taken effect: 26 October 2023 for Royal Assent, 17 March 2025 for the duty to protect users from illegal content online, and 25 July 2025 for the duty to protect children online. Use those dates as the baseline for your compliance calendar, then add any later Ofcom consultations, guidance updates, or internal review dates.
The calendar should also capture the service-scope decision, illegal-content duties, child-safety duties, age-assurance requirements, complaints handling, transparency reporting, and Ofcom enforcement follow-up so teams know what is due, who owns it, and what evidence proves completion.
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 Deadlines and Compliance Calendar into owners, evidence requests, review checkpoints, and reusable operating records inside Sorena.
Turn Deadlines and Compliance Calendar 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.