Skip to content
Landfall
IE OSC · IE-OSC-REPORTING-SYSTEM

IE OSC Online Safety Code, Part B s 15 (paras 15.1-15.3) - Reporting and flagging: mechanisms for seven content categories…

Operate transparent, user-friendly reporting and flagging for the para 15.1 categories, explain the effect given to reports, and point notifiers to the complaints procedure

HIGHProcess dutyUser rightsBinding regulationIn forceApplies from 21 July 2025

Where this comes from

Provision: Online Safety Code, Part B s 15 (paras 15.1-15.3) - Reporting and flagging: mechanisms for seven content categories, explaining the effect given to reports, pointing notifiers to the complaints procedure; Part A s 10 (paras 10.6(d)-(e))

Instrument: Ireland Online Safety Code

Citation: Coimisiun na Mean Online Safety Code (2024), Part B s 15, paras 15.1-15.3; Part A s 10, paras 10.6(d)-(e); s 16 (complaints route named in 15.3); s 11 (definitions of the reportable categories)

Text version: Coimisiun na Mean Online Safety Code, adopted 10 October 2024 under Section 139K of the Broadcasting Act 2009 as amended by the Online Safety and Media Regulation Act 2022; Part A applied from 19 November 2024 and Part B from 21 July 2025 (dates determined by the Commission; cnam.ie); retrieved from cnam.ie on 2026-09-21.

Read the official text ↗

Who it applies to

It applies when all of these are true:

  • Irish Code assessed scope Q_IE_OSC_IN_SCOPE: YES

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

  • Notification is sent within required timeframe (check regulation for deadline)
  • Notification content is in plain language, readable by target audience
  • Notification includes: what happened, why it matters, what to do next
  • User can access notification history in their account settings
  • Necessary notification delivery outcomes use scoped references, channel and attempt time without message bodies or extra recipient data

Questions people ask

Does IE OSC Online Safety Code, Part B s 15 (paras 15.1-15.3) - Reporting and flag… apply to my service?
It applies when Irish Code assessed scope Q_IE_OSC_IN_SCOPE: YES.
From when does this apply?
IE OSC Online Safety Code, Part B s 15 (paras 15.1-15.3) - Reporting and flag… applies from 21 July 2025. Its current status is: in force.

Find out whether this one lands on you

Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.

Run the pre-scanAll IE OSC obligations

Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.

What Landfall Is NOT

Critical Boundaries

Understanding these boundaries is essential before using this product. Misuse of this tool for purposes outside its scope may create legal, regulatory, or commercial risk for your organization.

NOT Legal Advice

This product does not provide legal advice and does not create an attorney-client relationship.

Interpretations are informational analysis, not legal counsel. Always consult qualified legal professionals for compliance decisions.

NOT a Risk Score

We do not quantify, calculate, or certify your compliance risk level.

No numerical risk rating, compliance percentage, or safety score. Risk assessment requires human judgment about your specific context.

NOT Runtime Enforcement

This is a planning and mapping tool, not a runtime enforcement system.

Does not integrate with your production systems. Does not block, filter, or enforce compliance in real-time. Implementation is your responsibility.

NOT Regulatory Approval

Using this tool does not mean you are compliant with any regulation.

No certification, seal of approval, or compliance guarantee. Regulators will evaluate your actual implementation, not your use of this tool.

NOT Authoritative Interpretation

Our interpretations are not binding and may differ from regulatory guidance.

Only regulators and courts provide authoritative interpretation. Our analysis reflects our reading of requirements, which may be incomplete or incorrect.

NOT a Safe Harbor

This tool does not shield you from enforcement actions or liability.

Documentation of your process is valuable, but does not constitute a legal defense. Compliance is ultimately your organization's responsibility.

NOT an AI Compliance Agent

AI features assist analysis but do not make compliance decisions for you.

AI-generated interpretations require human review and approval. Automated suggestions are starting points, not final answers.

NOT Complete Coverage

We do not cover all regulations, all obligations, or all jurisdictions.

Regulatory landscape is vast and evolving. Gaps in our coverage do not mean those requirements don't apply to you.

What This Tool IS:

  • A structured workflow for mapping regulatory requirements to implementation tasks
  • A documentation system for compliance decisions (audit trail)
  • A collaboration platform for compliance, legal, and engineering teams
  • An informational resource for understanding regulatory obligations