From Lab to Market: The EMC Testing Process Explained for Product Managers
Most product managers meet EMC testing the same way: a launch date is set, engineering says the design is basically done, and then a test report arrives with a failure on it. Suddenly a board revision sits between you and your ship date, and nobody can tell you with confidence how many weeks it will cost.
The problem is rarely that the engineering was careless. It’s that EMC compliance gets treated as a gate at the end of development rather than a workstream that runs alongside it. Product managers who understand the process can plan for it, budget for it, and stop it from becoming the reason a launch slips.
You don’t need to know how to fix a grounding problem. You do need to know what happens at each stage, what each stage can cost you in time, and where your decisions actually change the outcome.
What you'll take away from this article:
-
The stages a product moves through from first prototype to legally marketable, and what each one produces
-
Where schedule risk concentrates, and which decisions are yours rather than engineering's
-
What to ask a test lab before you book, so the quote you get matches the work you need
Why EMC Belongs on Your Launch Plan, Not Just the Engineering Backlog
Electromagnetic compatibility is the requirement that your product neither emits disturbances that interfere with other equipment nor malfunctions when other equipment interferes with it. Both directions are regulated, and for most electronic products in most markets, meeting them is a legal precondition for sale rather than a quality nicety.
That legal framing is why EMC is a product management concern. A failed EMC test doesn’t degrade your product, it blocks your market access. The launch can’t proceed, no matter how good the rest of the release is, and EMC testing sits alongside safety as a core reliability gate that determines whether you can sell at all.
The practical consequence is that EMC belongs on the same plan as your firmware freeze and your tooling lead times, with its own duration, dependencies, and contingency.
Stage 1: Decide Which Markets You Are Entering
Everything downstream depends on this, and it’s a product decision rather than a technical one. Each market has its own rulebook, and the rulebook determines which tests you will pay for.
For the European Union, EMC obligations flow from the EMC Directive 2014/30/EU, usually alongside the Low Voltage Directive 2014/35/EU for electrical safety, and compliance is signaled by CE marking. For the United States, unintentional radiators fall under FCC Part 15, which distinguishes Class A equipment intended for commercial and industrial environments from Class B equipment intended for residential use.
Two decisions here have outsized effects. Adding a market late means adding a test campaign late, and choosing to sell into residential environments generally means meeting tighter emissions limits than a commercial-only product would. Both are cheaper to decide now than to discover in a test report.
Stage 2: Identify the Applicable Standards and Build a Test Plan
Directives state the essential requirements, but they don’t tell your engineers what to do on a bench. Harmonised standards do that, and the right standard depends on what your product is and where it will be used.
Measurement, control, and laboratory equipment, for example, is generally covered by EN IEC 61326-1, which sets both emissions limits and a suite of immunity tests, and the applicable CE marking route for measurement and laboratory products follows from there. A product's intended environment matters as much as its function, because industrial settings and residential settings carry different limits.
The deliverable from this stage is a test plan:
-
the list of tests
-
the standards and limits they are run against
-
the operating modes your product must be in
-
the performance criteria that define a pass.
Get this agreed before anyone books chamber time, because a vague test plan is the most common reason a quote and an invoice do not match.
Stage 3: Run Pre-Compliance Testing While Fixes Are Still Cheap
Pre-compliance testing is the single highest-leverage thing a product manager can schedule. It’s informal testing on representative hardware, run before the formal campaign, specifically to find problems while they’re still board revisions instead of launch delays.
The economics are simple. A layout or filtering fix found on a prototype costs a design iteration, while the same fix found after formal testing costs a retest, new documentation, and whatever the delay does to your launch window. This is why catching problems before the final test consistently protects schedules more effectively than any amount of optimism about first-time pass rates.
Pre-compliance also tells you something a launch plan needs and a pass/fail report never gives you: how much margin you have. A product that passes by a hair is a product that can fail later after a component substitution, so margin is scheduled insurance.
Stage 4: Formal Testing at an Accredited Laboratory
Formal testing is the campaign that produces the report your compliance documentation rests on. This is where accreditation matters, because ISO/IEC 17025 is the international standard for the competence, impartiality, and consistent operation of testing laboratories, and it’s what gives a test report credibility with customers and market surveillance authorities.
Your product will typically move through emissions testing, which measures what it puts out through the air and along its cables, and immunity testing, which subjects it to disturbances such as electrostatic discharge, radiated and conducted RF, fast transients, and surges. Understanding the distinction between radiated and conducted emissions helps you read the resulting report rather than just look for the word "pass."
Two logistics items are genuinely yours to own.
-
Your product has to arrive in a testable state, with the cables, accessories, and software builds it will ship with
-
Someone technical needs to be reachable during the campaign so that questions do not become idle chamber time.
Stage 5: When Something Fails, the Diagnose-Fix-Retest Loop
This is the stage that consumes launch dates, so it deserves explicit planning rather than hope. A failure isn’t a verdict, it’s the start of a loop: diagnose the mechanism, change the design, then retest the affected areas.
How long that loop takes depends almost entirely on the nature of the fix. A ferrite, a gasket, or a firmware change that restores normal operation after an upset can sometimes be resolved quickly, while a fix requiring a new board layout pulls in fabrication and assembly lead times and can extend well beyond the test itself.
The failures that hurt most are often placement and layout issues rather than missing components. In one GME case study on crosstalk in a monitoring system control unit, a product with legitimate protection parts still failed transient testing because the internal wiring and traces ran too far before reaching them. That class of problem is cheap to prevent and expensive to discover late, which is precisely the argument for Stage 3.
Two planning habits help here.
-
Build contingency into the schedule for at least one retest cycle
-
Ask your lab whether a partial retest of affected tests is acceptable rather than repeating the full campaign.
Stage 6: Compile Documentation and Declare Conformity
Passing isn’t the same as being legally marketable. For the EU, the manufacturer compiles a technical file, issues an EU Declaration of Conformity, and then affixes the CE marking, taking on legal responsibility for the claim. Test reports are evidence inside that file, not a substitute for it.
For most EMC and product safety scenarios in this space, this is a self-declaration route rather than third-party certification, which means the burden of getting the paperwork right sits with you. The Declaration of Conformity and its supporting documentation must be available if a national authority asks for them, so treat document assembly as a real task with an owner and a due date, not an afterthought once the report arrives.
Stage 7: Manage Changes After You Ship
Compliance describes the product you tested, not every product you will ever ship under that name. A component substitution, a supplier change, a new enclosure, or a significant firmware change can all affect EMC behavior, and a design change late in a product's life can quietly invalidate the basis of your original declaration.
The product management practice worth building is a simple change-review trigger: when a change touches power, grounding, shielding, cabling, clocks, or the enclosure, ask whether it needs re-evaluation before it ships. Answering that question with your test lab takes an afternoon. Discovering the answer through a field interference complaint costs considerably more.
What to Ask Before You Book a Laboratory
The quality of your first conversation with a lab largely determines whether the engagement goes smoothly, and a good partner will answer these directly.
-
Which standards and limits will you test my product against, and why those?
-
Is your accreditation scope current for those specific tests?
-
What do you need from me for the product to be testable on day one?
-
If we fail, can you help diagnose the cause, and can we retest only the affected tests?
-
What is the realistic calendar duration, including one retest cycle?
The last question matters more than the price quote. A lab that gives you a defensible schedule with contingency in it is telling you something useful about how they work, and choosing a test laboratory on technical depth rather than price alone tends to be the decision that protects the launch.
Plan EMC as a Workstream, Not a Gate
The product managers who never seem to lose launches to EMC aren’t the ones with luckier designs. They decide their target markets early, get a written test plan before booking chamber time, spend a little on pre-compliance to buy information, and hold schedule contingency for one retest cycle. None of that requires an EMC background. It requires treating compliance as a workstream with a duration.
Green Mountain Electromagnetics is an ISO 17025-accredited EMC and product safety laboratory in Vermont, working with measurement, control, and laboratory equipment manufacturers on exactly this process, from early pre-compliance through formal testing and documentation support.
Bring us your launch timeline and we'll tell you what the EMC path realistically looks like. We’ll walk through the standards that apply to your product, what testing it needs, and where to build contingency so your ship date holds.