TemplatesEU

EU LVD 2014/35/EU Templates

Reusable artifacts for CE marking evidence packs.

Copy/paste these into your technical file system and keep them versioned.

Back to main artifact Review sources

Author

Sorena AI

Published

Feb 21, 2026

Updated

Feb 21, 2026

Sections

Structured answer sets in this page tree.

Primary sources

Cited legal and guidance references.

Publication metadata

Sorena AI

Published Feb 21, 2026

Updated Feb 21, 2026

Overview

These templates are designed to match how authorities and auditors actually review evidence: fast scope rationale, clear standards versions, hazard-to-test traceability, and an exportable technical file index. Use them per product family and link every field to evidence locations.

Section 1

1) Scope memo template (one page per product family)

Purpose: a defensible scope decision (voltage limits + Annex II exclusions + overlap list).

Product identification: model, variants, photos, intended use, target markets, and online sales channels.
Voltage: rated input, frequency, power architecture, external power supply strategy, and whether the marketed item is a finished product or component.
Scope outcome: in scope, excluded, or handled under another regime, with reasons.
Annex II exclusions checked: list each exclusion and mark not applicable with a short rationale.
Overlap list: LVD, EMC, RED, machinery, and Article 4 operator coverage where relevant.

Recommended next step

Keep EU LVD 2014/35/EU Templates in one governed evidence system

SSOT can take EU LVD 2014/35/EU Templates from reusing this material inside a governed evidence system to a reusable workflow inside Sorena. Teams working on EU LVD 2014/35/EU can keep owners, evidence, and next steps aligned without copying this guide into separate documents.

Evidence system

Open SSOT for EU LVD 2014/35/EU Templates

Start from EU LVD 2014/35/EU Templates and keep documents, evidence, and control records in one governed system.

Explore next step

Talk to Sorena

Talk through EU LVD 2014/35/EU

Review your current process, evidence gaps, and next steps for EU LVD 2014/35/EU Templates.

Explore next step

Section 2

2) Annex I mapping table (objective -> hazard -> control -> test -> evidence ID)

Purpose: turn safety objectives into an engineering-ready and reviewable evidence map.

Safety objective (Annex I) | Hazard | Design control | Verification method | Test/report ID | Residual risk + warning (if any)
Include non-electrical hazards caused by the equipment (fire, mechanical hazards, sharp edges).
Reference standards clauses (full or partial application) next to each control/test.

Section 3

3) Standards register + update review log template

Purpose: manage harmonised standards like controls and document update decisions.

Standard | Edition or amendment set | OJ decision reference | Hazards covered | Applied fully? | Clauses applied | Evidence IDs | Notes
Update log: decision reference | date checked | restrictions or withdrawal dates | impact summary | decision | owner | due date

Section 4

4) Test plan outline (make test evidence reproducible)

Purpose: define configurations, limits, and acceptance criteria before you test.

Configurations tested: worst-case thermal, worst-case insulation, overload/abnormal conditions as applicable.
Environmental assumptions: temperature, humidity, installation, duty cycle, ventilation, IP rating assumptions.
Tests by hazard: dielectric strength, leakage current/touch current, temperature rise, mechanical strength, abnormal operation, etc. (as applicable).
Acceptance criteria: standard clause limits and internal criteria; deviations and rationale.

Section 5

5) Annex III technical documentation index template

Purpose: an exportable index that makes the technical file reviewable in minutes.

00-Index with scope memo, applicable legislation list, and file index.
01-Design with drawings, schematics, BOM, and critical components list.
02-Risk with hazard log, Annex I mapping table, and residual risk decisions.
03-Standards with register, clause mapping, and update review logs.
04-Verification with test plan, test reports, and calculations or examinations.
05-Labels-and-Instructions with labels, safety info, and translations.
06-DoC with signed DoC, version history, and importer access notes.

Section 6

6) EU Declaration of Conformity (DoC) skeleton (Annex IV-aligned)

Purpose: a DoC that matches the technical file and can be kept continuously updated.

Product model identification and description linked to type, batch, or serial logic.
Manufacturer name and address, authorised representative if any, and Article 4 operator if relevant for the marketed product.
Statement that the declaration is issued under the sole responsibility of the manufacturer.
Applicable Union harmonisation legislation list, not just the LVD.
Standards and other technical specifications with versions and amendment sets.
Signatory name, function, place, date, signature, and translation control record.

Section 7

7) Market surveillance response pack checklist (what to export on request)

Purpose: a predictable, fast response that reduces escalation risk.

Signed DoC and version history.
Technical file index and scope memo.
Key test reports, hazard mapping summary, and standards register extract.
Labels, instructions, and translation set for affected markets.
Single contact point, response timeline commitment, and corrective action log if already opened.

Primary sources