Pre-Compliance vs Compliance: Why Test Results Differ

It’s not unusual for a product to pass a pre-compliance scan in the lab, only to fail the formal compliance test weeks later. The difference is rarely due to luck – it’s almost always down to setup, detector, environment, or uncertainty factors that are easy to overlook but hard to fix late in the project.

Pre-Compliance vs Compliance: What’s Actually Different?

Pre-compliance testing is a developer’s best friend for early-stage EMC debugging. It’s fast, flexible, and cost-effective. But it is not a substitute for formal compliance testing, which is required for CE marking, UKCA, FCC, and other regulatory approvals. The two approaches differ in several critical ways:

Setup difference: Pre-compliance is often performed on a bench or in a screened room, with improvised ground planes and cable layouts. Formal compliance requires a controlled environment, such as a CISPR 16-compliant semi-anechoic chamber or OATS, with strict adherence to test setups defined in standards.
Detector: Pre-compliance scans usually use peak or average detectors for speed. Compliance testing mandates specific detector types (CISPR quasi-peak, RMS average, etc.) at prescribed frequencies, which can reveal emissions missed by a simple peak scan.
Environment: Ambient noise, reflections, and even the presence of people or nearby equipment can skew pre-compliance results. Formal testing controls these variables tightly, often using shielded rooms, filtered mains, and calibrated reference antennas.
Uncertainty: Measurement uncertainty is rarely quantified in pre-compliance work. Accredited labs quantify and report uncertainty budgets in line with UKAS and ISO 17025 requirements, which can be critical if your product sits close to a limit.

Typical Scenario

Imagine a design team running radiated emissions scans on a prototype using a hired spectrum analyser and biconical antenna in a quiet corner of the lab. The product appears to pass the relevant CISPR 22 Class B limits with a few dB to spare. Confident, the team books a formal test slot at an accredited lab. On the day, the same unit fails at 230 MHz by 4 dB. The cause? The lab’s ground plane is larger and properly bonded, the cable routing is as per the standard, and the chamber’s lower noise floor reveals a previously masked emission. The team must now debug under time pressure, risking project delays and additional costs.

EMC Hire helps bridge this gap by providing calibrated equipment for pre-compliance work, as well as access to formal compliance testing facilities. This approach reduces CAPEX, matches short-term project peaks, and avoids the maintenance and calibration overhead of owned equipment. It also allows teams to debug with more representative setups, reducing the risk of late-stage surprises.

Setup Difference: The Devil in the Details

Small setup changes can produce large differences in EMC results. Common issues include:

Ground planes: A bench-top copper sheet is not equivalent to a bonded, standard-size ground plane. At higher frequencies, poor grounding introduces parasitic inductance, distorting emissions plots.
Cable routing and length: Cables act as antennas. Inconsistent routing or length between pre-compliance and compliance tests can shift resonances and emission peaks.
Test distance: Pre-compliance is often run at 1 m due to space constraints, while compliance may require 3 m or 10 m. Field strength falls off with distance, but not always linearly due to near-field/far-field effects.
LISN/CDN configuration: Using the wrong Line Impedance Stabilisation Network (LISN) or Coupling/Decoupling Network (CDN) can mask or exaggerate conducted emissions. Always match the standard’s requirements.

Failing to replicate compliance setups during pre-compliance can lead to false confidence. Where possible, use the same part numbers, cable types, and configurations as the final test. EMC Hire’s equipment selection guides can help you match your setup to the relevant standard.

Detector Choice: Why It Matters

Peak detectors are fast and useful for initial scans, but they do not always reflect compliance limits. CISPR quasi-peak and average detectors respond differently to pulsed or modulated signals. A product that passes with a peak detector may fail with a quasi-peak detector, and vice versa. Always verify which detector the standard requires at each frequency band. Many failures at formal test labs are due to incorrect detector settings during pre-compliance.

Environmental Factors: The Unseen Variables

Ambient RF noise, reflections from metal objects, and even the presence of people near the test setup can affect results. Compliance labs control these variables with shielded rooms, filtered mains, and strict personnel restrictions. In a typical development lab, ambient signals from Wi-Fi, mobile phones, or nearby equipment can mask or mimic emissions, leading to missed failures or false positives. Always perform a background noise scan before testing and keep the environment as controlled as possible.

Measurement Uncertainty: Not Just a Paper Exercise

Measurement uncertainty is a formal requirement for accredited labs under ISO 17025. It accounts for instrument calibration, cable losses, antenna factors, and environmental influences. In pre-compliance, this is rarely quantified, but it can be the difference between a pass and a fail if your results are close to the limit. If your margin is less than the typical uncertainty (often 3-6 dB), treat the result as inconclusive and retest in a more controlled environment.

Common EMC Testing Mistakes to Avoid

Poor cable management: Uncontrolled cable routing can introduce resonances and radiating loops. Secure cables at consistent heights and positions.
Incorrect grounding: Floating or poorly bonded ground planes invalidate results, especially above 100 MHz.
Wrong LISN/CDN setup: Using the wrong impedance or failing to bond LISNs to the ground plane will distort conducted emissions data.
Test distance errors: Inconsistent test distances make results non-comparable. Always measure and document antenna/EUT distances precisely.
Unrepresentative operating modes: Test the EUT in its worst-case mode, not just idle or standby. Missed emissions often hide in active states.
Uncalibrated equipment: Out-of-date calibration introduces unknown errors. Always check calibration certificates.
Incorrect detector settings: Using peak instead of quasi-peak or average where the standard requires otherwise leads to misleading results.
Poor ambient noise control: Failing to scan for background signals can result in chasing non-existent emissions or missing real ones.
Weak record keeping: Incomplete photos, setup notes, or test logs make it impossible to reproduce results or defend them in a Technical Construction File.

When to Hire EMC Equipment

Hiring EMC test equipment makes sense when you need to:

Save CAPEX and avoid tying up budget in specialist gear for short-term projects
Match equipment to project peaks, such as pre-launch debug sprints or regulatory test windows
Get the right instrument for a defined period, without the risk of obsolescence or under-utilisation
Avoid the overheads of ownership, including calibration, maintenance, and storage

EMC Hire offers a wide range of ISO 17025 calibrated equipment for both pre-compliance and formal compliance testing. This supports accurate, reliable, and repeatable measurements, helping you build defensible evidence for CE marking, FCC, and other market-entry requirements. For guidance on equipment selection, see our equipment selection guides.

Frequently Asked Questions (FAQs)

How close do pre-compliance results need to be to guarantee a pass at formal compliance?

No margin guarantees a pass, due to setup, detector, and environment differences. Aim for at least 6 dB below the limit in pre-compliance, but always treat results within the measurement uncertainty as inconclusive.

Can I use a peak detector for all EMC testing?

No. Many standards (e.g., CISPR 11, CISPR 32) require quasi-peak or average detectors for specific frequency ranges. Using only a peak detector can miss failures or produce false passes. Always check the detector requirements in the relevant standard.

Does the test environment really make that much difference?

Yes. Ambient noise, reflections, and even personnel near the EUT can shift results by several dB. Compliance labs control these variables tightly – a development lab rarely can.

What happens if my pre-compliance setup used the wrong LISN or CDN?

Your conducted emissions data may be invalid. The wrong impedance or poor bonding can mask or exaggerate emissions. Always match the LISN/CDN to the standard and check calibration.

How do I document my pre-compliance results for CE marking?

Take detailed photos of setups, log all instrument settings, keep calibration records, and document EUT operating modes. This supports your Technical Construction File and helps defend your compliance evidence.

Ready to Close the Gap Between Pre-Compliance and Compliance?

Pre-compliance scans are invaluable for catching issues early, but only formal compliance testing delivers market-ready evidence. EMC Hire supports every stage of your EMC journey, from pre-compliance debugging to formal compliance testing and facility access. All equipment is ISO 17025 calibrated and supported by experienced engineers who understand the real-world risks of setup, detector, environment, and uncertainty.

To discuss your requirements, request a quotation, arrange on-site testing, or book time at our test facility, contact the EMC Hire engineering team on +44 (0)1462 817111 or email sales@emchire.co.uk.

Always verify your equipment, test methods, and documentation against the latest active versions of the relevant standards and test plans (e.g., CISPR, IEC, UKAS, ISO 17025).