RoHSRequirements

EU RoHS Directive (2011/65/EU) Requirements

RoHS requirements are simple to state and hard to prove without a system.

Output: a requirements-to-evidence map you can operationalise across suppliers and SKUs.

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

The core RoHS requirement is a materials requirement: EEE placed on the market must not exceed restricted substance thresholds in homogeneous materials unless a valid exemption applies. The operational requirement is evidence: you must be able to demonstrate compliance with a technical documentation pack and supplier-backed proof.

Section 1

1) Substances restriction requirement (Annex II)

EEE must not contain restricted substances above the maximum tolerated values in homogeneous materials.

Implementation reality: your unit of control is the homogeneous material, not the part number.

Build a homogeneous-material model in your BOM and link evidence at that level
Maintain a restricted-substances risk map (hotspots like solders, cables, soft plastics)
Use supplier declarations and verification triggers; do not rely on compliant labels

Recommended next step

Turn EU RoHS Directive (2011/65/EU) Requirements into an operational assessment

Assessment Autopilot can take EU RoHS Directive (2011/65/EU) Requirements from turning the requirements into assigned actions to a reusable workflow inside Sorena. Teams working on EU RoHS Directive (2011/65/EU) can keep owners, evidence, and next steps aligned without copying this guide into separate documents.

Assessment workflow

Open Assessment Autopilot for EU RoHS Directive (2011/65/EU) Requirements

Start from EU RoHS Directive (2011/65/EU) Requirements and turn the guidance into owned tasks, evidence requests, and review checkpoints.

Explore next step

Talk to Sorena

Talk through EU RoHS Directive (2011/65/EU)

Review your current process, evidence gaps, and next steps for EU RoHS Directive (2011/65/EU) Requirements.

Explore next step

Section 2

2) Exemptions logic (Annex III/IV) and expiry risk

Exemptions are narrow allowances for specific applications and conditions, often time-limited and revised.

The requirement is not to have an exemption, but to prove that the exact application in your product matches the exemption scope and is still valid.

Traceability: exemption -> application -> part/material -> supplier
Expiry monitoring: plan redesign or renewal work 18 - 24 months ahead
Evidence pack: technical justification, supplier confirmations, and release/change control

Section 3

3) Supplier evidence and verification (your control layer)

RoHS is enforced through the supply chain: if suppliers can't back their claims, you can't back yours.

Implement supplier requirements as contractual and process controls.

Supplier declarations covering Annex II substances and homogeneous material scope
Change notification duties (material, process, formulation, plating, cable insulation changes)
Verification plan: when you test, how you sample, what you do with failures
Traceability: link supplier artifacts to specific SKUs/variants

Section 4

4) Technical documentation and CE evidence (EN IEC 63000)

A defensible RoHS program produces a technical documentation pack that is retrievable and consistent.

EN IEC 63000 is the harmonised standard referenced for RoHS technical documentation; use it to structure your evidence.

Article 13 also allows a single technical documentation set where another applicable Union conformity-assessment procedure is at least as stringent.

Technical file structure aligned to EN IEC 63000: evidence sources, evaluation logic, and conclusions
Evidence artifacts: declarations, test reports, exemption register, change history
Release governance: ensure the technical file matches the shipped configuration and suppliers
Retention: keep the technical documentation and DoC for 10 years and make sure importer copies remain available

Section 5

A simple requirements-to-evidence map (what 'done' means)

Use this mapping to assign owners and define acceptance criteria.

If you can't retrieve these artifacts quickly, your program is not operational.

Scope memo (owner: compliance/engineering): product category, variants, exclusions logic
Substances map (owner: engineering): homogeneous materials + hotspots + acceptance criteria
Supplier evidence pack (owner: procurement/quality): declarations + change controls + traceability
Exemption register (owner: compliance): applicability + expiry + redesign/renewal plan
Technical documentation pack (owner: compliance/QA): EN IEC 63000-aligned file + evidence links

Primary sources