Artifact GuideEU DMA

DMA Article 11 Compliance Reporting

Build an Article 11 compliance report that explains, obligation by obligation, how a designated gatekeeper ensures and demonstrates compliance with DMA Articles 5, 6, and 7.

Based on Regulation (EU) 2022/1925, the Commission's Article 11 compliance report template, and Commission procedural material for public summaries and report submission.

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

Structured answer sets in this page tree.

Primary sources
5

Cited legal and guidance references.

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

A designated gatekeeper must submit its first within six months after designation and publish and provide the Commission with a by the same deadline. The report must describe, in a detailed and transparent manner, the measures implemented for Articles 5, 6, and 7. Both documents must be updated at least annually. Build the package by designated service and obligation so each claim can be checked against the implemented measure and its evidence.

Section 1

What the Article 11 compliance report is for

DMA Article 11 requires each gatekeeper to provide the Commission with a report within 6 months after designation. The report must describe the measures implemented to ensure compliance with Articles 5, 6, and 7, and the gatekeeper must update the report and the at least annually.

Article 8 supplies the test the report has to meet: the gatekeeper must ensure and demonstrate compliance, and the measures must be effective in achieving the objectives of the DMA and of the relevant obligation. The report therefore needs an obligation-by-obligation dossier rather than one general compliance narrative.

Submitting a report does not amount to Commission approval of the measures. Article 11 is binding law; the Commission template states the minimum information gatekeepers should provide and may be updated. Use the latest official template, but keep the statutory deadline and duties separate from Sorena's evidence-management recommendations.

  • Start from the designation decision and list each designated core platform service.
  • For each core platform service, map every applicable Article 5, 6, and 7 obligation.
  • For each mapped obligation, state the measure, implementation status, evidence, responsible team, and effectiveness indicators.
  • Track the Article 11 report, , annexes, and underlying data as one controlled reporting package.
Section 2

Template evidence to collect before drafting

The Commission template asks for information about the reporting undertaking, the people who drafted the report, external counsel or technical experts involved, and separate standalone annexes for each designated core platform service.

For each applicable obligation, the template expects a compliance confirmation statement plus an exhaustive explanation of how the undertaking complies. That explanation should include supporting data and internal documents, and the gatekeeper should have underlying raw data ready if the Commission asks for it.

  • Create one annex per designated core platform service and keep the obligation mapping inside that annex.
  • Capture whether each measure was already in place before designation or implemented after designation.
  • For each measure, record the prior situation, implementation date, product, service and device scope, geographic scope, and any extension beyond the EEA.
  • Attach technical and engineering evidence such as data-flow changes, API changes, OS functionality changes, ranking or advertising-auction parameter changes, metrics, demos, and screenshots where relevant.
  • Attach customer-experience evidence such as choice screens, consent flows, warning messages, system updates, available functionalities, and click-by-click user journeys where relevant.
  • Keep the raw data, definitions, and calculation explanations behind reported indicators so the report can be tested.
Section 3

Obligation-by-obligation evidence matrix

The report should make each Article 5, 6, or 7 obligation reviewable without asking the Commission or a third party to infer how the control works. Each row in the evidence matrix should connect the legal obligation, the affected service, the implemented measure, the product facts, and the proof of effectiveness.

If an obligation cannot by nature apply to a relevant core platform service, the template allows that information to be omitted only when the undertaking explains why the obligation cannot apply. That is different from an Article 9 suspension or Article 10 exemption request.

  • Use columns for core platform service, DMA obligation, applicability position, compliance statement date, measure owner, implementation date, and evidence location.
  • For user-interface obligations, include the live flow, pre-change flow, choice-screen copy, consent-rate data where relevant, and testing methodology.
  • For data, interface, or technical-access obligations, include access procedure, format, frequency, terms, security controls, retention policies, and whether the access can be independently audited.
  • For business-user effects, include changes to fees, revenue shares, terms and conditions, pricing-policy clauses, negotiated agreements, and feedback or complaints from Union business users.
  • For effectiveness, include indicators chosen for the specific obligation and explain why those indicators show whether the measure achieves the DMA objective.
  • Where the matrix records non-applicability, cite the specific obligation text and explain why the obligation cannot by nature apply to that core platform service.
Section 4

Non-confidential summary and confidentiality handling

Article 11 requires the gatekeeper to publish and provide the Commission with a within the same deadline as the compliance report. The Commission makes a link to that summary available on its website.

The Commission template says the should give a faithful and meaningful picture of the report, follow the same structure, cover all sections and subsections, and use separate standalone annexes for each core platform service for Section 2. Redactions should not hollow out the summary: for confidential numerical data, the template asks for meaningful ranges, baseline levels, or aggregated data rather than complete removal.

  • Draft the public summary beside the full report so headings, section coverage, and obligation order stay aligned.
  • Mark each proposed redaction as business secret, other confidential information, or not confidential.
  • For each redaction, keep a clear non-confidential description of what was removed and why.
  • Replace sensitive underlying numbers with ranges, baselines, or aggregated values where the template calls for a meaningful public picture.
  • Ask business users that submitted feedback whether they request anonymity or confidentiality, and describe actions taken on feedback in non-confidential form.
Section 5

Submission, update, and operating cadence

The legal cadence should stay narrow and cited: the first Article 11 report is due within 6 months after designation, and the report and must be updated at least annually. The Commission template also expects gatekeepers to highlight differences from a previously submitted report, including relevant annexes.

Operationally, the reporting process should run continuously because the template refers to regular compliance dialogue and ongoing reporting when new compliance measures are developed or events affect DMA compliance. That does not supersede the Article 11 deadline or create one universal interim filing date; it keeps the evidence current enough to support the next report, update, or Commission request.

Trigger an out-of-cycle review when a designation decision adds or removes a service, a Commission specification or non-compliance decision changes the expected measure, a reported product flow or term changes, an indicator materially deteriorates, or complaints reveal that a reported right is not effective in practice.

  • Maintain a change log for every measure, annex, indicator, source dataset, and public-summary redaction.
  • When a product or policy change affects a DMA measure, update the obligation row before the next formal report cycle.
  • When an annual update is prepared, produce a clean version and a redline or equivalent comparison against the prior report and public summary.
  • Keep the report, annexes, public summary, and underlying data machine-readable with searchable and recognizable text.
  • Check the latest Commission template before submission because the Commission states that it may update the template and request further information, testing, indicators, or measures.
Section 6

Practical filing controls before submission

Before submission, check the package for completeness, searchable text, required signatures, and retrievable evidence. Commission Implementing Regulation (EU) 2023/814 says DMA documents are transmitted digitally by default, digitally transmitted documents must carry at least one qualified electronic signature, and the Commission's acknowledgement determines the receipt date.

The filing review should cover content, confidentiality, format, signature, and transmission. A digitally transmitted file can be deemed not received if it is inoperable or unusable, contains malware or another threat, or contains an electronic signature whose validity the Commission cannot verify. The Commission must notify the sender and allow a reasonable opportunity to respond and correct the problem.

What does DMA Article 11 require a gatekeeper to submit?

A designated gatekeeper must provide the Commission with a detailed and transparent compliance report describing measures implemented for DMA Articles 5, 6, and 7, and must also publish and provide a of that report.

How often must a DMA be updated?

The first report is due within 6 months after designation, and both the report and the must be updated at least annually.

Does filing an Article 11 report mean the Commission has approved the gatekeeper's compliance measures?

No. Article 11 requires reporting, while Article 8 requires the gatekeeper to ensure and demonstrate effective compliance. Filing the report does not convert the measures into an approved safe harbour or prevent the Commission from requesting information, specifying measures, opening proceedings, or finding non-compliance.

What evidence should the DMA Article 11 report keep for each obligation?

For each applicable Article 5, 6, or 7 obligation, keep the compliance statement, measure description, prior and current state, implementation date, product and geographic scope, technical changes, customer-experience changes, business-user effects, testing or survey methodology, indicators, raw data, monitoring outputs, and assessment or audit records where relevant.

Can confidentiality remove an obligation from the Article 11 public summary?

Confidentiality can justify protecting business secrets or other confidential information, but the Commission template expects the public summary to follow the report's structure and give a faithful, comprehensive, and meaningful picture. Use non-confidential descriptions, meaningful ranges, baselines, or aggregated data where appropriate instead of deleting the substance of an obligation section.

  • Run a completeness check against Sections 1 to 5 of the Commission template.
  • Verify that each annex has a matching section and that all headings remain visible.
  • Confirm that the head of the compliance function can sign the declaration that the submission is true, correct, and complete to the best of their knowledge and belief.
  • Check machine readability, file integrity, malware scanning, and qualified electronic signature validation before transmission.
  • Save the Commission acknowledgement of receipt with the submitted package and retain the exact version sent; an upload notice alone does not establish the receipt date under Article 11 of the implementing regulation.
Primary sources

References and citations

eur-lex.europa.eu
Referenced sections
  • Procedural rules for DMA document transmission, qualified electronic signatures, acknowledgement of receipt, and files that may be deemed not received.
"Transmission of documents to and from the Commission"
digital-markets-act.ec.europa.eu
Referenced sections
  • Commission page listing the DMA legal texts and the Article 11 compliance report template used to structure submissions.
"Article 11 DMA - Compliance Report Template Form"
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
Official source 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
Official source 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 an official source 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
Follow DMA enforcement from investigation and preliminary findings to non-compliance decisions, fines, daily payments, interim measures, commitments, and remedies.
DMA Gatekeeper Compliance Checklist for Articles 5, 6, 7 and 11
A cited 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 cited 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 DMA Article 7 messaging interoperability requests work, including phased functions, the three-month operational deadline, reference offers, evidence, and safeguards.
DMA penalties and fines: caps, triggers, and enforcement evidence
Compare DMA Article 30 fine ceilings, the narrow 20% repeat test, 1% procedural fines, and Article 31 daily payments, with decision-specific examples.
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
Compare the EU Digital Markets Act and Digital Services Act by covered services, regulated actors, core duties, reporting, dates, evidence, 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 duties with GDPR rules for personal-data processing, consent, lawful basis, portability, accountability evidence, and enforcement.
EU Digital Markets Act Article 11 Evidence Calendar
Build a DMA Article 11 compliance-report calendar with the correct designation trigger, service annexes, evidence owners, annual updates, and publication gates.
EU Digital Markets Act checklist for gatekeeper compliance
A source-grounded Sorena 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
Calculate DMA notification, designation, service-compliance, Article 11 reporting, concentration-notice, and profiling-audit deadlines from the correct legal trigger.
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: application, designation, reporting, and review
DMA timeline separating fixed legal dates, threshold and designation clocks, recurring reports, service-specific decisions, final enforcement, and the first Article 53 review.
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 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.