Market surveillance authorities expect clear, verifiable evidence that a product placed on the EU market is safe and that you can substantiate your safety claims quickly. In practice, that means complete product identification, a documented risk assessment, traceable test evidence where relevant, and controlled records that match what you sell.
This expectation is reinforced by the General Product Safety Regulation (EU) 2023/988 (GPSR) and the Market Surveillance Regulation (EU) 2019/1020 (MSR), which empower authorities to request EU product safety documentation and assess whether your controls are credible and up to date. The sections below break down what is typically requested, what counts as technical documentation, and how to respond without creating new compliance risks.
What evidence do market surveillance authorities typically request?
Authorities typically request market surveillance technical documentation that proves three things: the exact product you sell, the safety risks you identified, and the controls you implemented to reduce those risks. They also expect traceability and consistency across labels, listings, instructions, and supporting records so they can verify the product’s safety profile quickly.
In a product compliance documentation request, you should be ready to provide evidence such as:
- Product identification and traceability including model or SKU, batch or serial information where used, product photos, and supplier and manufacturer details.
- Safety risk assessment showing foreseeable use and misuse, hazard identification, and the measures taken to address risks.
- Test evidence and technical rationale such as relevant test reports, calculations, or engineering assessments that support safety claims.
- Labeling and consumer information including warnings, safety instructions, age grading where relevant, and language versions used for EU consumers.
- Complaint and accident monitoring records showing how you capture safety feedback and what corrective actions you take when issues arise.
- Supply chain and change control including how you manage design changes, material substitutions, and version control for instructions and labels.
Authorities often cross-check whether your EU product safety documentation matches what consumers actually receive. For example, if your online listing claims a feature or safety property, your technical file should support it with evidence, not marketing language.
Which documents count as technical documentation under EU product safety rules?
EU GPSR technical documentation evidence generally includes any controlled record that demonstrates product safety and supports the information you provide to consumers and authorities. Under EU product safety documentation expectations, the focus is not a single fixed template but a coherent set of documents that proves you assessed risks, implemented controls, and can trace what you placed on the market.
Common documents that count as technical documentation include:
- Product description including intended purpose, variants, components, and key safety-relevant characteristics.
- Design and manufacturing information such as drawings, specifications, bill of materials, and critical supplier specifications where safety depends on them.
- Risk assessment and safety rationale documenting hazards, foreseeable conditions of use, and mitigation measures.
- Test reports and evaluations including internal or third-party testing that is relevant to the product’s risks and claims.
- Instructions for use and warnings including the EU language versions you provide and the version history.
- Label and packaging files showing markings, identifiers, and safety statements as sold.
- Quality and control records such as incoming inspection criteria, production checks, and final release controls where they affect safety.
- Post-market monitoring including complaint handling, accident reports, and corrective action records.
Many businesses ask about declaration of conformity and test reports. A Declaration of Conformity is required under certain EU harmonization laws for specific product categories, but it is not a GPSR requirement by itself. Test reports, however, often form core evidence because they can substantiate specific safety properties when testing is relevant to the identified risks.
How should businesses respond to a technical documentation request?
The best response to a product compliance documentation request is fast, complete, and consistent: acknowledge the request, confirm the exact product and scope, and provide a controlled documentation package that matches the product as sold. Do not improvise new claims or backfill documents without clear versioning, because inconsistencies can trigger deeper scrutiny.
- Confirm scope and deadline by identifying the exact model, listing, batch, and the documents requested.
- Freeze the product version by documenting what is currently sold, including labels, instructions, and any recent changes.
- Assemble a single, indexed file set with clear filenames, revision dates, and a short index that maps each authority question to evidence.
- Check for internal consistency across packaging, instructions, online claims, and test evidence.
- Explain gaps transparently if something is not applicable, state why and provide alternative evidence where appropriate.
- Keep a submission record including what you sent, when you sent it, and who approved it internally.
If you operate without an EU presence, plan ahead for how you will make documentation available quickly. Under the MSR, the Responsible Person role is held by an economic operator in the EU and must be able to provide information to authorities and, when risks are identified, notify the manufacturer in line with Article 4 of the MSR. If an Authorized Representative is appointed, that role has separate obligations, including responsibilities related to notifying serious risks to authorities.
How EARP helps with technical documentation requests and EU market surveillance?
To handle EU market surveillance requests confidently, you need an EU-based economic operator that can manage documentation availability, verify completeness, and respond in a controlled way aligned with GPSR and MSR expectations. That is exactly what EARP is set up to do, with independent EU Authorized Representative and GPSR Responsible Person services focused on regulatory compliance.
- Documentation readiness checks to verify the presence and completeness of required product safety documents before a request arrives.
- Technical documentation storage and controlled access so files are organized, retrievable, and ready to be made available to authorities when requested.
- Structured response support to help compile an indexed evidence package that stays consistent with labels, instructions, and product versions.
- Clear role alignment so responsibilities under the Responsible Person role and Authorized Representative role are handled correctly under the MSR and GPSR.
If you want help preparing for or responding to a technical documentation request, review our compliance services and then reach out through our contact page to discuss your product and timeline.
Related Articles
- Who is responsible if I sell products in the EU without an importer?
- What is the first labeling mistake most US sellers make when they start shipping to Europe?
- Has anyone done CE testing outside the EU like in China and actually sold the product in the EU?
- What battery symbols and labels are mandatory in EU?
- What's the penalty for non-removable batteries in devices that require them?
