Calendar GuideEU DSA

EU Digital Services Act deadlines and compliance calendar

Track the DSA dates that change operating work: application, user-number publication, VLOP/VLOSE designation, transparency reports, and statement-of-reasons submissions.

Use this page to turn official DSA clocks into calendar records for legal, trust and safety, product, marketplace operations, data, and compliance teams.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
6

Structured answer sets in this page tree.

Primary sources
7

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 9, 2026
Overview

This DSA calendar separates fixed legal dates from repeating operating cadences. It is designed for providers that need to know when the Digital Services Act applies, when user-number and transparency reporting cycles repeat, and when a VLOP or VLOSE designation starts a separate four-month compliance clock.

Section 1

Fixed DSA application dates to anchor the calendar

The DSA entered force after publication in the Official Journal and applies generally from 17 February 2024. Several provisions applied earlier from 16 November 2022, including the user-number publication and designation machinery used for VLOP and VLOSE supervision.

For most providers, 17 February 2024 is the baseline date for DSA operating readiness. For online platforms and online search engines that may approach VLOP or VLOSE scale, the earlier Article 24 and Article 33 provisions matter because they drive user-number publication and designation evidence.

  • 16 November 2022: selected DSA provisions began to apply, including Article 24(2), Article 24(3), Article 24(6), and Article 33(3) to (6).
  • 17 February 2023: online platforms and online search engines had to publish average monthly active recipient information for each service, with updates at least once every six months.
  • 17 February 2024: the DSA applied generally, and Member States had to designate their Digital Services Coordinators by this date.
  • Calendar evidence: keep the legal basis, affected service, provider role, Article 24 publication URL, calculation period, and next review date in one register.
Section 2

VLOP and VLOSE designation clocks

The DSA threshold for very large online platforms and very large online search engines is 45 million average monthly active recipients in the Union. The Commission designates a service after considering reported user numbers, requests, or other available information.

Once designated, a VLOP or VLOSE has four months to comply with the DSA obligations that apply to very large services. The first set of 19 VLOPs and VLOSEs was designated on 25 April 2023 and had to comply by the end of August 2023.

  • Trigger: the service reaches at least 45 million average monthly active recipients in the EU and is designated by the Commission.
  • Clock: four months from Commission notification, where that date is earlier than 17 February 2024.
  • First designation cohort: 25 April 2023 designation of 17 VLOPs and 2 VLOSEs.
  • Evidence to retain: designation decision or Commission list entry, service name, provider entity, notified date, four-month due date, systemic-risk workstream, audit plan, data-access owner, ad-repository owner, and recommender-system owner.
  • Ongoing watch: if a designated service remains below the threshold for an uninterrupted year, the DSA text provides for termination of designation.
Section 3

Transparency-report calendar and reporting periods

Article 15 transparency reports are not a one-time publication. The 2024 transparency-reporting implementing regulation creates harmonised templates, reporting periods, transition rules, publication timing, and retention expectations.

For ordinary intermediary, hosting, and online-platform providers, the first DSA annual transparency report after full application had to be published no later than 16 February 2025. The transition period ends on 31 December 2025, and from 1 January 2026 the annual reporting period is 1 January to 31 December. Reports are due no later than two months after the reporting period ends.

  • 17 February 2024 to no later than 16 February 2025: first annual transparency-report cycle after the DSA's full application for intermediary, hosting, and online-platform providers.
  • 1 July 2025: providers covered by the implementing regulation begin using the Annex I templates for content-moderation reporting as specified for their category and transition cycle.
  • 31 December 2025: transition period ends.
  • 1 January 2026 to 31 December 2026: first full harmonised annual reporting cycle for intermediary, hosting, and online-platform providers.
  • Publication clock: publish transparency reports at the latest two months after the relevant reporting period concludes.
  • Retention evidence: keep each published transparency report publicly available for at least five years, including clearly marked updated versions if corrections are made.
Section 4

Additional six-month reporting cadence for VLOPs and VLOSEs

Very large online platforms and very large online search engines have a shorter reporting rhythm than ordinary providers. Article 42 requires them to publish the Article 15 reports within two months from their DSA application date under the designation rule and thereafter at least every six months.

The implementing regulation also gives VLOPs and VLOSEs a specific template transition: they collect information under the Annex instructions from 1 July 2025, and their first reporting cycle under those templates covers 1 July to 31 December 2025.

  • Designation calendar entry: record the notification date and the four-month application date for the service.
  • First VLOP/VLOSE report clock: two months from the service's DSA application date under the designation rule.
  • Recurring VLOP/VLOSE clock: at least every six months after the first report.
  • Template transition: collect Annex I template data from 1 July 2025 for content moderation engaged in from that date.
  • First harmonised VLOP/VLOSE template cycle: 1 July 2025 to 31 December 2025.
  • Evidence fields: reporting period, publication date, service, EU active-recipient count, moderator resources, language coverage, automated-moderation metrics, risk-assessment link, audit-report link, and owner sign-off.
Section 5

Statement-of-reasons and Transparency Database calendar evidence

Statement-of-reasons work is event driven rather than annual. Article 17 requires hosting services to give affected users a clear and specific statement of reasons for covered restrictions, and Article 24(5) requires online platforms to submit relevant decisions and statements of reasons to the Commission database without undue delay.

The practical calendar control is a daily or near-real-time queue, not a year-end report. The provider should reconcile moderation decisions, user notices, personal-data removal, and database submission status so that missing submissions are visible quickly.

  • Trigger event: restriction of user content or account functionality on grounds that content is illegal or incompatible with terms and conditions, where Article 17 applies.
  • Submission event: online platforms submit Article 17 decisions and statements of reasons to the Commission database without undue delay and without personal data.
  • Daily evidence: moderation decision ID, restriction type, legal or terms basis, user-notice timestamp, personal-data scrub check, database submission timestamp, failed-submission retry status, and reconciliation owner.
  • Database retention awareness: the Commission FAQ says statements are available from the following day, removed from search after six months, daily dumps retained for 18 months, and aggregated dashboard statistics retained for five years.
  • Calendar review: reconcile provider moderation logs against database submissions at a frequency that matches the platform's moderation volume.
Section 6

Practical DSA calendar records to maintain

A useful DSA calendar should distinguish fixed legal dates, repeating publication cycles, designation-triggered due dates, and event-driven evidence queues. Mixing those clocks is how teams miss obligations or overstate dates that apply only to VLOPs and VLOSEs.

Keep the calendar as a controlled record with one line per service and clock. Do not copy a VLOP/VLOSE date to an ordinary intermediary service unless the service has actually been designated or the source supports the same duty.

  • Service profile: service name, provider entity, DSA role, Member State of establishment, Digital Services Coordinator, and whether the service is designated as a VLOP or VLOSE.
  • AMAR record: six-month measurement period, Article 24(2) publication date, public URL, EU count, Member State breakdown if prepared, methodology owner, and next update date.
  • Designation record: Commission designation date, notification date, four-month application date, designation status, and link to Commission list or decision.
  • Transparency-report record: reporting period start and end, applicable template version, publication due date, publication URL, five-year retention end date, and correction/version history.
  • Statement-of-reasons record: daily export or reconciliation period, submission count, rejected-submission count, personal-data scrub outcome, and issue owner.
  • Evidence rule: every calendar line should cite an official external source URL and state whether the date is fixed by law, repeated by cadence, triggered by designation, or triggered by a moderation event.
Recommended next step

Turn DSA dates into service-level evidence records

Use the calendar structure on this page to track which DSA dates apply to each service, which clocks repeat, and which evidence proves publication, reporting, designation, and database submission.

Primary sources

References and citations

digital-strategy.ec.europa.eu
Referenced sections
  • Commission overview confirming the 45 million monthly-user threshold, six-month user-number updates, and four-month compliance period after designation.
"has 4 months to comply with the DSA"
eur-lex.europa.eu
Referenced sections
  • Supports Article 17 statement-of-reasons duties and Article 24(5) submission to the Commission database without undue delay.
"submit to the Commission the decisions and the statements of reasons"
Related guides

Explore more topics

DSA Ads and Recommender Systems: transparency duties, user choice, and evidence
A grounded DSA guide to ad labels, targeting restrictions, recommender parameter disclosure, non-profiling options for VLOPs and VLOSEs, ad repositories, and compliance evidence.
DSA Applicability Test: classify intermediary services, platforms, marketplaces, VLOPs and VLOSEs
A source-grounded EU Digital Services Act applicability test for classifying intermediary services, hosting services, online platforms, marketplaces, VLOPs and VLOSEs.
DSA Article 28 minors protection guide for online platforms
EU Digital Services Act guide to Article 28 minors protection: platform scope, child-safety measures, targeted ads limits, recommender controls, and grounded evidence.
DSA average monthly active recipients: what platforms must publish
A grounded FAQ on average monthly active recipients under the EU Digital Services Act, including publication, EU recipient scope, the 45 million VLOP/VLOSE threshold, and evidence records.
DSA Complaint and Dispute Workflows for Online Platforms
Build DSA complaint, appeal, statement-of-reasons, and out-of-court dispute workflows for online platform moderation decisions.
DSA crisis response for VLOPs and VLOSEs
EU Digital Services Act crisis response guide for VLOPs and VLOSEs: Article 36 Commission decisions, Article 48 crisis protocols, mitigation, governance, requests for information, and records.
DSA Dark Patterns: interface design checks for online platforms
Article 25 DSA guidance for reviewing online platform interfaces for deceptive, manipulative, or choice-distorting design patterns.
DSA Enforcement and Penalties in the EU
How Digital Services Act enforcement works: Commission and Digital Services Coordinator roles, VLOP and VLOSE investigations, fines, periodic penalty payments, and evidence readiness.
DSA illegal content notices: what must be included?
A grounded FAQ on EU Digital Services Act illegal-content notices: Article 16 notice elements, acknowledgement, decision notices, trusted flagger priority, statements of reasons, and records.
DSA Marketplace Trader Traceability FAQ
Answer to what EU Digital Services Act Article 30 requires online marketplaces to collect, verify, display, retain, and evidence for trader traceability.
DSA Marketplace Trader Traceability Guide
EU Digital Services Act guide for online marketplaces collecting, checking, displaying, storing, and evidencing trader traceability information.
DSA notice and action plus statements of reasons guide
A grounded Digital Services Act guide for notice intake, moderation decisions, statements of reasons, DSA Transparency Database submission, complaints, appeals, trusted flaggers, and records.
DSA Notice and Action Workflow for Hosting Services and Online Platforms
A grounded DSA notice-and-action workflow covering notice intake, completeness checks, trusted flaggers, decisions, user communications, statements of reasons, appeals, and records.
DSA recommender transparency FAQ: Article 27 and VLOP options
What EU Digital Services Act recommender transparency requires: main parameters, user options, VLOP/VLOSE non-profiling choices, and evidence to keep.
DSA researcher data access for VLOPs and VLOSEs
Article 40 DSA guide to vetted researcher data access for VLOPs and VLOSEs: DSC requests, eligibility checks, amendment grounds, confidentiality, security, and evidence records.
DSA service tier classifier for platforms, marketplaces, VLOPs and VLOSEs
Classify a digital service under the EU Digital Services Act as intermediary, hosting, online platform, marketplace, VLOP or VLOSE, with EU recipient-count evidence and obligation outputs.
DSA statement of reasons FAQ
When DSA statements of reasons are required, what they must contain, when online platforms submit them to the DSA Transparency Database, and what appeal records to keep.
DSA statement of reasons log workflow for online platforms
Build a DSA statement of reasons log for moderation decisions, Transparency Database submission, complaint links, retention, and QA controls.
DSA transparency report template fields and cadence
A source-grounded template outline for Digital Services Act transparency reports, covering applicable service tiers, reporting periods, CSV/XLSX format, retention, statement-of-reasons links, and required evidence tables.
DSA Transparency Reporting Obligations by Provider Tier
A grounded guide to EU Digital Services Act transparency reports, active-recipient publication, statements-of-reasons submissions, VLOP/VLOSE reports, templates, cadence, and evidence.
DSA VLOP and VLOSE Risk Assessments and Mitigation Guide
Grounded guide to Digital Services Act systemic risk assessments, mitigation measures, audits, transparency reports, data access, and governance evidence for VLOPs and VLOSEs.
DSA VLOP Audit Pack Workflow: Risk, Mitigation, Audit, and Transparency Records
Build a DSA VLOP or VLOSE audit pack covering Article 34 risk assessments, Article 35 mitigations, independent-audit evidence, transparency reports, data access, and compliance governance.
DSA VLOP Risk Assessment FAQ: Article 34, Mitigation, Audits
What VLOPs and VLOSEs must assess under the EU Digital Services Act, when to reassess, how Article 35 mitigation and annual audit evidence fit together, and what records to keep.
DSA vs DMA Platform Rules
Compare the EU Digital Services Act and Digital Markets Act by scope, designation thresholds, obligations, enforcement, evidence, and practical team ownership.
DSA vs GDPR: online-platform governance and personal-data obligations
Compare the EU Digital Services Act and EU GDPR by scope, ads, recommenders, minors, transparency, complaints, enforcement, and evidence.
DSA vs P2B Regulation: EU platform obligations compared
Compare the EU Digital Services Act with the Platform-to-Business Regulation for platform scope, business-user terms, content moderation, ranking transparency, complaints, enforcement, and evidence.
DSA vs Terrorist Content Online Regulation: notice-and-action vs removal orders
Compare DSA content-governance duties with the EU Terrorist Content Online Regulation removal-order workflow for scope, timing, evidence, authorities, and team ownership.
EU Digital Services Act checklist for platforms and hosting services
A grounded DSA checklist for classifying service tiers, notice-and-action, statements of reasons, complaints, transparency reports, ads, recommenders, trader traceability, VLOP/VLOSE duties, and evidence records.
EU Digital Services Act Compliance Guide
DSA compliance guide for intermediary services, hosting providers, online platforms, marketplaces, and VLOP/VLOSE teams: obligations, controls, and evidence to keep.
EU Digital Services Act FAQ: DSA scope, platform duties, VLOPs, reports, and penalties
Concise EU Digital Services Act FAQ covering intermediary-service scope, active-recipient thresholds, illegal-content notices, statements of reasons, trader traceability, recommender transparency, systemic-risk duties, reporting, penalties, and complaints.
EU Digital Services Act penalties and fines: caps and enforcement roles
DSA penalty caps and enforcement roles: Member State fines, Commission fines for VLOPs and VLOSEs, 1% procedural fines, and 5% periodic penalty payments.
EU Digital Services Act requirements by service tier
Overview of DSA obligations for intermediary services, hosting providers, online platforms, marketplaces, VLOPs and VLOSEs, including notices, complaints, ads, transparency reports, audits, data access and enforcement.
EU Digital Services Act service types and scope
Classify DSA service scope across mere conduit, caching, hosting, online platforms, marketplaces, online search engines, and VLOP/VLOSE threshold duties.
EU DSA Transparency Calendar: reporting, SoR database, AMAR updates
Build a DSA transparency calendar for annual reports, statement-of-reasons database submissions, active-recipient updates, and VLOP/VLOSE audit touchpoints.
EU DSA vs UK Online Safety Act: scope, duties, regulator, and evidence
Compare the EU Digital Services Act and UK Online Safety Act for platform scope, risk assessments, child protection, transparency, regulators, enforcement, and owners.