Evidence CalendarEU DMA

EU DMA Article 11 Compliance Report Evidence Calendar

Use this calendar to organize the evidence a designated DMA gatekeeper needs for its Article 11 compliance report and non-confidential summary.

The calendar is grounded in Article 11 and the Commission compliance report template: designation-based timing, annual updates, standalone annexes by core platform service, evidence owners, and review gates.

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

Structured answer sets in this page tree.

Primary sources
4

Cited legal and guidance references.

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

Article 11 requires every designated gatekeeper to provide a detailed compliance report to the Commission within six months of designation, publish a non-confidential summary, and keep the report updated at least annually. Track those obligations as milestones with owners, evidence, and review gates.

Section 1

Calendar anchors for Article 11 reporting

Use designation as the starting event for each gatekeeper and designated core platform service. Article 11 ties the first compliance report to the six-month period after designation, and the Commission template expects the report to explain how the gatekeeper demonstrates effective compliance with Articles 5 to 7.

For later cycles, use an annual refresh checkpoint for the compliance report and the non-confidential summary. Do not treat annual refresh as a light editorial update: the template asks prior submitters to highlight differences from the previous version, including relevant annexes.

  • Designation event: record the Commission designation decision, affected core platform services, and Article 5 to 7 obligations that apply to each service.
  • First report window: work back from the Article 11 six-month deadline after designation and reserve evidence gates for drafting, owner approval, non-confidential review, and machine-readable packaging.
  • Annual update: schedule a yearly refresh for the full compliance report and the public non-confidential summary, with a clean version and a marked comparison against the prior submission where a prior report exists.
  • Interim change trigger: reopen the evidence calendar when new compliance measures are elaborated or put in place, or when events affect DMA compliance, because the template expects ongoing compliance dialogue and reporting.
Section 2

Evidence pack by report section

Build the calendar around the template sections rather than around internal team names. Each reporting cycle should leave a traceable pack for the reporting undertaking, the Article 5 to 7 compliance annexes, the compliance function and monitoring section, the non-confidential summary, and the declaration.

For Section 2, use one standalone annex per designated core platform service and applicable obligation. The evidence pack should connect each compliance statement to the measure implemented, the affected product or service scope, the technical or engineering changes, the user or business-user changes, and the data or documents that support effectiveness.

  • Section 1 owner: corporate legal or regulatory operations collects the undertaking name, drafting owners, external counsel or expert details, and representation materials where used.
  • Section 2 owner: product counsel and service owners maintain one annex per core platform service and obligation, with compliance statements, implemented measures, implementation timing, product scope, geographic scope, technical changes, customer-experience changes, and supporting data.
  • Effectiveness evidence owner: analytics, experimentation, data governance, and engineering teams retain methodology, indicators, disaggregated data where informative, survey or testing outputs, system-monitoring outputs, and raw data readiness records.
  • Compliance-function owner: the head of compliance function owns evidence about report preparation, compliance-function independence and resources, management-body reports on non-compliance risk, replies, meeting materials, policies, training, and monitoring documents.
  • Public-summary owner: legal, communications, and confidentiality reviewers prepare a faithful non-confidential summary that follows the compliance report structure and preserves meaningful ranges, baselines, or aggregated data where confidential numerical data cannot be disclosed.
Section 3

Calendar rows to maintain for each reporting cycle

A useful evidence calendar should be a working table, not a generic reminder list. Each row should identify the report section, the affected core platform service, the obligation or template item, the evidence artifact, the accountable owner, the source of truth, the review gate, and the export format.

Do not add fixed public dates unless they come from the relevant designation decision or a Commission request. The stable cadence supported by Article 11 is the first six-month post-designation report and at-least-annual updates.

  • Row type: designation and scope record, with the designated core platform service, case or designation reference, applicable Articles 5 to 7 obligations, and exclusions that the undertaking says cannot apply by nature.
  • Row type: measure evidence, with pre-designation or post-designation status, implementation date, product and geographic scope, engineering changes, interface or customer-journey changes, terms or remuneration changes, consultation evidence, alternatives considered, and security or privacy justification where relevant.
  • Row type: effectiveness evidence, with indicators, definitions, calculation notes, testing or survey methodology, monitoring system output, raw data location, and the owner who can produce underlying data if the Commission requests it.
  • Row type: feedback and response, with business-user or end-user feedback grouped by topic where appropriate, confidentiality preference, action taken, and non-confidential wording for the summary.
  • Row type: governance evidence, with compliance-function reports to the management body, management replies, policy or strategy approvals, training materials, review meeting date, participants, agenda, and minutes.
  • Row type: publication package, with machine-readable clean report, annexes, redline or change log, non-confidential summary, confidentiality log, declaration, signatory details, and publication handoff.
Section 4

Review gates before submission and publication

Use review gates to stop weak Article 11 submissions before they become public or regulator-facing. The Commission template expects true, correct, and complete information, machine-readable files, and a non-confidential summary that lets third parties provide meaningful input.

The review should cover both the confidential compliance report and the public summary. A strong public summary should not simply redact entire sections; the template points to self-standing text, visible headings, coverage of all sections and sub-sections, and meaningful ranges or aggregated data for confidential numerical material.

  • Source gate: every obligation, deadline, designated service, exemption or non-applicability claim points to the DMA text, the Commission template, the designation material, or a Commission request.
  • Completeness gate: each Article 5 to 7 obligation annex has a compliance statement, explanation of measures, supporting data or documents, assessment evidence, feedback handling, and owner sign-off.
  • Raw-data gate: underlying data used for indicators, testing, surveys, and monitoring is identified and ready to be made available if the Commission asks for it.
  • Confidentiality gate: the public summary follows the same structure as the report, keeps headings visible, explains omitted confidential material, and uses meaningful ranges, baselines, or aggregated data instead of blank redactions where possible.
  • Format gate: the compliance report, annexes, non-confidential summary, and underlying data are prepared in machine-readable form with searchable and recognizable text.
  • Declaration gate: the head of the compliance function signs the submission and annex declarations only after owners have confirmed estimates, opinions, and completeness checks.
Primary sources

References and citations

digital-markets-act.ec.europa.eu
Referenced sections
  • The Commission gatekeepers page identifies designated gatekeepers, core platform services, compliance reports, and other DMA case resources that can anchor company-specific calendar rows.
"core platform services"
digital-markets-act.ec.europa.eu
Referenced sections
  • Commission source listing DMA legislation and official DMA templates, including the Article 11 compliance report template.
"Article 11 DMA"
eur-lex.europa.eu
Referenced sections
  • Article 11 requires the non-confidential summary to be published and provided to the Commission, and says the Commission will link to it on its website.
"non-confidential summary"
Related guides

Explore more topics

DMA Anti-Circumvention Design Review for Gatekeeper Product Changes
Review DMA Article 13 anti-circumvention risks in gatekeeper product, interface, contractual, commercial, and technical changes with obligation mapping and evidence records.
DMA Article 11 Compliance Report Template FAQ
How gatekeepers should use the DMA Article 11 compliance report template to document obligation-by-obligation measures, evidence, updates, and non-confidential summaries.
DMA Article 6 Business User Data Access Guide
Grounded guide to EU Digital Markets Act Article 6 data access for business users, end users, authorised third parties, consent boundaries, and evidence handoffs.
DMA Article 6(7) and Article 7 interoperability obligations
Grounded guide to DMA interoperability duties: Article 6(7) operating-system feature access, Article 7 messaging interoperability, request handling, security conditions, and compliance evidence.
DMA Articles 5, 6 and 7 obligations mapped to CPS evidence
Map EU Digital Markets Act Articles 5, 6 and 7 obligations to affected core platform services, product evidence, legal owners, and Article 11 compliance-report artifacts.
DMA compliance program and monitoring for gatekeepers
Build a DMA compliance program around Article 8 effective compliance, Article 11 reporting evidence, Article 13 anti-circumvention controls, and Article 28 compliance-function governance.
DMA Core Platform Service Scoping
Scope EU Digital Markets Act core platform services by service category, designation evidence, user thresholds, and Form GD service-boundary records.
DMA core platform services FAQ
FAQ on EU Digital Markets Act core platform services: Article 2 service categories, gatekeeper designation evidence, user thresholds, service scoping, and Article 11 reporting.
DMA CPS Obligation Matrix Workflow: Articles 5, 6, 7 and Article 11 Evidence
Build a DMA core platform service obligation matrix that links each designated CPS to Articles 5, 6 and 7 duties, product owners, designation evidence, Article 11 report artifacts and review gates.
DMA designation intake workflow for gatekeeper notifications
Build a grounded DMA designation intake record covering core platform service classification, Article 3 thresholds, Form GD evidence, Commission handoff, and Article 11 readiness.
DMA enforcement, penalties, and remedies: Commission powers and evidence
EU Digital Markets Act enforcement guide covering Commission non-compliance decisions, DMA fine caps, periodic penalty payments, remedies, interim measures, commitments, and Article 11 evidence.
DMA Gatekeeper Compliance Checklist for Articles 5, 6, 7 and 11
A grounded EU Digital Markets Act checklist for designated gatekeepers: core platform service scope, Article 5/6/7 controls, Article 11 report evidence, anti-circumvention checks, and review gates.
DMA Gatekeeper Designation Guide: Article 3 thresholds, Form GD, and Article 11 readiness
A grounded EU Digital Markets Act guide for assessing Article 3 gatekeeper thresholds, scoping core platform services, preparing Form GD evidence, handling rebuttal annexes, and planning Article 11 compliance reporting.
DMA gatekeeper thresholds: what counts and when to notify
Standalone FAQ on the EU Digital Markets Act gatekeeper thresholds, Article 3 notification timing, Form GD evidence, and active user-count methodology.
DMA interoperability requests: Article 7 and Commission guidance
How EU Digital Markets Act interoperability requests work for Article 7 messaging services, Article 6(7) operating-system access, gatekeeper evidence, requester evidence, and security safeguards.
DMA penalties and fines: caps, triggers, and enforcement evidence
EU Digital Markets Act penalties guide covering Article 30 fine caps, Article 31 periodic penalty payments, non-compliance decisions, remedies, and evidence records.
DMA Product Change Review Workflow for Articles 5, 6, 7, 11 and 13
Review DMA-relevant product releases for Article 5, Article 6, Article 7, anti-circumvention, Article 11 evidence, and product-owner/legal signoff.
DMA Self-Preferencing Compliance Examples for Ranking and Display
Examples and release-review controls for DMA Article 6(5) self-preferencing checks across ranking, indexing, crawling, search results, marketplaces, app stores, feeds, and virtual assistants.
DMA vs Data Act: gatekeeper duties compared with EU data-sharing rules
Compare the EU Digital Markets Act and EU Data Act by scope, actors, data access, interoperability, reporting, evidence, and enforcement without merging distinct obligations.
DMA vs DSA: Digital Markets vs Services Act
A grounded comparison of the DMA and DSA focused on gatekeepers, core platform services, DMA obligations, Article 11 reporting, interoperability, data access, and enforcement.
DMA vs EU competition law: gatekeeper obligations, Article 11 evidence, and enforcement
Compare the EU Digital Markets Act with EU competition law: ex ante gatekeeper and core platform service duties, Articles 5 to 7, Article 11 reports, penalties, and evidence records.
DMA vs GDPR: gatekeeper data obligations compared
Compare DMA gatekeeper obligations with high-level GDPR overlap for consent, combining personal data, data access, portability, and Article 11 reporting.
EU Digital Markets Act checklist for gatekeeper compliance
A source-grounded DMA checklist for designated gatekeepers and core platform services, covering scope, Articles 5, 6 and 7 obligations, Article 11 reporting, evidence, anti-circumvention, and governance.
EU Digital Markets Act compliance: gatekeeper obligations and evidence
DMA compliance guide for designated gatekeepers: core platform service scoping, Articles 5, 6 and 7 controls, Article 11 reports, anti-circumvention checks, interoperability evidence, and enforcement risk.
EU Digital Markets Act deadlines and compliance calendar
Track DMA notification, designation, six-month obligation start, Article 11 reporting, Article 14 concentration notices, Article 15 profiling audits, and preparation milestones using official EU sources.
EU Digital Markets Act FAQ: gatekeepers, DMA obligations, reports, and enforcement
Concise FAQ on the EU Digital Markets Act for gatekeeper designation, core platform services, Articles 5, 6 and 7 obligations, Article 11 reports, interoperability, business-user data access, compliance evidence, and enforcement.
EU Digital Markets Act requirements for gatekeepers
DMA requirements for designated gatekeepers: core platform service scope, Articles 5, 6 and 7 obligations, Article 11 reporting, anti-circumvention, evidence, remedies, and fines.
EU Digital Markets Act Timeline and Key Milestones: practical obligations and evidence guide
Practical EU Digital Markets Act guide to Timeline and Key Milestones: scope, owners, evidence, edge cases, checklist steps, and external source-linked citations.
EU DMA Applicability Test: gatekeeper thresholds, core platform services, and evidence
Test whether the EU Digital Markets Act may apply to a platform service using the DMA gatekeeper criteria, core platform service categories, EU user thresholds, notification steps, and evidence records.
EU DMA Article 11 Compliance Reporting Guide
Source-grounded guide to EU Digital Markets Act Article 11 compliance reports: report purpose, template evidence, non-confidential summaries, annual updates, and submission steps.
EU DMA do's and don'ts for product teams
Product release checks for designated DMA gatekeepers: Article 5, 6 and 7 obligations, anti-circumvention review, data access, interoperability, self-preferencing and Article 11 evidence.
What do DMA Articles 5, 6, and 7 require from gatekeepers?
FAQ explaining how EU Digital Markets Act Articles 5, 6, and 7 group gatekeeper obligations, what product evidence they require, and how Article 11 reporting connects.