Evidence GuideEU

EU MSR Authority Evidence Requests

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.

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

Structured answer sets in this page tree.

Primary sources
3

Cited legal and guidance references.

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

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.

Section 1

What authorities can ask for

Article 14 of Regulation (EU) 2019/1020 requires Member States to give market surveillance authorities investigation and enforcement powers. For evidence requests, the core powers are requests for documents, technical specifications, data, compliance information, technical aspects of the product, and access to embedded software 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.

  • Log the authority, legal basis cited, product model, serial or batch scope, market, sales channel, and requested response format.
  • Separate formal compliance evidence, such as declarations and labels, from technical evidence, such as test reports, risk assessments, drawings, specifications, software access notes, and notified-body certificates.
  • Capture supply-chain evidence that can answer who made, imported, fulfilled, distributed, or sold the product and how many units or equivalent models are in scope.
Section 2

Operator duties to cooperate

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.

  • Name the EU-established economic operator that is responsible for the Article 4 tasks and record why that role applies.
  • Keep the EU declaration of conformity or declaration of performance ready where sector legislation requires it, and maintain a technical-documentation index showing who can provide each item.
  • If the operator does not hold the full technical file, keep manufacturer assurances, request tickets, delivery confirmations, and escalation notes showing that the documentation can be produced for the authority.
Section 3

Documentation and test evidence pack

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.

  • Tie every test report or certificate to the product model, variant, firmware or hardware version, sample date, lab or conformity assessment body, standard or requirement tested, and conclusion.
  • Flag gaps separately: missing declaration, incomplete technical documentation, outdated test report, untested variant, supplier-only assertion, or documentation that does not match the marketed product.
  • Keep a response register showing what was requested, what was supplied, source owner, date sent, language used, confidentiality markings, and unresolved follow-up items.
Recommended next step

Prepare an authority-ready evidence response

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.

Section 4

Sampling, testing, and investigation records

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.

  • Record whether the authority request is documentary only, includes physical samples, or refers to authority testing already performed.
  • Preserve sample traceability: model, batch, seller, channel, date obtained, serial number, accessories, instructions, packaging, and software version.
  • Map each failed or questioned test result to the specific requirement, proposed corrective action, affected products, and communication to the authority.
Section 5

Escalation after non-compliance or serious risk

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.

  • Escalate internally when the request alleges non-compliance, risk, missing documentation, failed testing, unsafe use, online-interface concerns, or inability to obtain manufacturer evidence.
  • Keep corrective-action records that show the affected product population, root cause, action owner, authority deadline, customer or distributor communications, withdrawal or recall evidence, and closure confirmation.
  • When serious risk is alleged or found, preserve the risk assessment, authority measure, notification references, public-warning materials, and records of product withdrawal, recall, or sales restriction.
Section 6

Records to retain after the response

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.

  • Retain the original request, all submissions, translations, confidentiality assertions, acknowledgements, authority follow-ups, and closure communications.
  • Link the authority record to the product technical file, complaint file, supplier file, release record, and corrective/preventive-action record where those records exist.
  • Use a clear status: open, awaiting manufacturer evidence, submitted, corrective action requested, serious-risk escalation, withdrawn or recalled, closed, or monitoring.
Primary sources

References and citations

eur-lex.europa.eu
Referenced sections
  • 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"
single-market-economy.ec.europa.eu
Referenced sections
  • Commission overview describes market surveillance actions such as withdrawals, recalls, and sanctions to stop non-compliant products or bring them into compliance.
"actions such as product withdrawals, recalls and the application of sanctions"
eur-lex.europa.eu
Referenced sections
  • Article 34 grounds authority information-system records for measures, testing reports, corrective action, injuries, objections, and additional check information.
"reports of testing carried out by them"
Related guides

Explore more topics

EU Market Surveillance Regulation Checklist
Practical EU MSR checklist for Union harmonisation scope, Article 4 responsible operators, distance sales, labels, technical documentation, authority requests, border controls, corrective actions, ICSMS, and Safety Gate awareness.
EU Market Surveillance Regulation deadlines and compliance calendar
Grounded Regulation (EU) 2019/1020 calendar covering application dates, Article 4 checks, online sales, authority requests, border holds, documentation readiness, and corrective action triggers.
EU Market Surveillance Regulation FAQ
Concise FAQ on Regulation (EU) 2019/1020: Article 4 economic operators, distance sales, authority requests, customs controls, corrective action, serious risk, ICSMS, Safety Gate, and EUPCN.
EU Market Surveillance Regulation requirements
MSR requirements for Article 4 responsible economic operators, distance sales, authority requests, technical documentation, customs holds, corrective action, ICSMS, and Safety Gate.
EU Market Surveillance Regulation vs Decision No 768/2008/EC: side-by-side comparison
Compare Regulation (EU) 2019/1020 market-surveillance controls with Decision No 768/2008/EC product-marketing, CE marking, EU declaration, and conformity-assessment concepts.
EU MSR Applicability Test
Test whether Regulation (EU) 2019/1020 applies to a product, including Union harmonisation scope, EU distance sales, Article 4 operator duties, and evidence checks.
EU MSR Article 4 responsible person: practical duties and compliance obligations
Article 4 EU Market Surveillance Regulation guide covering eligible EU responsible economic operators, contact display, documentation access, and authority cooperation.
EU MSR Article 4 setup workflow
Set up Article 4 compliance for covered EU harmonised products: confirm scope, assign the EU economic operator, verify contact details, collect DoC and technical-documentation evidence, and prepare authority and import-release records.
EU MSR Article 4: who is the responsible economic operator?
Article 4 guide for products needing an EU responsible economic operator under Regulation (EU) 2019/1020, including roles, contact display, documentation, cooperation, and evidence.
EU MSR Article 6 distance sales and online offers
How Regulation (EU) 2019/1020 Article 6 treats online and distance-sales offers as made available on the EU market, including targeting indicators, marketplaces, Article 4 operator checks, and evidence to retain.
EU MSR authority request response playbook
Practical EU Market Surveillance Regulation playbook for triaging authority requests, compiling documentation, handling samples, checking Article 4 contacts, and preserving evidence.
EU MSR Authority Request Triage Workflow
A concrete EU Market Surveillance Regulation workflow for handling market surveillance authority requests, evidence packs, Article 4 contacts, samples, risk escalation, corrective action, and records.
EU MSR border hold response workflow
Workflow for responding to an EU customs suspension under Regulation (EU) 2019/1020, with Article 4 contact checks, evidence pack contents, release paths, and refusal outcomes.
EU MSR Compliance Obligations
EU Market Surveillance Regulation compliance guide covering Article 4 responsible operators, distance sales, authority requests, technical documentation, customs holds, and corrective action records.
EU MSR Corrective Actions
How Regulation (EU) 2019/1020 handles corrective action: operator remedies, withdrawal, recall, authority measures, serious-risk escalation, ICSMS, Safety Gate, and evidence records.
EU MSR corrective-action escalation workflow
Concrete EU Market Surveillance Regulation workflow for non-compliance findings, voluntary corrective action, authority measures, serious-risk escalation, ICSMS, Safety Gate, and records.
EU MSR customs and border controls
Customs control guide for Regulation (EU) 2019/1020: suspension triggers, release and refusal outcomes, Article 4 checks, and importer evidence records.
EU MSR Enforcement Powers and Penalties
source-linked guide to Regulation (EU) 2019/1020 enforcement powers: investigations, testing, corrective measures, serious-risk action, border refusals, coordination, and Member State penalties.
EU MSR Investigations and Evidence Requests
How to handle EU Market Surveillance Regulation investigation requests, technical-documentation demands, samples, Article 4 contacts, cooperation, escalation, and evidence records.
EU MSR market surveillance for online marketplaces
How online marketplaces and sellers should evidence EU targeting, Article 4 responsible economic operator checks, product listing data, authority requests, and corrective action under Regulation (EU) 2019/1020.
EU MSR online listings FAQ: Article 6 and Article 4 evidence
FAQ on when online offers are treated as EU market availability under the EU Market Surveillance Regulation and what Article 4 responsible-operator evidence should be ready.
EU MSR online marketplace surveillance
How EU market surveillance applies to online listings, targeted distance sales, Article 4 responsible-operator evidence, authority requests, and serious-risk escalation.
EU MSR online sales and marketplaces
How Regulation (EU) 2019/1020 treats online offers, EU targeting, Article 4 responsible economic operators, listing evidence, authority requests, and corrective action.
EU MSR penalties and fines: Article 41 enforcement risk
EU Market Surveillance Regulation penalties guide covering Article 41 Member State penalty-setting, authority measures, restrictions, withdrawal, recall, customs holds, and documentation failures.
EU MSR sector regulation interfaces
How the EU Market Surveillance Regulation connects with sector product laws: Union harmonisation coverage, Article 4 operators, technical files, DoC, CE marking, customs controls, serious risk, and corrective action.
EU MSR Union testing facilities
What Union testing facilities do under Regulation (EU) 2019/1020, who they serve, how market surveillance authorities use testing, and how they differ from notified bodies.
EU MSR vs DSA: cautious marketplace boundary comparison
MSR-grounded comparison of EU product compliance, Article 4, distance sales, marketplace workflows, customs controls, and when DSA questions need separate sourcing.
EU MSR: EUPCN, ICSMS, and Safety Gate
How the EU Product Compliance Network, ICSMS, and Safety Gate fit together under EU market surveillance, with practical evidence and response steps for operators.
FAQ: EU MSR Article 4 responsible person and economic operator duties
When Article 4 of Regulation (EU) 2019/1020 requires an EU-established responsible economic operator, who can serve, what must be shown, and what sellers should verify.
How does Regulation (EU) 2019/1020 apply to Distance Sales into the EU? | EU MSR FAQ
How EU MSR Article 6 treats online and distance-sale offers targeted at EU end users, with Article 4 and evidence implications.
How should companies respond to an EU market surveillance documentation request? | EU MSR FAQ
EU MSR FAQ on responding to product documentation requests, including Article 4 operator tasks, DoC and technical-file access, cooperation, language, and evidence to keep.
Market Surveillance Regulation vs GPSR
Grounded comparison of Regulation (EU) 2019/1020 and the General Product Safety Regulation for harmonised products, consumer safety, online marketplaces, Safety Gate, customs controls, and corrective actions.
MSR vs EMC, LVD, RED, and RoHS
Compare the EU Market Surveillance Regulation with EMC, LVD, RED, and RoHS: surveillance, customs, Article 4 operators, technical files, DoC, CE marking, and evidence requests.
Regulation (EU) 2019/1020 vs Blue Guide: binding rules and guidance
Compare binding MSR market-surveillance, customs, and Article 4 duties with Blue Guide guidance on EU product rules, economic operators, CE marking, declarations, and technical files.
What corrective actions can market surveillance authorities require under Regulation (EU) 2019/1020? | EU MSR FAQ
Concise EU MSR FAQ on corrective action triggers, voluntary measures, authority restrictions, serious-risk escalation, and records.
What counts as a Serious Risk under EU market surveillance rules? | EU MSR FAQ
EU MSR FAQ explaining serious risk, authority measures, Safety Gate/ICSMS awareness, and operator evidence under Regulation (EU) 2019/1020.
What penalties can apply under EU market surveillance rules? | EU MSR FAQ
How Regulation (EU) 2019/1020 treats market-surveillance enforcement, corrective measures, serious-risk action, and Member State penalties.
What Regulation (EU) 2019/1020 changes
Concrete changes introduced by the EU Market Surveillance Regulation: Article 4 responsible economic operators, distance sales, authority powers, border controls, corrective action, ICSMS, Safety Gate, and EUPCN coordination.
What should importers do when customs holds a product under EU MSR?
EU MSR FAQ on customs holds, release or refusal context, Article 4 contact checks, documentation evidence, and operator response.
When can a fulfilment service provider be the EU Article 4 operator? | EU MSR FAQ
EU MSR FAQ on when a fulfilment service provider can be the Article 4 economic operator, what fulfilment services mean, and what sellers should verify.