Chapter 1 – Introduction to RF & EMC Pre-Compliance Testing

Developing a wireless product involves far more than integrating a radio module and verifying that the device functions as intended. Before a product can be placed on the market in regions such as Europe, the United States or Canada, it must demonstrate compliance with a wide range of regulatory requirements covering radio performance, electromagnetic compatibility (EMC), electrical safety and, where applicable, RF exposure.

Many manufacturers perform regulatory testing only once the product design has been finalized. While this approach may appear to reduce development costs, it often results in expensive redesigns, additional laboratory testing and significant project delays when compliance issues are discovered during formal certification.

Pre-compliance testing offers an opportunity to identify potential problems before entering the official certification process. Rather than serving as a regulatory requirement, it is an engineering tool that allows development teams to evaluate critical aspects of product performance under conditions that closely resemble those used during accredited compliance testing.

Unlike formal certification testing, pre-compliance testing is flexible. Manufacturers can choose which test cases to perform based on their product, development stage, available budget and technical risks. The goal is not to prove regulatory compliance but to identify issues while design modifications can still be implemented quickly and at relatively low cost.

What Is RF & EMC Pre-Compliance Testing?

Pre-compliance testing is a series of engineering evaluations performed before official certification testing.

The objective is to determine whether a product is likely to comply with applicable regulatory requirements and to identify potential failures before submitting the product to an accredited laboratory.

These evaluations are typically performed using the same or similar measurement methods defined in the applicable standards, although the laboratory performing the work does not issue an official compliance report.

Depending on the product, pre-compliance testing may include:

• RF transmitter measurements
• RF receiver performance
• EMC emissions
• EMC immunity
• Antenna evaluation
• RF exposure measurements
• Product-specific regulatory tests

The scope is determined by the technologies integrated into the product and the regulations that apply in the intended target markets.

Why Pre-Compliance Testing Is Different from Certification Testing

One of the most common misconceptions is that pre-compliance testing is simply a “smaller certification test.”

In reality, the purpose is fundamentally different.

Official certification testing answers the question:

Does the product comply with all applicable regulatory requirements?

Pre-compliance testing answers a different question:

Which technical risks should be addressed before formal certification begins?

This distinction is important.

A manufacturer may intentionally test only a small number of critical RF or EMC test cases during pre-compliance, while leaving the remaining tests for the official certification phase.

For example, a development team may focus initially on transmitter output power, spurious emissions and radiated emissions because failures in these areas often require hardware modifications. Other test cases may be postponed until the design has matured further.

Pre-Compliance Is a Technical Decision, Not a Regulatory Requirement

Neither the Radio Equipment Directive (RED), the FCC Rules nor Innovation, Science and Economic Development Canada (ISED) require manufacturers to perform pre-compliance testing.

Products may be submitted directly for official certification.

However, most experienced manufacturers include at least one pre-compliance phase because it provides valuable engineering feedback before formal testing begins.

The decision regarding which tests to perform should therefore be based on technical risk rather than on regulatory obligation.

For example:

• Is this the first hardware revision?
• Is the antenna newly designed?
• Has the PCB layout changed?
• Is a new RF module being integrated?
• Have switching power supplies been added?
• Has the enclosure changed significantly?
• Has shielding been modified?

The greater the design risk, the more valuable targeted pre-compliance testing becomes.

The Objective of This Guide

Many articles explain why pre-compliance testing is useful.

Far fewer explain what manufacturers should actually test.

This guide focuses on that practical question.

Rather than discussing compliance in general terms, it examines the individual RF and EMC test cases commonly performed during product development and explains:

• What each test evaluates
• Why the test is important
• Which design problems it typically reveals
• When the test should be performed
• Whether the test is recommended during pre-compliance
• Which types of products benefit most from the test

The guide considers regulatory requirements commonly applicable in:

• European Union (RED)
• United States (FCC)
• Canada (ISED)

Although individual standards differ depending on the radio technology, many engineering principles remain identical across all three markets.

A Practical Guide for Product Developers

This guide is intended for:

• Product developers
• RF engineers
• EMC engineers
• Hardware designers
• Compliance engineers
• Certification managers
• Project managers
• Manufacturers preparing products for global markets

It assumes that the reader already understands the basics of product development and wants practical guidance on selecting the most valuable RF and EMC test cases before entering formal compliance testing.

Rather than recommending that every available test be performed, this guide explains how to prioritize testing based on technical risk, product maturity and the likelihood that a particular failure would require design changes.

By understanding the purpose of each individual test, manufacturers can develop a pre-compliance strategy that provides meaningful engineering information while making efficient use of laboratory time and development resources.

Chapter 2 – When Should RF & EMC Pre-Compliance Testing Be Performed?

One of the most common misconceptions about pre-compliance testing is that it should be performed immediately before formal certification. In reality, waiting until the product is considered “finished” often limits the value of pre-testing, because significant design changes become increasingly expensive and time-consuming as development progresses.

The primary purpose of pre-compliance testing is to support engineering decisions while design changes are still practical. The earlier potential compliance issues are identified, the easier they can usually be corrected without affecting the overall project schedule.

However, testing too early can also produce misleading results. A prototype that does not yet represent the final hardware or firmware may fail for reasons that disappear later in development, leading to unnecessary investigations and repeated testing.

For this reason, selecting the right moment for pre-compliance testing is just as important as selecting the right test cases.

There Is No Single “Correct” Time

Neither the Radio Equipment Directive (RED), FCC regulations nor ISED requirements specify when manufacturers should perform pre-compliance testing.

The timing depends entirely on the maturity of the product and the objectives of the development team.

In practice, manufacturers often perform multiple rounds of pre-compliance testing during product development, with each phase serving a different purpose.

For example:

• Early engineering evaluation
• Hardware validation
• Design verification
• Final risk assessment before certification

Each phase answers different technical questions.

Early Development Stage

During the first hardware revisions, engineers are primarily interested in understanding how the radio and electronic design behave.

Typical objectives include:

• Evaluating antenna performance
• Measuring transmitter output power
• Identifying obvious spurious emissions
• Checking basic EMC behaviour
• Comparing different hardware revisions

At this stage, the product is expected to evolve significantly.

Failures are not necessarily considered problems—they provide valuable feedback that helps engineers improve the design before it becomes fixed.

Prototype Validation

Once the hardware architecture has stabilized, manufacturers typically enter a more structured validation phase.

This is often the most valuable time for RF and EMC pre-compliance testing.

At this stage:

• PCB routing is largely complete.
• The antenna design is close to final.
• Major components have been selected.
• Firmware is approaching production maturity.
• Mechanical design is mostly finalized.

Because the product now closely resembles the intended production version, test results become far more representative of the final certification outcome.

Most significant hardware-related compliance risks can still be corrected without redesigning the entire product.

Before Design Freeze

Many experienced manufacturers schedule a comprehensive pre-compliance campaign immediately before the design freeze.

The objective is to answer a simple question:

Is there any technical issue that could prevent successful certification?

Typical concerns include:

• Excessive transmitter power
• Spurious emissions
• Radiated emissions
• EMC failures
• Antenna performance
• RF exposure concerns

Discovering these issues before tooling, production preparation or mass manufacturing begins can significantly reduce project risk.

Before Official Certification

Some manufacturers perform a final verification shortly before submitting products to an accredited laboratory.

This is particularly common when:

• Firmware has recently changed.
• Components have been substituted.
• PCB revisions have been introduced.
• Manufacturing processes have changed.
• Shielding has been modified.
• Production tolerances need verification.

The purpose is not to repeat every regulatory test, but to confirm that no unexpected changes have introduced new compliance risks.

When Pre-Compliance Testing May Be Too Early

Although early testing can provide valuable engineering information, certain measurements may not represent the final product if critical design elements are still changing.

Examples include:

• Temporary antennas
• Prototype enclosures
• Unoptimized firmware
• Engineering sample power supplies
• Incomplete shielding
• Debug hardware

Results obtained under these conditions should be interpreted carefully.

Measurements are often useful for engineering comparison but should not be used to predict final certification performance.

When Pre-Compliance Testing May Be Too Late

Waiting until the product is fully completed may reduce the engineering value of pre-testing.

For example, failures discovered after:

• PCB production,
• injection mould tooling,
• regulatory documentation,
• pilot production,

may require expensive redesigns and additional validation work.

Although pre-compliance testing can still identify problems at this stage, implementing corrective actions becomes considerably more difficult.

Product Changes That Should Trigger Additional Pre-Testing

Even after successful pre-compliance testing, certain design modifications may justify repeating selected tests.

Examples include:

RF Changes

• New antenna
• Different RF module
• Modified matching network
• New RF shield
• Power amplifier changes
• Firmware affecting radio performance

EMC Changes

• New switching regulator
• Different clock frequency
• PCB layout modifications
• Cable changes
• Connector changes
• Grounding modifications
• Mechanical housing changes

These modifications can significantly affect compliance performance even when the overall product functionality remains unchanged.

Align Pre-Testing with Technical Risk

The timing of pre-compliance testing should always reflect the technical risks associated with the product.

For example:

A completely new wireless product using a custom RF design will usually benefit from multiple rounds of RF pre-testing throughout development.

By contrast, a product integrating an already certified radio module without changes to the RF design may require a stronger focus on EMC, integration effects and host product performance.

The testing strategy should therefore be driven by engineering risk rather than by a fixed schedule.

Practical Recommendations

Although every project is different, the following approach is commonly used:

Development Stage	Typical Objective
Early prototype	Identify major RF and EMC design issues
Hardware validation	Verify design improvements and compare revisions
Before design freeze	Evaluate the highest-risk regulatory test cases
Before certification	Confirm readiness for formal testing
After major design changes	Re-evaluate affected RF or EMC test cases

This staged approach allows manufacturers to address technical issues progressively instead of discovering them all during certification.

Key Takeaways

There is no universally correct moment to perform RF and EMC pre-compliance testing. The optimal timing depends on the maturity of the product, the development objectives and the technical risks associated with the design.

Rather than treating pre-compliance as a single event immediately before certification, experienced manufacturers often integrate several targeted pre-testing phases throughout product development. This approach allows engineering teams to identify compliance risks early, validate design improvements and confirm readiness before entering formal regulatory testing.

In the following chapters, this guide examines the individual RF and EMC test cases commonly performed during pre-compliance testing and explains what each test evaluates, why it matters and when it should be included in a pre-test plan.

Chapter 3 – Building an RF & EMC Pre-Compliance Test Plan – Where Should You Start?

One of the biggest mistakes manufacturers make when planning pre-compliance testing is trying to perform every possible regulatory test. While this approach may seem thorough, it is rarely the most efficient use of engineering time or laboratory resources.

Modern wireless products may be subject to dozens of RF and EMC test cases depending on the applicable regulations, radio technologies and target markets. Attempting to perform every available test during an early development phase is often unnecessary and may even divert attention from the technical issues that present the greatest certification risk.

An effective pre-compliance strategy focuses on answering a much more practical question:

Which tests provide the greatest engineering value at the current stage of product development?

The answer depends on the maturity of the design, the technologies implemented in the product and the likelihood that a particular failure would require hardware, firmware or mechanical changes.

The Purpose of a Pre-Test Plan

A pre-compliance test plan should not simply reproduce the official certification test schedule.

Instead, it should prioritize those test cases that are most likely to:

• identify fundamental design issues;
• reveal integration problems;
• uncover RF performance limitations;
• detect EMC weaknesses;
• require hardware redesign if they fail;
• influence later certification results.

In other words, the goal is not to maximize the number of tests—it is to maximize the engineering information obtained from the available laboratory time.

Start with the Highest Technical Risks

Not every regulatory test carries the same engineering significance.

Some failures can usually be corrected through firmware updates or configuration changes, while others may require redesigning the RF section, modifying the PCB layout or changing the antenna.

For this reason, pre-compliance testing should generally begin with the tests that have the greatest potential to influence the product design.

Typical high-risk areas include:

RF

• Transmitter output power
• Band edge emissions
• Spurious emissions
• Antenna performance

EMC

• Radiated emissions
• Conducted emissions
• Electrostatic discharge (ESD)

These test areas frequently reveal issues that are expensive to correct late in the development process.

Do Not Organize the Test Plan by Standards

Many manufacturers begin by listing all applicable standards:

• EN 300 328
• EN 301 489-17
• FCC Part 15.247
• RSS-247
• CISPR 32

Although this approach is useful for official certification planning, it is less effective for pre-compliance.

During product development, engineers are generally interested in technical questions rather than regulatory documents.

For example:

• Is the transmitter operating within the intended power range?
• Does the antenna generate excessive emissions near the band edge?
• Does the product produce unexpected harmonics?
• Is the switching power supply creating excessive EMC emissions?
• Does ESD cause the product to reset?

A good pre-test plan therefore groups testing around engineering objectives rather than individual standards.

Think in Terms of Engineering Questions

Instead of asking:

Which standard applies?

Ask:

What do I want to learn about my product?

For example:

RF Performance

• Is the transmitter performing correctly?
• Is the antenna working efficiently?
• Are emissions properly controlled?
• Is the radio operating within the permitted spectrum?

EMC Performance

• What is generating the highest emissions?
• Which cables radiate most strongly?
• Does the enclosure influence emissions?
• Is the PCB layout creating EMC problems?

Product Robustness

• Does ESD affect product operation?
• Does RF immunity cause communication failures?
• Does the device recover automatically after disturbances?

This engineering-based approach often provides far more useful information than simply following the certification test order.

Prioritize Tests That May Require Hardware Changes

One of the most important principles of pre-compliance testing is to identify issues that become expensive to correct later.

As a general rule, tests that may lead to hardware modifications should receive higher priority than tests that primarily result in software adjustments.

For example:

Hardware-related failures

• Antenna redesign
• PCB layout modifications
• Shielding changes
• Matching network optimization
• Filter redesign
• Grounding improvements

These changes can significantly affect project schedules.

Software-related adjustments

• Transmitter power settings
• Channel configuration
• Timing parameters
• Duty cycle adjustments
• Country-specific operating modes

Although firmware changes may still require validation, they are generally less disruptive than hardware redesigns.

This distinction helps determine which tests should be performed earlier in the development process.

Consider the Product Type

No single pre-test plan is suitable for every wireless product.

The testing priorities depend heavily on the technologies being used.

For example:

Bluetooth Device

Typical priorities may include:

• Output power
• Occupied bandwidth
• Band edge emissions
• Spurious emissions
• Radiated emissions

Wi-Fi Product

Additional attention may be required for:

• Multiple operating modes
• DFS (where applicable)
• Wideband emissions
• High transmitter power
• EMC emissions from high-speed processors

Cellular Product

Additional considerations often include:

• Multiple frequency bands
• Carrier aggregation
• RF exposure
• Harmonics
• Simultaneous transmitters

Low-Power IoT Device

The focus may shift toward:

• Narrowband transmitter performance
• Receiver sensitivity
• Battery operation
• Long-duration EMC immunity
• Low-frequency emissions

Understanding the intended application helps prioritize the most valuable test cases.

Budget and Laboratory Time

Laboratory time is almost always limited.

For this reason, manufacturers should distinguish between:

Essential Tests

Tests that provide the highest engineering value and should almost always be included.

Recommended Tests

Tests that are useful once the most critical areas have been evaluated.

Optional Tests

Tests that may be postponed until later development phases or official certification.

This prioritization allows manufacturers to expand testing gradually as the product matures.

A Risk-Based Testing Strategy

Rather than asking:

How many tests should we perform?

A more useful question is:

Which failure would be the most expensive to discover during certification?

The answer to this question often determines which test should be performed first.

For example:

• If redesigning the antenna would delay the project by three months, antenna-related RF tests should receive high priority.
• If changing PCB shielding would require a new enclosure design, EMC emission testing should begin early.
• If firmware updates can easily resolve a particular issue, those tests may be scheduled later.

Risk-based prioritization ensures that laboratory resources are focused where they provide the greatest benefit.

What Comes Next?

The remainder of this guide examines the individual RF and EMC test cases commonly used during pre-compliance testing.

For each test, the following questions will be answered:

• What does the test measure?
• Why is the test performed?
• Which design problems does it typically reveal?
• When should it be included in a pre-compliance campaign?
• Which product types benefit most from the test?
• How important is the test when laboratory time is limited?

By understanding the purpose of each individual test case, manufacturers can develop a pre-compliance strategy that is based on engineering priorities rather than simply following the order of official certification standards.

Key Takeaways

An effective pre-compliance test plan is not a shortened version of the certification test program. Instead, it is a structured engineering strategy designed to identify the technical issues that present the greatest risk to successful certification.

By prioritizing test cases according to technical risk, product maturity and the likelihood of design changes, manufacturers can make better use of laboratory time, reduce development uncertainty and enter formal certification with greater confidence.

Chapter 4 – RF Transmitter Testing – Which Test Cases Should You Prioritize During Pre-Compliance?

For most wireless products, the transmitter is the component that receives the greatest regulatory attention. Whether a device uses Bluetooth®, Wi-Fi, Zigbee, LoRa®, cellular technology or another radio interface, the transmitter must operate within clearly defined technical limits to avoid causing harmful interference to other spectrum users.

Official certification requires manufacturers to demonstrate compliance with all applicable transmitter requirements defined in the relevant standards. During pre-compliance testing, however, the objective is different.

Rather than executing the complete certification test programme, manufacturers should focus on the transmitter measurements that provide the greatest engineering value. The most useful pre-compliance tests are those capable of revealing design problems while hardware, antenna design and firmware can still be modified.

This chapter introduces the most important RF transmitter test cases and explains which of them should normally receive the highest priority during pre-compliance testing.

Understanding RF Transmitter Tests

Every RF transmitter test evaluates a different aspect of radio performance.

Some measurements verify that the transmitter operates within regulatory limits.

Others evaluate spectrum efficiency or identify unwanted emissions that may interfere with neighbouring radio services.

It is therefore important to understand that no single RF measurement determines whether a transmitter is compliant. Instead, each test answers a different engineering question.

For example:

• Is the transmitter generating the intended output power?
• Is the transmitted signal occupying the correct bandwidth?
• Are emissions sufficiently suppressed outside the operating channel?
• Is the transmitter producing excessive harmonics?
• Does the antenna affect regulatory compliance?

Each of these questions should be considered independently when planning pre-compliance testing.

Which RF Tests Should Be Performed First?

Not every transmitter test has the same engineering importance.

Some failures can usually be corrected through software configuration, while others may require redesigning the RF hardware.

As a general rule, manufacturers should prioritize tests that are most likely to require hardware modifications if they fail.

For many wireless products, the following order represents a practical starting point:

Priority	Test Case	Typical Engineering Impact
★★★★★	Maximum Transmitter Output Power	RF design, firmware, antenna
★★★★★	Band Edge Emissions	RF filters, antenna, matching network
★★★★★	Spurious Emissions	PCB layout, shielding, RF circuitry
★★★★☆	Occupied Channel Bandwidth	Firmware, modulation configuration
★★★★☆	Power Spectral Density	Modulation behaviour, transmitter settings
★★★☆☆	Frequency Stability	Oscillator performance, temperature behaviour
★★★☆☆	Duty Cycle (where applicable)	Firmware configuration

The exact priorities depend on the applicable radio technology and regulatory standard, but these measurements frequently provide the greatest insight during early development.

Test Case 1 – Maximum Transmitter Output Power

Purpose

Maximum transmitter output power verifies that the radio does not exceed the maximum power permitted by the applicable regulation.

The measurement determines the highest RF power delivered by the transmitter under specified operating conditions.

Depending on the technology and regulatory framework, measurements may be performed as conducted power, radiated power or Effective Isotropic Radiated Power (EIRP).

Why Is It Important?

Excessive transmitter power is one of the most common reasons for certification failures.

Even relatively small deviations can result in non-compliance with RED, FCC or ISED requirements.

Measuring output power early allows engineers to determine whether the transmitter operates within the intended design margins before further optimisation begins.

Typical Problems Revealed

This measurement frequently identifies:

• Incorrect transmitter gain settings
• Firmware configuration errors
• Excessive power amplifier gain
• Incorrect antenna gain assumptions
• Matching network problems
• Manufacturing tolerances
• RF calibration issues

Typical Corrective Actions

If output power exceeds the intended limits, corrective actions may include:

• Reducing transmitter power through firmware
• Adjusting RF calibration values
• Optimising the matching network
• Selecting a different antenna
• Redesigning the RF front end
• Adjusting power amplifier settings

Some solutions involve only software changes, while others require modifications to the RF hardware.

Recommended During Pre-Compliance?

★★★★★ Essential

For virtually every wireless product, output power should be one of the first RF measurements performed.

Test Case 2 – Occupied Channel Bandwidth (Occupied Bandwidth)

Purpose

Occupied Channel Bandwidth (OCB or OBW) measures the bandwidth containing the majority of the transmitted signal energy.

The measurement confirms that the transmitted signal occupies the expected portion of the radio spectrum.

Why Is It Important?

The occupied bandwidth reflects whether the transmitter is behaving as intended.

Unexpected bandwidth increases may indicate:

• Incorrect modulation parameters
• Firmware configuration issues
• Excessive transmitter distortion
• Oscillator problems
• RF hardware instability

Although occupied bandwidth failures are less likely to require major hardware redesign than spurious emissions, they often reveal important transmitter configuration problems.

Typical Problems Revealed

Common findings include:

• Incorrect modulation settings
• Firmware defects
• Unexpected spectral spreading
• Oscillator instability
• Digital signal processing issues

Typical Corrective Actions

Possible solutions include:

• Firmware updates
• Modulation parameter adjustments
• Baseband optimisation
• Oscillator improvements
• RF calibration

Recommended During Pre-Compliance?

★★★★☆ Highly Recommended

Occupied bandwidth is relatively quick to measure and provides valuable information regarding transmitter performance.

Test Case 3 – Band Edge Emissions

Purpose

Band Edge measurements verify that transmitter emissions decrease sufficiently near the regulatory frequency boundaries.

The objective is to ensure that emissions outside the authorised frequency band remain within the applicable limits.

Why Is It Important?

Band edge failures frequently require significant RF design changes.

Products that perform well within the operating channel may still exceed emission limits close to the band boundaries.

Because band edge performance depends on multiple aspects of the RF design, early evaluation is strongly recommended.

Typical Problems Revealed

Band edge testing often identifies:

• Poor RF filtering
• Antenna mismatch
• Matching network deficiencies
• Excessive transmitter bandwidth
• Power amplifier distortion
• Firmware configuration issues

Typical Corrective Actions

Potential solutions include:

• RF filter optimisation
• Matching network redesign
• Antenna optimisation
• Output power adjustment
• Firmware modifications
• PCB layout improvements

Recommended During Pre-Compliance?

★★★★★ Essential

Band edge measurements should almost always be included in RF pre-compliance testing because failures often require hardware modifications.

What Comes Next?

The three transmitter measurements described in this chapter are among the most valuable engineering tools available during RF pre-compliance testing.

They allow manufacturers to verify that the transmitter operates within its intended design limits before investigating more detailed regulatory requirements.

The following chapter continues with additional transmitter test cases that frequently determine certification success, including Spurious Emissions, Power Spectral Density, Frequency Stability and other transmitter measurements commonly required by RED, FCC and ISED.

Key Takeaways

Not every RF transmitter measurement has the same importance during product development. Maximum Output Power, Occupied Channel Bandwidth and Band Edge Emissions provide some of the earliest indications of whether the transmitter, antenna and RF design are functioning as intended.

By prioritising these measurements during pre-compliance testing, manufacturers can identify design issues while corrective actions remain practical and before entering formal certification testing.

Chapter 5 – RF Transmitter Testing (Part 2) – Spurious Emissions, Power Spectral Density, Frequency Stability and Other Critical Test Cases

The transmitter measurements introduced in the previous chapter represent only part of the RF evaluation performed during product development. Once output power, occupied bandwidth and band edge performance have been verified, manufacturers should continue with additional transmitter tests that frequently determine whether a product successfully passes formal certification.

Unlike the previous measurements, many of the test cases described in this chapter are intended to identify unwanted radio emissions generated by the transmitter. These emissions may occur inside or outside the operating frequency band and, if not properly controlled, can interfere with other radio services.

Although every applicable standard defines its own detailed measurement procedures and limits, the engineering objectives remain largely the same across RED, FCC and ISED requirements.

Test Case 4 – Spurious Emissions

Purpose

Spurious Emissions are unwanted radio emissions produced by a transmitter outside its necessary transmission bandwidth.

They are not part of the intended communication signal and generally provide no useful functionality.

Depending on the applicable standard, spurious emissions may be measured as:

• Conducted Spurious Emissions
• Radiated Spurious Emissions
• Out-of-Band Emissions (where separately defined)

The objective is to verify that unwanted emissions remain below the applicable regulatory limits.

Why Is This Test Important?

For many wireless products, spurious emissions represent one of the highest certification risks.

Unlike output power or occupied bandwidth, excessive spurious emissions often indicate fundamental RF design issues that cannot simply be corrected through software configuration.

Failures may require modifications to:

• RF circuitry
• PCB layout
• Shielding
• Matching network
• Filters
• Antenna design

For this reason, spurious emission testing should almost always be included in an RF pre-compliance programme.

Typical Problems Revealed

Spurious emission measurements frequently identify:

• Insufficient RF filtering
• Harmonics generated by the power amplifier
• Poor PCB layout
• Inadequate shielding
• RF leakage
• Poor grounding
• Antenna mismatch
• Clock-related emissions
• Coupling from digital circuitry

In many cases, several of these factors contribute simultaneously.

Typical Corrective Actions

Depending on the root cause, engineers may consider:

• Optimising RF filters
• Redesigning the matching network
• Improving PCB routing
• Adding or modifying RF shielding
• Improving grounding
• Adjusting antenna placement
• Reducing transmitter power
• Optimising firmware where appropriate

Hardware modifications are often required.

Recommended During Pre-Compliance?

★★★★★ Essential

If laboratory time is limited, spurious emission measurements should almost always be prioritised.

Test Case 5 – Power Spectral Density (PSD)

Purpose

Power Spectral Density (PSD) evaluates how transmitter power is distributed across the occupied bandwidth.

Rather than measuring total transmitter power, PSD determines the power contained within a defined measurement bandwidth.

Several wireless technologies include PSD limits to prevent excessive concentration of RF energy within a narrow frequency range.

Why Is This Test Important?

PSD provides valuable information about transmitter behaviour and modulation quality.

Unexpected PSD results may indicate:

• Incorrect modulation settings
• Firmware configuration issues
• Signal processing problems
• Excessive transmitter gain
• Spectral shaping errors

Although PSD failures are generally less likely to require major hardware redesign than spurious emissions, they often reveal important configuration issues before certification.

Typical Problems Revealed

Common findings include:

• Incorrect transmitter configuration
• Firmware defects
• Modulation parameter errors
• Digital signal processing issues
• Calibration errors

Typical Corrective Actions

Possible improvements include:

• Firmware updates
• Modulation optimisation
• Digital baseband adjustments
• RF calibration
• Transmitter parameter optimisation

Recommended During Pre-Compliance?

★★★★☆ Highly Recommended

PSD measurements provide valuable insight with relatively little additional laboratory time.

Test Case 6 – Frequency Stability

Purpose

Frequency Stability evaluates whether the transmitter remains within the permitted frequency tolerance under varying operating conditions.

Measurements are typically performed while changing:

• Temperature
• Supply voltage
• Operating conditions

The objective is to ensure that the transmitter continues operating on the intended frequency under all expected environmental conditions.

Why Is This Test Important?

A transmitter that drifts excessively may interfere with neighbouring channels or fail to meet regulatory requirements.

Frequency instability may also indicate underlying hardware quality issues.

Typical Problems Revealed

Frequency stability testing may identify:

• Oscillator instability
• Temperature sensitivity
• Power supply variation
• Crystal tolerance issues
• RF calibration problems

Typical Corrective Actions

Possible corrective actions include:

• Selecting a higher stability crystal
• Improving oscillator design
• Temperature compensation
• RF calibration improvements
• Power supply optimisation

Recommended During Pre-Compliance?

★★★☆☆ Recommended

Although failures are relatively uncommon in mature designs using qualified RF chipsets, frequency stability should still be verified before certification.

Test Case 7 – Duty Cycle (Where Applicable)

Purpose

Certain radio technologies impose duty cycle restrictions that limit how long a transmitter may occupy the radio channel.

The purpose of duty cycle measurements is to verify compliance with these operational limits.

This test is particularly relevant for some Short Range Device (SRD) applications operating in frequency bands where spectrum sharing relies on restricted transmission times.

Why Is This Test Important?

Duty cycle non-compliance is generally caused by software behaviour rather than RF hardware.

Nevertheless, identifying excessive transmission time early prevents unnecessary certification delays.

Typical Problems Revealed

Typical findings include:

• Incorrect firmware timing
• Excessive transmission duration
• Improper retry algorithms
• Incorrect sleep behaviour
• Protocol implementation issues

Typical Corrective Actions

Most issues can be resolved by:

• Firmware optimisation
• Protocol adjustments
• Timing changes
• Improved power management

Hardware modifications are rarely required.

Recommended During Pre-Compliance?

★★★☆☆ Recommended when applicable

Perform this test whenever regulatory duty cycle limits apply to the intended operating band.

Prioritising Transmitter Tests

When laboratory time is limited, manufacturers should focus first on those measurements that are most likely to require hardware redesign if problems are discovered.

A practical priority ranking is:

Priority	Test Case	Recommended
★★★★★	Maximum Output Power	Yes
★★★★★	Band Edge Emissions	Yes
★★★★★	Spurious Emissions	Yes
★★★★☆	Occupied Channel Bandwidth	Yes
★★★★☆	Power Spectral Density	Yes
★★★☆☆	Frequency Stability	Usually
★★★☆☆	Duty Cycle	When applicable

This order is not intended to replace the official certification programme. Instead, it reflects the engineering value of each measurement during product development.

By identifying failures that are likely to require hardware modifications as early as possible, manufacturers can significantly reduce technical risk before entering formal compliance testing.

Key Takeaways

Not all RF transmitter tests contribute equally during pre-compliance testing. Measurements such as Maximum Output Power, Band Edge Emissions and Spurious Emissions frequently reveal hardware-related issues that become expensive to correct late in development and should therefore receive the highest priority.

Other measurements, including Power Spectral Density, Frequency Stability and Duty Cycle, provide additional confidence that the transmitter is operating as intended and help identify configuration or environmental issues before formal certification.

Chapter 6 – RF Receiver Testing – Which Receiver Test Cases Should You Include During Pre-Compliance?

When engineers think about regulatory testing, they often focus almost exclusively on the transmitter. This is understandable, as transmitter measurements such as output power, spurious emissions and band edge performance frequently determine whether a product complies with regulatory limits.

However, many wireless standards also include receiver performance requirements. Although receiver tests rarely attract the same attention as transmitter measurements, they are essential for demonstrating that a wireless device can operate reliably in the presence of other radio signals and under realistic operating conditions.

From a pre-compliance perspective, receiver testing serves a different purpose than transmitter testing. While transmitter failures often require modifications to the RF hardware, many receiver-related issues are associated with antenna performance, receiver architecture, firmware behaviour or product integration.

For this reason, manufacturers should understand which receiver tests provide the greatest engineering value before entering formal certification.

Why Receiver Testing Matters

A receiver is expected to detect and correctly process weak radio signals while rejecting unwanted interference from other transmitters.

Poor receiver performance may not immediately prevent a product from functioning in a laboratory demonstration or during short-range testing. However, under real operating conditions it can result in:

• Reduced communication range
• Unstable wireless connections
• Increased packet loss
• Unexpected disconnects
• Poor coexistence with other wireless systems
• Increased retransmissions
• Higher power consumption

Many of these problems become visible long before certification if the appropriate receiver tests are included in a pre-compliance programme.

Should Receiver Tests Receive the Same Priority as Transmitter Tests?

In most development projects, the answer is no.

For many wireless products, transmitter measurements should generally be completed first because transmitter failures frequently require hardware redesign.

Receiver tests, on the other hand, often evaluate how well an already functioning receiver performs under challenging conditions.

This does not mean that receiver testing is less important.

Instead, it means that receiver testing is often more valuable once engineers have confidence that the transmitter and RF hardware are operating as intended.

A practical development sequence is therefore:

1. Verify transmitter performance.
2. Verify unwanted emissions.
3. Evaluate receiver performance.
4. Confirm EMC robustness.
5. Perform final certification.

Which Receiver Tests Are Commonly Performed?

The exact receiver test programme depends on the applicable technology and regulatory standard.

Typical receiver-related test cases include:

Priority	Test Case	Typical Engineering Impact
★★★★★	Receiver Sensitivity	Antenna, RF front-end, matching
★★★★☆	Adjacent Channel Selectivity	Receiver filtering
★★★★☆	Blocking Performance	RF front-end, filtering
★★★☆☆	Intermodulation Response	RF architecture
★★★☆☆	Receiver Spurious Response	Receiver design
★★☆☆☆	Co-channel Rejection	Protocol performance

Not every technology requires all of these tests, but they represent the most common receiver evaluations encountered during RF compliance testing.

Test Case 1 – Receiver Sensitivity

Purpose

Receiver sensitivity measures the minimum signal level that the receiver can correctly detect while maintaining the required communication performance.

In simple terms, it determines how weak a signal the product can still receive successfully.

Sensitivity directly influences communication range and overall wireless performance.

Why Is This Test Important?

Receiver sensitivity is often one of the first measurements engineers perform after transmitter verification.

Poor sensitivity does not necessarily prevent certification, but it often indicates underlying RF design problems that may also affect other receiver tests.

Early sensitivity measurements help determine whether the radio architecture is performing as expected before investigating more complex receiver behaviour.

Typical Problems Revealed

Sensitivity testing frequently identifies:

• Antenna mismatch
• Poor antenna efficiency
• Excessive RF losses
• Incorrect matching network
• Receiver gain issues
• PCB layout problems
• Shielding effects
• Connector losses

Typical Corrective Actions

Possible improvements include:

• Optimising the antenna
• Improving antenna placement
• Redesigning the matching network
• Reducing RF losses
• Improving PCB routing
• Reviewing RF shielding
• Improving receiver calibration

Recommended During Pre-Compliance?

★★★★★ Essential

Receiver sensitivity should normally be one of the first receiver tests included in any RF pre-compliance programme.

Test Case 2 – Adjacent Channel Selectivity

Purpose

Adjacent Channel Selectivity evaluates the receiver’s ability to receive the desired signal while a strong interfering signal is present on a neighbouring channel.

This simulates real-world environments where multiple wireless systems operate close together.

Why Is This Test Important?

Products that perform well in quiet laboratory environments may behave very differently in crowded RF environments.

Poor adjacent channel selectivity can lead to:

• Connection failures
• Reduced throughput
• Increased retransmissions
• Poor coexistence with nearby devices

Typical Problems Revealed

This test may identify:

• Insufficient receiver filtering
• Front-end overload
• RF architecture limitations
• Antenna coupling effects
• Poor channel isolation

Typical Corrective Actions

Possible improvements include:

• Better RF filtering
• Receiver front-end optimisation
• Matching network adjustments
• Antenna improvements
• RF architecture refinement

Recommended During Pre-Compliance?

★★★★☆ Highly Recommended

Especially for Bluetooth, Wi-Fi and other technologies operating in crowded spectrum, adjacent channel performance should be verified before certification.

Test Case 3 – Blocking Performance

Purpose

Blocking tests evaluate whether the receiver continues to operate correctly when exposed to strong unwanted signals outside the desired operating channel.

Unlike adjacent channel testing, blocking signals may be located significantly further away in frequency but still have the potential to degrade receiver performance.

Why Is This Test Important?

Blocking performance reflects the robustness of the receiver under realistic RF conditions.

Poor blocking behaviour may cause communication failures in environments containing multiple high-power transmitters.

Typical Problems Revealed

Blocking tests frequently reveal:

• Receiver front-end overload
• Poor filtering
• RF amplifier saturation
• Insufficient dynamic range
• PCB coupling effects

Typical Corrective Actions

Engineers may improve performance through:

• Front-end redesign
• Improved RF filtering
• Better shielding
• PCB optimisation
• Receiver architecture improvements

Recommended During Pre-Compliance?

★★★★☆ Highly Recommended

Blocking performance provides valuable engineering information for products expected to operate in challenging RF environments.

Key Takeaways

Unlike transmitter testing, receiver pre-compliance focuses less on regulatory emission limits and more on communication robustness under realistic operating conditions.

For most wireless products, Receiver Sensitivity, Adjacent Channel Selectivity and Blocking Performance provide the greatest engineering value during development. These measurements help engineers optimise antenna performance, receiver architecture and RF integration before entering formal certification, reducing the likelihood of communication problems in both laboratory testing and real-world deployments.

Chapter 7 – EMC Emissions Testing – Which EMC Measurements Should You Prioritise During Pre-Compliance?

For many manufacturers, EMC testing represents one of the greatest sources of uncertainty during product development. Unlike RF testing, where measurements focus primarily on the intentional transmitter, EMC emissions can originate from almost every electronic component inside the product.

A wireless product may fully comply with all applicable RF requirements while still failing EMC testing because of excessive emissions generated by switching power supplies, processors, displays, clocks or external cables.

This is precisely why EMC pre-compliance testing is so valuable.

Rather than waiting until formal certification identifies an emission problem, manufacturers can investigate the primary emission sources while the product design can still be modified efficiently.

This chapter explains which EMC emission tests should normally be prioritised during pre-compliance testing, what each test evaluates and which engineering problems they commonly reveal.

Understanding EMC Emissions

Every electronic circuit generates electromagnetic energy.

The objective of EMC emissions testing is not to eliminate these emissions completely, but to ensure they remain below the limits defined by the applicable standards.

For most commercial products, emissions are divided into two categories:

• Radiated Emissions
• Conducted Emissions

Although both measurements evaluate unwanted electromagnetic energy, they investigate different mechanisms by which interference leaves the product.

Understanding this distinction is essential when developing an effective pre-compliance strategy.

Which EMC Emission Tests Should Be Performed First?

Not every emission measurement provides the same engineering value.

Some failures can be corrected relatively easily through filtering or firmware adjustments.

Others may require redesigning the PCB, changing component placement or modifying the enclosure.

For most electronic products, the following priority is recommended:

Priority	Test Case	Typical Engineering Impact
★★★★★	Radiated Emissions	PCB layout, shielding, enclosure
★★★★★	Conducted Emissions	Power supply, filters, grounding
★★★★☆	Harmonic Analysis / Diagnostic Scans	Root cause identification
★★★☆☆	Cable Emission Investigation	Harness design, cable routing

The exact test programme depends on the product type, power supply configuration and applicable EMC standards, but Radiated and Conducted Emissions almost always provide the greatest engineering value.

Test Case 1 – Radiated Emissions

Purpose

Radiated Emissions testing measures the electromagnetic energy unintentionally emitted into free space by the product during normal operation.

These emissions may originate from:

• High-speed digital circuits
• Clock signals
• Switching power supplies
• RF leakage
• Display interfaces
• Poor PCB layout
• Connected cables

Measurements are typically performed over a defined frequency range using calibrated antennas in a controlled test environment.

Why Is This Test Important?

Radiated Emissions testing is often the single most valuable EMC pre-compliance measurement.

Unlike many other EMC tests, excessive radiated emissions frequently indicate design issues that cannot be corrected by minor adjustments.

Failures discovered during certification often require redesign of:

• PCB layout
• Shielding
• Component placement
• Cable routing
• Mechanical enclosure

Because these changes become increasingly expensive later in development, Radiated Emissions testing should usually be performed as early as practical.

Typical Problems Revealed

Radiated emission measurements commonly identify:

• Poor PCB layout
• Large current loops
• Inadequate grounding
• High-speed clock radiation
• Switching regulator noise
• Insufficient shielding
• Cable radiation
• Display interface emissions
• RF leakage

Very often, several emission mechanisms contribute simultaneously.

Typical Corrective Actions

Possible engineering improvements include:

• PCB layout optimisation
• Reducing loop areas
• Improved grounding
• Shield redesign
• Ferrite implementation
• Clock optimisation
• Cable routing improvements
• Enclosure modifications
• Filter optimisation

Some products require several design iterations before acceptable emission margins are achieved.

Recommended During Pre-Compliance?

★★★★★ Essential

Radiated Emissions should almost always be one of the first EMC tests performed during product development.

Test Case 2 – Conducted Emissions

Purpose

Conducted Emissions testing measures unwanted electromagnetic disturbances travelling along power lines or other connected conductors.

Rather than being radiated into free space, these disturbances leave the product through electrical connections.

Measurements are commonly performed using a Line Impedance Stabilisation Network (LISN) or other standardised measurement equipment.

Why Is This Test Important?

Many products that successfully pass radiated emission testing still fail conducted emissions because noise generated inside the product is coupled onto power cables.

Conducted emission failures frequently originate from:

• Switching power supplies
• DC/DC converters
• Motor controllers
• Digital electronics
• Inadequate filtering

Early identification allows engineers to optimise the power architecture before certification.

Typical Problems Revealed

Typical findings include:

• Switching regulator noise
• Power supply ripple
• Inadequate EMI filtering
• Poor grounding
• Cable coupling
• Converter harmonics

Typical Corrective Actions

Common improvements include:

• Additional EMI filters
• Ferrite components
• Power supply redesign
• Improved PCB grounding
• Layout optimisation
• Shield improvements

Recommended During Pre-Compliance?

★★★★★ Essential

For mains-powered equipment and many externally powered products, Conducted Emissions testing should always be included.

For battery-powered products without external power connections, this test may not be applicable depending on the applicable standard.

Test Case 3 – Diagnostic Emission Scans

Purpose

Diagnostic emission scans are not formal compliance tests.

Instead, they are engineering investigations used to identify the physical origin of unwanted emissions detected during radiated or conducted measurements.

Measurements may involve:

• Near-field probes
• Spectrum analysers
• Current probes
• Differential probes

The objective is to locate the components or PCB regions responsible for excessive emissions.

Why Is This Test Important?

A compliance measurement identifies that a product exceeds a limit.

A diagnostic scan explains why.

Without understanding the source of the emissions, corrective actions often become trial and error.

Diagnostic investigations therefore play a critical role during pre-compliance.

Typical Problems Revealed

Diagnostic scans frequently locate:

• Noisy DC/DC converters
• Oscillator leakage
• Clock harmonics
• Poor return current paths
• PCB resonances
• Shield leakage
• Cable coupling

Typical Corrective Actions

Once the dominant emission source has been identified, engineers can implement targeted improvements instead of modifying unrelated parts of the design.

This significantly reduces development time.

Recommended During Pre-Compliance?

★★★★☆ Highly Recommended

Whenever elevated emissions are detected, diagnostic scans should normally be performed before attempting design modifications.

Should Every Product Perform Conducted Emissions Testing?

Not necessarily.

The applicability of Conducted Emissions depends on both the product design and the relevant EMC standard.

For example:

• Products powered directly from the AC mains are typically subject to conducted emissions measurements.
• Products powered exclusively by internal batteries may not require this particular test.
• Equipment supplied through external DC power adapters should be evaluated based on the applicable product standard and the intended installation.

Manufacturers should therefore determine the applicable emission requirements before scheduling EMC pre-compliance testing.

Prioritising EMC Emission Tests

When laboratory time is limited, manufacturers should concentrate on the measurements most likely to identify hardware-related design issues.

A practical order is:

Priority	Test Case	Recommended
★★★★★	Radiated Emissions	Yes
★★★★★	Conducted Emissions (where applicable)	Yes
★★★★☆	Diagnostic Emission Investigation	Yes
★★★☆☆	Cable-specific investigations	As needed

This prioritisation focuses laboratory resources on the measurements most likely to influence product design before certification.

Key Takeaways

Radiated and Conducted Emissions are among the most valuable EMC measurements performed during product development because they frequently reveal design weaknesses that become expensive to correct late in a project.

Radiated Emissions primarily expose issues related to PCB layout, shielding, clock signals and cable radiation, while Conducted Emissions focus on disturbances coupled onto power connections. Diagnostic emission investigations complement both measurements by identifying the physical source of excessive emissions and enabling targeted engineering improvements before formal compliance testing begins.

Chapter 8 – EMC Immunity Testing – Which Immunity Tests Should You Include During Pre-Compliance?

Passing EMC emissions testing does not necessarily mean that a product is electromagnetically robust.

While emissions testing verifies that a product does not generate excessive electromagnetic disturbances, immunity testing evaluates the opposite question:

Can the product continue to operate correctly when exposed to electromagnetic disturbances generated by its environment?

Modern electronic products are expected to operate reliably in the presence of electrostatic discharge, radiated RF fields, electrical fast transients, surge events and other electromagnetic phenomena that occur during normal operation.

Official EMC testing verifies compliance with the applicable immunity requirements. During pre-compliance testing, however, the objective is to identify weaknesses in product robustness before certification and before the product reaches customers.

Unlike emissions testing, immunity failures do not necessarily indicate excessive electromagnetic energy leaving the product. Instead, they reveal weaknesses in the product’s ability to tolerate external disturbances.

Understanding EMC Immunity

Every electronic product is exposed to electromagnetic disturbances during its lifetime.

These disturbances may originate from:

• Other electronic equipment
• Mobile phones
• Wi-Fi transmitters
• Industrial machinery
• Switching equipment
• Lightning events
• Electrostatic discharge from users
• Power distribution systems

A properly designed product should continue operating correctly under these conditions without unacceptable degradation of performance.

EMC immunity testing evaluates whether this objective has been achieved.

Which Immunity Tests Should Be Prioritised?

Not every immunity test provides the same engineering value during product development.

Some tests frequently reveal PCB or grounding problems that are relatively inexpensive to correct early in development.

Others become more relevant once the product architecture has stabilised.

For most electronic products, the following order is recommended:

Priority	Test Case	Typical Engineering Impact
★★★★★	Electrostatic Discharge (ESD)	PCB, enclosure, grounding
★★★★★	Radiated RF Immunity	Shielding, PCB, RF design
★★★★☆	Electrical Fast Transients (EFT/Burst)	Power supply, I/O protection
★★★★☆	Conducted RF Immunity	Cable design, filtering
★★★☆☆	Surge Immunity	Protection circuits
★★★☆☆	Voltage Dips & Interruptions	Power architecture

The applicable tests depend on the product category, intended installation and relevant EMC standard.

Test Case 1 – Electrostatic Discharge (ESD)

Purpose

Electrostatic Discharge (ESD) testing evaluates how the product responds when subjected to sudden electrostatic discharges.

These events occur frequently in everyday use.

Examples include:

• A user touching the product after walking across a carpet
• Plastic enclosures generating static electricity
• Connectors being plugged in or disconnected
• Dry environmental conditions

The objective is to determine whether the product continues operating correctly after electrostatic discharge.

Why Is This Test Important?

ESD is one of the most valuable immunity tests during product development.

Unlike several other immunity tests, ESD frequently exposes practical design weaknesses that users may encounter immediately after product launch.

Many field failures reported by customers are eventually traced back to insufficient ESD robustness.

Typical Problems Revealed

ESD testing frequently identifies:

• Product resets
• Software crashes
• Display corruption
• Communication failures
• Sensor malfunction
• Processor lock-up
• Memory corruption
• Unintended outputs

Typical Corrective Actions

Engineers may improve ESD robustness by:

• Improving PCB grounding
• Adding ESD protection devices
• Optimising enclosure design
• Improving connector protection
• Revising PCB layout
• Improving return current paths
• Updating firmware recovery behaviour

Often a combination of hardware and firmware improvements is required.

Recommended During Pre-Compliance?

★★★★★ Essential

ESD testing should almost always be included in EMC pre-compliance programmes because it provides excellent insight into overall product robustness.

Test Case 2 – Radiated RF Immunity

Purpose

Radiated RF Immunity evaluates whether the product continues operating correctly while exposed to controlled electromagnetic fields.

The test simulates environments where nearby transmitters generate significant RF energy.

Typical sources include:

• Mobile phones
• Wi-Fi access points
• Bluetooth devices
• Industrial transmitters
• Broadcast equipment

Why Is This Test Important?

Many products perform perfectly in quiet laboratory environments but behave differently when strong RF fields are present.

Radiated RF Immunity evaluates whether external radio signals influence:

• Normal operation
• Communications
• User interfaces
• Safety functions
• Control systems

Typical Problems Revealed

Common findings include:

• Communication interruptions
• False triggering
• Sensor errors
• Display disturbances
• Processor instability
• Software resets
• RF coupling into cables
• PCB susceptibility

Typical Corrective Actions

Possible improvements include:

• Better PCB grounding
• Improved shielding
• Cable filtering
• Ferrites
• PCB layout optimisation
• Improved enclosure design
• Firmware robustness improvements

Recommended During Pre-Compliance?

★★★★★ Essential

Products intended for industrial, commercial and wireless environments should normally include Radiated RF Immunity during pre-compliance testing.

Test Case 3 – Electrical Fast Transients (EFT/Burst)

Purpose

Electrical Fast Transients simulate high-frequency switching disturbances commonly generated by:

• Relay contacts
• Industrial switching
• Inductive loads
• Motor controllers

These disturbances are injected onto power and signal lines.

Why Is This Test Important?

Products installed in industrial environments frequently encounter burst disturbances.

Early testing allows engineers to evaluate the effectiveness of:

• Input filtering
• PCB design
• Power supply architecture
• Protection circuitry

Typical Problems Revealed

Typical findings include:

• Unexpected resets
• Communication errors
• Input/output malfunction
• Software instability
• Temporary lock-up

Typical Corrective Actions

Possible improvements include:

• Better filtering
• Improved decoupling
• PCB redesign
• Ground optimisation
• Input protection
• Firmware recovery mechanisms

Recommended During Pre-Compliance?

★★★★☆ Highly Recommended

Especially for industrial equipment and products connected to external wiring.

Test Case 4 – Conducted RF Immunity

Purpose

Conducted RF Immunity evaluates whether RF signals coupled onto external cables affect product operation.

Instead of radiating RF energy through free space, disturbances are injected directly onto connected conductors.

Why Is This Test Important?

External cables often behave as unintended antennas.

Products with long communication or power cables may therefore experience unexpected interference.

Typical Problems Revealed

Conducted RF testing commonly identifies:

• Communication errors
• Sensor instability
• Control malfunction
• Unexpected resets
• Cable coupling effects

Typical Corrective Actions

Engineers may improve performance through:

• Cable filtering
• Ferrites
• Shielded cables
• PCB improvements
• Grounding optimisation

Recommended During Pre-Compliance?

★★★★☆ Highly Recommended

Especially for products with external communication or power cables.

Should Every Immunity Test Be Performed?

Not necessarily.

The applicable immunity programme depends on:

• Product category
• Installation environment
• Applicable EMC standard
• Intended use
• Customer expectations

For example:

A battery-powered Bluetooth sensor installed indoors will typically require a different immunity evaluation than an industrial controller connected to long field cables.

Manufacturers should therefore prioritise immunity testing according to technical risk rather than attempting every available test during early development.

Prioritising EMC Immunity Tests

When laboratory time is limited, the following order usually provides the greatest engineering value:

Priority	Test Case	Recommended
★★★★★	Electrostatic Discharge (ESD)	Yes
★★★★★	Radiated RF Immunity	Yes
★★★★☆	Electrical Fast Transients (EFT/Burst)	Usually
★★★★☆	Conducted RF Immunity	Usually
★★★☆☆	Surge	Where applicable
★★★☆☆	Voltage Dips & Interruptions	Where applicable

This sequence focuses on the immunity tests most likely to expose product robustness issues before formal certification.

Key Takeaways

Unlike EMC emissions testing, immunity testing evaluates how well a product continues to function when exposed to external electromagnetic disturbances.

Among all immunity evaluations, Electrostatic Discharge (ESD) and Radiated RF Immunity generally provide the greatest engineering value during pre-compliance because they frequently reveal weaknesses in PCB layout, grounding, shielding and overall system robustness.

Additional tests such as Electrical Fast Transients, Conducted RF Immunity, Surge and Voltage Dips should be selected according to the intended operating environment and applicable EMC standards, allowing manufacturers to build a pre-compliance programme that reflects the real technical risks of their product rather than simply repeating every certification test.

Chapter 9 – RF Exposure Assessment – Should You Perform SAR or MPE Pre-Compliance Testing?

Not every wireless product requires RF exposure testing. However, for products that do, RF exposure assessments are among the most important aspects of regulatory compliance.

Manufacturers often discover late in a project that their product requires either a Specific Absorption Rate (SAR) evaluation or a Maximum Permissible Exposure (MPE) assessment. In some cases, the product design itself determines which evaluation method applies. In others, relatively small design decisions—such as antenna placement or the intended operating distance—can significantly affect the applicable regulatory requirements.

Unlike many RF transmitter measurements, RF exposure testing is not intended to evaluate spectrum use or transmitter performance. Instead, it assesses whether the radio-frequency energy generated by the product remains within internationally accepted human exposure limits.

From a pre-compliance perspective, the objective is straightforward:

Determine as early as possible whether RF exposure is likely to become a certification risk.

Early assessment allows manufacturers to make informed engineering decisions before product design becomes fixed.

What Is RF Exposure?

Whenever a wireless transmitter operates, part of its transmitted energy is absorbed by nearby objects, including the human body.

International regulations therefore define exposure limits intended to ensure that wireless devices can be used safely under their intended operating conditions.

Depending on the product and intended use, compliance is typically demonstrated using one of two approaches:

• Specific Absorption Rate (SAR)
• Maximum Permissible Exposure (MPE)

Although both methods evaluate human RF exposure, they apply to different product categories and operating scenarios.

SAR vs MPE

Understanding the difference between SAR and MPE is one of the first steps when planning compliance activities.

Specific Absorption Rate (SAR)

SAR evaluates the amount of RF energy absorbed by human tissue.

It is generally applicable to products that are intended to operate close to the human body.

Typical examples include:

• Smartphones
• Tablets
• Wearable devices
• Smart watches
• Wireless headphones
• Handheld radios
• Portable medical devices

SAR measurements are performed using specialised laboratory equipment and anatomically representative phantoms filled with tissue-simulating liquid.

Maximum Permissible Exposure (MPE)

MPE evaluates the RF power density at a specified separation distance from the product.

Rather than measuring energy absorbed by the body, MPE calculations determine whether exposure remains below the applicable limits.

MPE commonly applies to products that normally operate at a sufficient distance from people.

Examples include:

• Wi-Fi access points
• Industrial wireless equipment
• Fixed wireless gateways
• Outdoor communication equipment
• Infrastructure devices

Many products demonstrate compliance through engineering calculations instead of physical measurements.

Why Evaluate RF Exposure Early?

One of the most common mistakes is assuming that RF exposure can always be addressed at the end of a certification project.

In reality, RF exposure depends directly on product design decisions such as:

• Antenna location
• Antenna gain
• Maximum transmitter power
• Operating frequency
• Product enclosure
• Intended use
• Separation distance
• Simultaneous transmitters

Changing any of these parameters late in development may affect the RF exposure assessment.

An early engineering review therefore reduces the risk of unexpected redesign work before certification.

Should Every Product Be Pre-Tested?

No.

Many products can determine their RF exposure requirements without performing laboratory measurements.

For example:

• Products clearly operating under MPE limits may only require engineering calculations.
• Some products integrating pre-certified radio modules may already have supporting RF exposure documentation.
• Low-power devices operating with very low transmit power may present minimal RF exposure concerns.

Nevertheless, every wireless product should undergo an early RF exposure assessment to determine which regulatory path applies.

What Should Manufacturers Evaluate During Pre-Compliance?

Rather than immediately performing SAR measurements, manufacturers should first answer several engineering questions.

1. How Will the Product Be Used?

Will the product be:

• Handheld?
• Body-worn?
• Installed on a wall?
• Mounted on a ceiling?
• Used on a desk?
• Installed outdoors?

The intended operating conditions strongly influence the applicable RF exposure requirements.

2. How Close Will Users Be?

Operating distance is often one of the most important factors.

Products intended for direct body contact may require SAR evaluation, whereas products installed at larger distances may qualify for MPE assessment.

3. What Is the Maximum RF Output Power?

Higher transmitter power generally increases RF exposure.

Manufacturers should therefore confirm:

• Maximum conducted power
• Maximum radiated power
• Antenna gain
• Operating modes
• Simultaneous transmission conditions

4. Are Multiple Radios Operating Simultaneously?

Many modern products include:

• Wi-Fi
• Bluetooth
• Cellular
• GNSS
• Thread
• Zigbee

Operating multiple transmitters simultaneously may influence the RF exposure assessment and should be considered early in development.

Typical Design Problems Identified During Early RF Exposure Assessment

An early engineering review frequently identifies issues such as:

• Antenna placement too close to users
• Higher-than-expected antenna gain
• Incorrect separation assumptions
• Excessive simultaneous transmit power
• Product intended for a different use case than originally assumed
• Mechanical design limiting compliance options

These issues are generally much easier to resolve before tooling and production begin.

Typical Corrective Actions

Depending on the findings, manufacturers may consider:

• Relocating the antenna
• Reducing transmitter power
• Selecting a different antenna
• Modifying product usage instructions
• Increasing operating separation distance
• Adjusting simultaneous transmission behaviour
• Updating firmware power management

Many RF exposure issues can be addressed through design optimisation if identified early enough.

Recommended During Pre-Compliance?

★★★★★ Essential Engineering Review

An RF exposure assessment should be performed for virtually every wireless product during development.

However, this does not mean that every product requires SAR laboratory testing.

The first objective should always be to determine:

• Whether RF exposure requirements apply.
• Whether SAR or MPE is applicable.
• Whether engineering calculations are sufficient.
• Whether laboratory testing will be required.

Practical Decision Flow

Before scheduling RF exposure testing, manufacturers should consider the following sequence:

1. Identify all integrated radio transmitters.
2. Determine maximum transmit power.
3. Review antenna characteristics.
4. Define the intended operating distance.
5. Evaluate simultaneous transmitter operation.
6. Determine whether SAR or MPE is applicable.
7. Decide whether engineering calculations or laboratory measurements are required.

This structured approach prevents unnecessary testing and allows RF exposure activities to be planned efficiently.

Key Takeaways

RF exposure assessments are fundamentally different from RF transmitter or EMC testing. Rather than evaluating radio performance or electromagnetic compatibility, they determine whether a wireless product complies with human exposure limits.

For most manufacturers, the greatest value during pre-compliance lies not in performing SAR measurements immediately, but in conducting an early engineering assessment of antenna configuration, transmit power, operating distance and intended product use. This allows potential RF exposure risks to be identified while design changes remain practical, ensuring that the correct regulatory assessment path—whether SAR, MPE or engineering analysis—is selected before formal certification begins.

Chapter 10 – Recommended Pre-Compliance Test Plans for Different Product Types

One of the most common questions manufacturers ask before starting pre-compliance testing is:

“Which tests should I actually perform for my product?”

Unfortunately, there is no universal answer.

Two products using the same radio technology may require completely different pre-compliance strategies depending on factors such as:

• Product type
• Intended use
• Target markets
• Radio architecture
• Antenna design
• Power supply
• Mechanical construction
• Applicable regulations

A Bluetooth temperature sensor, for example, presents very different technical risks than a Wi-Fi router, even though both operate in the 2.4 GHz band.

For this reason, pre-compliance testing should always be based on engineering risk, not simply on the list of tests contained in the applicable standard.

This chapter provides practical recommendations for several of the most common wireless product categories and explains which tests generally deserve the highest priority.

Bluetooth® Products

Typical products include:

• Sensors
• Remote controls
• Smart home devices
• Wearables
• Medical devices
• Industrial monitoring equipment

Bluetooth products usually operate in the globally available 2.4 GHz ISM band and often integrate certified radio chipsets. Nevertheless, the final product must still demonstrate compliance with the applicable regulatory requirements.

Recommended RF Priorities

★★★★★ Maximum Output Power

★★★★★ Band Edge Emissions

★★★★★ Spurious Emissions

★★★★☆ Occupied Bandwidth

★★★★☆ Receiver Sensitivity

★★★★☆ Adjacent Channel Selectivity

★★★☆☆ Frequency Stability

Recommended EMC Priorities

★★★★★ Radiated Emissions

★★★★★ ESD

★★★★☆ Radiated RF Immunity

★★★★☆ Conducted Emissions (where applicable)

★★★★☆ EFT/Burst (products with external interfaces)

Typical Engineering Risks

• Poor antenna placement
• Ground plane interaction
• Metal enclosure effects
• Coexistence with Wi-Fi
• RF leakage from digital electronics
• Battery-powered layout constraints

Wi-Fi Products

Typical products include:

• Routers
• Access points
• Smart cameras
• Industrial gateways
• Consumer electronics
• IoT hubs

Compared with Bluetooth, Wi-Fi products generally operate at higher transmit powers and often support multiple frequency bands and bandwidths.

As a result, RF performance usually becomes a higher engineering risk.

Recommended RF Priorities

★★★★★ Maximum Output Power

★★★★★ Band Edge Emissions

★★★★★ Spurious Emissions

★★★★★ Power Spectral Density

★★★★☆ Occupied Bandwidth

★★★★☆ Receiver Sensitivity

★★★★☆ Blocking Performance

★★★★☆ Adjacent Channel Selectivity

★★★☆☆ Frequency Stability

Recommended EMC Priorities

★★★★★ Radiated Emissions

★★★★★ Radiated RF Immunity

★★★★★ ESD

★★★★☆ Conducted Emissions

★★★★☆ Diagnostic EMC Investigation

Typical Engineering Risks

• High transmitter power
• Multiple antennas
• High-speed processors
• Ethernet interfaces
• Power supply noise
• Coexistence between multiple radios

Cellular Products

Typical products include:

• LTE gateways
• 5G routers
• Asset trackers
• Vehicle telematics
• Industrial modems
• Medical communication devices

Cellular products often operate over numerous frequency bands and may support carrier aggregation, MIMO and simultaneous transmitters.

Consequently, RF integration becomes significantly more complex.

Recommended RF Priorities

★★★★★ Maximum Output Power

★★★★★ Spurious Emissions

★★★★★ Band Edge Emissions

★★★★★ RF Exposure Assessment

★★★★☆ Receiver Sensitivity

★★★★☆ Blocking

★★★★☆ Adjacent Channel Selectivity

★★★★☆ Frequency Stability

Recommended EMC Priorities

★★★★★ Radiated Emissions

★★★★★ Radiated RF Immunity

★★★★★ ESD

★★★★☆ Conducted Emissions

★★★★☆ EFT/Burst

★★★★☆ Conducted RF Immunity

Typical Engineering Risks

• Multiple antennas
• Simultaneous transmitters
• RF exposure
• Power amplifier harmonics
• Complex RF front-end
• Thermal effects
• Grounding

LoRa® Products

Typical products include:

• Smart metering
• Agricultural sensors
• Industrial monitoring
• Environmental monitoring
• Asset tracking

LoRa devices usually prioritise long communication range over high data throughput.

Although transmitter power is often relatively low, receiver performance becomes particularly important.

Recommended RF Priorities

★★★★★ Receiver Sensitivity

★★★★★ Maximum Output Power

★★★★★ Band Edge Emissions

★★★★☆ Spurious Emissions

★★★★☆ Frequency Stability

★★★★☆ Duty Cycle (where applicable)

Recommended EMC Priorities

★★★★★ Radiated Emissions

★★★★★ ESD

★★★★☆ Radiated RF Immunity

★★★★☆ Conducted Emissions (where applicable)

Typical Engineering Risks

• Receiver sensitivity
• Oscillator stability
• Long communication range
• Battery lifetime
• Outdoor installation

Zigbee® and Thread Products

Typical products include:

• Building automation
• Smart lighting
• Smart energy
• Home automation
• Mesh networking devices

These products usually operate in the crowded 2.4 GHz ISM band and depend heavily on reliable receiver performance.

Recommended RF Priorities

★★★★★ Receiver Sensitivity

★★★★★ Adjacent Channel Selectivity

★★★★★ Maximum Output Power

★★★★☆ Spurious Emissions

★★★★☆ Occupied Bandwidth

★★★★☆ Band Edge Emissions

Recommended EMC Priorities

★★★★★ Radiated Emissions

★★★★★ ESD

★★★★☆ Radiated RF Immunity

★★★★☆ Conducted Emissions

Typical Engineering Risks

• Mesh communication
• Dense RF environments
• Antenna efficiency
• Coexistence with Bluetooth and Wi-Fi

Products Using Pre-Certified Radio Modules

Many manufacturers assume that integrating a certified radio module eliminates the need for RF pre-compliance testing.

In reality, this is rarely the case.

Although the module itself may already comply with applicable RF regulations, the final product may still be affected by:

• Antenna changes
• Enclosure effects
• Ground plane modifications
• EMC emissions
• Host integration
• RF exposure
• Multiple transmitter operation

Consequently, pre-compliance testing remains highly valuable even when certified modules are used.

Selecting the Right Test Plan

Rather than asking:

“Which standard applies?”

Manufacturers should first ask:

“Which technical risks are most likely to affect my product?”

The answer determines which tests deserve the highest priority.

For example:

• A battery-powered Bluetooth sensor should focus heavily on antenna performance, radiated emissions and ESD.
• A Wi-Fi access point will generally require greater emphasis on transmitter performance, EMC emissions and RF exposure.
• An industrial cellular gateway should prioritise RF exposure, EMC immunity and conducted disturbances because of its installation environment.

By selecting tests according to engineering risk instead of simply following the order of certification standards, manufacturers obtain more useful information while making better use of limited laboratory time.

Key Takeaways

There is no universal pre-compliance test programme suitable for every wireless product.

The most effective strategy is always one that reflects the technical characteristics of the product, the applicable regulations and the engineering risks associated with its design.

Bluetooth devices, Wi-Fi equipment, cellular products, LoRa sensors and Zigbee systems each present different technical challenges. Prioritising the right RF, EMC and RF exposure tests for each product category enables manufacturers to identify design weaknesses early, optimise development resources and enter formal certification with significantly greater confidence.

Chapter 11 – Why Products Fail Certification – The Most Common Engineering Mistakes and How to Avoid Them

One of the biggest misconceptions about regulatory compliance is that products fail certification because laboratories are overly strict or because regulatory requirements are excessively demanding.

In reality, most certification failures have much simpler causes.

They are usually the result of engineering decisions made months earlier during product development.

Many of these issues could have been identified through targeted pre-compliance testing before the design was frozen.

Understanding the most common reasons products fail certification helps manufacturers focus their development effort where it has the greatest impact.

This chapter discusses the engineering mistakes most frequently encountered during RF, EMC and RF exposure testing and explains how they can be identified before formal certification begins.

Most Certification Failures Are Not Random

Certification laboratories perform standardised measurements using internationally recognised procedures.

They do not “create” problems.

Instead, they reveal weaknesses that already exist within the product.

In many projects, the first visit to the laboratory is effectively the first time the complete product is evaluated under realistic regulatory conditions.

By that point, hardware, firmware and mechanical design are often largely fixed, making corrective actions expensive and time-consuming.

Successful projects therefore focus on identifying technical risks long before formal testing begins.

Engineering Mistake 1 – Antenna Integration Is Treated as a Mechanical Problem

Perhaps the most common engineering mistake is assuming that the antenna is simply another mechanical component.

In reality, the antenna is one of the most critical parts of the RF system.

Even a certified radio module cannot compensate for poor antenna integration.

Common problems include:

• Antennas placed too close to metal parts
• Insufficient ground clearance
• Plastic housings replaced by metal enclosures
• Nearby batteries affecting antenna performance
• Display cables routed close to the antenna
• Changes made after antenna tuning

Typical consequences include:

• Reduced output power
• Poor receiver sensitivity
• Increased spurious emissions
• Band edge failures
• RF exposure changes

Engineering Mistake 2 – EMC Is Considered Too Late

Many development teams focus heavily on product functionality while assuming EMC can be addressed shortly before certification.

Unfortunately, EMC performance is largely determined by early design decisions.

Examples include:

• PCB stack-up
• Ground plane design
• Component placement
• Switching regulator selection
• Return current paths
• Cable routing

Once the PCB has been manufactured, correcting EMC problems becomes significantly more difficult.

Radiated emissions are particularly expensive to improve late in development.

Engineering Mistake 3 – Using a Certified Radio Module Guarantees Compliance

This misconception appears in almost every industry.

A certified radio module significantly reduces development effort.

However, certification applies to the module—not automatically to the final product.

The complete device may still fail because of:

• Different antennas
• Host PCB effects
• Mechanical enclosure changes
• Additional transmitters
• EMC emissions
• RF exposure
• Power supply noise

Module certification should therefore be viewed as an excellent starting point—not the end of compliance activities.

Engineering Mistake 4 – RF and EMC Are Treated as Independent Topics

Many organisations assign RF development and EMC development to different teams.

While this is understandable from an organisational perspective, the product itself does not separate these disciplines.

For example:

• Poor grounding affects RF performance and EMC.
• Antenna matching influences both transmitter performance and emissions.
• PCB layout affects receiver sensitivity, EMC emissions and immunity.
• Shielding influences RF characteristics as well as EMC robustness.

Considering RF and EMC together usually leads to better engineering decisions.

Engineering Mistake 5 – Firmware Is Ignored During Compliance Development

Compliance is often viewed as a purely hardware-related activity.

In reality, firmware influences many regulatory measurements.

Examples include:

• Transmitter power control
• Duty cycle
• Channel selection
• Sleep modes
• RF calibration
• Error recovery
• Simultaneous transmitter operation

Many apparent hardware problems are ultimately resolved through firmware improvements.

Likewise, firmware changes introduced late in development can unintentionally create new compliance issues.

Engineering Mistake 6 – No Engineering Risk Assessment Before Certification

Many companies schedule laboratory testing immediately after completing product development.

However, no one has asked a fundamental question:

Which part of the product is most likely to fail?

Without a structured engineering review, laboratory time is often spent investigating predictable problems that could have been identified internally.

A simple technical risk assessment before certification frequently saves significant development time.

Questions worth considering include:

• Which RF measurements present the highest risk?
• Which EMC tests are most likely to reveal failures?
• Does the antenna design introduce uncertainty?
• Is RF exposure likely to become an issue?
• Which hardware changes would be most expensive?

Engineering Mistake 7 – Treating Certification as the Final Development Step

Perhaps the biggest misconception is that certification begins after product development has finished.

Successful manufacturers follow the opposite philosophy.

Compliance is considered throughout development.

Every design review becomes an opportunity to ask:

• Does this affect RF performance?
• Does this influence EMC?
• Will this change RF exposure?
• Will this affect certification?

By integrating compliance into engineering decisions from the beginning, certification becomes a validation activity rather than a debugging exercise.

How Pre-Compliance Testing Prevents These Problems

Pre-compliance testing cannot guarantee that certification will always be successful.

However, it significantly improves the likelihood of success because it allows engineering teams to identify technical risks while corrective actions remain practical.

Rather than asking:

Will the product pass certification?

Pre-compliance asks:

What could prevent the product from passing certification?

This shift in perspective is one of the greatest advantages of pre-compliance testing.

A Risk-Based Engineering Mindset

The most successful compliance projects rarely belong to products with the largest budgets.

Instead, they belong to projects that identify technical uncertainty early.

Risk-based development means continuously asking:

• Which subsystem is least understood?
• Which measurement could require hardware redesign?
• Which issue would delay certification the most?
• Which problem is easiest to solve today rather than six months from now?

Answering these questions throughout development dramatically reduces certification risk.

Key Takeaways

Most certification failures are not caused by unexpected regulatory requirements—they are the consequence of engineering decisions made much earlier in the development process.

Poor antenna integration, late EMC consideration, incorrect assumptions about certified radio modules, weak RF/EMC integration, firmware-related issues and the absence of structured technical risk assessments are among the most common reasons products fail formal compliance testing.

By identifying these risks through engineering reviews and targeted pre-compliance testing, manufacturers can resolve problems while design changes remain practical, reducing both certification delays and costly redesign work.

Chapter 12 – Preparing for the Official Test Laboratory – What Should Be Ready Before Certification Begins?

For many manufacturers, scheduling the official certification tests marks the final milestone before product launch. Unfortunately, this is also the stage where avoidable delays often occur.

In many projects, laboratory testing begins while technical documentation is incomplete, firmware is still changing, hardware revisions are not final or important engineering decisions remain unresolved.

As a result, valuable laboratory time is spent identifying issues that could have been resolved before the product ever entered the test chamber.

Successful certification projects therefore begin long before the first measurement is performed.

Preparation is not simply an administrative task—it is an engineering activity that ensures the laboratory evaluates a stable, representative product rather than a prototype that is still under development.

This chapter explains what manufacturers should complete before submitting a product for formal RF and EMC certification.

Certification Should Validate the Product—Not Develop It

One of the most common misconceptions is that the certification laboratory will identify all remaining design issues and help optimise the product.

That is not the purpose of certification.

The laboratory’s responsibility is to determine whether the submitted product complies with the applicable regulatory requirements.

Although many laboratories provide excellent technical support, the official certification programme is not intended to be an engineering development exercise.

Ideally, the product entering certification should already be technically mature.

Formal testing should confirm compliance—not become the first opportunity to discover design weaknesses.

Is the Hardware Really Final?

Before booking certification, manufacturers should critically evaluate whether the hardware is genuinely ready.

Questions worth asking include:

• Has the PCB design been frozen?
• Has the antenna been finalised?
• Are all RF components identical to those used during pre-compliance testing?
• Has the enclosure been completed?
• Are all shielding components installed?
• Have thermal modifications been completed?
• Are production materials identical to the test samples?

Even seemingly minor hardware changes may influence:

• RF performance
• EMC emissions
• EMC immunity
• RF exposure
• Safety compliance

If important hardware changes are still expected, certification should usually be postponed.

Is the Firmware Stable?

Firmware is frequently updated until shortly before product release.

However, firmware changes can significantly influence compliance measurements.

Manufacturers should verify that:

• RF power settings are final.
• Channel configurations are complete.
• Sleep modes operate correctly.
• Duty cycle behaviour has been verified.
• Country-specific settings are implemented.
• Simultaneous transmitter behaviour is final.
• Recovery after EMC disturbances has been validated.

A firmware update introduced after successful testing may invalidate previous certification results if it affects regulated functions.

Is the Antenna Configuration Final?

Antenna-related changes represent one of the most common causes of repeated testing.

Manufacturers should confirm:

• Final antenna type
• Final antenna gain
• Final antenna position
• Matching network configuration
• Cable routing
• Mechanical spacing

Changing an antenna after certification planning has begun frequently requires partial or complete retesting.

Have All Required Product Configurations Been Identified?

Many products support multiple operating modes.

Examples include:

• Different frequency bands
• Various bandwidth settings
• Multiple antennas
• Optional accessories
• Internal and external power supplies
• Different communication interfaces

Manufacturers should determine which configurations represent:

• Worst-case RF operation
• Worst-case EMC emissions
• Worst-case immunity performance
• Highest RF exposure

Selecting the correct test configurations before laboratory testing prevents unnecessary delays.

Is the Technical Documentation Complete?

Certification laboratories depend heavily on accurate technical information.

Typical documentation includes:

• Product description
• Block diagrams
• Schematics
• PCB layouts
• Bill of Materials (where required)
• Operational description
• Antenna specifications
• User manual
• Installation instructions

Incomplete documentation frequently delays certification even when the product itself performs well.

Have Applicable Standards Been Confirmed?

One of the most common project risks is discovering late that an applicable standard was overlooked.

Before certification begins, manufacturers should verify:

• Applicable RF standards
• Applicable EMC standards
• Electrical safety standards
• RF exposure requirements
• Cybersecurity requirements (where applicable)
• National deviations for target markets

Completing this review before laboratory testing helps prevent unexpected scope changes.

Are the Test Samples Representative?

The samples submitted to the laboratory should represent normal production.

Manufacturers should avoid sending:

• Hand-built prototypes
• Temporary PCB modifications
• Development firmware (unless intended for certification)
• Temporary antennas
• Unapproved components

Certification should always be performed using hardware representative of the final product.

Practical Pre-Laboratory Checklist

Before scheduling certification, manufacturers should ideally confirm the following:

Product Design

✔ Hardware frozen

✔ Firmware stable

✔ Antenna finalised

✔ Mechanical design completed

Technical Review

✔ RF pre-compliance completed

✔ EMC pre-compliance completed

✔ RF exposure reviewed

✔ Applicable standards confirmed

Documentation

✔ Schematics available

✔ Block diagrams completed

✔ User manual prepared

✔ Product description completed

✔ Antenna documentation available

Test Planning

✔ Worst-case operating modes identified

✔ Required accessories available

✔ Test samples prepared

✔ Laboratory questions clarified

Completing this checklist significantly improves the efficiency of laboratory testing.

Why Good Preparation Saves More Than Laboratory Time

Many manufacturers assume that poor preparation only results in additional laboratory costs.

In reality, the consequences often extend much further.

A failed certification programme may lead to:

• Product launch delays
• Additional PCB revisions
• New tooling
• Production rescheduling
• Additional engineering effort
• Customer delivery delays
• Increased certification costs

By comparison, investing time in careful preparation before entering the laboratory is usually one of the most cost-effective decisions a manufacturer can make.

Certification Should Be Predictable

The objective of pre-compliance testing is not to eliminate every possible technical issue.

Instead, it is to eliminate uncertainty.

A well-prepared project enters certification with a clear understanding of:

• Applicable regulations
• Expected technical performance
• Remaining engineering risks
• Product configurations
• Documentation requirements

When these elements are already under control, certification becomes a structured validation process rather than an expensive troubleshooting exercise.

Key Takeaways

Successful certification begins long before the product arrives at the test laboratory.

Manufacturers should ensure that the hardware, firmware, antenna configuration and mechanical design are final, that all applicable standards have been identified and that the submitted samples accurately represent the production version of the product.

Equally important is the completion of pre-compliance testing and technical documentation before formal certification starts. Thorough preparation reduces uncertainty, avoids unnecessary retesting and allows the laboratory to focus on confirming compliance rather than uncovering preventable engineering issues.

Chapter 13 – Conclusion – Building a Successful RF & EMC Compliance Strategy

Bringing a wireless product to market has become significantly more complex over the past decade.

Modern products often combine multiple radio technologies, high-speed digital electronics, switching power supplies, battery management systems and sophisticated software within increasingly compact mechanical designs. At the same time, regulatory requirements continue to expand, covering not only RF, EMC and electrical safety, but also areas such as RF exposure, cybersecurity and environmental legislation.

Against this background, successful certification is no longer achieved simply by selecting a laboratory and waiting for the final test results.

It begins much earlier.

The most successful projects integrate regulatory compliance into the engineering process from the very beginning.

Compliance Is an Engineering Process

Throughout this guide, one principle has appeared repeatedly:

Certification does not create compliance. It verifies compliance.

The laboratory evaluates the finished product exactly as it is presented.

If weaknesses exist in the antenna design, PCB layout, EMC performance, firmware or product architecture, certification will simply reveal them.

For this reason, compliance should not be treated as a final administrative step before product launch.

Instead, it should become an integral part of product development.

Every important engineering decision has the potential to influence:

• RF performance
• EMC emissions
• EMC immunity
• RF exposure
• Safety
• Certification cost
• Project schedule

The earlier these interactions are understood, the lower the technical and commercial risk.

There Is No Universal Test Plan

One of the most important messages of this guide is that there is no single pre-compliance programme suitable for every product.

A Bluetooth sensor, a Wi-Fi access point, an industrial LTE gateway and a wearable medical device all present different engineering challenges.

Consequently, their pre-compliance strategies should also be different.

Rather than attempting every available laboratory test, manufacturers should ask:

Which measurements provide the greatest engineering value for this specific product?

Answering this question allows laboratory resources to be used efficiently while maximising the information obtained from each test.

Risk Should Determine Priorities

Throughout the previous chapters, a recurring recommendation has been to prioritise testing according to engineering risk.

The objective is not to perform the greatest number of tests.

The objective is to identify the issues that would become the most expensive if discovered during formal certification.

For many projects, these include:

• Antenna integration
• RF transmitter performance
• EMC emissions
• ESD robustness
• Receiver sensitivity
• RF exposure
• PCB layout

Identifying these risks early frequently prevents costly redesigns later in development.

Pre-Compliance Is About Reducing Uncertainty

Many people assume that pre-compliance testing exists to save money.

Although it often does, this is not its primary purpose.

The true objective is to reduce uncertainty.

When entering formal certification, manufacturers should already understand:

• Which standards apply
• Which tests are required
• Which configurations represent the worst case
• Which technical risks remain
• Which measurements deserve particular attention

Projects with fewer unknowns generally progress faster, require fewer engineering changes and produce more predictable certification outcomes.

Good Engineering Produces Good Compliance

Successful compliance rarely depends on luck.

Products that pass certification smoothly typically share several characteristics:

• Well-planned RF architecture
• Good PCB layout
• Careful antenna integration
• Stable firmware
• Effective EMC design
• Structured engineering reviews
• Targeted pre-compliance testing

These characteristics are engineering achievements—not regulatory ones.

Certification simply confirms their quality.

Looking Beyond Certification

Passing certification is an important milestone, but it should not be the final objective.

Manufacturers should aim to develop products that:

• Perform reliably in real operating environments
• Continue complying throughout production
• Can be updated without introducing regulatory issues
• Are easier to adapt for additional global markets
• Require minimal redesign during future product generations

Thinking beyond the first certification often produces significant long-term engineering and commercial benefits.

How ScopeRight Supports Manufacturers

Managing RF, EMC and global regulatory requirements has become increasingly complex. Determining the applicable standards, identifying the required test programme and planning certification activities across multiple markets can consume considerable engineering time before a product even enters the laboratory.

ScopeRight was developed to simplify these early project stages by helping manufacturers structure their compliance strategy before formal testing begins.

The platform supports engineering teams by helping them:

• determine applicable RF, EMC, Safety and Cybersecurity requirements;
• identify relevant standards for Europe, the United States, Canada and other markets;
• generate structured compliance scopes based on the product’s technical characteristics;
• understand which RF, EMC and RF exposure assessments are applicable;
• prepare laboratory test plans before certification;
• generate product compliance documentation;
• evaluate global market access requirements; and
• manage certification projects in a structured and traceable way.

Rather than replacing engineering expertise or accredited testing laboratories, ScopeRight helps manufacturers make informed technical decisions earlier in the development process, reducing uncertainty before formal certification begins.

Final Thoughts

Successful compliance is not determined by what happens during the final week of laboratory testing.

It is determined by hundreds of engineering decisions made throughout the entire product development cycle.

Every decision involving the antenna, PCB layout, firmware, power supply, enclosure and system architecture contributes to the final certification result.

Manufacturers who integrate compliance into product development from the beginning are generally able to reduce technical risk, shorten certification timelines and bring products to market with greater confidence.

Pre-compliance testing is therefore not simply another project milestone.

It is an engineering methodology that transforms compliance from a reactive activity into a structured design process—one that helps manufacturers build better products long before formal certification begins.