How to build an EMC technical file

An EMC test report can show what happened to one sample on one day. An EMC technical file must explain why that evidence supports the compliance claim for every product placed on the market.

That distinction catches out otherwise well-run projects. Passing results are useful, but without an identified product configuration, applicable requirements, design records and controlled supporting evidence, the file may not withstand customer scrutiny, internal audit or regulatory review.

What an EMC technical file needs to demonstrate

An EMC technical file is the organised body of evidence supporting the manufacturer's conformity assessment. For EMC, it should create a traceable chain from the product and its intended electromagnetic environment through to the standards selected, tests performed, results obtained and controls applied to production.

The file is not merely a folder of laboratory reports. It should allow a technically competent reviewer to answer four questions:

• What product and configuration does the compliance claim cover?
• Which legislation, standards and technical requirements were considered?
• What evidence shows that emissions and immunity risks have been addressed?
• How is continued conformity controlled when hardware, firmware or suppliers change?

The applicable legal route depends on the product, market and economic operator. Manufacturers should check current official guidance, including the relevant GOV.UK guidance on UKCA marking, and obtain specialist advice where interpretation is uncertain. Testing alone does not complete every conformity obligation.

A practical EMC technical file checklist

Define the product before presenting the evidence

Start with an unambiguous product identity. Record the model, variants, hardware revision, PCB revision, firmware version, power supply, cables, accessories and optional modules covered by the assessment. Include photographs, block diagrams and relevant assembly drawings.

Variant coverage deserves particular attention. A report for a basic model does not automatically cover a higher-power version, a longer cable set or an optional radio module. If variants are grouped, document the engineering rationale for selecting the representative worst-case configuration. Otherwise, the file contains an assumption rather than design evidence.

Identify legislation and product scope

List the legislation considered for each target market and explain why it applies. A product containing intentional radio functionality may need a different conformity route from non-radio electrical equipment. Machinery, automotive components, medical equipment and defence products can also sit within sector-specific frameworks or contractual schemes.

Record the manufacturer's decision, not just the conclusion. Scope notes, intended use, foreseeable operating conditions and exclusions help a later reviewer understand the reasoning. The responsible manufacturer or economic operator remains accountable for confirming the applicable legislation and conformity assessment route.

Create a standards selection record

List the product-specific or product-family standards used, including edition and amendment status. Generic standards should normally be considered only when no more appropriate product standard covers the equipment and environment.

Product standards may define emissions limits, immunity test levels, performance criteria, port applicability and operating modes. Basic immunity methods such as the IEC 61000-4-x series describe test techniques, but they do not by themselves establish the complete product requirement. Record which product standard calls up each method and why the selected ports and configurations are applicable.

Standards change. Use the latest active editions appropriate to the conformity route and verify test levels, frequency ranges, limits, equipment configurations and documentation requirements against the published documents. EMC Hire's EMC standards guidance can help teams structure that initial review, while current documents should be obtained through an authorised source such as BSI.

Document the EMC risk assessment

The risk assessment should connect the product's electromagnetic environment to credible emission and immunity phenomena. Consider mains and DC power ports, signal and control cables, enclosure apertures, radio transmitters, inductive loads, electrostatic discharge, surge exposure and nearby high-current equipment where relevant.

A warehouse controller connected by a 30-metre unshielded cable has different coupling paths from a battery-powered bench instrument. Treating both as generic electronic products can leave a significant port untested or apply an unrealistic operating environment.

For each identified risk, record the control measure and evidence. That evidence might include filtering, shielding, PCB return-path design, transient protection, component ratings, simulation, inspection or testing. The assessment should also identify residual uncertainty and any installation restrictions required to maintain the intended EMC performance.

Preserve design evidence and engineering rationale

Useful design evidence includes schematics, PCB stack-up information, grounding architecture, filter calculations, shielding details, cable specifications and component selection records. The technical file need not expose every design detail to every party, but the manufacturer should retain enough information to explain the mitigation strategy.

Capture failed pre-compliance results and corrective work as well as final passes. A documented change from a high-inductance chassis connection to a controlled, low-impedance bond may explain why later results improved. Deleting that history removes valuable mitigation evidence and makes regression analysis harder.

Test reports that remain defensible

Test reports should identify the equipment under test, applicable method, test equipment, calibration status, setup, cables, support equipment, operating mode, environmental conditions where relevant, test levels, limits, detector settings and results. Photographs should show enough detail to reproduce cable routing, table arrangement, antenna orientation, bonding and auxiliary equipment placement.

For conducted emissions, the record should identify the relevant LISN arrangement and measured power ports. For conducted RF immunity, document the CDN or other coupling method required by the applicable procedure. A BCI probe belongs only in a current-injection method that specifies or permits it. Substituting these devices without technical justification changes the coupling path and weakens the evidence.

Record peak, quasi-peak and average detector results only where required by the applicable emissions method. Likewise, receiver resolution bandwidth must match the relevant standard and frequency range. A convenient analyser setting is not automatically a compliant setting.

EMC Hire uses test equipment with calibration traceable through an appropriate ISO/IEC 17025 accredited calibration provider. Suitable traceable calibration supports measurement accuracy, repeatability and comparison between development and formal testing. It does not, by itself, make a test compliant or mean that the physical instrument is accredited.

Control changes after testing

A technical file becomes unreliable if it is frozen while the product continues to change. Link engineering change control to the compliance process. Changes to clock frequencies, switch-mode power supplies, PCB layout, enclosure coatings, cable assemblies, filters, firmware timing or component sources can alter EMC behaviour.

Each relevant change should trigger a documented review. The outcome may be no further action, focused pre-compliance checks or formal retesting. State the rationale. A signed note explaining why a passive cosmetic change has no EMC effect is more defensible than silence, while replacing a shielded cable with an unshielded alternative usually warrants technical investigation.

Also retain the Declaration of Conformity, user instructions, installation restrictions, production controls and authorised approvals. For self-certification routes, the manufacturer must confirm the applicable legal requirements and ensure that the declaration and technical file remain consistent.

Typical scenario

Consider an illustrative industrial controller offered with two power supplies, three I/O configurations and optional long sensor cables. The initial formal test report covers one configuration, but it does not state the firmware mode or explain why that model represents the family.

The compliance manager first creates a configuration matrix. Engineering then identifies the highest-power supply, fastest interface activity and longest cable arrangement as likely emission or immunity worst cases, subject to confirmation through investigation. Pre-compliance conducted and radiated emissions measurements can compare variants before the formal programme. Immunity checks can exercise the functions whose degradation would carry the highest operational risk.

Early work often exposes documentation gaps as well as design problems. If cable routing changes the result by several decibels, the installation instructions and test setup need tighter control. Entering formal testing without resolving that variability risks an expensive repeat and leaves uncertainty over production installations.

EMC Hire can support equipment selection, pre-compliance EMC testing, on-site investigation, facility access and formal compliance testing where appropriate. The resulting calibrated engineering data can strengthen the technical file and improve confidence before a self-certification decision, but pre-compliance results should not be presented as automatic proof of conformity.

When to Hire EMC Equipment

Hiring is technically sensible when demand is short-term, irregular or tied to one development stage. A team investigating a six-week emissions problem may need a suitable receiver, LISNs, antennas, current probes and near-field probes, but ownership also brings storage, servicing, calibration and utilisation costs.

Defined hire windows let teams access equipment matched to the test plan without committing capital to an instrument that may be unsuitable for the next product family. Hiring also allows capability to scale during project peaks, particularly when several prototypes need comparison before a booked formal test date.

Equipment selection still needs engineering discipline. Frequency coverage, dynamic range, detector capability, transducer factors, power ratings and connector interfaces must suit the intended method. EMC Hire can help specify a practical setup, provide equipment for on-site debugging or combine hire with test-facility access. This reduces ownership risk while preserving a traceable record of what was used.

Common EMC Testing Mistakes to Avoid

Testing an unidentified configuration

A passing plot has little evidential value if the hardware, firmware, cables and operating mode cannot be traced. Record identifiers at the time of test, rather than reconstructing them from memory after the project closes.

Using an unrepresentative operating mode

Idle firmware may suppress clocks, communications and power-converter loading. The resulting emissions measurement can create false confidence, while immunity testing may fail to exercise the function most likely to show degradation.

Changing cable routing without recording it

Cables are often efficient common-mode antennas. Moving one cable relative to the reference plane can materially alter a radiated result. Photographs, dimensions and cable types are needed if the setup must be reproduced.

Confusing pre-compliance with formal evidence

Near-field probing and informal chamber measurements are excellent diagnostic tools, but their limitations must be stated. Presenting screening data as though it were a fully controlled standards-based result produces an unsuitable compliance evidence trail.

Applying the wrong coupling device

A LISN supports conducted emissions measurements on relevant power ports. A CDN is used for conducted RF immunity where required by the applicable method, while a BCI probe serves specified current-injection procedures. Treating them as interchangeable changes the physical test and may invalidate the conclusion.

Failing to preserve raw records

Keep instrument files, photographs, configuration sheets, calibration information and deviation records. A polished summary without underlying data makes later technical review, comparison or failure diagnosis much harder.

Frequently Asked Questions (FAQs)

Does a passing EMC test report complete the technical file?

No. It is one part of the evidence. Product identification, applicable legislation, standards selection, risk assessment, design evidence, change control, instructions and the relevant declaration are also commonly required.

Can pre-compliance data be included?

Yes, provided it is labelled accurately and its limitations are clear. Pre-compliance data can document design decisions, mitigation work and variant comparisons. It should not be represented as formal proof of compliance.

How should product variants be handled?

Build a variant matrix covering EMC-relevant differences, then document the rationale for representative or worst-case selection. Focus on power, clocks, interfaces, cables, enclosures, firmware and optional modules rather than relying only on commercial model names.

How long should EMC records be retained?

Retention periods depend on the applicable legislation and market. Check current official requirements for the product and economic operator. The file should remain accessible, controlled and linked to the versions placed on the market.

Is accredited testing always required?

Not in every self-certification route, but contractual, sector or regulatory requirements may call for an appropriately accredited laboratory. Defence, automotive and aerospace programmes often impose specific approval and evidence conditions. Confirm these before booking final testing.

What should be reviewed after a design change?

Assess whether the change affects coupling paths, switching behaviour, shielding, filtering, cable configuration, software activity or installation conditions. Record the decision and perform proportionate pre-compliance or formal retesting where the existing evidence no longer covers the design.

Build the file alongside the product

Retrospective document recovery is slow and uncertain. Building the EMC technical file through design reviews, pre-compliance work and formal testing produces a clearer evidence chain and makes gaps visible while they are still affordable to correct. The EMC test guides and CE marking support information provide further planning context.

To discuss an evidence gap, request an equipment hire quotation, arrange on-site testing, book space at the EMC Hire test facility or plan pre-compliance and formal compliance testing, contact the engineering team on +44 (0)1462 817111 or email sales@emchire.co.uk.