This implementation guide helps translate the UK Online Safety Act duties into owned controls, evidence, review checkpoints, and escalation paths.
Compliance is service-specific and ongoing. The provider must connect each legal duty to current risk evidence, an implemented measure, a named owner, and a review trigger.
Run the program in dependency order: approve service scope, complete the illegal-content assessment, implement core safety and user processes, assess child access, complete child-safety work where triggered, map Part 5 pornography duties, then add formal category duties. Treat each issued as a statutory compliance route, while keeping the underlying duty and any alternative-measure rationale visible. Keep the records current and ready for Ofcom information requests.
1
Section 1
How should teams structure a UK Online Safety Act Compliance plan?
Create a scope record for each regulated user-to-user part, public search engine, and provider-pornography service. Identify the provider entity, UK link, exemptions, users, content flows, and features that affect risk.
Complete separate illegal-content and, where triggered, children's risk assessments. Consult the current Ofcom risk profiles and guidance, record all aspects of the assessment in an understandable form, and complete a new assessment before a .
Translate each risk into a measure, owner, evidence, monitoring signal, and review date. Map issued Ofcom code measures or explain how an satisfies the underlying duty. Maintain content-reporting, complaints, terms, privacy, and freedom-of-expression controls alongside moderation and product measures.
Add Part 5 age-verification or age-estimation work for provider pornographic content and category-specific work only where those legal triggers apply. Ofcom's register, first published on 30 June 2026 and updated on 10 July 2026, is the source for formal , 2A, and 2B status.
Sequence timing from the actual trigger. The first illegal-content and child-access deadlines for existing services passed in March and April 2025, and the first children's risk-assessment deadline passed on 24 July 2025. A later launch, a service coming into scope, or a can create a new assessment deadline; preserve the trigger date and calculation instead of copying the historic calendar.
Use one controlled register linking duty, service part, risk, measure, owner, evidence, legal source, status, and review trigger.
Treat completed 2025 deadlines as historical evidence and use event-based timing for new or materially changed services.
Keep drafts, guidance, issued codes, binding provisions, and Ofcom notices clearly labelled by legal status.
Escalate gaps where the team cannot show the service facts, risk evidence, control operation, or decision rationale.
Who should own the UK Online Safety Act compliance, and what evidence should prove the decision?
As an operating control, assign an accountable program owner with authority to resolve gaps across product, engineering, trust and safety, data, privacy, legal, support, and communications. Give each control and assessment an operational owner and a named reviewer.
Keep signed or approved scope and risk records, code mappings, control specifications, test results, moderation and complaint evidence, age-assurance decisions, terms versions, incident reviews, category records, review logs, and regulator correspondence.
Give owners authority to change the feature or process that creates the risk, not only to write a policy.
Use evidence dates and service versions so a record proves the current control rather than a retired design.
Track open assumptions, accepted residual risks, overdue actions, control failures, and the decision-maker for each.
Prepare a response protocol for accurate, complete, and timely Ofcom information-notice handling.
Which edge cases should teams check before relying on a UK Online Safety Act compliance decision?
A policy or completed assessment does not prove compliance if the service has not implemented and maintained the measures. Code measures are not the only route, but an alternative requires a defensible connection to the underlying duty.
Do not merge different legal tests into one risk score. Scope, illegal-content risk, child access, child harm, provider pornography, and category thresholds each require their own conclusion.
Ofcom can investigate, require information, and enforce the Act. For a breach, the maximum penalty can be the greater of £18 million or 10% of qualifying worldwide revenue. The Act also provides court-based service-restriction and access-restriction routes in specified serious cases. The available response depends on the breached duty, notice, and facts.
Check feature launches before release; a post-launch review may be too late for the significant-change assessment duty.
Check outsourced moderation and age assurance against the provider's own duties, evidence access, testing, and incident response.
Check that safety processing also meets data-protection requirements and that privacy controls do not silently disable required safety measures.
Check whether the formal category register or an Ofcom notice changes reporting, fee, risk-record, or additional-duty work.
How should teams run and review the compliance program?
Use stage gates: no duty mapping without an approved service boundary; no final control plan without completed risk assessments; no without the required pre-change assessment; and no closure without implementation and test evidence.
Review on a scheduled cadence and after changes in service design, user base, risk evidence, incidents, complaints, control performance, formal category, or official codes and guidance. Record whether each change requires a new statutory assessment, a control retest, an updated record, or all three.
Report status by service and duty, not only by project completion percentage.
Keep a dated log of control decisions, exceptions, approvals, tests, and corrective actions.
Use complaints, moderation errors, incidents, and user research as inputs to the next assessment and review.
For and 2A services, update and prepare current illegal-content risk-assessment records for Ofcom's October 2026 expectation.