Annex III/IVExemptions

EU RoHS Directive (2011/65/EU) Exemptions Tracking

Exemptions are product risk - manage them like expiring certificates.

Output: an exemption register tied to part numbers, homogeneous materials, and redesign decisions.

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

RoHS exemptions are not a blanket permission to use restricted substances in the product. They are narrowly scoped allowances for specific applications and conditions, typically time-limited and updated over time. If you can't trace an exemption to a specific homogeneous material and usage, you can't defend it.

Section 1

What a defensible exemption looks like

A defensible exemption is specific, traceable, and evidence-backed.

Your objective is to prove: which exemption applies, where it applies in the BOM (homogeneous material), and why you still meet the exemption conditions.

Traceability: exemption -> application -> part number -> homogeneous material
Time control: expiry/renewal dates and status (valid, renewed, sunset, replaced)
Evidence: technical justification, supplier confirmations, and change control

Section 2

Annex III vs Annex IV (practical difference)

RoHS exemptions are listed in annexes and can differ by equipment category and application.

Implementation tip: do not store exemptions only at the 'product' level - store them at the 'application' level.

Annex III: exemptions applicable across a broad set of EEE applications (application-specific allowances)
Annex IV: exemptions focused on certain categories (commonly medical devices and monitoring/control applications)
Maximum validity is usually 5 years for categories 1 to 7, 10 and 11, and 7 years for categories 8 and 9 unless a shorter period is specified
Many exemptions are revised: always check the latest official version and amendment history

Section 3

A tracking workflow that prevents surprises

Build a simple, non-negotiable workflow: identification -> registration -> monitoring -> decision -> execution.

Your surprise prevention is the monitoring and redesign decision timing.

Identify: which restricted substances exist and which uses rely on exemptions
Register: exemption ID, exact wording, scope conditions, affected parts/materials, suppliers
Monitor: expiry dates, renewal status, Commission timelines, and any official updates
Decide: renew vs redesign vs dual-source vs discontinue
Execute: redesign plan, supplier change, and evidence updates (technical file + declarations)

Section 4

Evidence pack per exemption (what to keep)

The evidence pack makes the exemption defensible in audits and market surveillance requests.

Keep it lightweight but complete: scope proof, technical justification, and current supplier confirmations.

Where used: BOM link and homogeneous material definition
Why needed: technical feasibility and substitution assessment (what alternatives were evaluated)
Supplier evidence: declarations for the specific application and change-notification duty
Release control: product variants affected and what changes require re-evaluation

Section 5

How to avoid an 'exemption cliff'

Exemption cliffs happen when expiry is discovered too late to redesign. Prevent that with early trigger points.

If your redesign cycle is 12 - 24 months, your trigger must be at least that early.

Set a trigger horizon: start redesign and renewal planning 18 to 24 months before expiry
File renewal applications no later than 18 months before expiry if you need continued use
If renewal is filed in time, the exemption remains valid until the Commission decision
If a renewal is rejected or an exemption is revoked, expect a 12 to 18 month transition window
Prioritise high-volume SKUs and single-source components
Decouple program work: redesign planning can run while you monitor renewal decisions
Keep a fallback: dual-source or alternative part qualified before sunset

Recommended next step

Use EU RoHS Directive (2011/65/EU) Exemptions Tracking as a cited research workflow

Research Copilot can take EU RoHS Directive (2011/65/EU) Exemptions Tracking from clarifying scope and applicability with cited answers 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.

Research workflow

Open Research Copilot for EU RoHS Directive (2011/65/EU) Exemptions Tracking

Start from EU RoHS Directive (2011/65/EU) Exemptions Tracking and answer scope, timing, and interpretation questions with cited outputs.

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) Exemptions Tracking.

Explore next step

Primary sources