CE Test Plan for a Connected Device Before You Book a Lab

A useful CE test plan tells the laboratory exactly which product configuration, interfaces and operating modes it will assess, and why the proposed tests address the applicable requirements. Booking “the CE test” without that information invites missing coverage and expensive repeat visits.

Use the lab brief and matrix before requesting a quotation. This is a planning workflow for connected electronics. It is not a prescribed test programme for every device.

Freeze a reference configuration

Record hardware revision, firmware hash, enclosure, supply, battery, antennas, cables and accessories. Include production tolerances and variants. Give every specimen an identifier so the report can later be traced to the configuration on sale.

If the design is still changing, tell the lab. A pre-compliance session can answer design questions without being presented as final release evidence. Record which results are exploratory and which form part of the eventual conformity assessment.

Firmware used to force a transmit mode needs its own identity. Explain how that mode relates to normal operation and whether it changes duty cycle, power control or coexistence behaviour. An undocumented “test build” can make a report difficult to interpret.

Agree the legislative scope first

For radio equipment, RED covers safety, electromagnetic compatibility and efficient use of radio spectrum through its essential requirements. Applicability of additional requirements depends on the equipment and current legislation. The Commission's RED portal is the starting point; the actual directive and applicable acts govern the assessment.

Do not mechanically apply standalone EMC and LVD assessments to every radio product. Ask the conformity specialist to document the legal basis for the complete product and any separately supplied equipment. Address RoHS documentation separately from the radio chamber schedule.

The lab proposal should identify standards and editions, methods, assumptions, exclusions and the conformity assessment route. Check relevant Official Journal citations and restrictions before agreeing that a particular standard provides the intended coverage.

Describe modes by the risks they expose

These are candidate modes, not a claim that all require the same test. The lab and product specialist select the relevant combinations and explain omissions. “Worst case” needs a reason: highest radio power is not necessarily worst for every EMC or safety question.

A model configuration decision

A fictional wall sensor ships with USB power and two antenna options. Engineering proposes testing only its low power idle state because that is how most users operate it.

The brief instead identifies charging plus active transmission as a candidate condition, asks whether both antenna options are covered and describes the maximum permitted cable arrangement. The reviewer has not concluded which tests are mandatory; the improved brief makes that decision possible.

Keep this distinction in your records. A planning hypothesis does not become a measured finding until a test is performed and documented.

Prevent avoidable surprises on the test day

Provide connection diagrams, working instructions, login arrangements for any test UI, spare units and a responsible engineer who can answer configuration questions. Avoid sharing production customer credentials. Make the specimen recoverable without changing its relevant settings unnoticed.

Agree how failures, repairs and deviations will be recorded. If a filter is added during testing, the final report must identify the changed configuration. Passing results for a hand modified sample do not automatically cover the unchanged production design.

Ask what raw evidence will be retained and what the report includes. Photographs, cable arrangements, specimen IDs and software versions can be as important to later traceability as the results table.

Close the loop after the laboratory

Map each report back to the requirement and product variant in the matrix. Record uncovered conditions, remaining design actions and who accepts the final evidence. Update manufacturing drawings and release records if the assessed configuration changed.

For the technical file structure, see our IoT technical file template. No measurements or pass results are claimed here.