Radio Equipment Directive Red Compliance Services
Radio Equipment Directive (RED) compliance services coordinate an identifiable radio product from intake through requirements mapping, testing, conformity assessment, technical documentation and EU market release. The deliverable is not a generic “RED certificate”: it is a defensible conformity route, a traceable technical file and manufacturer-approved release materials. The manufacturer remains legally responsible even if laboratories and advisers perform the work.
From intake to an identifiable RED product
Freeze exactly what will be sold and where. A radio module test report does not automatically cover the finished host, its antennas, enclosure, software or modes. Start with a configuration register linking each proposed model and variant to the sample and evidence.
- Product identification, intended use, target EU Member States, brand/manufacturer, importer and other economic operators.
- Radio technologies, operating bands, transmit power, antennas, module identifiers, host integration and firmware versions.
- Power supply, charging interface, accessories, user environment, intended users and possible safety or exposure risks.
- Existing test reports, drawings, bill of materials, risk assessment, instructions, labels and planned production changes.
Choose the conformity-assessment route before ordering tests
Apply RED Article 3 requirements to the final product: health and safety under 3(1)(a), electromagnetic compatibility under 3(1)(b), efficient spectrum use under 3(2), and the additional 3(3) requirements only where legally activated for that class. For the relevant requirement, check the current Official Journal citation, version, restrictions and actual full application of harmonised standards; a laboratory’s preferred standard list is not the legal decision.
| Evidence position | Practical route | Release consequence |
|---|---|---|
| Applicable harmonised standards are fully applied for 3(2) and applicable 3(3) requirements. | Annex II internal production control may be used; the manufacturer still prepares evidence, risk analysis and declaration. | No notified-body certificate is automatically required solely because the equipment has a transmitter. |
| For a relevant 3(2) or 3(3) requirement, no cited standard is used, it is applied only partly, or no applicable cited standard exists. | Use Annex III (EU-type examination plus conformity to type) or Annex IV (full quality assurance); verify the notified body’s designated RED scope. | Book notified-body review before committing the release date; resolve findings and certificate conditions. |
| Assessment concerns only Article 3(1) safety/health and EMC. | RED Article 17 permits Annex II, III or IV for these requirements; document the selected approach. | Do not mistakenly treat a notified body as mandatory for every safety or EMC test. |
Execute the work in six controlled handoffs
Use a stage-gate plan with one evidence owner and a release criterion per phase:
- Intake and scope lock. Manufacturer approves the exact equipment type, versions, intended markets and responsibility map; output: configuration baseline and open-question register.
- Requirement and standards map. Map each applicable RED requirement, other relevant EU acts, OJ-cited standards and uncovered risks; output: route decision and test matrix.
- Sample and laboratory handoff. Freeze sample hardware, antenna, firmware and test modes; commission RF, EMC, safety/exposure and relevant cybersecurity work; output: sample traceability and test orders.
- Failure resolution. Review deviations against legal requirements, implement engineering fixes and determine which evidence must be repeated; output: deviation/retest register.
- Conformity procedure and file. Obtain notified-body review when the chosen route requires it; complete Annex V documentation and draft the EU declaration; output: reviewed, versioned technical file.
- Launch sign-off. Check instructions, language, frequency/power statements, restrictions, operator identification, CE marking and declaration; manufacturer signs off before placing on the market.
Build the evidence file, not just a stack of test reports
The Annex V technical documentation should be constructed around the equipment type and allow an assessor or market-surveillance authority to follow each conclusion to evidence. Depending on the product, the handover index should contain:
- Description, photographs, design/manufacturing drawings, circuit diagrams, software/firmware identification and explanations needed to understand operation.
- List of applicable requirements and harmonised standards, including editions, OJ publication status, limitations and any alternative technical solutions.
- Design calculations, risk assessment, explanations of how essential requirements are met, and test reports linked to sample/version IDs.
- Laboratory reports and, where required by the route, notified-body EU-type examination certificate plus conditions or quality-system approvals.
- EU declaration of conformity in the Annex VI format, or simplified declaration wording in Annex VII with a functioning link to the full declaration.
- CE marking artwork, manufacturer/importer identification, user instructions, safety information and geographic-use restrictions where applicable.
- File owner, revision history and secure retention plan: manufacturer retains the technical file and declaration for 10 years after placing the equipment on the market.
Do not confuse a provider’s evidence package with an official EU-wide filing. Under the normal RED route, a declaration and CE mark are issued by the manufacturer; there is no routine central EU application that automatically “approves” all radio products. A notified body is involved only when the assessment route calls for one.
Check time-sensitive obligations before freezing the label
The release checklist must reflect the actual date of placing on the EU market and the particular product category:
- Cybersecurity. Delegated Regulation (EU) 2022/30 applies since 1 August 2025 to specified equipment under RED Article 3(3)(d)–(f), subject to scope rules and exceptions. EN 18031-series citations include restrictions; do not assume a standard gives full presumption of conformity in every case. Regulation (EU) 2026/339 repeals the delegated act with effect from 11 December 2027, when the Cyber Resilience Act’s main obligations apply.
- Common charger. For covered device categories, Directive (EU) 2022/2380 requirements have applied since 28 December 2024 and for laptops since 28 April 2026; review USB-C/charging protocol, pictogram, power label and charger-unbundling obligations against the precise category and charging design.
- Spectrum and national use. RED compliance does not erase restrictions on putting equipment into service or national frequency authorisations. If restrictions apply, prepare the required packaging information and instructions for affected Member States.
- Related EU legislation. Map other applicable regimes, such as RoHS, batteries, or product cybersecurity, separately; one EU declaration may cover multiple relevant Union acts, but a RED test report does not discharge other duties.
Allocate decisions and deliverables to the right party
Commercial coordination can be outsourced; legal responsibility and document custody cannot simply be reassigned by calling an adviser a “certifier”. Use named sign-off owners:
| Party | Hands over | Decides or remains responsible for |
|---|---|---|
| Manufacturer | Approved configuration, design evidence, production controls, signed EU declaration, labelling. | Applicable conformity route, final compliance, CE marking and production consistency. |
| Test laboratory | Sample IDs, methods, reports, uncertainties/deviations and retest scope. | Technical testing findings within its documented competence; not universal market authorisation. |
| Notified body, where required | EU-type examination review/certificate or Annex IV quality-system decisions. | Only the designated assessment work under the selected RED procedure. |
| Importer/distributor and coordinator | Verification records, translated market documents, supplier/file handoff and release checklist. | Each economic operator’s own RED duties; coordinator tracks gaps but does not inherit manufacturer obligations. |
Close the release gate and control later changes
Before the first EU placement, run a release gate against the exact production configuration:
- Every applicable requirement has a named evidence reference and any unresolved test or notified-body condition blocks release.
- CE mark, product/operator identifiers, user language, declaration access, frequency/power information and any use restrictions match the marketed unit.
- Manufacturer approves the EU declaration and technical-file revision; importer knows how to obtain supporting documents on request.
- Production, software updates, substitute antennas, radio modules or enclosure changes have an impact-assessment owner and stop/retest criteria.
- A surveillance-response procedure covers complaints, corrective measures, withdrawal/recall where appropriate and authority requests.
Typical blocking examples: a Bluetooth module was tested with a different antenna; a firmware update changes transmit behaviour; a cited standard covers only part of the cybersecurity requirement; or the CE label refers to a variant not documented in the file. Each needs an evidence decision, not merely a new label. For advisory-only scope selection consult the RED consultant page; for detailed laboratory methods consult the RED testing services page.
Related specialist scopes:
RED regulatory strategy and classification · RED laboratory testing and retesting
RED compliance: practical questions
Is a notified body always mandatory for RED?
No. For Article 3(2) and applicable 3(3) requirements, full application of relevant OJ-cited harmonised standards can permit Annex II internal production control. Missing or partially applied standards trigger Annex III or IV. The exact assessment must be recorded for the final equipment type.
Can existing radio-module test reports replace finished-product assessment?
Not automatically. They may support the technical file only where integration, antennas, firmware, installation conditions and applicable requirements remain covered. Any gaps require reasoned supplementary assessment and sometimes further tests.
Do we file the EU declaration with an EU authority before selling?
Normally no general central RED registration or prior EU filing is required. The manufacturer completes conformity assessment, draws up the EU declaration, affixes CE marking and maintains the file; notified-body involvement is route-dependent. Separate obligations must be checked if relevant.
Which products require RED cybersecurity work in October 2026?
Assess the specific categories and conditions under Regulation (EU) 2022/30, including internet-connected equipment and certain childcare, toy and wearable uses; exceptions apply. Check Article 3(3)(d), (e) and (f) separately and the restricted harmonised-standard citations.
Does a passing test report allow us to launch after a firmware update?
Not by itself. Compare the updated build with tested sample and risk assessment, evaluate the changed radio/security/safety behaviour, obtain additional evidence or notified-body review if needed, and update documentation and declaration before release.
Official legal and technical sources
- Directive 2014/53/EU — RED, especially Articles 3, 10, 17–21 and Annex V
- Implementing Decision (EU) 2022/2191 — OJ harmonised standards and limitations
- Delegated Regulation (EU) 2022/30 — RED cybersecurity categories
- Delegated Regulation (EU) 2026/339 — repeal effective 11 December 2027
- European Commission — common charger scope and application dates
- Implementing Decision (EU) 2025/138 — cybersecurity harmonised-standard restrictions