CE Marking Consultants In The Eu

Scope and evidence must be confirmed before any paid tests or filings.

A CE marking consultant is most useful before testing is booked or a declaration is drafted. The first job is not to “obtain a CE certificate”; it is to determine whether CE marking applies, identify every relevant EU legal act, choose the permitted conformity-assessment route, and decide what evidence is still missing for the exact product configuration.

The manufacturer remains responsible for conformity assessment, the technical documentation, the EU declaration of conformity and the CE marking. A consultant can structure the analysis and challenge gaps, but cannot transfer that legal responsibility. For products touched by several EU rules, the practical objective is one coherent compliance position in which each requirement is mapped to evidence and no report is relied on outside its scope.

Start with the facts that can change the legal route

A reliable strategy starts with a product boundary, not a generic list of directives. Before selecting standards, a laboratory or a notified body, assemble the facts that can move the product into or out of a legal scope or change the conformity-assessment procedure.

Product identity and variants: model families, options, accessories, software/firmware versions and which variants will share evidence.
Intended use and users: what the product is designed to do, foreseeable use, professional/consumer setting and any safety-critical function.
Technical characteristics: voltage, radio functions, pressure, moving parts, energy sources, substances/materials, protective functions and other scope-relevant features.
Supply-chain role: who designs, manufactures, has the product made, brands it and places the final product on the EU market.
Existing evidence: reports, certificates, risk assessments, drawings, bills of materials, declarations from suppliers and their exact model/scope references.
Change history and launch plan: current design maturity, pending substitutions, firmware releases, target configuration and the date/market context in which the product will be placed on the market.

Multi-act route decision matrix

A product can fall under more than one EU directive or regulation. The strategy therefore has to be built requirement by requirement: establish applicability, then identify the assessment route under each applicable act, then reconcile the evidence into one technical file.

Decision	Questions to resolve	Strategic consequence
1. Is CE marking required for this product?	Which Union harmonisation acts cover the product, and do they provide for CE marking? Are there scope exclusions?	Do not affix CE marking merely because a customer asks for it. First document the legal basis for every applicable act.
2. Which acts apply simultaneously?	Which functions, hazards or intended uses trigger separate rules? Does one act address a different aspect of the same product?	Build a requirements map by act and avoid assuming that compliance with one regime satisfies another.
3. Which conformity route is permitted?	Does the applicable act allow manufacturer internal control for this product/class, or require third-party involvement or another module/system?	Select the route from the legislation before appointing a laboratory or notified body.
4. Which standards will be used?	Which harmonised standards are currently relevant and cited, and which requirements remain outside their coverage?	Use standards as evidence tools, not as substitutes for checking the legal essential requirements.
5. Can evidence be shared?	Does an existing report cover the same model, configuration, test method, requirement and relevant version of the standard?	Reuse only within demonstrated scope; record why the evidence is transferable or why supplementary work is needed.
6. What blocks the declaration?	Which applicable requirement lacks credible evidence, contains a contradiction, or depends on an unresolved design decision?	Prioritise blocking gaps before polishing documentation or commissioning non-critical work.

The output of this matrix should be a documented route decision, not a shopping list of tests. Where the legislation requires a notified body, its designation must be checked for the relevant legislation and task; the fact that an organisation is notified in one area does not make it competent for every CE regime.

Evidence reuse and gap analysis: test the scope, not the logo

Existing certificates and reports can reduce unnecessary work, but only after their scope is compared with the product and the legal requirement being supported. A CE mark on a component does not automatically prove conformity of the assembled final product.

Evidence item	Reuse test	Typical gap to flag
Supplier test report	Same component/model, relevant configuration, method, standard edition and operating conditions?	Report covers a different variant, old standard edition or isolated component conditions.
Supplier EU declaration	Does it identify the component and applicable legislation relevant to the claim being reused?	Declaration is generic, model reference is unclear or it addresses a different regulatory object.
Previous product-family report	Is the new variant technically equivalent for the tested characteristic, with the difference justified?	Design delta can affect the tested outcome but no engineering bridge is documented.
Risk assessment	Does it cover current intended use, hazards, protective measures and residual risks?	Risk file predates a design, software, supplier or use change.
Drawings/BOM/specification	Do controlled documents match the tested and production configuration?	Technical file and production baseline identify different parts or revisions.
Notified-body certificate, where applicable	Does the certificate cover the exact product/type, conformity task and current conditions?	Certificate exists, but its scope does not cover the new variant or required module/system.

The useful deliverable is a traceability matrix: requirement → evidence → scope/variant → status → action. This exposes both missing evidence and duplicated work, and makes later changes easier to assess.

Technical-file preflight before execution

A technical-file review should challenge consistency, not just count documents. Before the final declaration is signed, test whether a market-surveillance reviewer could follow the chain from product identity and applicable requirements to the evidence and the production configuration.

Product description and model/variant boundaries are unambiguous and match labels, reports and declarations.
Applicable EU acts are listed with a reasoned scope conclusion; exclusions and borderline assumptions are recorded where material.
Essential or other mandatory requirements are mapped to standards, calculations, risk controls, tests or other evidence.
Applied harmonised standards and editions are identified; partial application and non-harmonised methods are explained instead of being silently treated as full coverage.
Risk assessment reflects intended use, reasonably foreseeable misuse and the current design safeguards.
Test reports and certificates can be traced to the same hardware, software/firmware and critical components represented in controlled drawings/BOMs.
User instructions, safety information and markings are consistent with the risks and restrictions used in the conformity argument.
Where a notified body is involved, its certificate/task/scope and identification data correspond to the route actually selected.
The EU declaration of conformity is prepared only after the evidence set supports every applicable act and the signatory can assume responsibility for that conclusion.

Technical documentation must be prepared before placing the product on the market and retained for the period required by the applicable legislation. EU general guidance states ten years as the default unless the sector legislation specifies otherwise, so the sector-specific act must control the final retention rule.

Sequence the work to avoid expensive false starts

The order matters. Testing too early can produce a technically valid report that does not answer the final regulatory question; documentation too early can lock the file to a design that is still changing.

Freeze the decision baseline: exact product/variant, intended use, economic-operator role and planned EU market configuration.
Map legislation and requirements: record applicable acts, exclusions, classification assumptions and permitted conformity routes.
Inventory existing evidence: assess every report, certificate and supplier document for scope and transferability.
Close blocking gaps first: decide design actions, targeted testing, calculations or notified-body tasks only after the route is fixed.
Reconcile the technical file and declaration: confirm that final production configuration, evidence, instructions, markings and declarations tell the same story.

Detailed execution belongs on the dedicated pages for CE marking consultancy ; CE marking services ; CE marking cost ; CE documentation and registration ; CE compliance testing .

When testing or a notified body belongs in the strategy

Neither “self-certification” nor “third-party certification” should be assumed across all CE products. The applicable legislation determines the conformity-assessment options. Testing may be needed to build evidence even where a notified body is not mandatory; conversely, a notified body may have a defined assessment task that is narrower than the whole technical file.

Check the product classification and the conformity-assessment module/system in each applicable act before requesting quotations.
If a notified body is required, verify in NANDO that the organisation is designated for the relevant legislation and assessment task.
Define the evidence question before the test: requirement, model/configuration, operating conditions, method and acceptance criterion.
Treat a test report as one part of the conformity case; do not let testing replace risk assessment, requirement mapping or design-control evidence.

This separation is important commercially as well: it lets the manufacturer buy only the testing or third-party assessment that the chosen route and unresolved gaps actually require.

Change-control map: when the route must be reopened

CE conformity is tied to a defined product and evidence baseline. A change does not automatically mean “start again”, but it should trigger a documented impact review whenever it can affect scope, classification, essential requirements, risk controls or the validity of relied-on evidence.

Change trigger	Review question	Possible action
New function or intended use	Does it bring the product within another act, classification or hazard set?	Re-run applicability and requirement mapping.
Critical component or supplier substitution	Does the change affect safety, EMC, radio, materials, pressure, performance or another assessed characteristic?	Bridge by justified equivalence or obtain targeted new evidence.
Hardware or enclosure redesign	Are tested paths, clearances, protection, thermal behaviour or mechanical risks changed?	Review risk controls and affected test coverage.
Firmware/software update	Can the change alter a safety, radio, control or protective function?	Assess software change impact and repeat only affected verification where justified.
Standard or legislation update	Has the legal requirement, transition, OJ citation or presumption-of-conformity basis changed?	Review the compliance basis and transition obligations before the relevant market date.
New model/variant under an existing family	Is the variant genuinely covered by the family rationale and existing evidence?	Document equivalence or create a delta assessment and close new gaps.

What to send a consultant for a useful route opinion

A vague request for “CE certification” usually produces a vague quote. A compact evidence pack lets the adviser answer the real question: what rules apply, what can be reused, what is missing and which decision comes next.

Product name, model list, photographs and a concise functional description.
Intended use, users, environment and any prohibited or safety-critical uses.
Architecture/block diagram plus key electrical, radio, mechanical, pressure or other relevant characteristics.
Current BOM or list of critical components and any planned substitutions.
Existing EU declarations, supplier certificates, test reports and risk assessments in their complete versions.
Applicable-standard list already used by engineering, including editions/dates if known.
Labels, draft instructions, warnings and current technical-file index if one exists.
Planned launch configuration and a list of unresolved design, supplier or firmware changes.

A competent strategic review should return assumptions and boundaries, not just conclusions. If a fact is missing and it could change the legal route, it should be listed as an open decision rather than guessed.

Official sources to verify the final route

The exact sector legislation remains controlling. These official EU sources are useful starting points for the general CE framework, technical documentation, declarations, standards and notified-body verification.

Frequently asked questions on CE marking strategy

Can a CE marking consultant issue a CE certificate for every product?

No. CE marking is not a universal certificate sold by a consultant. The permitted conformity-assessment route depends on the applicable EU legislation. Some routes are based on manufacturer responsibility without a notified body; others require a designated third party for defined tasks. The route must be established before anyone promises a “certificate”.

If all major components are CE marked, is the final product automatically compliant?

No. Component declarations and reports may be useful evidence, but the manufacturer of the final product remains responsible for the conformity of the final configuration. Integration can create new hazards or alter EMC, radio, mechanical, thermal or other characteristics, so component evidence has to be assessed for scope and relevance.

Do we have to use harmonised standards?

In general, use of harmonised standards is voluntary, but standards whose references are appropriately cited can provide a presumption of conformity for the requirements they cover. If a standard is not used, is only partly used, or does not cover a requirement, the technical file should explain the alternative evidence and reasoning. Product-specific legislation must always be checked.

Can an old test report be reused for a new model?

Sometimes, but only after a documented equivalence or delta analysis. Check the tested model, critical components, construction, firmware, operating conditions, test method, standard edition and the requirement being supported. If a difference can affect the result, targeted new evidence may be needed.

What is the first deliverable to request from a CE consultant?

For a complex or multi-regime product, request a written applicability and route map with assumptions, open questions, applicable acts, conformity route, evidence inventory and blocking gaps. That gives engineering and procurement a defensible basis for deciding which testing, documentation or notified-body work should happen next.