Documentation & Labelling
EU Technical Documentation Requirements: The Cross-Regime Reference
GPSR, CE marking and RoHS each set their own technical documentation rules — and each of our dedicated guides covers its own piece. This page is the missing cross-reference: what a technical file actually needs to contain across all three at once, how long you have to keep it, and what "in the right language" really means for labelling.
What This Page Adds
- One field list: every document GPSR, CE marking and RoHS can each require, cross-referenced
- Labelling language: what "in the language of the market" actually means in practice
- Retention, side by side: how long each regime expects records kept
- Honest gaps: we say plainly where no downloadable template exists yet
Quick answer: "EU technical documentation" is not one file with one fixed content list — it is a union of what each applicable regulation separately requires. GPSR needs a risk assessment and supporting technical documentation, producible within 10 days of a request. CE marking needs a Declaration of Conformity backed by a technical file referencing the specific harmonised standards tested against. RoHS documentation is typically folded into that same CE technical file as substance-restriction evidence. A product touching all three needs a file that satisfies all three sets of expectations at once, not three separate files.
Why a Separate Page
Why "CE Technical Documentation" and "EU Technical Documentation" Aren't the Same Question
Search "ce technical documentation" and you land on content scoped to CE marking alone — correct for a CE-marked product, but silent on whatever GPSR or RoHS separately also requires for that same product. Search "eu technical documentation requirements" more broadly and you mostly get either a CE-scoped page wearing a broader title, or a generic compliance-agency landing page that lists regimes by name without saying what document each one actually expects. Neither answers the real question a seller with a multi-regime product is asking: "what do I actually need to put in front of a regulator if more than one of these applies at once."
That is the specific gap this page fills — not by replacing the dedicated GPSR, CE marking and RoHS guides (each stays the authority on its own regime's detail), but by sitting above them as the cross-reference that shows where their documentation requirements overlap, where they diverge, and what a combined file actually needs to contain.
The Field List
Every Field a Cross-Regime Technical File Can Need
Built from what's actually specified across our GPSR, CE marking and RoHS guides — not a generic template. Not every field applies to every product; the "applies when" column tells you which regime actually requires it.
| Field | What it actually contains | Applies when |
|---|---|---|
| Product description | Sufficient detail to identify safety-relevant characteristics — not just a product name | Every product (GPSR baseline) |
| Risk assessment | Documented analysis of characteristics, packaging, instructions and foreseeable misuse | Every product (GPSR) |
| Standards applied | The specific harmonised EN standards tested against, listed by number | CE-marked categories |
| Test reports | Evidence the product actually meets the standards claimed, not just a statement that it does | CE-marked categories; RoHS substance testing |
| Substance-restriction evidence | Test reports or supplier declarations per homogeneous material, for each of the 10 restricted substances | Electrical/electronic equipment (RoHS) |
| Declaration of Conformity | Signed document listing every applicable directive/regulation and standard relied upon | CE-marked categories only — GPSR has no equivalent signed declaration |
| Notified-body certificate | Third-party conformity assessment result, where the applicable directive mandates one | Higher-risk CE categories only |
| Responsible Person / AR details | Name and contact address, held by the RP/AR and producible with the file | Non-EU manufacturer, any regime requiring an EU-based role |
Which of these actually applies to your product depends on which regimes reach it — see the full EU Product Requirements index if you haven't mapped that yet.
Labelling & Language
"In the Language of the Market" Is Not One Rule
GPSR requires consumer-facing safety information "in a language consumers in the country of sale can understand" — a deliberately flexible standard, not a fixed list of approved languages, and one that plays out differently depending on the market.
Single-language markets
Most member states have one clearly dominant official language for consumer-facing communication — safety warnings, instructions and labelling are expected in that language, with the technical file itself (test reports, standards references) commonly kept in English regardless.
Multi-language markets
Some member states have more than one official or co-official language for consumer information depending on region — this is the pattern to check for explicitly per country before assuming one language label covers the whole market, rather than a rule to generalise from a single-language example.
This page states the pattern, not a definitive per-country legal list — national labelling-language rules are set at member-state level and can change; verify the specific requirement for each market you actually sell into rather than relying on a generic multi-market assumption.
Retention
How Long Each Regime Expects Records Kept
| Regime | Stated retention | In practice |
|---|---|---|
| GPSR | No fixed calendar period stated | Kept current — reviewed whenever the product, a relevant standard, or an incident report changes, per our GPSR guide |
| CE marking | Generally 10 years from when the last unit of that model is placed on the market | Varies slightly by the specific directive — verify against the one that applies, per our CE marking guide |
| RoHS | Follows the CE technical file it's typically bundled into | Same practical horizon as the CE file, since the evidence usually lives in the same document set |
Where GPSR and CE marking both apply to the same product, the longer, fixed CE retention period is the safer floor to plan around rather than the open-ended GPSR standard alone.
How to Assemble It
Building a Cross-Regime File in Practice
The field list above tells you what's needed. This is the order that actually works when you're starting from scratch or consolidating scattered records.
Map which regimes actually reach the product
Start from the rules index or the free compliance check — the field list only applies where the underlying regime does, and assembling evidence for a regime that doesn't reach your product wastes real budget.
Pull existing evidence before commissioning anything new
Factory test reports, prior design records and existing supplier declarations often already cover part of the file — commissioning fresh testing before checking what already exists is the single most common source of wasted cost.
Translate and format the consumer-facing layer separately
The technical file itself can stay in a working language, but labels, warnings and instructions need to go into whatever language the actual market requires — treat this as its own task, not an afterthought once the technical file is done.
Assign who holds it and confirm they can actually produce it
A file that exists somewhere but that no named person can retrieve within the applicable window does not satisfy the "on request" obligation in practice — confirm the Responsible Person, Authorised Representative or manufacturer contact actually has the current version.
Common Mistake
A Pattern Worth Checking Your Own File Against
The technical file that only exists in the factory's language
A genuinely common pattern for sellers sourcing from a non-English-speaking factory: the factory hands over test reports and a declaration in its own language, the seller translates only the customer-facing label, and the underlying technical file itself is never put into a form an EU regulator or the seller's own Responsible Person could actually review on request. The file exists, but it isn't producible in a form that satisfies the "on request" obligation both GPSR and CE marking impose — which is functionally close to not having it at all when a market surveillance authority actually asks.
There is no universal downloadable technical-file template that works across every product category — the honest reason is that the fields that actually apply change with which regimes reach your product, which is exactly why this page is a field list cross-referenced by regime rather than a single fill-in-the-blank form.
Who Holds What
Who Actually Has to Produce This on Request
Manufacturer
Holds the primary technical file and Declaration of Conformity — the party of first accountability across every regime on this page.
Responsible Person / Authorised Representative
Must be able to produce the GPSR technical documentation, or the CE technical file for the categories requiring an AR, on request — not just confirm it exists.
Importer
Must verify the documentation exists and looks complete before placing the product on the market, without being the party that drafts it from scratch.
Full role-by-role detail lives on the Economic Operators guide.
Cost
What Assembling This Actually Costs
Already-compliant product, missing paperwork
The lower-cost end — the underlying evidence exists somewhere (factory test reports, design records), and the work is compiling and translating it into a producible, defensible file.
Genuine documentation gap
The higher-cost end — new testing or a fresh risk assessment is needed because the original evidence was never actually produced, not just poorly organised.
The free Product Compliance Check flags which of these two situations you're actually in before you spend on either path.
FAQ
Common Questions About EU Technical Documentation
What are the EU technical documentation requirements, in one sentence?
There is no single technical-documentation law — GPSR requires a risk assessment and supporting records for essentially every consumer product, while CE marking additionally requires a Declaration of Conformity and technical file referencing the specific harmonised standards tested against, and RoHS adds substance-restriction evidence for electrical/electronic products.
Is CE technical documentation the same file as GPSR technical documentation?
They can overlap in practice but are not legally the same requirement — a CE-marked product needs both its GPSR risk-assessment file and its CE technical file, and in practice these are usually maintained as one combined document set rather than two entirely separate ones, but each regime's specific content requirement still has to be satisfied.
How fast do I need to be able to produce technical documentation on request?
GPSR specifies technical documentation must be producible within 10 days of a market surveillance authority's request. CE marking and RoHS do not state an identical fixed number of days in the same way, but the practical expectation is the same: on-request, not eventually.
Does product technical documentation for the EU need to be in English?
The underlying technical file (test reports, standards references) is commonly kept in English in practice, but customer-facing safety information and labelling need to be in a language consumers in the actual country of sale can understand — English alone is not sufficient for that consumer-facing part in most markets.
Is there a downloadable EU technical documentation template?
Not a single universal one, honestly — the fields that actually apply depend on which regimes reach your specific product, which is why this page is a cross-referenced field list rather than a fill-in-the-blank form. Our CE marking guide has the same honest gap noted for its Declaration of Conformity specifically.
What happens if my technical documentation is incomplete when requested?
Consequences scale with the regime and severity — a marketplace can suspend a listing pending proof of compliance, a market surveillance authority can order the product off the market, and national-level penalties can apply, following the same enforcement pattern described on our GPSR and CE marking guides.
Who is actually allowed to write or sign EU technical documentation?
There is no licensing requirement to write the documentation itself — the manufacturer, or a competent person acting on its behalf, can compile the technical file. What matters legally is not who typed it but whether the evidence behind it (test results, standards applied, risk analysis) is genuine and defensible, and who is named as accountable for its accuracy — the Declaration of Conformity specifically must be signed by the manufacturer or its authorised representative.
Does a small product with low perceived risk still need full technical documentation?
Yes, in reduced but not eliminated form — GPSR's risk assessment and documentation obligation applies to essentially every consumer product regardless of perceived risk level, though the depth genuinely scales: a simple plastic item needs a shorter file than a corded electrical appliance, but "low risk" is not the same as "no documentation required."
Is there a single product technical documentation EU standard that covers everything?
No — as this page explains, product technical documentation EU-wide is a union of separate regime requirements (GPSR, CE marking, RoHS), not one standard document. Which fields actually apply depends on which regimes reach your specific product.
Related Guides
The Regime-Specific Guides This Page Cross-References
GPSR & Responsible Person
The baseline risk-assessment and documentation requirement for almost every consumer product.
CE Marking
The Declaration of Conformity and technical file this page's field list draws heavily from.
RoHS
Substance-restriction evidence, usually folded into the same technical file.
Where the Facts Come From
Sources for This Page
This page's field list is drawn directly from the primary sources already cited in depth on our GPSR, CE marking and RoHS guides — Regulation (EU) 2023/988, the harmonised CE-marking directives, and Directive 2011/65/EU respectively, all Tier 1 EUR-Lex sources. No new legal claims are introduced on this page beyond what those guides already establish.
Free Tool
Not sure which fields actually apply to you?
Run the free Product Compliance Check — it maps which regimes reach your specific product, so you know which parts of this field list you actually need before you start assembling anything.