CE Marking · Hazloc Labs

CE Marking Technical File: What Hardware Teams Must Assemble

CE marking is not a lab stamp you buy at the end. It is a manufacturer’s declaration that essential requirements are met — backed by a technical file you can defend if market surveillance asks.

This guide focuses on ordinary-location hardware (electronics, machinery interfaces, wireless hosts). Explosive-atmosphere ATEX files are a parallel discipline.

Start with applicability — not a standard shopping list

List every market claim (EU, and UK if UKCA still applies to your SKU). Then map directives that actually attach to the product:

• Low Voltage Directive (LVD) — mains and related electrical safety
• EMC Directive — emissions and immunity for apparatus
• Radio Equipment Directive (RED) — if intentional radiators are present
• RoHS / related substance rules — materials declarations
• Machinery / GPSR / other — only when the product type triggers them

Over-scoping burns budget. Under-scoping blocks customs. The first deliverable is an applicability matrix signed off by engineering and compliance.

What belongs in the technical file

File element	Why it matters
Product description & variants	Defines the family covered by one DoC
Risk assessment / essential requirements checklist	Shows how you addressed each obligation
List of applied standards (with editions)	Links design to presumed conformity
Test reports & certificates	Evidence from accredited or justified sources
Circuit diagrams, PCB, BOM, critical components	Traceability for construction
User instructions & safety warnings	Part of placing on the market
Label artwork & marking plan	CE, ratings, importer/manufacturer details
Declaration of Conformity (DoC)	Legal statement you keep and update

Practical build sequence

1. Freeze the SKU set — options and antennas that change EMC/radio must be listed.
2. Lock Class A vs B / environment for EMC before chamber booking.
3. Run gap review on construction (creepage, insulation, enclosure openings) before safety samples ship.
4. Execute tests with a sample matrix that matches production intent.
5. Close findings with documented redesign or justification — not verbal “it passed after we taped the cable.”
6. Issue DoC only when evidence matches the product you will ship.

Common failure modes

• DoC lists standards never tested (or wrong editions).
• Wireless module grants assumed to cover host EMC/radio without host evidence.
• Labeling missing manufacturer/importer address required for the market.
• Change control: firmware or PSU swap with no impact assessment.

FAQ

Do we need a Notified Body?

Only for certain modules (e.g. some RED cases). Many LVD/EMC products are manufacturer self-declaration with accredited test evidence. Scope this early.

Is UKCA the same file?

Often the technical content tracks CE, but marking, responsible person, and designated standards can differ. Treat GB as its own column in the matrix.

← Back to Blog