- Article 4 guidance supports response records for declarations, technical documentation, other conformity evidence, cooperation, and corrective action.
"within a reasonable timeframe or within any deadline set"
Regulation (EU) 2019/1020 gives market surveillance authorities powers to request compliance documents, technical data, supply-chain information, samples, and corrective action for products covered by Union harmonisation legislation.
Use this page to build a response file for declarations, technical documentation, test evidence, authority correspondence, product samples, and escalation records.
Structured answer sets in this page tree.
Cited legal and guidance references.
An EU MSR authority evidence request should be handled as a product-specific investigation record. The response file should identify the product, the economic operator role, the authority request, the documents supplied, any sampling or testing, and the corrective-action path if non-compliance or serious risk is found.
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.
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.
Turn an EU MSR evidence request into a traceable response file with product scope, operator role, declarations, technical documentation, test records, sample handling, and corrective-action status.
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.
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.
"within a reasonable timeframe or within any deadline set"
"actions such as product withdrawals, recalls and the application of sanctions"
"reports of testing carried out by them"