esc to close

Radio Compliance Preparation Guide

Wireless products need to meet the radio requirements of their target markets. Depending on the product, radio parameters, and market, compliance may be demonstrated through test evidence, technical documentation, a manufacturer declaration, and/or a certification or authorization procedure. This guide explains how to prepare samples, documentation, and test configurations for an efficient radio compliance project.

Preparing your product for radio compliance testing? We help define the project scope and advise on sample preparation, then carry out the measurements and provide the report. → Radio testing services

TL;DR – Quick Summary

  • Radio compliance testing provides evidence that a wireless device meets applicable requirements for spectrum use and emissions, but it is only one part of market-specific compliance.

  • Key regulatory frameworks such as the EU RED, FCC rules, ISED requirements, and Japan's Radio Act define technical and conformity requirements. The required route depends on the product and target market.

  • Proper preparation of test samples, firmware, and documentation helps avoid delays and test failures.

  • Different technologies such as Bluetooth, Wi-Fi, and cellular have product- and region-specific requirements.

  • A structured checklist and clear testing workflow help coordinate testing, documentation, and any subsequent declaration, certification, or authorization steps.

What is RF Compliance Testing?

Radio Frequency (RF) compliance testing evaluates whether a wireless device meets the technical requirements that apply to its spectrum use and emissions. The required evidence and conformity procedure depend on the product, operating bands, power, intended use, and target market.


RF testing can help manufacturers:

  • Generate evidence for the applicable conformity or authorization procedure

  • Demonstrate efficient use of assigned frequency bands

  • Assess and reduce the risk of harmful interference


Regulatory frameworks vary by region:

RF compliance helps protect the integrity of the radio spectrum and supports reliable operation where multiple wireless technologies coexist.

Why Does Preparation Matter?

Radio compliance testing is not a plug-and-play process. Most products require specific configurations, activated test modes, and technical documentation that go beyond regular operation. Without these preparations, delays and re-tests are likely.


Typical challenges:

  • Missing configuration modes for transmit and receive operation (TX/RX)

  • Embedded SIMs without test access

  • Region-specific rules not considered in design

  • Firmware limitations or untested software paths

  • Incompatible accessories or control interfaces

Preparation can also differ depending on the technology involved:

Bluetooth modules, Wi-Fi chipsets, cellular modems, or proprietary RF systems each require specific test setups and documentation. The following overview highlights typical wireless technologies and use cases, each with their own regional compliance challenges.

Supported Technologies

We support radio compliance testing for a broad range of wireless technologies commonly used in consumer, industrial, and IoT applications.

Technology Typical Applications
Bluetooth Audio devices, wearables, smart home
Wi-Fi Routers, smartphones, IoT devices
Cellular (2G–5G) Smartphones, modules, M2M, eCall
UWB Indoor positioning, access systems
Zigbee / Thread Home automation, building control
Broadcast-related testing Broadcast receivers and related equipment
Custom RF Proprietary protocols, GNSS, RFID

The overview below shows typical regulatory examples for selected technologies and regions.

Technology Typical Applications
Supported Technologies
Bluetooth Audio devices, wearables, smart home
Wi-Fi Routers, smartphones, IoT devices
Cellular (2G–5G) Smartphones, modules, M2M, eCall
UWB Indoor positioning, access systems
Zigbee / Thread Home automation, building control
Broadcast-related testing Broadcast receivers and related equipment
Custom RF Proprietary protocols, GNSS, RFID

The overview below shows typical regulatory examples for selected technologies and regions.

Typical Requirements by Technology and Region

The examples below support early project planning. The applicable requirements depend on the product, operating band, power, intended use, and target market; confirm the current standards and conformity route for each project.

Technology EU (examples) USA (examples) Canada (examples) What Determines the Route
Bluetooth EN 300 3281 Part 15.2472 RSS-247 + RSS-Gen3 Radio mode, band, output power, and RF exposure configuration4
Wi-Fi (2.4/5 GHz) EN 300 328 / EN 301 8931 Part 15.247 / 15.4072 RSS-247 + RSS-Gen3 Band, channel set, device role, and DFS where applicable5
Cellular (2G–5G) EN 301 511 / EN 301 908 series1 Parts 22/24/272 RSS-132/133/139/199 + RSS-Gen3 Radio technology, bands, carrier configuration, RF exposure, and authorization route4
UWB EN 302 065 series1 Part 15 Subpart F2 RSS-220 + RSS-Gen3 Application class, operating band, power limits, and installation or use case6
Zigbee / Thread EN 300 328 for 2.4 GHz applications1 Part 15.2472 RSS-247 + RSS-Gen3 Operating band, modulation, output power, and application
Custom RF / ISM Depends on band and application Depends on band and equipment class Applicable RSS + RSS-Gen3 Band, use case, radio parameters, and target markets (early review recommended)
Technology Typical Examples and Decision Factors
Bluetooth EU: EN 300 3281
USA: Part 15.2472
Canada: RSS-247 + RSS-Gen3
Depends on: radio mode, band, output power, and RF exposure configuration4
Wi-Fi (2.4/5 GHz) EU: EN 300 328 / EN 301 8931
USA: Part 15.247 / 15.4072
Canada: RSS-247 + RSS-Gen3
Depends on: band, channel set, device role, and DFS where applicable5
Cellular (2G–5G) EU: EN 301 511 / EN 301 908 series1
USA: Parts 22/24/272
Canada: RSS-132/133/139/199 + RSS-Gen3
Depends on: radio technology, bands, carrier configuration, RF exposure, and authorization route4
UWB EU: EN 302 065 series1
USA: Part 15 Subpart F2
Canada: RSS-220 + RSS-Gen3
Depends on: application class, operating band, power limits, and installation or use case6
Zigbee / Thread EU: EN 300 328 for 2.4 GHz applications1
USA: Part 15.2472
Canada: RSS-247 + RSS-Gen3
Depends on: operating band, modulation, output power, and application
Custom RF / ISM EU: depends on band and application
USA: depends on band and equipment class
Canada: applicable RSS + RSS-Gen3
Depends on: band, use case, radio parameters, and target markets (early review recommended)

Notes on Regional Requirements:

1 Harmonised standards referenced in the EU Official Journal can provide a presumption of conformity with the RED requirements they cover. Confirm the applicable edition, scope, restrictions, and transition dates.

2 FCC references are typical examples. The equipment class, operating band, and applicable authorization procedure determine the complete route.

3 In Canada, RSS-Gen is used within its scope together with the applicable technology-specific RSS. The Category I or Category II classification affects certification and laboratory requirements.

4 RF exposure evaluation may involve SAR or maximum permissible exposure (MPE), depending on frequency, power, distance, simultaneous transmission, and available exemptions.

5 DFS applies where the device operates on radar-protected 5 GHz channels under the rules of the target market; device role and operating modes also matter.

6 UWB requirements depend on the application category, operating band, power limits, and installation or use case.

Japan (MIC): The applicable technical requirements depend on the device category and operating band under the Radio Act and its ministerial ordinances. See the Japan (MIC) requirements overview.

Pre-Compliance Testing

Reducing Risk Before Formal Compliance Testing

Pre-compliance testing allows you to evaluate the radio performance of your device early in the development process. It can identify technical issues before formal compliance testing, reducing avoidable rework, delays, and cost.

When is pre-compliance testing useful?

  • You’re working with a new chipset or custom RF design

  • You’re unsure about the regulatory behavior of your device

  • You need to optimize antenna layout, firmware, or RF output settings

  • You want to test performance under specific conditions (e.g., low voltage, temperature)

What’s included?

  • Conducted and/or radiated emission measurements

  • Key parameter evaluation (e.g., output power, bandwidth, spurious emissions)

  • Comparison with applicable limits (e.g., ETSI EN 300 328, FCC Part 15)

  • Technical guidance from lab engineers, where applicable

Pre-compliance testing is optional, but it can reduce the risk of delays during formal testing and subsequent conformity or authorization steps.

You can learn more about our pre-compliance services here.

Radio Testing Preparation Checklist

The exact preparation requirements depend on the product, technology, and agreed test plan. Confirm the required samples, accessories, software, and documents with the laboratory before your scheduled test date.

Category Requirement Check
Documentation
Project Scope Target markets, radio technologies and operating bands, product variants, intended use, and antenna configuration, as requested for the project
Forms Completed application forms requested for the applicable technology and project scope
Test Instructions Clear, step-by-step instructions to configure the device under test (DUT), including screenshots or photos
User Manual The user manual or software guide for test mode activation1
Hardware
Radiated Sample Sample with integrated or detachable antennas for radiated tests (if applicable)
Conducted Sample A modified sample may be required for direct connection (e.g., 50 Ω SMA or U.FL connector)
EMC & Safety Sample A production-representative sample with all intended functions enabled, where required for EMC or safety tests
Power Supply Power accessories requested for the test plan, which may include a battery eliminator2, chargers, and spare batteries
Software & Configuration
Test Modes Depending on the technology and test plan, access may be needed to the following settings:
– Channel selection
– Output power configuration (e.g., max/min)
– Modulation and/or bandwidth control
– Data rate selection
– Continuous Wave (CW) mode
– Receive-only mode (disables transmissions)
– Frequency hopping: enabled/disabled (if applicable)
Cellular Access Where applicable, access to a test SIM profile or a suitable eUICC/UICC test configuration
Support Equipment
Laptop If requested, a laptop with the required drivers and test software pre-installed
Cabling Required data and power cables in the lengths agreed with the laboratory3
Converters Any requested cable converters (e.g., USB to serial) with working drivers
Receiver Testing Visual or digital indicator of packet reception (e.g., LED or frame/packet error rate [FER/PER]); companion device if required4

Footnotes:

1 A user manual or software guide helps avoid delays during configuration and setup.

2 A battery eliminator may be requested for voltage variation testing or longer test cycles.

3 Long cables may be needed for climatic testing so that the DUT can remain inside the chamber during configuration; confirm the required lengths with the laboratory.

4 For proprietary receiver technologies (e.g., IEEE 802.15.4), a matching transmitter sample (companion device) may be required.

Category Requirement Check
Documentation
Project Scope Target markets, radio technologies and operating bands, product variants, intended use, and antenna configuration, as requested for the project
Forms Completed application forms requested for the applicable technology and project scope
Test Instructions Clear, step-by-step instructions to configure the device under test (DUT), including screenshots or photos
User Manual The user manual or software guide for test mode activation1
Hardware
Radiated Sample Sample with integrated or detachable antennas for radiated tests (if applicable)
Conducted Sample A modified sample may be required for direct connection (e.g., 50 Ω SMA or U.FL connector)
EMC & Safety Sample A production-representative sample with all intended functions enabled, where required for EMC or safety tests
Power Supply Power accessories requested for the test plan, which may include a battery eliminator2, chargers, and spare batteries
Software & Configuration
Test Modes Depending on the technology and test plan, access may be needed to the following settings:
– Channel selection
– Output power configuration (e.g., max/min)
– Modulation and/or bandwidth control
– Data rate selection
– Continuous Wave (CW) mode
– Receive-only mode (disables transmissions)
– Frequency hopping: enabled/disabled (if applicable)
Cellular Access Where applicable, access to a test SIM profile or a suitable eUICC/UICC test configuration
Support Equipment
Laptop If requested, a laptop with the required drivers and test software pre-installed
Cabling Required data and power cables in the lengths agreed with the laboratory3
Converters Any requested cable converters (e.g., USB to serial) with working drivers
Receiver Testing Visual or digital indicator of packet reception (e.g., LED or frame/packet error rate [FER/PER]); companion device if required4

Footnotes:

1 A user manual or software guide helps avoid delays during configuration and setup.

2 A battery eliminator may be requested for voltage variation testing or longer test cycles.

3 Long cables may be needed for climatic testing so that the DUT can remain inside the chamber during configuration; confirm the required lengths with the laboratory.

4 For proprietary receiver technologies (e.g., IEEE 802.15.4), a matching transmitter sample (companion device) may be required.

Radio Testing Workflow

Once your documentation and test samples have been submitted, the testing process follows a defined sequence. This helps ensure traceability, transparency, and efficient communication throughout your project.

01
Test slot confirmed
Your assigned project manager confirms the agreed test schedule and advises on next steps.
02
Sample & documentation check
We verify that the application forms, test instructions, and hardware are complete and ready for testing.
03
Initial project review
Engineers review the setup and clarify open points before testing. Minor issues are often resolved at this stage.
04
Radio compliance testing
Testing is performed as agreed using the applicable standards and test methods.
05
Internal technical review
The test data is reviewed for completeness, accuracy, and conformance to requirements.
06
Test result discussion
Your project manager reviews the results with you. Retesting may be required if issues are found.
07
Final report issued
A formal test report is issued after the measurements and technical review are complete. The reporting schedule depends on the agreed project scope.
08
Project Closure
Any agreed sample return is arranged before the project is closed. The test report can support the next conformity or authorization steps.

FAQ – Practical Questions

Can I send a regular production sample for testing?

It depends on the test scope. A production-representative sample is often suitable for EMC or safety testing, while conducted RF testing may require antenna connectors, modified firmware, or another prepared sample. Confirm the sample configuration with the laboratory before shipment.

Do I need to provide a test SIM for cellular devices?

A test SIM or suitable eSIM/eUICC configuration may be required for cellular testing. The device may also need to be unlocked or otherwise configured for the agreed test network. Confirm the required setup with the laboratory before shipment.

What if my device has no external interface for test mode control?

The laboratory needs a reliable way to activate and control the test modes required by the agreed test plan. If no external interface is available, coordinate an alternative such as pre-configured software, serial access, or documented hardware controls before shipment.

Which documents should I include when submitting my device?

You should provide all relevant materials required to set up and test the device effectively. This includes completed application forms, detailed configuration instructions (with screenshots, if possible), and the user manual or software guide for test mode activation. PDF format is acceptable as long as the content is complete and clearly structured.

What happens if my sample fails during testing?

Your project manager will contact you to discuss the result. A re-test can be scheduled after technical adjustments or with an updated sample.

Need Help?

For any technical questions regarding your test project, get in touch with us. Our team will connect you with the appropriate project lead.

Further Reading & Official Resources

Regulatory Portals

This is a curated selection of key sources. For complete and current regulatory documentation, refer to the official portals of the relevant authorities. The visible references on this page were reviewed on October 15, 2026.

ILAC-MRA DAkkS-01 ILAC-MRA DAkkS-01