What a notified body or test lab may ask for

A sound EMC result can become difficult to defend if nobody can establish which product variant was tested, how its cables were arranged or what software was running.

Test laboratories, notified bodies and UK approved bodies may ask for different information because their roles and scopes differ. The request will also depend on the product, intended use, conformity route, market and applicable legislation. The underlying engineering question is usually the same: does the available EMC compliance evidence represent the product that will actually be placed on the market?

Why the requested evidence extends beyond a test report

An emissions or immunity report records results for a defined equipment under test, configuration and test programme. It does not automatically establish that every production variant, accessory, cable or operating state is covered.

Regulatory teams should expect questions about the relationship between the tested sample and the final product. A laboratory may need this information to construct a representative test setup. A conformity assessment body may examine it when considering whether the evidence supports the stated product range. Manufacturers following a self-certification route need the same reasoning for their own technical file.

The manufacturer or responsible economic operator remains responsible for identifying the applicable legislation, standards, conformity assessment procedure and documentation obligations. The GOV.UK guidance on UKCA marking and the European Commission's CE marking guidance provide useful regulatory starting points, but product-specific requirements still need to be established.

EMC Hire's guidance on EMC testing and CE marking explains how test work can contribute to the wider conformity process. Testing is evidence within that process, not a substitute for the complete assessment.

Product identity and intended use

Start with an unambiguous product description. Model numbers, hardware revisions, printed circuit board revisions, firmware versions and build status should match the sample presented for testing. If a label says revision C but the report identifies revision B, a later reviewer cannot safely assume that the products are electrically equivalent.

The intended use sets the context for selecting standards and configurations. Useful information commonly includes:

• the product function, users and intended electromagnetic environment;
• installation method, including fixed, portable, vehicle-mounted or rack-mounted use;
• mains supply characteristics and any external DC supplies;
• external ports, maximum supported cable lengths and specified cable types;
• required peripherals, antennas, loads, sensors and accessories;
• environmental or enclosure restrictions stated in the user instructions;
• safety-related or performance-related functions that must be monitored during immunity tests.

Environment descriptions should be specific enough to support the engineering judgement. Terms such as residential, commercial, light industrial, heavy industrial, automotive or controlled military environment carry different EMC implications. A bare statement that a product is for “professional use” may not resolve the applicable emissions limits, immunity levels or installation assumptions.

Standards selection and the compliance rationale

A test laboratory may ask which standards have been selected, which editions apply and why they are suitable for the product. Product-specific or product-family standards normally take precedence where their scope covers the equipment. Generic standards may be appropriate where no more specific standard applies, but that decision should be recorded rather than assumed.

The standards list should distinguish emissions requirements from immunity requirements. CISPR 32, for example, contains multimedia equipment emissions requirements. The IEC 61000-4-x documents are basic immunity test methods called up by product or generic standards. IEC 61000-4-6 describes conducted RF immunity methodology and is not a conducted emissions limit standard.

Check the latest active edition and any applicable national adoption, amendment or transition arrangement. Also confirm product scope, ports, limits, frequency ranges, performance criteria, operating modes and test configurations. Customer specifications and contractual programmes may impose additional requirements, particularly in defence, automotive and aerospace projects.

Where a standard does not address a relevant characteristic, the technical file may need a documented EMC risk assessment or gap analysis. That could include an unusual RF environment, long field cables, high-power transmitters nearby or a product mode omitted from a standardised configuration. The reasoning matters. A bare standards list does not show why the resulting programme is adequate.

The test setup must represent foreseeable operation

Laboratories regularly ask for installation drawings, cable schedules and operating instructions before the test date. This is not administrative housekeeping. An incorrect test setup can alter common-mode current paths, antenna efficiency and coupling into susceptible circuits.

For conducted emissions on relevant power ports, a suitable LISN provides a defined impedance and measurement connection. Its use, supply arrangement, earthing and cable placement must follow the applicable method. Substituting an arbitrary mains filter or extension lead can suppress or reshape disturbances, producing data that cannot be compared reliably with the required limit.

Radiated emissions depend strongly on cable routing, enclosure bonding, attached peripherals and equipment orientation. Coiling excess cable tightly may reduce its effective antenna length and understate emissions. Spreading every cable artificially across the ground plane can create the opposite problem. The configuration should reflect the applicable standard and foreseeable installation while seeking representative worst-case emissions.

Immunity setups require equally careful definition. A CDN used for conducted RF immunity under an applicable IEC 61000-4-6-based programme is not interchangeable with a BCI probe required by a specified automotive, military or aerospace current-injection method. Coupling device, calibration arrangement, injection position and monitored performance criteria must match the called-up procedure.

Photographs should show cable positions, support heights, auxiliary equipment, bonding and orientation. Record dimensions where position affects repeatability. A photograph taken from across the chamber rarely provides enough detail to rebuild the arrangement six months later.

Variants, accessories and worst-case selection

Variant coverage is one of the harder evidence questions. Products may share an enclosure and trading name while containing different processors, displays, power supplies, radio modules or interface populations. Those differences can change clock spectra, cable currents, immunity behaviour and enclosure resonances.

A laboratory may ask for a variant matrix showing the differences and the engineering basis for selecting the tested configuration. The highest clock frequency is not automatically the worst case. A slower processor with stronger edge rates, a different DC-DC converter or an additional unshielded cable can dominate the result.

Accessories also need control. Include part numbers or clear descriptions for power adaptors, harnesses, docking stations, antennas and representative loads. If several external power supplies are permitted, evidence may be needed to justify whether one result covers all of them. Treating a materially different supply as an administrative variant can leave conducted and radiated emissions insufficiently assessed.

Operating modes and immunity performance criteria

The EUT should exercise functions likely to maximise emissions and expose susceptible behaviour. A communications product sitting idle may produce a clean trace that says little about operation at maximum data throughput. Likewise, testing a motor controller with no representative load can miss switching and regeneration conditions relevant to its intended use.

Provide a reproducible operating procedure, software version and means of monitoring the product. For immunity testing, define what constitutes acceptable performance before testing starts. Statements such as “no malfunction” are often too vague. Specify whether temporary degradation is allowed, whether operator intervention is permitted and how data integrity, communications, outputs or safety-related functions will be checked.

Automated monitoring can help, provided that the monitoring equipment does not create a new coupling path. Long unfiltered Ethernet or oscilloscope leads entering the test volume can affect both emissions and immunity. Fibre links, filtered interfaces or suitably isolated monitoring methods may be preferable where technically appropriate.

Calibration, raw data and traceability

Expect requests for equipment identities, calibration status, transducer factors, uncertainty information where relevant and confirmation of the detector and measurement settings used. Peak, quasi-peak and average detectors serve different purposes in emissions work. Resolution bandwidth and frequency range must follow the applicable standard rather than a convenient analyser preset.

EMC Hire uses test equipment with calibration traceable through an appropriate ISO/IEC 17025 accredited calibration provider. The accreditation relates to the relevant calibration provider or activity, not to the physical instrument. Suitable traceable calibration supports repeatability, comparison between development and formal measurements, and confidence in recorded engineering data.

Retain more than the final pass or fail table. Useful records include exploratory scans, final measurements, ambient observations, photographs, EUT monitoring logs, deviations and details of any modification made during testing. If a ferrite, bonding change or firmware update was introduced, the report should make clear which configuration generated the final data.

Information about laboratory accreditation can be checked through the United Kingdom Accreditation Service. Where a contract or sector requires accredited testing, confirm that the laboratory's current scope covers the specific method, standard and activity required rather than relying on a general accreditation statement.

Typical scenario

Consider an illustrative industrial controller offered with two processor boards, three plug-in communications modules and two approved external power supplies. The regulatory team has one working prototype and a fixed launch date.

The first decision is whether a single configuration can reasonably represent the range. Engineering review may identify the faster processor, the noisiest converter, the longest external cable and the communications mode with continuous traffic as likely contributors. That does not justify assembling an impossible combination if customers cannot purchase it. The selected setup must remain a valid production configuration.

Early pre-compliance work can compare modules using conducted emissions measurements on relevant power ports, radiated emissions scans and applicable immunity investigations. This does not prove compliance, but it can expose a poor enclosure bond or power supply variant before the final housing and production tooling are fixed.

EMC Hire can support the equipment selection, provide suitable hire equipment, arrange accessible pre-compliance work, undertake on-site testing where the product cannot readily be moved, or provide access to an EMC test facility. Formal compliance testing may then generate controlled evidence for the technical file, Declaration of Conformity and internal approval process where the chosen conformity route permits it.

For defence, automotive or aerospace programmes, EMC Hire can provide pre-compliance engineering support. Final evidence may need to come from an appropriately accredited laboratory where the contract, regulator or programme requires it.

When to Hire EMC Equipment

Hiring is technically sensible when the test requirement is defined but irregular. A regulatory team may need a CISPR receiver, LISN, current probe, ESD simulator or conducted immunity equipment for two development windows each year. Purchasing can leave expensive equipment unused while calibration, servicing, storage and accessory control continue.

A defined hire period also allows the equipment to be matched to the current standard and frequency range. That reduces the risk of buying an analyser with inadequate performance, a LISN intended for the wrong supply conditions or a coupling device that future programmes cannot use.

Project peaks are another common reason. Extra equipment can allow parallel debugging while a formal sample is being prepared, avoiding competition for an internal compliance bench. Hiring does not remove the need for competent setup or a written test plan, but it can provide measured, calibrated data without committing capital to a capability that may not suit the next product generation.

Common EMC Testing Mistakes to Avoid

Testing an undocumented engineering sample

If board revision, firmware and modifications are not recorded, the report cannot be tied confidently to production hardware. Capture the as-tested state before the sample enters the laboratory.

Choosing a convenient rather than representative mode

Idle operation can suppress clock activity, switching load and interface traffic. The resulting pass may offer false confidence because the marketed function was never meaningfully exercised.

Changing cable routing between scans

Moving a cable alters its coupling and radiation. Without photographs and position records, an apparent design improvement may simply be a setup change and cannot be reproduced.

Applying the wrong network or injection device

A LISN belongs to conducted emissions measurements on applicable power ports. A CDN supports applicable conducted RF immunity methods, while BCI probes serve specified current-injection procedures. Using the wrong device invalidates the physical coupling model and usually the evidence.

Recording only final compliant points

Missing exploratory data, ambients and configuration notes makes later diagnosis difficult. It also weakens the explanation if a derivative product produces different results.

Assuming one variant covers the family

Shared branding is not technical equivalence. Differences in power conversion, processing, interfaces and enclosure construction should be assessed and the coverage rationale retained.

Frequently Asked Questions (FAQs)

Does a test report alone provide sufficient EMC compliance evidence?

Not usually by itself. The technical file may also need product identification, standards rationale, risk assessment, variant justification, test configurations, instructions and evidence linking the tested sample to production. The exact requirement depends on the applicable legislation and conformity route.

Will a notified body always be involved in EMC conformity assessment?

No. Some regimes allow manufacturer self-assessment where the applicable conditions are met. Notified bodies relate to EU conformity procedures, while UK approved bodies perform defined functions under relevant UK legislation. The manufacturer should confirm whether third-party involvement is required or voluntarily chosen.

How much test setup detail should be retained?

Enough for a competent engineer to reconstruct the material configuration. Record cable types and positions, support arrangements, EUT orientation, accessories, software, operating mode, monitoring, grounding, bonding and deviations. EMC Hire's technical EMC FAQs provide further practical guidance.

Can pre-compliance data be included in the technical file?

Calibrated pre-compliance data can support engineering decisions, risk assessment and mitigation records. Its limitations should be stated, particularly where the setup differs from the formal method. It should not be presented as proof that formal requirements have been met.

Must every product variant be tested?

Not necessarily. A documented technical assessment may support representative or worst-case selection, depending on the product, differences and applicable requirements. Material changes may require additional testing. The reasoning should be specific and evidence-based.

What should be agreed with the laboratory before booking?

Agree the product scope, standards and editions, ports, variants, operating modes, performance criteria, accessories, test levels, frequency ranges, documentation and reporting expectations. EMC Hire's service FAQs can help resolve practical booking and equipment questions.

Preparing a defensible evidence package

A useful evidence package tells a coherent story from intended use and standards selection through to the tested sample, setup, results and production variants. Contradictions should be resolved before external review. A polished report cannot repair an unidentified sample or an unrepresentative operating mode.

EMC Hire can help regulatory and engineering teams review test requirements, select equipment, debug prototypes, arrange on-site measurements and plan formal compliance or pre-compliance testing. Test facility space is also available for teams needing a controlled environment without establishing a permanent in-house laboratory.

To discuss EMC compliance evidence, request an equipment hire quotation or book testing support, contact the EMC Hire engineering team on +44 (0)1462 817111 or email sales@emchire.co.uk.