Explore Cenitia’s compliance workflow and availability.Cenitia compliance workflow

How it works →
Cenitia
How it worksServicesLibraryGlossaryRegulationsToolsAbout
Reserve your spot
How it worksServicesLibraryGlossaryRegulationsToolsAbout

On this page

  • Define the example scope first
  • An unsigned declaration worksheet
  • Determine the assessment route from the requirements
  • Keep specifications tied to evidence
  • Issue and preserve the actual record
  • Primary references
← Library
tutorial·RED, RoHS, CRA·4 min read

Sample Declaration of Conformity — annotated walkthrough with template

An unsigned RED and RoHS declaration worksheet for a fictional radio product, with fields that require actual configuration and assessment evidence.

By Vladimír Vician · 14 June 2026 · Updated 5 October 2026

This is an unsigned worksheet for a fictional radio product. It is not a declaration issued by Cenitia, Inovasense or a customer. No product was tested or certified for this example. Replace every placeholder with supported facts and complete the applicable assessment before issuing a declaration.

Define the example scope first

Assume a radio sensor placed on the EU market in October 2026, with RED and RoHS applicable after a real scope review. RED covers its electrical safety and EMC requirements; standalone LVD and EMC are not added to the same radio equipment. A separately supplied mains adapter may require its own assessment.

Manufacturer CRA Article 14 reporting already applies to in-scope products, but the main CRA product-conformity obligations generally apply from 11 December 2027. This contemporary worksheet therefore does not pretend that an October 2026 CRA conformity assessment has been completed. For a later product, reassess CRA scope, transition, classification, requirements and declaration structure.

An unsigned declaration worksheet

Use RED Annex VI and RoHS Annex VI to check the required content. A combined declaration must satisfy the applicable structures; a fixed nine-field template is not a substitute for reading them.

FieldInformation to establish before issuance
Product identificationActual type, model, batch or serial identification and the covered configuration
ManufacturerActual legal name and contact address; representative details where applicable
Responsibility statementDeclaration issued under the manufacturer's sole responsibility
Object and traceabilityDescription and any illustration needed to identify the actual radio equipment
Applicable legislationOnly acts established as applicable: RED 2014/53/EU and RoHS 2011/65/EU in this conditional example
Standards or specificationsDated references actually applied, their scope and any partly applied provisions
Notified body, if applicableActual body, identification number, performed assessment and certificate reference
Additional informationRelevant configuration limits or other necessary information
Issue and signatureActual place/date, authorised signatory's name/function and signature on behalf of the manufacturer

This table is a preparation aid. It deliberately supplies no invented manufacturer, certificate, standard test result or signature. The real issued declaration must use the applicable wording and facts.

Determine the assessment route from the requirements

Under RED Article 17(2), the Article 3(1) requirements can use Annex II, III or IV. For Article 3(2) and 3(3), internal control depends on the Article 17(3) conditions; missing or partly applied harmonised standards require Annex III or IV under Article 17(4).

An EN 18031 title on a document does not establish full coverage. Check the exact OJ reference and restrictions in Decision 2025/138 and the actual product assessment. For RED, the notified-body number follows CE when the Annex IV procedure is used; type examination alone does not trigger that marking rule.

Keep specifications tied to evidence

Do not copy a list of EN 62368-1, EN 55032, EN 55035 or EN 18031 editions because another sensor listed them. Confirm each standard's scope, relevant OJ citation and the performed tests or alternative technical assessment for the final configuration. RoHS material evidence should address applicable substances, homogeneous-material limits and any justified exemption.

Keep the technical file and the declaration distinct. The declaration is the manufacturer's statement; the file explains the supporting evidence. A laboratory report for another antenna, power supply or firmware build needs a reasoned mapping before it supports the final product.

Issue and preserve the actual record

Review required languages and how the full or simplified declaration accompanies the equipment. Record the true issue date; do not backdate a document or pre-authorise unknown future firmware releases. Retain issued versions and the units they cover. Reassess significant design, software, intended-use and legislative changes.

The manufacturer remains responsible. An AI draft, QR record or worksheet completed with placeholders is not certification. See DoC 101, translation requirements and notified-body routes.

Primary references

  • RED: Articles 10, 17, 18, 20 and Annex VI
  • RoHS: Article 7 and Annex VI
  • EN 18031 OJ citations and restrictions: Decision 2025/138
  • Commission: CRA manufacturer reporting

FAQ

Frequently asked questions

  • Can I issue this worksheet as my declaration?+

    No. It contains no established product facts, performed assessment or signature. Complete the applicable declaration structure with verified facts and evidence, obtain the required review and issue the actual declaration on behalf of the manufacturer.

  • Should I list RED, LVD and EMC for the same radio product?+

    Standalone LVD and EMC do not apply to in-scope radio equipment; RED covers the relevant safety and EMC requirements. Separately supplied equipment can have its own scope. Include only legislation established as applicable to the declared product.

  • Must the declaration fit on one page?+

    No universal one-page limit applies. Use enough space to identify the product and provide the information required by every applicable declaration structure without sacrificing clarity or traceability.

Portrait of Vladimír Vician

Written by

Vladimír Vician

Founder, Cenitia · Founder & Managing Director, Inovasense s.r.o.

Founded Inovasense in Bratislava in 2016. Specialises in EU-sovereign hardware — FPGA and embedded systems design, embedded security, and regulatory compliance under the CRA, RED (EN 18031), and the harmonised standards each cites. Named signatory on every Declaration of Conformity Inovasense ships.

Best reached on LinkedIn. For longer enquiries, the Inovasense contact form.

Inovasense profile · More about Cenitia

Continue reading

Related guides

  • reference

    eIDAS and Declarations of Conformity — signature claims and evidence

    A concise overview of Cenitia’s signature record and its limits: issuance evidence does not establish a qualified eIDAS signature or product conformity.

    3 min read

  • reference

    Declaration of Conformity translation requirements — every EU language explained

    Separate declaration language, accompanying user information and authority requests; verify the applicable act and target Member State before translating.

    3 min read

  • guide

    Updating a Declaration of Conformity after a regulation amendment

    When a cited EU regulation or harmonised standard is amended, the Declaration of Conformity may need to be reissued. This guide explains when, how, and what to retain.

    9 min read

  • guide

    Declaration of Conformity 101 — what it is, who needs it, how it's signed

    How to identify applicable EU declaration requirements, confirm product evidence, choose language and signatory, and retain an issued declaration.

    4 min read

Put this into practice

Free tools & references

  • EU Directive SelectorDescribe your product and find which EU directives and regulations apply.Open tool →
  • Do I need a Notified Body?Find out, per regulation, whether a Notified Body is required.Open tool →

New to the terminology? Browse the compliance glossary — plain-English, citation-backed definitions of every term above.

Explore Cenitia’s compliance workflow

Review the supported scope and workflow

← Back to Library

Cenitia

The EU compliance engine for hardware manufacturers. Cited drafts, electronic signing, regulation watching — all in one place.

A product of Inovasense s.r.o., Bratislava, Slovakia · Data hosted in Stockholm, EU

Site

  • How it works
  • Expert services & pricing
  • Library
  • Glossary
  • Regulations
  • By product type
  • Tools
  • About

Legal

  • Imprint
  • Privacy
  • Terms

© 2026 Inovasense s.r.o. · cenitia.com

Operated in Slovakia · Evidence, expert review and clear service scope