| Scope boundary | LVD applies to electrical equipment designed for use with a voltage rating between 50 and 1,000 V AC or between 75 and 1,500 V DC, other than Annex II exclusions. | The LVD source set supports only a high-level RoHS boundary: it is a separate electric and electronic engineering area and may apply alongside LVD. | Record the LVD voltage and exclusion analysis separately from any RoHS scoping record. |
|---|
| Covered actors | LVD addresses safety objectives for electrical equipment: health and safety of persons and domestic animals, and protection of property. | RoHS is treated here only as the separate hazardous-substance restriction workstream that may also apply to electrical and electronic products. | Use LVD for safety evidence and RoHS for substance-control evidence; do not swap one for the other. |
|---|
| Trigger | LVD technical documentation must allow assessment of conformity, include an adequate risk analysis and assessment, and cover design, manufacture, and operation as relevant. | RoHS documentation may be indexed beside LVD evidence, but this LVD-only source set does not support detailed RoHS documentation contents. | Use one evidence index if helpful, but label each item by legal act and do not let the LVD technical file stand in for a RoHS file. |
|---|
| Core obligations | LVD requires the manufacturer to draw up an EU declaration of conformity and affix CE marking after LVD conformity is demonstrated. | Where RoHS is also an applicable Union act requiring an EU declaration, LVD Article 15 supports using a single declaration that identifies each Union act and publication reference. | A combined declaration can reduce paperwork, but each listed act still needs its own supporting evidence. |
|---|
| Evidence record | LVD presumption of conformity depends on harmonised standards or parts of standards whose references have been published in the Official Journal and that cover the relevant LVD safety objectives. | RoHS appears as a separate standards area in the Commission overview, so RoHS standards evidence should be tracked separately from LVD safety standards evidence. | Keep the standards table explicit so each row shows the legal act, the publication basis, and the file section it supports. |
|---|
| Timing and deadlines | LVD evidence should prove the electrical safety conclusion: safety objectives, applied standards, design/manufacturing assessment, examinations, test reports, declaration, and CE marking. | RoHS evidence should not be inferred from LVD safety evidence in this artifact; this source set supports only the fact that RoHS can be a separate applicable act. | Separate the file chronology as well: keep LVD technical documentation and RoHS substance records in their own dated evidence chains, even if they sit in one index. |
|---|
| Enforcement | LVD addresses safety objectives for electrical equipment: health and safety of persons and domestic animals, and protection of property. | RoHS is treated here only as the separate hazardous-substance restriction workstream that may also apply to electrical and electronic products. | Use LVD safety conclusions for safety claims and RoHS substance conclusions for restricted-substance claims; do not treat either one as a substitute for the other. |
|---|
| Overlap and reuse | LVD technical evidence can be reused across products only when the same voltage scope, safety objective, and applied standard basis still match. | RoHS evidence may share the same file index, but it must still be supported by its own substance-control basis and not by LVD safety testing alone. | Share the container, not the conclusion: one index can hold both workstreams, but each workstream needs its own support line. |
|---|
| Practical decision rule | LVD applies when the product is electrical equipment within the voltage limits and not excluded; then the file must contain the safety, standards, and CE-marking evidence tied to LVD. | RoHS applies when the product is electrical and electronic equipment in a separate hazardous-substance scope; the LVD source set here only supports naming that workstream, not detailing it. | Decide first which legal act each document supports, then build the file around that act instead of asking one act to prove the other. |
|---|