Technical documentation: what goes in a technical file, with a checklist

Marc HaddadForward Deployed Regulatory Engineer
A technical file (most EU product laws call it technical documentation) is the manufacturer’s evidence that a product meets the EU laws that apply to it: design, risk analysis, standards applied, test results and production control. You build it before the product is placed on the market, keep it, usually for 10 years, and produce it when an authority asks.
Key points
- What it is: the technical file is your evidence of compliance, and it stays with you, not with the product.
- No single EU list: each product law sets its own contents, so build the file from the laws your product and its parts bring in.
- Not the declaration: where a law requires an EU declaration of conformity, it is a short signed statement rather than the file, and a copy goes inside the file.
- Kept for 10 years: under most laws the manufacturer keeps the file for 10 years after the product is placed on the market.
What is a technical file?
A technical file is the set of documents showing how your product meets each EU law that applies to it. Most laws call it technical documentation and the Machinery Directive calls it the “technical file,” but they mean the same thing.
EU product laws mostly set outcomes (the product must be safe, must not disturb other equipment, must use the radio spectrum properly) and leave you to show how you met them. The European Commission’s Blue Guide, which is guidance rather than law, describes the file as information “on the design, manufacture and operation of the product.”[1] Think of it as the audit trail an inspector asks for when your product turns up in a market check.
Is a technical file the same as a declaration of conformity?
No. The EU declaration of conformity is a signed page or two naming the product, the laws and the standards. The technical file is the full evidence behind the declaration, and a copy of the declaration goes inside it. Whether your product has a declaration at all depends on the law:
- Electrical and radio equipment, toys, machinery and batteries: the CE-marking laws for these products require a declaration.[2–5] Decision No 768/2008/EC sets its model structure,[6] and each law has its own model, such as the one in the Radio Equipment Directive 2014/53/EU (RED).[7]
- Furniture, textiles and other consumer products: if the GPSR is the only safety law that covers them, they need technical documentation but no declaration, because the GPSR does not provide for one.[8]
- Cosmetics: there is no declaration either. The responsible person keeps a product information file for each cosmetic product instead.[9]
Instructions and safety information are a third document: they go to the user with the product, and a copy goes in the file.
Which EU laws require a technical file?
Each product law that requires one sets the contents in its own article or annex, so there is no single EU list, although most files still share a core.
The shared pattern comes from Decision No 768/2008/EC, the template the newer product laws copy. It ties technical documentation to its conformity modules, starting with Module A (internal production control), and sets duties for manufacturers, authorised representatives and importers.[6]
Consumer products that no specific law covers fall under the General Product Safety Regulation (EU) 2023/988 (GPSR), which has applied since December 13, 2024. It requires at least “a general description of the product and its essential characteristics relevant for assessing its safety,” plus, where appropriate, a risk analysis and the standards applied.[8]
How do you work out which laws apply to your product?
Start the file with a list of laws. First ask what the product is and who it is for, then go through your bill of materials (BOM) line by line. Each part can bring in its own law, and those laws decide which annexes the file has to satisfy.
- Every consumer product: the GPSR covers any safety risk that no specific EU law addresses, so it sits underneath the other laws on your list.[8]
- Furniture and textiles: where no specific safety law applies, the GPSR sets what the file holds. Textile products also need a label or marking giving their fibre composition.[10]
- Toys: a product designed or intended for play by children under 14, whether or not exclusively, falls under the Toy Safety Directive 2009/48/EC.[3]
- Machinery: a motor that moves under its own power can make the product machinery.
- Electrical and electronic products: a mains adaptor in the box is electrical equipment in its own right. Each electronic board brings in the Restriction of Hazardous Substances (RoHS) Directive 2011/65/EU, which requires technical documentation under Module A, internal production control.[11]
- Radio products: a radio module brings in the RED.
- Products with batteries: the battery’s manufacturer draws up its technical documentation under the Batteries Regulation (EU) 2023/1542.[5] From February 18, 2027, anyone placing products with portable batteries on the market must make those batteries readily removable and replaceable by the end user.[5]
- Cosmetics: the Cosmetics Regulation (EC) No 1223/2009 applies, and its version of the file, the product information file, must include a cosmetic product safety report.[9]
Radio equipment within the RED is not subject to the Low Voltage Directive 2014/35/EU (LVD) except through RED Article 3(1)(a), which applies the LVD’s safety objectives with no voltage limit.[7] Electromagnetic compatibility (EMC) comes in through Article 3(1)(b), so one RED file covers all three. That means a 3.7 V device the LVD would never have caught still needs its safety evidence.
The list moves whenever the product or the law changes, and that is the part Daptic covers: it works out which product laws apply to your product in each market and flags the changes that affect it.
What goes in a technical file? A checklist
Most annexes share a core of nine items, so check each one against the annex of every law on your list.
- Identification and description: model, variants and intended use. For radio equipment, include photographs or illustrations of the external features, marking and internal layout, and the “versions of software or firmware affecting compliance.”[7] For toys, add the addresses of the places of manufacture and storage.[3]
- Design and manufacturing information: conceptual design and manufacturing drawings, schemes of components, sub-assemblies and circuits, and the explanations needed to read them.[7, 12] Your BOM, critical components and their suppliers belong here. For toys, list the components and materials and add the safety data sheets on chemicals obtained from your chemical suppliers.[3] For machinery under the Machinery Regulation (EU) 2023/1230, add copies of the declarations of conformity for products you incorporate.[4]
- Standards applied: the harmonised standards applied in full or in part and, for anything they don’t cover, the solutions adopted and other specifications used.[7, 13]
- Risk assessment and measures taken: Module A asks for “an adequate analysis and assessment of the risk(s),”[6] and the GPSR asks, where appropriate, for the possible risks and the solutions adopted.[8] Categories add their own:
- Electrical and electronic products: the LVD asks for a risk analysis,[2] and the EMC Directive 2014/30/EU asks for an electromagnetic compatibility assessment covering all normal intended operating conditions and representative configurations.[12]
- Toys: an analysis of the chemical, physical, mechanical, electrical, flammability, hygiene and radioactivity hazards, with an assessment of potential exposure to them.[3]
- Machinery: machinery files add the protective measures and residual risks.[4]
- Cosmetics: the cosmetic product safety report.[9]
- Test reports and calculations: the test reports and calculations, plus any certificate from a notified body where a third-party route was used.[7]
- Labels and instructions: labels, markings, instructions and safety information in the required languages.[7, 13]
- Declaration of conformity: a copy of the EU declaration of conformity, where the law requires one.[7]
- Production control: how series production stays in conformity.[4, 13]
- Change control and version history: where a product has been redesigned and re-assessed, the Blue Guide says the file must reflect all versions, the changes made and how each version can be identified.[1]
Number the index the way the annex numbers its points, keep one master folder per model, and link supplier documents by revision rather than pasting copies that go stale.
Can you use supplier test reports in your technical file?
Yes, as evidence, but they are not your file. Supplier certificates, material declarations and test reports go in, and the file has to show how they add up for your product, under your name. A supplier’s report describes its part on its own, while the authority looks at the finished product. A fabric is tested before it is upholstered, a paint before it goes on a toy, and a pre-certified radio module in its own test setup rather than in your enclosure, antenna placement and power design.
Some laws name supplier documents outright. Toy files include safety data sheets on the chemicals used, obtained from chemical suppliers,[3] and machinery files include the declarations of conformity of products you incorporate.[4]
How do technical file requirements differ by product type?
The table shows where each main product law sets out the file’s contents and what it adds to the shared core.
| Product family | Law | Where the contents are | What stands out |
|---|---|---|---|
| Machinery | Directive 2006/42/EC (until January 19, 2027); Regulation (EU) 2023/1230 (from January 20, 2027) | Directive Annex VII, Part A; Regulation Annex IV, Part A | The Regulation adds source code of safety software on reasoned request (point (m)) and, for sensor-fed, remotely driven or autonomous machinery, a description of the system’s characteristics, capabilities and limitations (point (n)) |
| Electrical equipment | LVD 2014/35/EU | Annex III (Module A), point 2 | The risk analysis is part of the file |
| Electromagnetic compatibility | EMC 2014/30/EU | Annex II (Module A), point 3 | A separate EMC assessment (point 2) |
| Radio equipment | RED 2014/53/EU | Article 21 and Annex V | Firmware versions, internal photos, spectrum and packaging statements (point (i)) |
| Toys | Directive 2009/48/EC | Article 21 and Annex IV | Translation on request, with a 30-day deadline |
| PPE | Regulation (EU) 2016/425 | Annex III | Assessment of the risks the PPE protects against (point (b)) |
| Other consumer products, such as furniture and textiles, where no specific safety law applies | GPSR (EU) 2023/988 | Article 9(2) | A general description is the minimum; a risk analysis and the standards applied are added where appropriate, and there is no declaration of conformity |
| Batteries | Regulation (EU) 2023/1542 | Article 38(2) and Annex VIII | Drawn up by the battery’s manufacturer; series production can use Module A or a quality assurance route (Article 17(1)) |
| Cosmetics | Regulation (EC) No 1223/2009 | Article 11(2) | Called the product information file, kept by the responsible person for 10 years after the last batch is placed on the market, and includes the cosmetic product safety report |
Who has to keep the technical file, and for how long?
Mostly the manufacturer, for 10 years. The clock runs from placing on the market rather than from launch, so a model sold for six years keeps its file well beyond 10 years from launch.
- Manufacturer: 10 years after the product is placed on the market under the LVD, EMC Directive, RED, Toy Safety Directive, PPE Regulation, RoHS Directive, GPSR and Machinery Regulation.[2–4, 7, 8, 11–13] The Machinery Directive 2006/42/EC counts at least 10 years from the date of manufacture or, for series production, from the last unit produced.[4]
- Authorised representative: the mandate must allow it to keep the declaration and the technical documentation at the authorities’ disposal.[7] Drawing up the file, though, cannot be handed to it unless the law says so.[1]
- Importer: under laws such as the RED and LVD, it checks that the manufacturer has drawn up the file and ensures it can be made available on request, but does not have to hold it.[2, 7] Under the GPSR, importers keep a copy for 10 years.[8]
- EU-based operator: for products under the laws listed in Regulation (EU) 2019/1020, an operator established in the EU must ensure the file can be made available to authorities on request.[14]
When do you have to show the technical file to an authority?
When an authority asks for it. Under internal production control nobody receives the file at the point of sale, and you produce it on a reasoned request. Where a notified body is involved, it reviews the file as part of that procedure.
The file goes to the authority in a language it can easily understand.[2, 14] Most laws set no fixed deadline, and the request itself may set one.[1] The Toy Safety Directive is the exception: the authority can require a translation of the relevant parts and set a deadline of 30 days, or shorter for a serious and immediate risk.[3]
When does a technical file need updating?
Whenever a design change touches compliance. New editions of harmonised standards can mean re-testing, and the laws change too:
- Machinery: on January 20, 2027, the Machinery Regulation, which is already adopted, replaces Directive 2006/42/EC. Units placed on the market up to January 19, 2027, are documented to Directive Annex VII. Units placed from January 20, 2027, need Regulation Annex IV, which includes the source code or programming logic of safety software, provided on reasoned request.
- Toys: on August 1, 2030, the Toy Safety Regulation (EU) 2025/2509 replaces Directive 2009/48/EC. The Regulation is dated November 26, 2025, and was published on December 12, 2025. Under it, every toy will need a digital product passport, which replaces the declaration of conformity.
- Omnibus IV, still a proposal: on July 14, 2026, Parliament’s committee approved the provisional agreement that Council and Parliament negotiators reached on the Omnibus IV regulation on digitalisation and common specifications. The European Parliament’s first-reading vote (procedure 2025/0134(COD)) is indicatively set for November 23, 2026. Read the adopted text for any change to how documentation is kept or supplied.
Frequently asked questions
Do you have to submit a technical file before selling in the EU?
No. Under internal production control nobody receives the file at the point of sale, and you produce it when an authority makes a reasoned request.
How long do you have to keep a technical file?
Usually 10 years after the product is placed on the market, not 10 years from launch. Under the Machinery Directive 2006/42/EC it is at least 10 years from manufacture or, for series production, from the last unit produced.
Does the importer have to keep the technical file?
Usually not. Under most EU product laws the importer only has to be able to get the file for an authority, but under the General Product Safety Regulation importers keep a copy for 10 years.
Is there a standard EU technical file template?
No. Each product law sets its own contents in an article or annex, so build the file from the annexes of the laws your product falls under.
What language does a technical file have to be in?
One the requesting authority can easily understand. For toys, the authority can also require a translation of the relevant parts and set a 30-day deadline.
Notes and sources
- Blue Guide 2022, Commission Notice 2022/C 247/01), sections 3.1, 3.2, 4.3 and 4.4
- Directive 2014/35/EU (LVD), Articles 6 and 8, Annex III
- Directive 2009/48/EC (toys), Articles 2, 4, 18 and 21, Annex IV; Regulation (EU) 2025/2509; Commission toy safety page
- Directive 2006/42/EC, Annex VII; Regulation (EU) 2023/1230, Article 10 and Annex IV
- Regulation (EU) 2023/1542 (batteries), Articles 11, 17, 38 and 96, Annex VIII
- Decision No 768/2008/EC, Annex I, Articles R2 to R4 and R10, and Annex II, Module A
- Directive 2014/53/EU (RED), Articles 1, 3, 10, 11, 12 and 21, Annexes V and VI
- Regulation (EU) 2023/988 (GPSR), Articles 2, 9, 11 and 52
- Regulation (EC) No 1223/2009 (cosmetics), Articles 10 and 11
- Regulation (EU) No 1007/2011 (textile labelling), Article 14
- Directive 2011/65/EU (RoHS), Article 7
- Directive 2014/30/EU (EMC), Article 7, Annexes II and IV
- Regulation (EU) 2016/425 (PPE), Article 8, Annex III
- Regulation (EU) 2019/1020, Article 4
Additional sources:
- Delegated Regulation (EU) 2022/30, Article 1; Delegated Regulation (EU) 2023/2444
- European Parliament Legislative Observatory, procedure 2025/0134(COD)
- Last reviewed: November 9, 2026
This article reflects Marc Haddad’s independent opinions, not necessarily those of Daptic.



