EU RED scope classification workflow

Start with Article 1 and Article 2 of Directive 2014/53/EU. The Directive establishes the EU framework for making radio equipment available on the market and putting it into service. Radio equipment is an electrical or electronic product that intentionally emits or receives radio waves for radio communication or radiodetermination, including a product that needs an accessory such as an antenna to perform that function.

Write the initial decision as a fact chain rather than a label. Identify the product configuration, radio interface, receiver or transmitter function, antenna dependency, software or firmware version affecting the radio function, intended use, and whether the product is being made available on the Union market, first placed on that market, or put into service.

Before opening a test plan, rule out the explicit exclusions. Directive 2014/53/EU excludes equipment listed in Annex I and radio equipment exclusively used for public security, defence, State security, certain State economic-security matters, and State criminal-law activities. The Commission RED Guide warns that equipment used by public authorities can still be in scope when it is not exclusively used for excluded activities.

Then resolve common borderline cases with product facts. Commission guidance treats radio and television receivers, equipment below 9 kHz, radiodetermination equipment, and active antennas as RED scope examples. It distinguishes passive antennas sold alone, pure DVB-C receivers receiving a wired CATV signal, custom-built evaluation kits for professional R&D facilities, amateur-radio cases, construction kits, infrared devices, and products using waves for non-radio purposes.

When RED applies, classify the product against Article 3 before selecting standards. Article 3(1)(a) covers health and safety objectives, Article 3(1)(b) covers electromagnetic compatibility, and Article 3(2) covers effective and efficient use of radio spectrum to avoid harmful interference. Article 3(3) adds category-specific requirements such as network protection, personal-data and privacy safeguards, fraud protection, emergency-service access, accessibility, and software-loading controls where delegated or implementing acts make them applicable.

A release-ready workflow should therefore produce a requirement matrix, not only a scope conclusion. For each radio interface and product configuration, record whether Article 3(1), 3(2), and any Article 3(3) requirement applies, what evidence will demonstrate conformity, and whether the decision relies on a harmonised standard cited in the Official Journal or on another technical specification.

RED scope classification now needs two extra gates for many connected or rechargeable products. Delegated Regulation (EU) 2022/30 applies Article 3(3)(d) to internet-connected radio equipment, Article 3(3)(e) to specified radio equipment capable of processing personal, traffic, or location data, and Article 3(3)(f) to internet-connected radio equipment enabling transfer of money, monetary value, or virtual currency. Delegated Regulation (EU) 2023/2444 moved the application date for those cybersecurity requirements to 1 August 2025.

For common charging, classify whether the product is one of the listed portable radio-equipment categories subject to the RED common-charger amendments. Commission guidance states that the common charging requirements apply to listed handheld devices since 28 December 2024 and to laptops as of 28 April 2026. If in scope, route the product to USB-C, fast-charging, charger-unbundling, pictogram, and charging-information evidence.

Once the scope and requirement buckets are set, choose the evidence route. RED gives presumption of conformity for harmonised standards or parts of standards whose references are published in the Official Journal for the Article 3 requirements they cover. Article 17 then links the standards position to conformity-assessment options: internal production control, EU-type examination followed by conformity to type, or full quality assurance.

If harmonised standards for Article 3(2) or 3(3) are missing, not applied, or only partly applied, the workflow should flag the notified-body route under Article 17 instead of closing on internal production control alone. The technical file should show the applicable requirements, standards used in full or in part, alternative technical specifications, test reports, EU declaration of conformity, CE marking basis, and copies of certificates where the selected module requires them.

The finished record should let a reviewer understand the answer without replaying the meeting. It should name the product, model, radio functions, intended use, Union-market fact pattern, exclusions considered, Article 3 requirement buckets, cybersecurity and common-charger gates, standards route, conformity-assessment route, evidence owners, and open assumptions.

Use a clear status for each configuration: in RED scope, outside RED scope with reason, in RED scope but requiring escalation, or blocked pending missing facts. Do not cite local PDFs, file paths, copied guidance, or public URLs without `ref=sorena.io`; source entries should be external HTTPS references that support the classification claim.