FAQEU

RED FAQ SAR and RF Exposure

Under RED, SAR and RF exposure sit in the Article 3(1)(a) health and safety assessment. The evidence should connect the actual radio configuration to intended and reasonably foreseeable use, not just cite a general CE or lab certificate.

This FAQ helps decide which frequency, power, antenna, body-position, accessory, software, harmonised-standard, and test-report records belong in the RED technical documentation.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Questions
5

Structured answer sets in this page tree.

Primary sources
3

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 24, 2026
Overview

For RED and wireless exposure, start with Article 3(1)(a): radio equipment must protect health and safety. SAR is one exposure metric, not the required method for every radio product. The applicable assessment depends on the frequency, power, antenna, distance from the body, operating mode, and product scenario. Exposure-related harmonised standards listed for RED address specific cases, including wireless communication devices used next to the ear or close to the human body. The evidence file should show the operating frequency bands, , antenna configuration, intended body position, , accessories and software that affect transmission, the applicable OJEU-listed standard or other technical specification, and the test or engineering evidence used to support the conclusion.

Search this module

Find a question or answer quickly

5 of 5 questions
Question 1

What SAR and RF exposure evidence is needed under RED?

The RED does not treat or as a separate marketing claim. It is part of the Article 3(1)(a) health and safety essential requirement, assessed through the conformity assessment and documented in the technical documentation.

Answer the exposure question directly: identify the radio equipment, each intentional transmitter, frequency band, , antenna and enclosure configuration, operating modes, intended distance from the body, foreseeable near-body or next-to-ear use, and the standard or technical specification used to evaluate exposure. State whether the evidence is a measurement, another measurement, a calculation, or a standards-based low-power assessment, and why that method fits the scenario.

  • Use Article 10(8) data as a starting point: instructions for intentional transmitters must include frequency bands and maximum radio-frequency power.
  • For devices used next to the ear or close to the human body, check whether the current OJEU references for EN 50360:2017/A1:2023 and EN 50566:2017/A1:2023 cover the product and operating scenario; do not assume those two standards cover fixed, remote, implanted, or every low-power product.
  • Keep the or test report, standard-selection rationale, antenna drawings, radio settings, software version, accessory assumptions, separation-distance assumptions, and engineering judgement with the RED technical documentation.

What and evidence is needed under RED?

Keep evidence that links the actual transmitter configuration to Article 3(1)(a): frequency bands, , antenna and enclosure design, intended and reasonably foreseeable body position, operating modes, accessories, software or firmware affecting transmission, selected standard or technical specification, and the or assessment or test report.

Does a general CE certificate answer the question?

No. A CE mark or certificate is not enough by itself. The technical documentation should show why the specific radio equipment, in its intended and , meets the health and safety requirement for human exposure to electromagnetic fields.

Citations
Recommended next step

Keep the RF exposure evidence traceable

Turn this RED exposure FAQ into a repeatable evidence workflow for engineering, test, quality, regulatory, and product teams. Keep transmitter facts, use assumptions, standards, test reports, citations, owners, and review triggers together.

Question 2

How do Article 3(1)(a), Article 10(8), Article 17, and Article 21 fit together?

Article 3(1)(a) is the obligation: radio equipment must protect health and safety. Article 17 is the assessment rule: the conformity assessment must cover intended operating conditions and, for Article 3(1)(a), reasonably foreseeable conditions. Article 10(8) supplies key transmitter facts for intentional emitters. Article 21 is where the supporting technical documentation is anchored.

That means the exposure answer should not be written only as a standards citation. It should be a traceable chain from product facts, to exposure scenario, to standard or technical specification, to test or analysis, to the declaration of conformity.

  • Record the frequency band and used for each intentional transmitter and operating mode.
  • State whether users can hold, wear, mount, carry, or operate the product next to the ear, close to the body, at a fixed distance, or in an installation.
  • Include the standard edition or alternative specification used, and explain any exclusions, partial application, or product differences from the tested configuration.
Citations
Question 3

What records should stay in the technical documentation?

The exposure file should be reviewable without project history. A market-surveillance reviewer should be able to see what was assessed, what transmitter configuration was tested or analysed, which standard or specification was used, and why the conclusion still matches the product placed on the EU market.

For RED and , use an evidence map covering the Article 3(1)(a) health and safety requirement, Article 17 use-condition assumptions, Article 10(8) frequency and power information, applicable harmonised standards, test reports, EU declaration, and change-control triggers.

  • Keep product identifiers, hardware revision, antenna layout, enclosure material, radio module data, transmitter power settings, and software or firmware versions that can affect RF output.
  • Keep , , or engineering assessment reports with the tested modes, channels, antennas, accessories, duty cycles, and separation distances clearly tied to the marketed configuration.
  • Reopen the assessment when the antenna, enclosure, radio module, maximum power, firmware, accessory set, user instructions, intended body position, , or market restriction changes.
Citations
Directive 2014/53/EU on radio equipment

Binding RED source for technical documentation, conformity assessment, instructions, and the 10-year retention obligation for technical documentation and the EU declaration of conformity.

Question 4

Implementation checklist for SAR and RF exposure

Use the checklist to produce a documented yes, no, or needs-escalation answer for the specific radio equipment, not for a generic product category.

  • Confirm whether the product intentionally emits radio waves and list every transmitter, antenna, operating band, and setting.
  • Classify the use scenario: next to ear, hand-held, body-mounted, close proximity to the body, fixed installation, remote from users, or multiple configurations.
  • Select the current OJEU-listed where it covers the product; if using another specification, document why it is adequate and whether notified-body involvement is triggered for the relevant RED requirement.
  • Tie each or test report to the marketed hardware, software, antenna, accessory, and user-instruction configuration.
  • Update instructions and safety information so users understand the intended use conditions relied on in the exposure assessment.
Citations
Question 5

Common SAR and RF exposure documentation mistakes

The main failure mode is mismatch: the evidence exists, but it does not match the product, antenna, firmware, accessory, frequency band, power setting, or use distance being sold in the EU.

  • Do not reuse a module, supplier, or lab report unless the host-product antenna, enclosure, RF settings, installation, and user-position assumptions still match.
  • Do not cite an old standard reference without checking whether the OJEU listing has been amended, withdrawn, restricted, or replaced for the exposure scenario.
  • Do not bury separation-distance or body-position assumptions in engineering notes if the user instructions need those conditions for the assessment to remain true.
  • Do not let a firmware or power-table change ship without checking whether it changes the Article 3(1)(a) exposure conclusion.
Citations
Primary sources

References and citations

eur-lex.europa.eu
Referenced sections
  • OJEU source showing amended exposure-standard references and deferred withdrawal of earlier EN 50360 and EN 50566 references.
"it is necessary to defer the withdrawal of the references"
eur-lex.europa.eu
Referenced sections
  • Binding RED source requiring technical documentation to contain relevant data and to be continuously updated.
"technical documentation shall be drawn up before radio equipment is placed on the market"
Related guides

Explore more topics

Are radio kits and evaluation boards covered by the RED? | RED FAQ
RED FAQ for radio kits, construction kits, amateur-radio kits, and custom-built professional R&D evaluation boards under Directive 2014/53/EU.
EU Radio Equipment Directive Timeline: RED, Cyber and USB-C Dates
Understand which RED dates changed market-access rules, including 2016 application, the 2017 transition cutoff, common-charger dates, and cybersecurity requirements from 1 August 2025.
EU RED Applicability Test for Radio Equipment
Decide whether Directive 2014/53/EU applies to a connected product, which RED requirements are triggered, and what evidence belongs in the technical file.
EU RED Common Charger FAQ: Which devices need USB-C?
FAQ on EU RED common charger scope, 28 December 2024 and 28 April 2026 dates, USB-C, USB Power Delivery, charger unbundling, labels, pictograms, and evidence.
EU RED Common Charger Obligations: USB-C scope, dates, labels
Check RED common-charger device categories, application dates, USB-C and USB Power Delivery specifications, charger unbundling, consumer pictograms, labels, and release evidence.
EU RED compliance evidence guide
Build a Radio Equipment Directive compliance file with Article 3 requirement mapping, harmonised-standard checks, conformity assessment evidence, EU declarations, CE marking, and RED source links.
EU RED Cybersecurity Product Categories: 2022/30 scope
Classify products under RED Delegated Regulation (EU) 2022/30, including exclusions, EN 18031 evidence, and the 1 August 2025 to 10 December 2027 transition.
EU RED FAQ: Scope, CE and USB-C
Answers to common EU RED questions on radio equipment scope, Article 3 requirements, cybersecurity, USB-C common charger rules, CE marking, and technical-file evidence.
EU RED Radio Equipment Scope: products and exclusions
Decide whether a product is radio equipment under Directive 2014/53/EU, with RED scope tests, exclusions, examples, and evidence records.
EU RED Requirements Map: CE and Article 3
Map Radio Equipment Directive requirements for radio products: Article 3 safety, EMC, spectrum, selected Article 3(3) duties, common charger rules, conformity assessment, CE marking, EU declaration, and technical documentation.
EU RED Scope and Classification
Classify products under the EU Radio Equipment Directive with cited tests for radio equipment scope, exclusions, Article 3 requirement buckets, cybersecurity, common charging, and evidence records.
EU RED Scope Classification Workflow
Classify products under the EU Radio Equipment Directive with a cited workflow for RED scope, exclusions, Article 3 requirements, standards, CE evidence, cybersecurity, and common-charger triggers.
RED Article 10 labelling, instructions, and restrictions
Apply RED Article 10 to product identifiers, manufacturer contacts, instructions, declaration statements, radio-frequency information, charging labels, and use restrictions.
RED Article 3 requirement selection workflow
Select the right RED Article 3 branches for radio equipment: safety, EMC, spectrum, delegated Article 3(3) duties, cybersecurity, common charging, evidence, and conformity assessment.
RED Article 3 Requirements: Safety, EMC, Spectrum and Cyber
Map Radio Equipment Directive Article 3(1), 3(2), and 3(3) requirements to safety, EMC, spectrum, interoperability, emergency, software, and cyber evidence.
RED Compliance Checklist for Radio Equipment
Use this RED release checklist for product scope, Article 3 requirements, technical documentation, EU declarations, CE marking, cybersecurity, common charging, and notified-body decisions.
RED compliance deadlines calendar: 2016 to 2027
Calendar EU Radio Equipment Directive launch dates through 2027: RED applicability, common charger, cybersecurity, standards, CE marking, declarations and retention.
RED conformity assessment and CE marking
EU Radio Equipment Directive guide to Article 17 conformity modules, notified-body triggers, technical documentation, EU declarations, and CE marking.
RED Conformity Assessment Template
Template fields for documenting RED Article 3 requirements, Article 17 route selection, harmonised standards, notified-body evidence, technical documentation, EU declaration, CE marking, cybersecurity, and common-charger checks.
RED Cyber Compliance Workflow for Article 3(3)(d/e/f)
A cited RED cybersecurity workflow for internet-connected radio equipment, privacy and data safeguards, payment-fraud features, evidence packs, and CE release gates.
RED Cybersecurity Delegated Act Guide | Article 3(3)(d/e/f)
Guide to RED Article 3(3)(d), (e), and (f) scope, EN 18031 evidence, the 1 August 2025 application date, and repeal of Delegated Regulation (EU) 2022/30 from 11 December 2027.
RED Cybersecurity Requirements for Radio Equipment
EU RED cybersecurity requirements under Article 3(3)(d), (e), and (f): scope, affected radio equipment, application date, standards, notified bodies, and evidence.
RED DoC and CE marking file: what to include
FAQ answer for Radio Equipment Directive declarations of conformity, CE marking evidence, technical documentation, notified-body records, and related labels.
RED EMC and LVD Safety Interplay for Radio Equipment
Explain how EU RED Article 3 applies LVD safety objectives and EMC requirements to radio equipment, with evidence, test-plan, and technical-file guidance.
RED Harmonised Standards and Test Plans: OJEU evidence guide
Build a Radio Equipment Directive standards matrix and test plan around OJEU-cited harmonised standards, Article 3 requirements, Article 17 route triggers, and Annex V technical-file evidence.
RED importer obligations FAQ | Directive 2014/53/EU
What importers must check before placing radio equipment on the EU market: conformity assessment, spectrum use, technical documentation, EU declaration, CE marking, traceability, instructions, restrictions, storage, corrective action, and authority cooperation.
RED notified body route selection under Article 17
Decide when RED radio equipment can use internal production control and when Article 17 requires Annex III EU-type examination or Annex IV full quality assurance.
RED Notified Body Trigger Workflow: Article 17 evidence guide
Decide when the EU Radio Equipment Directive needs a notified body by mapping Article 3 requirements, OJEU-cited harmonised standards, Annex III EU-type examination, and Annex IV full quality assurance evidence.
RED penalties, fines, and enforcement actions
EU Radio Equipment Directive penalties guide covering Article 46, Member State penalty rules, recalls, withdrawals, formal non-compliance, and enforcement evidence.
RED radio modules FAQ: host product assessment
FAQ on how Directive 2014/53/EU treats RF modules and host products, including module evidence, final-product responsibility, Article 3 assessment, technical documentation, instructions, antennas, software, and DoC records.
RED software update impact for radio equipment
Assess when firmware, app, and software updates can affect EU Radio Equipment Directive conformity, technical documentation, DoC, standards, and notified-body evidence.
RED standards not cited in the OJEU: can you use them?
FAQ answer for Radio Equipment Directive products when a standard is useful but not OJEU-cited, including presumption of conformity, Article 17 route selection, and technical-file evidence.
RED vs Cyber Resilience Act for radio equipment
Compare EU RED cybersecurity and Cyber Resilience Act duties for connected radio equipment, including scope, dates, evidence, reporting, and conformity routes.
RED vs EMC Directive: which law applies to radio equipment?
Decide when EU radio equipment uses RED instead of the EMC Directive and how to place EMC tests, declarations, fixed installations, and technical evidence.
RED vs ETSI EN 303 645: what the IoT standard proves
Compare binding EU RED cybersecurity duties with ETSI EN 303 645 consumer IoT standard, current editions, EN 18031, evidence reuse, and CE conformity.
RED vs LVD: electrical safety for radio equipment
Decide when EU radio equipment uses RED safety requirements instead of the Low Voltage Directive, including voltage limits, chargers, evidence, and declarations.
RED vs Market Surveillance Regulation for radio equipment
Compare RED product-conformity duties with Regulation (EU) 2019/1020 for responsible operators, online offers, customs controls, authority requests, and corrective action.
RED vs UK PSTI for connected radio products
Compare EU RED with the UK PSTI consumer connectable product regime, including scope, exclusions, passwords, updates, vulnerability reporting, evidence, and dates.
When do RED cybersecurity requirements apply to connected radio equipment? | RED FAQ
RED FAQ explaining when Article 3(3)(d), (e), and (f) cybersecurity requirements apply to internet-connected, childcare, toy, wearable, and payment-capable radio equipment.
Which receivers and transmitters are covered by RED? | Directive 2014/53/EU FAQ
RED scope FAQ for products that intentionally emit or receive radio waves for radio communication or radiodetermination, including receiver-only products, transmitters, accessory-dependent products, and common exclusions.
Wi-Fi and Bluetooth Products Under the EU RED
FAQ for assessing Wi-Fi, Bluetooth, BLE and other short-range wireless products under the EU Radio Equipment Directive, including Article 3, CE, technical file, cybersecurity and notified-body triggers.