ChecklistEU DMA

EU Digital Markets Act Gatekeeper checklist

Use this checklist to test whether DMA work is anchored to a designated gatekeeper, a listed core platform service, and the specific Article 5, 6 or 7 obligation being implemented.

The checks focus on scope, interoperability, data access, self-preferencing, Article 11 reporting, anti-circumvention, evidence, and governance records.

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

Structured answer sets in this page tree.

Primary sources
6

Cited legal and guidance references.

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

The Digital Markets Act checklist should start with the designation decision and the relevant core platform service, not a generic platform policy. A control is ready for review only when it identifies the gatekeeper, the listed core platform service, the Article 5, 6 or 7 obligation, the implemented measure, and the evidence that demonstrates effective compliance. Timings in this page are source-linked; verify current legal source language before implementation decisions.

Section 1

1. Confirm gatekeeper and core platform service scope

Apply DMA obligation checks only to the core platform services listed for a designated gatekeeper. Article 3 requires the Commission designation decision to list the relevant core platform services, and Article 3(10) ties the compliance obligation to those listed services.

For internal triage, separate three questions: whether the undertaking is or may be a gatekeeper, which core platform service is listed or under assessment, and which product features or business user flows sit inside that service.

  • Record the gatekeeper name and the exact core platform service from the Commission designation or gatekeepers page.
  • Check whether the service category is a DMA core platform service, such as an online intermediation service, online search engine, online social networking service, video-sharing platform service, number-independent interpersonal communications service, operating system, web browser, virtual assistant, cloud computing service, or online advertising service.
  • If relying on the Article 3 quantitative presumption, keep evidence for Union turnover or market value, Member State presence, monthly active end users in the Union, yearly active business users in the Union, and the three-financial-year durability test.
  • Treat designation and scope as service-specific: a company may be designated for some core platform services and not for every product it operates.
  • Open a reassessment when there is a substantial change in the facts behind designation, a new listed service, a concentration involving digital services or data collection, or a Commission review of gatekeeper status.
Section 2

2. Check Article 5 obligations that apply without further specification

Article 5 controls should be tested at the level of the relevant core platform service and the affected user flow. The checklist should show whether the gatekeeper has stopped the prohibited conduct or enabled the required access, communication, pricing, complaint, and advertising transparency rights.

Do not close an Article 5 item with a policy statement alone. Keep product screenshots, terms, API behavior, consent records, ad reporting samples, or business user communications that prove the measure works in practice.

  • Personal data combination and cross-use: verify that advertising use, data combination, cross-use, and cross-service sign-in for data combination are blocked unless the required GDPR consent choice is captured, and that refused or withdrawn consent is not requested again for the same purpose more than once in a year.
  • Anti-steering and business user communication: confirm business users can offer different prices or conditions through third-party channels or direct sales channels, promote offers to acquired end users free of charge, and conclude contracts outside the gatekeeper service.
  • Access to acquired content: confirm end users can access subscriptions, features, content, or other items through a business user app even if acquired outside the gatekeeper core platform service.
  • Complaint rights: confirm contracts, support flows, and account controls do not directly or indirectly restrict business users or end users from raising non-compliance issues with public authorities or courts.
  • Tying and registration checks: confirm business users and end users are not required to use the gatekeeper's identification service, browser engine, payment service, payment technical services, or additional core platform services as a condition of using the listed service.
  • Advertising transparency: for online advertising services, test whether advertisers and publishers can receive daily, free-of-charge information on prices, fees, remuneration, deductions, surcharges, and calculation metrics where Article 5(9) or 5(10) applies.
Section 3

3. Check Article 6 obligations for product, data, ranking, access, and portability

Article 6 obligations often require engineering, product, marketplace, advertising, search, and data teams to produce evidence together. The record should connect the legal obligation to the affected interface, ranking system, data pipeline, API, default setting, access condition, or termination condition.

Where a gatekeeper uses security, integrity, privacy, or operating-system protection as a reason for a limitation, keep the justification and show why the measure is strictly necessary and proportionate.

  • Business user data firewall: confirm the gatekeeper does not use non-public data generated or provided by business users, including their customers' activity data, to compete with those business users.
  • Uninstall and defaults: test that end users can easily uninstall non-essential apps and change default settings for operating systems, virtual assistants, and web browsers that steer users to gatekeeper products or services.
  • Third-party apps and stores: verify installation, effective use, alternative access, and default-setting options for third-party apps or app stores, subject only to justified, strictly necessary and proportionate integrity or security measures.
  • Self-preferencing: test ranking, indexing, and crawling so the gatekeeper's own services or products are not treated more favourably than similar third-party services or products, and keep the ranking methodology and monitoring evidence.
  • Switching and interoperability: confirm there are no technical or other restrictions on switching between, or subscribing to, different apps and services accessed through the core platform service.
  • Advertising measurement: confirm advertisers, publishers, and their authorised third parties can access performance measurement tools and the data needed for independent verification.
  • End user data portability: test free, effective portability for data provided by or generated through end user activity, including continuous and real-time access where required.
  • Business user data access: verify free, high-quality, continuous and real-time access to aggregated and non-aggregated data generated in the relevant core platform service context, with personal data shared only where directly connected to the end user's use of the business user's offering and supported by opt-in consent.
  • Search data access: for online search engines, verify fair, reasonable and non-discriminatory access for third-party search engines to ranking, query, click and view data, with personal data anonymised.
  • Access terms and termination: check fair, reasonable and non-discriminatory access conditions for app stores, online search engines, and online social networking services, and confirm termination terms are not disproportionate or unduly difficult to exercise.
Section 4

4. Check Article 7 communications interoperability

Article 7 applies where the designated core platform service is a number-independent interpersonal communications service. The checklist should distinguish Article 7 communications interoperability from Article 6(7) operating-system, hardware, software, or virtual-assistant interoperability.

The compliance record should cover the reference offer, requester intake, technical interfaces or equivalent solutions, security preservation, personal-data minimisation, and the timing for making requested functionalities operational.

  • Confirm whether the designated service is a number-independent interpersonal communications service and whether the requested basic functionality is provided to the gatekeeper's own end users.
  • Verify that interoperability is available upon request and free of charge through necessary technical interfaces or similar solutions.
  • Check the Article 7 functionality sequence: one-to-one text and file sharing after listing, group text and group file sharing within two years from designation, and voice and video calling functions within four years from designation.
  • Confirm the reference offer publishes technical details, general terms, and security details, including end-to-end encryption where applicable.
  • Track each third-party provider request, whether it is reasonable, which functionalities it covers, and whether requested basic functionalities are made operational within three months after receipt.
  • Keep evidence that the gatekeeper preserves its own level of security, collects and exchanges only personal data strictly necessary for interoperability, and justifies any integrity, security, or privacy measures as strictly necessary and proportionate.
Section 5

5. Build the Article 11 compliance report evidence pack

Article 11 requires a detailed and transparent report on measures implemented to ensure compliance with Articles 5, 6 and 7, plus a non-confidential summary. The Commission template expects the report to be organised by each listed core platform service and each applicable obligation.

Use the template as an evidence checklist even before the reporting deadline: it shows the level of specificity needed to demonstrate effective compliance under Article 8(1).

  • For each listed core platform service and applicable Article 5, 6 or 7 obligation, include a compliance statement, the implemented measure, and whether it existed before designation or was implemented after designation.
  • Describe the prior situation, implementation date, product, service or device scope, geographic scope, technical or engineering changes, and customer experience changes.
  • Keep proof for changes to data flows, internal data use policies, security measures, metrics, APIs, operating-system functions, ranking parameters, ad auctions, choice screens, consent forms, warnings, system updates, and user journeys.
  • Document fee, revenue-share, remuneration-flow, terms-and-conditions, privacy-policy, access-condition, and interoperability-condition changes where relevant.
  • Record consultation with end users, business users or interested parties, external consultant involvement, alternatives assessed, user communications, feedback, testing, surveys, consent rates, and impact monitoring.
  • Prepare the compliance report, annexes, non-confidential summary, and underlying data in machine-readable form with searchable and recognisable text, and keep raw data ready for Commission requests.
  • Highlight differences from any previous report and disclose any retention policy for responsive documents without undue delay.
Section 6

6. Test anti-circumvention, governance, and reopening triggers

A DMA checklist should fail any control that works on paper but is undermined by technical design, contract terms, commercial incentives, degraded service quality, non-neutral choices, or interface design. Article 13 makes anti-circumvention a separate governance check.

Governance evidence should show who owns the service scope, legal interpretation, product change, engineering implementation, data access, business-user communication, reporting, and retained proof.

  • Check that services are not segmented, divided, subdivided, fragmented, or split through contractual, commercial, technical, or other means to avoid Article 3 quantitative thresholds.
  • Review whether any contractual, commercial, technical, behavioural, or interface-design practice undermines effective compliance with Articles 5, 6 or 7.
  • Confirm consent flows needed for DMA compliance are not more burdensome for business users than for the gatekeeper's own services.
  • Test whether users or business users who exercise DMA rights face degraded service conditions or quality, undue difficulty, non-neutral choice presentation, or subverted autonomy through interface design.
  • Assign accountable owners for each listed core platform service, obligation, implementation measure, evidence store, report annex, non-confidential-summary entry, requester intake process, and escalation to counsel.
  • Reopen the checklist after product releases, ranking changes, ad auction changes, access-term changes, API or data-pipeline changes, interoperability requests, new consent flows, acquisitions involving digital services or data collection, Commission specification discussions, or Article 11 report updates.
Primary sources

References and citations

digital-markets-act.ec.europa.eu
Referenced sections
  • Commission page identifying designated gatekeepers and their listed core platform services.
"In total, 23 core platform services provided by those gatekeepers are currently designated."
digital-markets-act.ec.europa.eu
Referenced sections
  • Commission Q&A illustrates DMA interoperability specification work and requester process expectations under the DMA.
"free and effective interoperability with hardware and software features controlled by its operating systems"
digital-markets-act.ec.europa.eu
Referenced sections
  • Commission legislation page links the DMA text, procedural regulation, notices, guidelines, and official templates used for compliance governance.
"The DMA contains the main rules"
digital-markets-act.ec.europa.eu
Referenced sections
  • Commission resource page for business-facing DMA materials, including interoperability, data portability, and data access resources.
"Resources for businesses"
eur-lex.europa.eu
Referenced sections
  • Article 13 supports anti-circumvention checks for service fragmentation, technical or contractual undermining of compliance, burdensome consent, degraded conditions, non-neutral choices, and interface design.
"The gatekeeper shall not engage in any behaviour that undermines effective compliance"
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 Article 11 Evidence Calendar
Build a source-grounded DMA Article 11 compliance report calendar with evidence owners, annual update checkpoints, report sections, and review gates.
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.