Radio Equipment Directive Red Testing Services
RED testing services should start with an evidence plan, not a generic “CE test” quotation. For a device with Wi-Fi, Bluetooth, cellular, NFC or another radio function, identify its exact radio configuration and the legal requirement each proposed test will support. Directive 2014/53/EU places conformity responsibility on the manufacturer; a test report is evidence, not an EU market-entry licence.
The decision before booking a laboratory is: which tests cover the finished product, which earlier results remain usable, and whether a notified-body conformity-assessment route is triggered. The matrix and checkpoints below are a commissioning tool—not a claim that every test applies to every device.
Freeze the testing input
Before requesting a price, send one controlled configuration sheet: product model and variant list; radio technologies, bands, channels, output power and antennas; intended EU countries and operating environment; host and radio-module identifiers; PCB/hardware revisions, power supply and accessories; firmware build, regional locks and possible modes; intended user, distance from the body and installation geometry. Record which parameters are fixed in production and which can be changed by software. Ask the lab to mark assumptions and excluded configurations in writing. Also verify national spectrum allocations and any operating restrictions in each intended EU market: passing RED testing alone does not make every band usable in every Member State (Articles 10(2) and 10(10)).
RED evidence matrix: test only what the product needs
| RED requirement / evidence area | Typical assessment and test questions | Scoping trap to avoid |
|---|---|---|
| Art. 3(1)(a): health and safety | Electrical and mechanical safety plus exposure to electromagnetic fields (assessment, measurement or SAR where relevant); consider intended and reasonably foreseeable use. | Do not assume a low-voltage threshold exemption or that every wireless device needs SAR measurements. |
| Art. 3(1)(b): EMC | Emissions and immunity of the radio equipment in representative transmit, receive and operating states; check mains ports, cables and accessories. | A bare module EMC result does not automatically cover a newly designed host. |
| Art. 3(2): spectrum | Applicable radio-standard tests for the actual bands and radio interfaces, such as unwanted emissions, output power, occupied bandwidth or receiver behaviour where specified. | A foreign FCC report or a generic “RF pass” is not proof against the specific RED requirement. |
| Art. 3(3)(d)–(f): cybersecurity, if in scope | Document the applicability of Delegated Regulation 2022/30; assess network protection, privacy/personal-data safeguards and/or fraud protection as applicable. Assess the OJ limitations on EN 18031-1/-2/-3:2024. | Not every connected item is subject to every subsection; a nominal EN 18031 report may not create full presumption of conformity. |
| Other activated/specific requirements | Check the specific delegated act on emergency caller location under Article 3(3)(g) for covered mobile devices. Separately, check Article 3(4) common-charging requirements only for the equipment categories and wired-charging cases covered by Annex Ia; plan the evidence accordingly. | Do not apply all special requirements to every radio product or confuse charging checks with spectrum tests. |
Match test standards to the actual conformity-assessment route
Harmonised standards are voluntary technical routes, not legislation. For a presumption of conformity, check the precise edition and any restrictions published in the Official Journal for the relevant RED requirement—using Decision 2022/2191 as amended, including Decision 2026/2003 of 4 September 2026. An undated standards-list screenshot or the latest ETSI edition alone is insufficient. Record standard, version, OJ status, restriction, requirement covered and assessment method in the test plan. Check the entry-specific dates: amendments may provide deferred application or withdrawal of individual standard references.
Article 17 differentiates the routes. For Art. 3(1)(a), 3(1)(b) and, where applicable, 3(4), internal production control (Annex II, Module A) can be used. For Art. 3(2) and applicable Art. 3(3) requirements, when relevant OJ-cited harmonised standards are not applied in full or do not cover the requirement, a notified-body route under Annex III (EU-type examination plus conformity to type) or Annex IV (full quality assurance) is needed. OJ restrictions can remove presumption for an uncovered aspect. A laboratory test, ISO/IEC 17025 accreditation and notified-body designation are three different things.
Cybersecurity timing matters: delegated RED requirements have applied to covered equipment since 1 August 2025. Regulation 2026/339 repeals Delegated Regulation 2022/30 only with effect from 11 December 2027. Do not remove current cybersecurity assessment from a 2026 test scope just because repeal has been published.
Select the laboratory: six acceptance checks
Ask for documentary answers before reserving chamber time. Accreditation is valuable evidence of laboratory competence only for the tests actually included in its scope; it is not, by itself, a notified-body appointment or proof that a report fits the chosen RED route.
- Provide the actual test site, ISO/IEC 17025 accreditation body, certificate and scope for each relevant method—or explain if a test is not accredited.
- Show experience with the exact radio technology, standard edition, antenna/exposure setup and the planned operating modes.
- State whether the quoted work is pre-compliance screening or final documented testing, and who signs each report.
- If notified-body review is needed, identify the separate legal entity and verify its RED designation and relevant scope in the Commission NANDO database.
- Confirm the standard/OJ edition, deviations, measurement uncertainty, pass/fail rule, witness needs and report language before test start.
- Specify sample count, fixture/cabling, firmware control, estimated rerun criteria and any excluded variants in the written quotation.
Sample plan: what the laboratory must reproduce
The RED assessment must cover relevant intended operating conditions and configurations. The test engineer may justify a worst-case reduction, but “one sample covers all SKUs” is not a legal default. Agree a traceable coverage map first.
- Build a SKU-to-technology matrix: every radio interface, concurrent-transmit combination, frequency range, antenna type/gain and regional setting.
- Provide production-representative units and, where needed for the selected test methods, dedicated engineering/test modes; record any mode unavailable in normal operation.
- Identify stress states for power, temperature, supply, host loading and cables where the test method and risk assessment require them.
- Record serial number, photographs, PCB revision, firmware hash/build, configuration files, antenna, power supply and test fixture for each sample.
- Set a written rule for which changes or failures require a replacement sample, partial rerun or full assessment; retain pre- and post-fix traceability.
Can earlier reports be reused?
| Earlier evidence | Practical acceptance check | Safe decision |
|---|---|---|
| Report for the same finished model | Compare exact hardware, antenna, firmware, supported bands, OJ edition, configurations and test conditions. | Reuse only for demonstrably unchanged covered characteristics; close missing requirements. |
| Radio-module report or EU-type examination | Verify the module identity, permitted antenna/host conditions and actual integration; identify host-created RF, EMC or exposure changes. | Treat it as supporting evidence, not an automatic whole-product exemption. |
| FCC, ISED or another non-EU report | Compare the actual measurements and methods clause by clause with the applicable RED standards and technical risks. | Data may help; foreign approval alone does not establish RED conformity. |
| Old RED report or superseded standard | Check OJ citation and withdrawal/effective dates for units newly placed on the EU market, plus design drift and restrictions. | Do targeted gap testing, alternative technical justification and, when required, notified-body assessment; no automatic blanket retest date. |
Failures, retests and engineering change control
Record failures against the requirement and measurement, not just “failed CE”. A controlled failure log is more useful than repeatedly paying for the same chamber session.
- Excess unwanted emissions: isolate antenna, filtering, clock harmonics or host enclosure; retest the affected radio measurements and relevant interactions.
- EMC immunity failure: document observed malfunction and acceptance criteria; fix shielding/layout/firmware and rerun the affected configurations.
- Exposure margin or setup issue: revisit user distance, duty cycle, power-control logic and documented use; re-evaluate only after validating assumptions.
- Cybersecurity control gap: capture the product state and remediation evidence; assess the changed software/security features against all applicable clauses.
- New antenna, RF power table, PCB, module, firmware or accessories: evaluate which previous test results the change undermines; write and approve a delta-test plan before release.
Define deliverables and send a test-ready request
A useful RED test purchase order should deliver an evidence pack, not only a summary certificate. Require the following, subject to the particular assessment method:
- Approved test scope and rationale, with standards, editions, OJ limitations and excluded requirements.
- Sample/configuration register and test-mode instructions, including deviations from production state.
- Signed test reports with methods, conditions, measured values, uncertainty as applicable, results and traceability.
- Defect log, corrective-action record and targeted retest reports linked to the original results.
- Residual gap/coverage table and the inputs needed for the manufacturer’s technical documentation under RED Article 21 and Annex V.
Before awarding the laboratory purchase order, ask these questions in one email:
- Which Article 3 requirements and product-specific acts are in scope, and which are not?
- Which exact harmonised-standard editions have current OJ effect, and what restrictions apply?
- What is the defensible sampling and simultaneous-radio test strategy?
- Which previous module or product results can you use, and on what documented conditions?
- Which tests are within your accredited scope, and who is the actual performing laboratory?
- Is an independent RED notified-body step triggered for any Art. 3(2)/3(3) aspect?
- What will trigger a rerun after RF, antenna, firmware, enclosure or power changes?
- What exact reports, deviations and coverage matrix will the manufacturer receive?
Where testing stops and compliance advice begins
This page concerns laboratory evidence, acceptance and retest decisions. End-to-end declarations, production obligations and market-entry execution belong on the RED compliance services page; strategic classification or multi-regime gap decisions belong on the RED consultancy and scope advice page. The lab cannot transfer the manufacturer’s legal responsibility for the product.
Questions frequently asked before RED testing
Does every RED device require a notified body?
No. Article 17 allows Module A for specified aspects, and for spectrum/applicable Article 3(3) requirements when the relevant harmonised standards are fully applied. If the relevant coverage is missing or only partial, check the mandatory notified-body route for those aspects.
Can I place a Bluetooth module into a new product without further testing?
Do not assume so. Compare antenna, host EMC, RF integration, exposure, firmware and intended use with the module evidence, then define a documented host-level gap assessment.
How long is a RED test report valid?
RED does not establish a universal expiry period for every test report. Its usefulness depends on product identity, modifications, the chosen conformity route, and changes to applicable OJ-cited standards or requirements for future placing on the market.
Do RED cybersecurity requirements still apply in October 2026?
Yes, to products within Delegated Regulation 2022/30. Regulation 2026/339 repeals it only from 11 December 2027. Assess the device category and any EN 18031 restrictions; this duty to demonstrate conformity does not, by itself, mandate purchasing independent laboratory tests for every product. The notified-body route depends on Article 17 and the harmonised-standard coverage.
Can an FCC report or a passing RF test replace the full RED evidence pack?
No automatic substitution. Evaluate the underlying data against the actual RED requirements, complete safety/EMC/security gaps and preserve traceability to the finished EU configuration.
Official sources
- Directive 2014/53/EU (Articles 3, 17, 21; Annex V)
- European Commission RED Guide (2026; non-binding)
- OJ harmonised standards and 2026 amendment
- 2026 OJ amendment (2026/2003)
- Current RED cybersecurity scope (2022/30)
- EN 18031 publication and restrictions (2025/138)
- Cybersecurity delegated rules and deferred repeal
- Commission NANDO listing
- Delegated Regulation 2019/320: emergency caller location (selected devices)
- Directive 2022/2380: common charging (specified categories)