An evidence-based approach: writing documentation replaces neither necessary testing nor regulatory assessment.
Identify applicable requirements
Scoping starts with the product, its intended use, interfaces, versions and the role of each economic operator. CE marking is a regulatory process, not a certification that we issue.
- Identify legislation applicable to CE marking and the RED for radio equipment within scope, without treating every connected product as radio equipment.
- Review applicable cybersecurity requirements and their timelines, including RED and the Cyber Resilience Act where relevant to the product.
- Clarify manufacturer, importer and brand responsibilities, standards to examine and the applicable assessment route.
Assess risks and missing evidence
We map product risks and identified requirements to the available evidence, distinguishing documentation gaps from technical shortcomings.
- Risk analysis covering intended use, data, interfaces, failure scenarios and attack scenarios.
- A matrix of requirements, risks, available evidence, missing evidence and prioritised actions.
- Check that test reports match the hardware references, firmware versions and variants actually placed on the market.
Evaluate the product and its ecosystem
Assessment depth depends on authorised access to the device, firmware, source code, application, APIs, documentation or test environment. Access limitations and areas not assessed are recorded.
- Firmware: exposed interfaces, authentication, secrets, components, boot mechanisms and updates.
- Application, communications and associated services: access control, encryption, network exchanges, APIs and cloud dependencies.
- Evidence-backed findings, remediation recommendations and further checks within the agreed scope, without guaranteeing the absence of vulnerabilities.
Build usable technical documentation
We organise existing evidence and prepare missing documents that can be supported by verified information. Draft documents remain clearly identified as drafts.
- Product description, architecture, references, versions, risk analysis, existing reports and an evidence index.
- Prepare instructions, warnings, traceability information and draft EU declarations of conformity.
- A declaration cannot be finalised through document writing alone: sufficient technical evidence and validation and signature by the authorised responsible party are required.
Document device-generated data
We identify information about data generated by the product and related services, considering Data Act requirements and personal data protection where applicable.
- Types of generated data, formats, estimated volume, collection frequency, storage and retention.
- Methods for accessing, retrieving and sharing data and identification of the relevant contacts.
- Prepare user information, including pre-contractual disclosures where required by the applicable rules.
Identify and coordinate further testing
Regulatory assessment, cybersecurity analysis and documentation are distinct from physical testing. Radio, EMC, electrical safety and other tests are identified for the product and assigned to competent providers when needed.
- A testing plan defining samples, configurations and expected evidence.
- Technical coordination with laboratories or bodies required by the selected assessment route, without implying any existing partnership.
- Review results, track gaps and update documentation; regulatory conclusions remain conditional on results and the assessed scope.