01 / PUBLIC TOOL
EU directive selector
Explore which EU legislation may be relevant to your product.
Open toolEuropean product compliance
The evidence
behind your
technical file.
Connect product claims to the right report, page and revision. See what needs checking before a draft moves forward.
For connected hardware. Start with the files you already have.
NXS-01 / EVIDENCE TRAILExample
DRAFT R03TECHNICAL FILE / SUPPORTING EVIDENCE
What supports
this configuration?
Current productNXS-01HW B / FW 1.4.2
“The radio evidence refers to the current hardware and firmware configuration.”
A linked source is the beginning of the review.
Illustrative product recordTry the full review
For teams building connected hardware
Industrial sensorsMonitoring devicesConnected electronics
A version number changes the question
Does this report
cover this product?
Follow one example from the current configuration to the source passage and a recorded review. The difference stays visible until a person resolves it.
The product
Nexus S1
Hardware revision B
Current firmware 1.4.2
Illustrative product
The question in the evidence
1.4.01.4.2
A different identifier needs supporting evidence or a documented assessment.
The review record
Keep the reason
with the reference.
Report version, page, product configuration and reviewer note travel together.
Work through the exampleThe working process
One product record,
from scope to revision.
A considered sequence for product teams. Define the scope, organise the evidence and make informed review decisions.
Explore the process- 01
Define the product.
Capture the configuration, intended use and features that shape the scope.
- 02
Bring the evidence together.
Keep datasheets, lab reports and component records beside the product.
- 03
Review with context.
Check the draft, its references and unresolved questions in one workspace.
- 04
Keep the record current.
Separate new revisions from signed records when the product or sources change.
A useful place to start
Start with the right
compliance questions.
The practical library
Practical guides for
connected hardware.
Start with one product
Start with the evidence
you already have.
Bring a datasheet, a report or an existing declaration. Discuss your use case and the right starting point.
Software subscription and specialist technical review have separate scopes.
Keep in touch
Your first workspace.
Register your interest to receive an availability update.
Product questions and requirements first. No documents are uploaded through this form.
Clear expectations
Before you begin.
Does Cenitia certify my product?
Cenitia helps organise product information, evidence and document drafts. The manufacturer and its qualified reviewers assess the content and the applicable conformity assessment route. Cenitia does not issue a product certification or replace a notified body.
Can I work with the evidence I already have?
Start with your datasheets, test reports and component records. File processing and human review are separate steps: an indexed file still needs to be checked for relevance to the product configuration.
What happens when the product changes?
Keep the new configuration and its review work separate from previously issued documents. Product versions, document revisions and source assessments preserve the context of each decision.
Who reviews the generated drafts?
Your team reviews the draft, its evidence and unresolved questions. Assigned review decisions are recorded against the relevant revision. Signing remains a separate action under the manufacturer’s responsibility.
Keep product context with the evidence
Review before signing
Preserve issued revisions