| Scope boundary | Covers equipment as apparatus or fixed installations. Apparatus includes finished appliances or combinations made available as a single functional unit that can generate electromagnetic disturbance or be affected by it. | Covers radio equipment. Commission evaluation material describes products with radio functionality as RED cases for EMC-related requirements instead of EMCD cases. | Start with the final product boundary. A non-radio electrical product may be EMCD apparatus; a product with an intentional radio function usually needs RED treatment for the whole radio equipment claim. |
|---|
| What the law covers | EMCD requires equipment to meet essential EMC requirements: disturbance must be limited so other equipment can operate as intended, and equipment must have adequate immunity in its intended electromagnetic environment. | RED includes EMC essential requirements for radio equipment. The EMC work is still needed, but it supports RED conformity rather than a separate EMCD declaration for the radio product. | Do not confuse an EMC test report with an EMCD legal citation. The same technical evidence may support different declarations depending on whether the product is in EMCD or RED scope. |
|---|
| Integration trigger | A host without radio functionality can be EMCD apparatus. If a radio module is added, reassess the final host product, antenna, enclosure, power supply, cables, software configuration, and intended environment. | A RED module declaration can be useful evidence, but it does not automatically prove the final host product remains compliant after integration. The final product evidence should show the radio and EMC assumptions still hold. | Keep the module DoC, module test reports, installation restrictions, antenna conditions, host EMC assessment, and final-product standards matrix together. Escalate when integration changes the declared radio or EMC conditions. |
|---|
| Core obligations | For EMCD apparatus, the manufacturer draws up technical documentation, performs conformity assessment, affixes CE marking to compliant apparatus, and keeps the DoC and technical documentation available to authorities for 10 years after placing on the market. | For RED products, the RED conformity assessment, RED technical documentation, RED DoC, and CE marking route control the radio equipment. EMC evidence is included as part of that RED compliance file. | Use one evidence index, but tag each document to the applicable law. The DoC should cite the law that applies to the product, not every test discipline used during development. |
|---|
| Standards and evidence | EMCD harmonised standards published in the Official Journal under Implementing Decision (EU) 2019/1326 can give presumption of conformity for the EMCD essential requirements they cover. | RED products may need RED-cited standards for radio, spectrum, safety, and EMC-related requirements. Commission evaluation material notes stakeholder concern about different EMC-related harmonised standards depending on EMCD or RED. | Maintain separate OJEU citation checks for EMCD and RED. A standard useful for engineering may still need a source-linked link to the legal route claimed in the DoC. |
|---|
| Route at release | Use EMCD when the product is non-radio apparatus or a fixed installation in EMCD scope, or when a formerly telecom-terminal style product is outside RED and still has EMC characteristics to assess. | Use RED when the final product is radio equipment. Keep EMC evidence, but route the product declaration, CE marking file, and standards mapping through RED for the radio product. | Release should be blocked until the product boundary, applicable law, standards route, DoC citation, technical documentation, and integration assumptions all say the same thing. |
|---|
| Scope and boundary check | EMCD covers equipment as apparatus or fixed installations. Apparatus is the finished product or combination made available as one functional unit, while fixed installations are permanent combinations assembled at a predefined location. | RED covers radio equipment and the same finished product is normally treated under RED when the radio function is intentional. Commission material says products with radio functionality move to RED for EMC-related requirements. | Skim this row when you need the first question to answer at release: is the placed-on-market product radio equipment, or is it a non-radio apparatus or fixed installation in EMCD scope? |
|---|
| Overlap and reuse | A single engineering evidence pack can often support both routes, but the legal citation must match the route actually governing the product. Keep one traceable file, but separate the EMCD and RED legal claims. | For radio products, EMC testing, standards mapping, and technical file evidence may still be reused, but the RED file should carry the conformity claim and DoC. Do not duplicate EMCD and RED declarations for the same EMC requirement. | Reuse test reports where possible, but do not reuse the legal label. The question is not whether the evidence is useful twice; it is whether the same evidence supports two different legal claims. |
|---|
| Practical decision rule | If the final product is a non-radio apparatus or fixed installation, route the conformity work through EMCD. If the product is radio equipment, use RED and keep the EMC evidence inside the RED compliance file. | If integration changes the radio module, antenna, enclosure, cable routing, power supply, or software configuration, re-check the product boundary before release. A module certificate alone is not enough for the final host product. | Ask two questions in order: what is the final product, and which Union law governs that final product? That sequence avoids the most common EMCD-RED mix-up. |
|---|