CE Marking Technical File:What Manufacturers Need to Include in Technical Documentation

A CE mark is visible on the finished product, but the technical file is where a manufacturer records the evidence behind that conformity decision. For SEO and practical usefulness, this guide focuses specifically on how that evidence should be organised, controlled and kept traceable—not on repeating the complete CE marking process.

The technical file is not simply a collection of certificates. Its purpose is to demonstrate how the manufacturer established that a product satisfies the applicable European requirements. If a market-surveillance authority, importer, customer or technical reviewer asks how conformity was determined, the documentation should provide a clear and traceable answer.

Manufacturers beginning the wider conformity process should first establish which legislation applies to the product. CE Marking Authority's CE marking guidance provides broader information on the compliance framework, while this guide focuses specifically on building and maintaining the technical evidence behind the declaration.

What Is a CE Marking Technical File?

A technical file is the body of documentation used to demonstrate conformity with the legislation applicable to a product. The precise contents depend on the product, its risks, the relevant directive or regulation, the conformity-assessment route and the standards used.

A useful technical file allows a competent reviewer to understand what the product is, how it was designed and manufactured, which legal requirements apply, what hazards were identified, what standards were used, what testing or calculations were completed and why the manufacturer concluded that the product conforms.

This means the file should tell a coherent compliance story. Supplier declarations, laboratory reports and drawings can be important evidence, but simply storing them in one folder does not automatically demonstrate conformity.

Why Technical Documentation Matters for CE Marking

Technical documentation supports the manufacturer's legal declaration of conformity. It also provides a record of the engineering and regulatory decisions made during product development.

Good documentation can help a manufacturer respond efficiently to regulatory enquiries, maintain consistency across product variants, assess later design changes and demonstrate why particular safety measures were selected. Weak documentation creates the opposite problem: the product may appear safe, but the manufacturer may struggle to prove that the applicable requirements were systematically assessed.

The site's existing article on CE certification for manufacturers also identifies technical documentation as a central stage of the overall conformity process.

What Should a CE Technical File Contain?

There is no single universal contents list that applies identically to every CE-marked product. Product-specific legislation must always be checked. However, manufacturers commonly need to assemble the following categories of evidence.

1. General Product Description

Start with enough information to identify and understand the product. This may include the product name, model or type, intended purpose, variants, key specifications, photographs and a description of how the product operates. The description should also make clear the intended user and foreseeable operating environment where these factors affect compliance.

2. Product Identification and Traceability Information

The technical documentation should connect clearly to the actual product being placed on the market. Model numbers, serial-number conventions, revision status, labels and other traceability information help ensure that the evidence relates to the correct design.

3. Applicable EU Directives and Regulations

The manufacturer should record the European legislation considered applicable to the product. A product can fall within more than one legal instrument, so the technical file should reflect the complete compliance scope rather than focusing only on the most obvious directive.

4. Applicable Essential Requirements

The documentation should show which essential safety, health, electromagnetic, environmental or other requirements apply and how they have been addressed. A requirements or compliance matrix is often useful because it creates a direct link between legal requirements and supporting design or test evidence.

5. Design and Manufacturing Drawings

Relevant drawings can include general arrangements, detailed component drawings, schematics, electrical diagrams, control-circuit information, layouts and assembly drawings. They should be sufficiently clear for a technical reviewer to understand the safety-relevant aspects of the product.

6. Bills of Materials and Critical Components

Where component selection affects compliance, records should identify critical parts and specifications. Supporting supplier documentation may be included, but manufacturers should evaluate how those components behave within the finished product rather than assuming a component certificate proves conformity of the complete assembly.

7. Risk Assessment

Within the technical file, the risk assessment should function as traceable evidence showing which hazards were considered and where the corresponding design measures, safeguards, verification records or user information can be found. The technical-file objective is document control and traceability rather than repeating the full risk-assessment methodology.

8. Standards and Technical Specifications

The file should identify standards and other technical specifications used to demonstrate conformity. Manufacturers should record the relevant editions and, where appropriate, the clauses applied. If a standard is only partly applied or the design deviates from it, the reasoning and alternative evidence should be documented.

9. Calculations and Engineering Evidence

Some compliance decisions rely on calculations rather than laboratory tests. Structural calculations, safety distances, thermal calculations, electrical ratings, stability analysis and other engineering evidence may therefore form part of the technical documentation.

10. Test Reports and Verification Records

Testing should correspond to the applicable requirements and selected standards. Reports should identify the product or sample tested, method used, results obtained and acceptance criteria. Where testing is performed internally, records should still be sufficiently controlled and understandable to support the conformity decision.

11. Instructions for Use

Operating and safety instructions should be consistent with the actual product and its risk assessment. Depending on the product, documentation can cover installation, commissioning, operation, cleaning, maintenance, troubleshooting, transport, storage and disposal. Residual risks should be communicated where required.

12. Product Labels and Marking Information

Keep copies or controlled artwork showing CE marking, manufacturer details, model identification, warnings, ratings and other required product information. This helps demonstrate that the physical product and accompanying information match the assessed design.

13. Supplier and Subassembly Documentation

Supplier declarations, certificates, component data sheets and subassembly documentation can support the file. They should be relevant to the final product and should not be treated as a substitute for the manufacturer's own assessment of the complete product.

14. Conformity Assessment Evidence

If the applicable conformity procedure requires involvement of a Notified Body or another assessment body, the relevant certificates, reports and correspondence should be retained as part of the compliance evidence.

15. EU Declaration of Conformity

The EU Declaration of Conformity should be retained as the formal legal output supported by the technical evidence. From a technical-file perspective, the key requirement is consistency: product identification, legislation, standards and conformity information in the declaration should match the records held in the file.

For declaration content, signatory responsibilities and common declaration errors, see EU Declaration of Conformity: Requirements, Common Mistakes & Manufacturer Responsibilities.

How to Structure the Technical File

A technical file does not need to be one enormous document. In many organisations it is a controlled set of linked records stored electronically. What matters is that the information can be located, understood and connected to the relevant product revision.

·        Product identity and scope

·        Applicable legislation and requirements

·        Risk assessment

·        Standards assessment

·        Design evidence and drawings

·        Calculations and testing

·        Instructions and labelling

·        Supplier and component evidence

·        Conformity-assessment records

·        Declaration and approval records

A technical-file index or master document can make the package easier to manage. It can identify each required record, document number, revision and storage location.

Technical Files for Machinery

For machinery, the technical file should be organised so a reviewer can move from the machine description to applicable requirements, risk evidence, drawings, verification records, instructions and the final declaration without losing traceability between documents.

This article deliberately stays focused on documentation. Manufacturers looking for the complete conformity sequence—from classification and legislation through verification and final marking—should use the CE Marking for Machinery compliance checklist.

Where machinery hazards are significant, the file should reference the current machine-specific risk assessment and the technical evidence used to validate its controls.

Technical Documentation for Electrical and Electronic Products

Electrical and electronic equipment may be subject to several overlapping requirements. For example, products within scope of the EMC Directive need evidence supporting electromagnetic compatibility in addition to other applicable safety or product requirements.

Technical evidence may therefore include circuit diagrams, PCB information, component specifications, enclosure information, EMC test reports, electrical-safety evidence, user instructions and labelling. The exact package depends on the product and legislation.

How Long Should Technical Documentation Be Retained?

Retention periods are defined by the legislation applicable to the product. Ten years after a product is placed on the market is a common requirement across CE-marking legislation, but manufacturers should verify the exact obligation for each product category rather than applying one assumption universally.

The practical point is equally important: documentation must remain accessible even after employees change, suppliers disappear or a product is discontinued. A controlled retention system should therefore be part of the compliance process.

When Should a Technical File Be Updated?

Technical documentation should represent the product actually being manufactured and supplied. It should be reviewed when changes could affect conformity.

·        A safety-critical component is replaced.

·        The electrical or control architecture changes.

·        Software or firmware changes affect safety or regulated functionality.

·        A product is redesigned or a new variant is introduced.

·        The intended use or operating environment changes.

·        Relevant legislation or standards change.

·        Testing reveals a new compliance issue.

·        A field incident or complaint identifies a previously unrecognised hazard.

Change control is particularly important for long-running product families. Without it, the technical file can gradually become evidence for an earlier design rather than the product currently on the market.

Common Technical File Mistakes

No master index or document map: When evidence is spread across departments, suppliers and systems, a controlled index helps a reviewer locate each record and understand how it supports conformity.

Poor revision control: Drawings, test reports, manuals and declarations should identify the product revision they support. Mixing evidence from different revisions can make the file unreliable.

Unclear evidence ownership: Assign responsibility for maintaining risk records, drawings, test evidence, supplier documents, instructions and declarations so important records do not disappear between teams.

Supplier evidence stored without evaluation: Component certificates and data sheets should be connected to the manufacturer's assessment of the finished product rather than archived without explanation.

No traceability between requirements and evidence: A compliance matrix or equivalent structure should show where each applicable requirement is addressed and which record demonstrates the result.

Failure to update the file after controlled changes: Engineering changes should trigger a documented review of the affected risk records, drawings, verification, instructions and declaration.

Technical File Checklist for Manufacturers

☐ Product description and identification

☐ Intended use and relevant product variants

☐ Applicable EU legislation

☐ Applicable essential requirements

☐ Risk assessment

☐ Standards and technical specifications

☐ Design and manufacturing drawings

☐ Schematics and control diagrams where relevant

☐ Critical-component information

☐ Engineering calculations

☐ Test and verification reports

☐ Instructions for use

☐ Labels and CE-marking artwork

☐ Supplier and subassembly evidence

☐ Conformity-assessment body records where required

☐ EU Declaration of Conformity

☐ Document revision and change-control records

When Professional Technical Documentation Support Is Useful

Manufacturers do not necessarily need an external consultant to write every document. However, specialist support can be valuable where the applicable legislation is unclear, multiple directives overlap, risk assessment is complex, existing documentation has significant gaps or a product is approaching market launch without a structured compliance file.

An independent technical review can also identify inconsistencies between drawings, testing, risk assessments, manuals and declarations before those issues are raised by a customer or authority.

CE Marking Authority supports manufacturers with regulatory scoping, technical documentation, machinery compliance and broader CE marking assistance. For a specific product or technical-file review, contact the CE Marking Authority team to discuss the available evidence and the compliance route.

Frequently Asked Questions

Is a technical file mandatory for CE marking?

Where the applicable CE-marking legislation requires technical documentation, the manufacturer must compile and retain evidence demonstrating conformity. The exact content and retention requirements depend on the product legislation.

Does the technical file need to be sent to an authority before CE marking?

Not necessarily. For many conformity routes the manufacturer retains the documentation and makes it available when required. Certain product categories and assessment routes can involve third-party review, so the applicable legislation must be checked.

Can a supplier certificate replace a technical file?

No. Supplier documentation can form part of the evidence, but it does not by itself demonstrate conformity of the manufacturer's finished product.

Does every technical file contain the same documents?

No. The required content varies with the product, applicable legislation, risks, standards and conformity-assessment procedure.

Can technical documentation be stored electronically?

In practice, technical documentation is often maintained electronically. It should remain controlled, readable, accessible and capable of being supplied in accordance with the applicable legal requirements.

Who is responsible for the CE technical file?

Primary responsibility normally rests with the manufacturer. Specific obligations can also apply to authorised representatives and other economic operators depending on the legislation and market arrangement.

Conclusion

A strong CE marking technical file is a controlled evidence system, not a folder assembled at the end of a project. Its value comes from traceability: a reviewer should be able to connect the product version with applicable requirements, design evidence, risk records, standards, testing, instructions and the final declaration.

Manufacturers can use this article as the documentation-focused part of a wider compliance cluster. For the complete machinery process, use the CE Marking for Machinery checklist; for detailed machinery risk methodology, use the ISO 12100 risk-assessment guide; and for the final legal declaration, use the EU Declaration of Conformity guide.

For manufacturers that need help identifying documentation gaps, structuring technical evidence or reviewing an existing file, CE Marking Authority can provide product-specific compliance support.