EU Technical Documentation and Risk Assessment Guide

EU Technical Documentation and Risk Assessment Guide

Your Bluetooth speaker passed CE testing. You have the test report from a Shenzhen lab, a certificate with the CE logo, and a product that works. Your EU distributor asks for the technical file. You send the test report. They ask for the risk assessment. You ask what that is. They ask for the user instructions in German. You send the English version. They ask for the Declaration of Conformity signed by the manufacturer. You send the one the lab prepared. Then they ask for the bill of materials, the circuit diagrams, and the list of harmonised standards applied. At this point, the test report that felt like the finish line turns out to be roughly 20% of what an EU technical file actually contains.

This is the gap that catches almost every Chinese manufacturer entering Europe. Factories are good at building products and getting them tested. They are less good at assembling the documentation package that EU regulators consider the actual proof of compliance. The test report says your product passed. The technical file proves why it should be allowed on the market in the first place.

Here is what an EU technical documentation file actually contains, how to build a risk assessment that regulators accept, what GPSR changed about documentation requirements, and how to set this up so you never have to rebuild it from scratch when a marketplace or customs officer comes asking.

What EU Technical Documentation Actually Is

Technical documentation — sometimes called the technical file or technical construction file — is the complete set of documents that proves your product meets all applicable EU safety, health, and environmental requirements. It is not a single document. It is a structured collection of design specifications, test reports, risk assessments, declarations, labels, and instructions that together demonstrate compliance.

The CE mark on your product is the conclusion. The technical file is the evidence. If a market surveillance authority in Germany, the Netherlands, or France asks you to prove compliance, they do not want to see the CE logo. They want to see the file. No file, no compliance — regardless of how many tests your product passed.

The requirement exists across virtually every EU product directive. CE directives like the Low Voltage Directive (LVD), the Electromagnetic Compatibility Directive (EMC), the Radio Equipment Directive (RED), the Toy Safety Directive, and the Machinery Regulation each define their own technical file requirements. GPSR adds a broader layer: every consumer product on the EU market — whether CE-regulated or not — must have technical documentation including a risk assessment, kept available for 10 years.

This means even product categories that historically needed no CE marking — kitchen accessories, pet products, home decor, fitness equipment — now need a technical file under GPSR. The scope expanded dramatically in December 2024.

The Nine Components of a Complete Technical File

A properly assembled EU technical file contains nine categories of documents. Not every product needs all nine at the same depth, but every file should address each one. Skipping a section because you think it does not apply is the most common reason files get rejected during a market surveillance check.

1. Product Description and General Specifications

The file opens with a clear description of what the product is, what it does, and who it is for: product name, model number, variant identifiers, intended use, target user group, and any limitations on use. The intended use determines which directives and standards apply. A Bluetooth speaker marketed for outdoor use faces different requirements than the same speaker marketed as a children's toy with a cartoon design.

2. Design and Manufacturing Documentation

This is the engineering core: circuit diagrams, mechanical drawings, bill of materials (BOM), component specifications, PCB layouts, and manufacturing flow descriptions. The level of detail must allow a qualified third party to understand how the product was designed and built without disassembling it. Chinese factories often have this documentation internally but in formats that are not EU-ready — hand-drawn schematics, BOMs in Chinese without English translations, or drawings referencing components by internal factory codes rather than standardised part numbers.

3. List of Applicable Harmonised Standards

The EU publishes harmonised standards — technical specifications that give "presumption of conformity" with directive requirements. If you test against the correct harmonised standards, regulators presume your product meets the essential requirements. For a Bluetooth speaker, the applicable standards typically include EN 62368-1 (audio/video and IT equipment safety), EN 300 328 (wideband data transmission), EN 301 489-17 (electromagnetic compatibility for radio equipment), and EN 62479 (human exposure to electromagnetic fields). The file lists each standard, the version number, and the date of application. Using outdated standard versions is a common reason files fail review.

4. Test Reports

Test reports from accredited laboratories demonstrate that your product meets the requirements of the listed standards. The reports must come from labs accredited to ISO 17025 for the specific test scope — not just any lab with testing equipment. Reports from Chinese labs are accepted if the lab holds valid ISO 17025 accreditation for the relevant scope. TÜV, SGS, Intertek, and Bureau Veritas all operate accredited labs in China. Costs typically range from €1,500 for a simple EMC test to €8,000 or more for a full LVD + EMC + RED test suite on a complex wireless product.

5. Risk Assessment

The document that most Chinese manufacturers skip — and the one that GPSR made non-optional. You must systematically identify every reasonably foreseeable hazard your product could present, evaluate the risk level, and document the measures you took to reduce it. It is the analytical backbone of the technical file, and it drives many of the other documentation decisions. A risk assessment that says "this product has no risks" is not a risk assessment. It is a liability.

6. EU Declaration of Conformity

The EU Declaration of Conformity (DoC) is the legal document in which the manufacturer declares that the product meets all applicable EU requirements. It is signed by an authorised person at the manufacturing company — not by the test lab, not by the EU Responsible Person, not by the distributor. The manufacturer signs it. The DoC must include the manufacturer's name and address, product identification, the directives applied, the harmonised standards used, and the Notified Body details if applicable. It must be translated into the language of each EU country where the product is sold.

7. User Instructions and Safety Information

Instructions and safety warnings must be provided in the language of every EU country where the product is sold. Under GPSR, safety warnings must be clear, visible, and in the consumer's language — not buried in a multilingual booklet. For a product sold in Germany, France, Italy, and Spain, you need safety instructions in all four languages. The instructions must cover installation, use, maintenance, cleaning, storage, and disposal, including warnings about reasonably foreseeable misuse.

8. Label and Packaging Documentation

The file must include samples or mock-ups of the product label, packaging label, and accompanying documentation. This includes the CE mark with correct dimensions and placement, manufacturer name and address, product identification, batch or serial number, and any required warning symbols. GPSR also requires traceability information — batch numbers, serial numbers, or equivalent — on the product or its packaging.

9. Documentation from the EU Responsible Person

If you have appointed an EU Responsible Person (mandatory under GPSR), the technical file should include the mandate or contract appointing them, their contact details, and a description of assigned tasks. The Responsible Person must have access to the technical file and must be able to provide it to market surveillance authorities within a reasonable timeframe, typically 7 to 14 days.

Risk Assessment: The Document Most Factories Skip

If there is one document that separates a technical file that passes review from one that fails, it is the risk assessment. CE directives have required it for years. GPSR made it mandatory for every consumer product. And yet, most Chinese factories either do not produce one, or produce one so generic that it has no evidentiary value.

What a Risk Assessment Actually Requires

A proper risk assessment follows a structured process:

1. Hazard identification. List every reasonably foreseeable hazard during the product's entire lifecycle — storage, transport, installation, use, maintenance, and disposal. For a kitchen blender: electrical shock, mechanical injury from blades, thermal burns, fire from motor overheating, chemical exposure from food-contact materials, and noise.
2. Risk estimation. For each hazard, estimate the severity of potential harm (slight, serious, severe) and the probability of occurrence (unlikely, possible, likely).
3. Risk evaluation. Determine whether each risk is acceptable, tolerable, or unacceptable. Unacceptable risks must be eliminated through design changes. Tolerable risks must be reduced through protective measures and user warnings.
4. Risk reduction. Document the measures taken — design modifications, protective features (thermal fuse, blade guard), and user information (warning labels, manual warnings).
5. Residual risk documentation. After all measures, document the remaining residual risks and confirm they are acceptable. If a residual risk is still unacceptable, the product cannot be placed on the market.

The format matters less than the rigour. A one-page table listing hazards, severity, probability, and mitigation measures is far more useful than a ten-page narrative that never identifies a single specific risk.

Common Risk Assessment Mistakes

• Copying a generic template. A template filled in with just the product name is immediately recognisable to any regulator. Each risk assessment must be product-specific.
• Ignoring foreseeable misuse. EU assessments must account for reasonably foreseeable misuse. If a consumer might remove a safety guard to clean a blade, that is foreseeable misuse and the assessment must address it. "The user should not do this" is not an acceptable mitigation.
• Not covering the full lifecycle. A lithium battery that is safe during use can present a fire risk during transport or disposal. Transport, storage, installation, maintenance, and disposal all need coverage.
• No residual risk analysis. Many assessments stop after listing mitigation measures. Regulators want to see the residual risk and confirmation it is acceptable.

What GPSR Changed About Documentation

Before GPSR, technical documentation was primarily a CE marking requirement — it applied to products under CE directives like electronics, toys, and machinery. A kitchen utensil with no electrical components had no formal documentation requirement. GPSR changed that. Under Article 9, every manufacturer placing a consumer product on the EU market must prepare and keep technical documentation including:

• A clear description of the product and its intended use
• A risk assessment
• A list of applicable harmonised standards (or a description of how the product meets safety objectives if no standards apply)
• Test reports (where testing was performed)
• The EU Declaration of Conformity or an equivalent statement of compliance
• Design drawings, manufacturing specifications, and component lists
• Safety information and user instructions
• Information enabling product traceability (batch numbers, serial numbers)

The documentation must be kept for 10 years after the product was last placed on the market. It must be produced for market surveillance authorities on request, typically within 7 to 14 days. The practical impact: if you sell five product variants across Germany, France, and the Netherlands, you need a GPSR technical file for each variant, maintainable for a decade.

The Real Cost of Building a Technical File

Costs depend on product category, applicable directives, and how much engineering documentation already exists in usable form:

• Test reports: €1,500–€8,000 per product family. A simple EMC test runs €1,500–€2,500. A full LVD + EMC + RED suite for a wireless product runs €5,000–€8,000.
• Risk assessment: €800–€3,000 if produced by a compliance consultant. A proper assessment takes 2–5 days of engineering work for a moderately complex product.
• Translation and localisation: €400–€1,200 per language for user instructions and safety information. Four EU languages means €1,600–€4,800.
• Technical file assembly and review: €1,000–€3,000 if you hire a compliance service to assemble, review, and validate the complete file.

For a moderately complex electronic product entering four EU markets, total documentation cost runs roughly €8,000–€15,000. It is not recurring — once built, the file serves for the product's entire market life plus the 10-year retention period. The expensive version is not building it properly the first time and having to redo it under pressure while your listings are down and your inventory sits in a German warehouse — that costs 2–3x more.

How Marketplaces Verify Documentation

EU marketplaces use a combination of pre-listing checks and post-listing enforcement:

Amazon requires sellers to upload compliance documents for regulated categories through the Product Compliance dashboard. Since GPSR enforcement began, Amazon also requires EU Responsible Person details for all consumer product listings. If automated checks flag a gap — missing DoC, expired test report, no Responsible Person — the listing is suspended until documentation is provided.

bol.com requires compliance documentation for specific categories and has tightened GPSR enforcement since early 2025. Otto requires compliance documentation during seller onboarding for regulated categories and conducts periodic reviews.

Customs checks happen at the border. Shipments arriving at EU ports without proper documentation can be held for inspection. Customs officers can request the technical file, the Declaration of Conformity, and proof of Responsible Person appointment. If you cannot provide them within the deadline (usually 10 days), the shipment is refused entry.

Building a Documentation System, Not a One-Time File

The biggest mistake is treating the technical file as a one-time project — build it, file it, forget it. Products change, components are substituted, standards are updated, and new regulations come into force. The technical file is a living document.

• Version control. Every product change — new component supplier, modified circuit, firmware update — should trigger a file review. Maintain a change log recording what changed, when, and why.
• Standard monitoring. Harmonised standards are updated every few years. Your file must reference the current version. Subscribe to updates or work with a compliance partner who monitors this.
• Document accessibility. The EU Responsible Person must be able to produce the file on request. If it lives on a factory server in Shenzhen that no one in Europe can access, you have a problem. Use a cloud-based system the Responsible Person can access.
• Annual compliance review. Once a year, review the file against current regulations, standards, and product specifications. A 2–4 hour exercise that catches problems before a regulator does.

What Happens When You Cannot Produce the File

If a market surveillance authority requests your technical file and you cannot produce it:

• Listing suspension. The authority notifies the marketplace, which suspends the listing within 24–48 hours under GPSR cooperation requirements.
• Market withdrawal. If the authority determines the product may be unsafe and the manufacturer cannot prove otherwise, they can order a withdrawal — recalling stock, removing listings, and notifying distributors at the manufacturer's expense.
• Safety Gate notification. Non-compliant or dangerous products are listed in the EU Safety Gate. This is public and permanent, appears in search results for your brand name, and triggers automatic suspensions across other EU marketplaces.
• Fines. Under GPSR, fines can reach up to 4% of annual EU turnover for the most serious violations. National fines range from €5,000 to €100,000+ per violation. Failure to maintain documentation is itself a violation.

The cost of not having the file is always higher than the cost of building it.

Practical Steps: Building Your First EU Technical File

1. Identify applicable directives and regulations. Determine which CE directives apply and confirm GPSR applies (it does, for any consumer product).
2. Identify applicable harmonised standards. Work with your test lab or compliance consultant to list the correct standards and current versions.
3. Conduct the risk assessment. Do this before testing. It identifies hazards that testing should address and may reveal design changes needed before you spend money on testing.
4. Have the product tested. Use an ISO 17025-accredited lab. Ensure reports reference the product model, standard version, and pass/fail criteria.
5. Assemble the technical file. Collect all nine components into a single, indexed, version-controlled document set. Translate user instructions into target market languages.
6. Prepare and sign the EU Declaration of Conformity. The manufacturer signs it. Translate into required languages.
7. Appoint an EU Responsible Person. Give them access to the technical file and a clear mandate.
8. Store the file in a cloud-accessible system. Ensure it can be produced within 7–14 days. Set a calendar reminder for the annual compliance review.

This process takes 4–8 weeks for a moderately complex product. Starting early — before you ship inventory to Europe — is the single most important decision you can make.

How FiveX Helps

FiveX works with Chinese brands every day on EU market entry, and technical documentation is one of the most common areas where brands need support. We help you identify the correct directives and standards, connect you with accredited testing labs, review risk assessments for completeness, validate the technical file before submission, and ensure your EU Responsible Person has everything they need.

Our Go-to-Market program handles the compliance architecture alongside marketplace selection, listing setup, logistics, advertising, and pricing — so you are not solving compliance problems in isolation while trying to launch. Technical documentation is not the fun part of selling in Europe, but it is the part that determines whether you are still selling in Europe six months from now.

If you are planning to enter the EU market, or if you suspect your documentation may not survive a regulator's request, book a Go-to-Market Meeting with our team. We will review your current documentation, identify gaps, and give you a clear roadmap to full compliance — before it becomes a problem you have to solve under pressure.