- The template supports the review gates for machine-readable submissions, raw data readiness, public-summary structure, confidentiality handling, and declaration language.
"machine-readable format"
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.
Structured answer sets in this page tree.
Cited legal and guidance references.
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.
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.
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.
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.
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.
Use the cited sources listed here to verify obligations and the supporting evidence requirements.
Verify the following areas from the cited sources: Article 11 report sections, evidence categories, annual updates, and public-summary requirements using the cited sources on this page.
Walk through your DMA Article 11 reporting owners, gaps, source support, and publication gates with Sorena.
"machine-readable format"
"core platform services"
"Article 11 DMA"
"non-confidential summary"