EU MSR Authority Evidence Requests

Article 14 of Regulation (EU) 2019/1020 requires Member States to give market surveillance authorities investigation and enforcement powers. Those powers are exercised under Union and national law, applicable procedural safeguards, proportionality, and data-protection rules. For evidence requests, the core powers cover documents, technical specifications, data, compliance information, technical aspects of the product, and access to embedded software only where necessary to assess compliance.

Authorities can also request supply-chain and distribution-network information, quantities of products on the market, and information about other models with the same technical characteristics where that is relevant to compliance. The request may therefore reach beyond a single certificate if the authority is checking product variants, online sales, import routes, or a wider distribution batch.

Article 4 creates a practical response anchor for covered products: there must be an EU-established economic operator responsible for specified tasks. Depending on the fact pattern, that operator can be an EU manufacturer, importer, authorised representative, or fulfilment service provider.

For evidence requests, the Article 4 task list is direct: verify that the EU declaration of conformity or declaration of performance and technical documentation have been drawn up where required, keep the declaration available, ensure technical documentation can be made available on request, provide information and documentation necessary to demonstrate conformity in a language the authority can easily understand, and cooperate on corrective action.

Build the response pack around the authority's question, not around a generic compliance binder. A formal-documentation request normally needs the declaration, product identity, applicable Union harmonisation legislation, labels and instructions, responsible economic operator details, and a traceable technical-documentation index. The Commission's Article 4 notice is guidance on practical implementation; Articles 4, 11, 14, 16, 18, 19, and 34 of the Regulation are the binding rules described here.

A technical request may need test reports, certificates, standards mapping, product drawings, bill of materials, software or firmware version evidence, risk assessment, quality records, sample identifiers, and explanations for any product variants. Article 11 says authorities must take due account of test reports or certificates from accredited conformity assessment bodies, but that does not supersede the need to match the evidence to the exact model, configuration, and legal requirement.

Evidence requests can move from documents to product checks. Article 11 requires authorities to perform appropriate checks through documentary checks and, where appropriate, physical and laboratory checks based on adequate samples. Article 14 also includes powers to acquire product samples, including under a cover identity, inspect them, and reverse-engineer them to identify non-compliance and obtain evidence.

When sampling or testing is involved, keep chain-of-custody records, sample identifiers, purchase or selection method if known, product configuration, lab instructions, test method, results, authority correspondence, and any business explanation submitted in response. The record should distinguish authority testing from operator-submitted test reports.

If an authority finds that a product does not conform or is liable to compromise protected interests, Article 16 requires the relevant economic operator to take appropriate and proportionate corrective action within a period specified by the authority. Corrective action can include bringing the product into compliance, preventing availability, withdrawal, recall, destruction or making the product inoperable, warnings, prior conditions for availability, and alerts to end users. Warnings, prior conditions, and end-user alerts under Article 16(3)(e) to (g) may be required only where the product presents a risk in certain conditions or only to certain end users.

If the operator does not take corrective action or the non-compliance or risk persists, authorities must ensure withdrawal, recall, prohibition, or restriction and inform the public, Commission, and other Member States. If the product presents a serious risk, Article 19 requires withdrawal or recall where no other effective means eliminates the risk, or prohibition on making the product available, with immediate Commission notification.

Close the matter with an authority-response file that can be reopened if another Member State, customs authority, distributor, marketplace, or notified body raises the same product. Article 34 supports structured information sharing between market surveillance authorities, including measures, test reports, corrective action, and additional information related to checks and testing.

For the operator, the durable record is the response chronology: authority request, internal triage, role analysis, evidence sent, documents withheld or unavailable with reasons, testing and sample records, corrective-action status, and final authority outcome. Avoid inventing retention periods in the response file; use the retention period required by the applicable sector legislation for declarations and technical documentation.