EU MSR authority request response playbook

Open one response record as soon as a market surveillance authority, customs authority, online-platform escalation, Safety Gate follow-up, or importer/distributor request arrives. Capture the authority name, country, contact channel, product identifier, listing or shipment reference, cited legislation, requested documents, requested language, requested sample or test action, and the response date stated by the authority.

Do not add a generic EU-wide operator response deadline if the request does not state one. Regulation (EU) 2019/1020 refers to reasoned authority requests and cooperation obligations, while some sector-specific product rules may contain their own timing rules. Its 30-day period for an Article 22 information request runs between Member State authorities, not from the authority to the economic operator. Treat the request's stated date, the relevant sector law, and the approved escalation path as the controlling schedule.

Before answering substance, identify the exact product population: model, variant, batch, software or firmware version, serial range, packaging language, importer, distributor, marketplace seller, fulfilment provider, country of first EU placement, and whether the offer was targeted at EU end users through online or distance sales.

Then map the product to the applicable Union harmonisation legislation and the economic-operator role. For Article 4 products, the responsible EU economic operator can be an EU manufacturer, importer, authorised representative with a written mandate, or EU fulfilment service provider where no manufacturer, importer, or authorised representative is established in the Union.

Create a pack that answers the request without over-disclosing unrelated products. The baseline pack should include a cover letter, product identification table, applicable legislation matrix, Article 4 economic-operator details where relevant, EU declaration of conformity or declaration of performance, technical documentation index, test reports, risk assessment, instructions and safety information, label and packaging evidence, supply-chain traceability, and prior corrective-action history.

If the authority asks for technical documentation, verify whether the company holds it directly or needs manufacturer, authorised representative, importer, or fulfilment-service-provider cooperation. Article 4 guidance treats existence and availability of technical documentation as a practical obligation, not merely a paper label.

If the request involves samples or testing, preserve chain of custody. Record who selected the unit, whether it came from stock, retail, customs, marketplace fulfilment, or a customer return, what condition it was in, and whether the authority, company, or a third-party laboratory performed the test.

Regulation (EU) 2019/1020 allows authorities to perform documentary, physical, and laboratory checks based on adequate samples and gives them power to acquire product samples, including under a cover identity. Where no other effective means can eliminate a serious risk, Article 14 also supports proportionate warning, content-removal, or access-restriction measures for online interfaces. The response record should keep product evidence, testing evidence, and online-content actions together.

For Article 4 products, verify that the EU economic operator's name, registered trade name or trademark, and contact details including postal address are indicated on the product, packaging, parcel, or accompanying document. A website may help contact speed, but the cited Article 4 guidance says it is not a replacement for a postal address.

The Article 4 contact should be able to provide or obtain conformity documentation, inform authorities when it has reason to believe the product presents a risk, and cooperate on corrective action. If the Article 4 contact is an authorised representative, preserve the written mandate and confirm that it covers the Article 4 tasks.

After the initial evidence review, classify the issue as no finding, documentation gap, formal non-compliance, technical non-compliance, product presenting a risk, serious-risk escalation, unauthorised channel, or counterfeit or suspected-counterfeit scenario. Match the action to the finding: provide documents, correct labels, amend instructions, stop a listing, hold stock, update importer or fulfilment instructions, repair, withdraw products still in the supply chain, recall products already with end users, or otherwise mitigate the risk.

Safety Gate and ICSMS are authority coordination systems, not company filing portals or substitutes for the response file. The authority, not the economic operator, makes the MSR Article 20 rapid-alert notification and enters the Article 34 information-system record. The company should supply accurate product, risk, distribution, and measure data and retain any references the authority provides.

Keep a complete response file that a later reviewer can follow without reopening chat threads or inboxes. The record should show what the authority requested, what product population was in scope, which law and economic-operator role applied, what evidence was sent, what was withheld as unrelated or privileged, what corrective action was decided, and the outcome: no finding, further request, voluntary measure, authority-ordered measure, customs release, continued hold, refusal, appeal, or verified closure.

Use the evidence record for future authority requests, distributor questions, marketplace reviews, customs holds, insurance questions, and product changes. Reopen it when the product changes materially, a supplier changes, a test report is superseded, new incident data arrives, the Article 4 contact changes, or an authority asks a follow-up question.