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.
By Vladimír VicianUpdated
Fact-checked against the law as of Reviewed by Vladimír Vician on How we check
A signed Declaration of Conformity is not a static document. EU legislation is amended, harmonised standards are revised and withdrawn, products are modified and manufacturers reorganise. This guide explains when a new version of the declaration is required, how to issue it and what to keep.
When the declaration must be updated
The product acts require the declaration to be kept current: it must be continuously updated under Article 18(2) of the Radio Equipment Directive 2014/53/EU (RED), Article 15(2) of the Low Voltage Directive and Article 15(2) of the EMC Directive, updated under RoHS Article 13(2), and updated as appropriate under Article 28(2) of the Cyber Resilience Act (CRA) once that provision applies on 11 December 2027.
The Commission's Blue Guide (2022/C 247/01, section 4.4) explains what this means in practice: as soon as any element of the declaration changes, the version has to be updated for products placed on the market after that change. It gives changes in the legislation, changes in the versions of the harmonised standards and changes in the contact details of the manufacturer or authorised representative as examples. Units already placed on the market stay covered by the version that was current when they were placed.
There are four kinds of trigger.
1. The legislation changes
- An amending act changes requirements that apply to the product. Read the amending act for its application date and transitional provisions, and identify the units affected. If the product has to change to meet the new text, change and reassess the product first; the declaration follows the assessment.
- New requirements become applicable under an act already cited. Delegated Regulation (EU) 2022/30 made RED Article 3(3)(d), (e) and (f) applicable to the radio equipment it lists from 1 August 2025. A declaration for such equipment placed on the market from that date has to rest on an assessment against those requirements.
- An act is replaced. The Machinery Regulation (EU) 2023/1230 applies from 20 January 2027 and replaces the Machinery Directive 2006/42/EC; machinery placed on the market before that date in conformity with the Directive may still be made available (Machinery Regulation, Article 52(1)). The Blue Guide (section 2.11), discussing earlier directives that were replaced by aligned versions, states that from the date the new directives took effect the declaration had to refer to them for products placed on the market to be considered compliant. A declaration for machinery placed on the market from 20 January 2027 therefore refers to Regulation (EU) 2023/1230.
The new version cites the legislation as it applies on the date of issue. The earlier version stays in the Technical File and continues to cover the units placed on the market before the new requirement applied.
2. A harmonised standard you cite is revised or withdrawn
When a harmonised standard is revised, the Commission decides the date on which the reference of the superseded edition is withdrawn from the Official Journal. Until that date both editions usually give a presumption of conformity; after it, only the revised edition does (Blue Guide, section 4.1.2.5).
- RED Article 10(5) requires changes in the harmonised standards or other technical specifications by reference to which conformity is declared to be adequately taken into account.
- The Blue Guide adds that the manufacturer must assess the changes to the superseded edition and take action where needed. What action depends on whether the changes are material for the essential requirements and whether they concern the product.
- Withdrawal of a reference does not automatically invalidate certificates already issued by notified bodies (Blue Guide, section 4.1.2.5).
- Once you rely on the revised edition, the declaration for units placed from then on cites that edition with its version and date (RED Annex VI, point 6).
Harmonised standards remain voluntary (Blue Guide, section 4.1.2.3). A standard that is cited in the Official Journal for the first time does not oblige you to adopt it or to reissue anything. If you do switch to it, for example to move from a notified-body procedure to internal production control under RED Article 17(3), reassess the product against it and update the declaration for units placed afterwards. You may also keep demonstrating conformity by other means, with the consequences the act attaches to that choice; under RED Article 17(4), that means a notified-body procedure for the requirements of RED Article 3(2) and 3(3).
3. The product changes
RED Article 10(5) requires changes in the design or characteristics of radio equipment to be adequately taken into account, and RoHS Article 7(e) says the same for electrical and electronic equipment. A change needs a new assessment, and usually a new declaration version, when it alters something the declaration states or relies on:
- A new radio function or internet connectivity can bring further essential requirements into scope. Under Delegated Regulation (EU) 2022/30, RED Article 3(3)(d) applies to internet-connected radio equipment.
- A feature that processes personal data in internet-connected, childcare, toy or wearable radio equipment brings RED Article 3(3)(e) into scope under the same Delegated Regulation.
- New accessories, components or software versions. RED Annex VI, point 8, lists the accessories, components and software covered by the declaration, so a change to them changes the declaration.
- A substantial modification under the Cyber Resilience Act. A product placed on the market before 11 December 2027 becomes subject to the CRA requirements only if it is substantially modified from that date (CRA Article 69(2)).
A change of colour, branding or packaging that leaves the identified product and its assessment untouched does not usually need a new version. Check that the product identification on the declaration still matches.
4. The parties or certificates named on the declaration change
- Manufacturer or authorised representative. A change of name or address changes point 2 of the declaration. The Blue Guide lists changes in the contact details of the manufacturer or authorised representative among the changes that require a new version for products placed on the market afterwards.
- Notified-body certificate. Where the declaration names a notified body and a certificate (RED Annex VI, point 7), the expiry or withdrawal of that certificate is not an administrative detail. The Blue Guide (section 4.1.2.5) describes products as able to be placed on the market until the end of the validity of the relevant certificates. Settle the conformity assessment basis first, by renewal or a new certificate, and then update the declaration.
- Signatory. The provisions cited in this guide say nothing about a signatory who later leaves the company or changes role, and the Blue Guide does not list it among its examples. A declaration signed by a person who was authorised at the time records what the manufacturer declared then. The next version is signed by a person who is authorised when it is issued.
Amending versus reissuing
The acts say that the declaration must be updated. They do not say whether to change the existing document or to issue a new one. The difference is one of record-keeping:
| Amend the existing document | Reissue as a new version | |
|---|---|---|
| Effect on the earlier record | The earlier text is overwritten | The earlier version is superseded and kept |
| Identification | Same number and date, different content | New date and, where a number is used, a new number or version |
| Traceability | It is hard to show which text covered a unit placed earlier | Each unit corresponds to one identifiable version |
This guide recommends reissuing. Assigning a number to the declaration is optional (footnote to RED Annex VI), but a number or version identifier makes the sequence easy to follow. The earlier version stays in the Technical File with the firmware version, hardware revision and Technical File version it corresponded to, so that the manufacturer can show which version covered a given unit when it was placed on the market.
The reissue workflow
- Identify the trigger: an amending act, the withdrawal of a standard's reference, a product change, or a change to the parties or certificate named.
- Assess the impact. Does the product still conform on the date the new requirement applies? What has to change in the Technical File?
- Update the Technical File: the applicable legislation, the standard editions applied, test reports and the risk assessment.
- Draft the new version with the true date of issue and, if you number declarations, the next number (for example DoC-2026-0042 followed by DoC-2026-0043).
- Sign the new version. It is signed by a person authorised by the manufacturer at the date of issue, with name and function. The product acts require a signature but prescribe no type. Under eIDAS Article 25, an electronic signature cannot be refused legal effect solely because it is electronic or not qualified, and a qualified electronic signature has the equivalent legal effect of a handwritten one. The legal effect of other electronic signatures is left to national law (eIDAS, recital 49). See the signature guide.
- Archive the earlier version in the Technical File for the retention period, with a note of the units it covered.
- Give the new version to those who must hold it. Importers keep a copy of the declaration at the disposal of the authorities (RED Article 12(8)), and an authorised representative keeps the declaration under its mandate (RED Article 11(2)(a); CRA Article 18(3)(a) from 11 December 2027).
- Update what accompanies the product. Each item of radio equipment is accompanied by the full or simplified declaration (RED Article 10(9)). Replace printed copies in stock and check that the internet address in a simplified declaration serves the current full text.
For products with digital elements, this workflow runs alongside the Cyber Resilience Act. Its Article 14 reporting duty has applied since 11 September 2026; the vulnerability handling obligations of CRA Article 13 apply from 11 December 2027. See CRA timeline and reporting obligations.
Detecting changes
An update is possible only if you know that something has changed. Three sources cover the triggers above:
- The Official Journal, L series, publishes amending acts and the Commission implementing decisions that cite harmonised standards and set the date on which a superseded reference is withdrawn. The Blue Guide (section 4.1.2.5) notes that it is in manufacturers' interest to check every publication of the list of harmonised standards and to verify the validity of the standards they have applied.
- Consolidated versions on EUR-Lex show, for each directive or regulation, the amending acts incorporated up to a given date. They are documentation tools without legal effect; the Official Journal text is authentic.
- Your own change records: engineering changes, firmware releases, certificate expiry dates and changes to company details.
Cenitia assists with a limited EU regulatory catalogue, evidence-linked drafts and recorded human review. Its watcher detects changes in validated supported source pages and prompts review. It does not automatically ingest national legislation, all OJ standard editions or clause-level changes, certify conformity, or reissue signed declarations.
What to retain in the Technical File
For each version issued, keep:
- The earlier declaration as issued (PDF or paper)
- The supersession record, for example "DoC-2026-0042 superseded by DoC-2026-0043 on 25 June 2026"
- The trigger for the new version: the amending act and its application date, the withdrawal date of a standard's reference, or the product change record
- The units covered by each version: serial number ranges and the dates on which they were placed on the market
- The Technical File version that supports each declaration version
The retention period is set by each act and runs from the placing on the market of the product, so each version is kept for the period that applies to the units it covered:
- RED Article 10(4), LVD Article 6(3), EMC Directive Article 7(3) and RoHS Article 7(d): ten years after the product has been placed on the market.
- CRA Article 13(13), from 11 December 2027: at least ten years after the product has been placed on the market or the support period, whichever is longer.
- MDR Article 10(8): at least ten years after the last device covered by the declaration has been placed on the market, and at least fifteen years for implantable devices.
Common reissue mistakes
- New declaration, old Technical File. The declaration cites the new legislation or standard edition but the Technical File still documents the old one, so the declaration is not supported by its evidence.
- Changing the document in place. The same number and date with different content removes the record of what was declared for earlier units.
- Leaving the authorised representative with the old version. The representative keeps the declaration at the authorities' disposal under its mandate, so it needs the current version and the superseded ones.
- Shipping with the old declaration in the box. Review stock of printed declarations and simplified declarations when a new version is issued.
- No record of which units each version covered. Without it, the manufacturer cannot show which declaration applied to a given serial number.
- Treating a new edition of a cited standard as a formality. Assess whether the changes are material for the essential requirements and whether they concern the product before deciding that nothing needs to be done.
Review the supported scope and workflow
Related from the Library
- Declaration of Conformity 101 — pillar context
- Sample DoC walkthrough — the annotated structure that gets reissued
- Technical File 101 — where the prior DoC version is retained
- CRA timeline and reporting obligations — the reporting and vulnerability handling duties under the CRA
Further reading
- Commission Blue Guide 2022 (2022/C 247/01): sections 2.3, 2.11, 4.1.2.3, 4.1.2.5 and 4.4
- Radio Equipment Directive 2014/53/EU: Articles 10, 11, 12, 17, 18 and Annex VI (consolidated 30 May 2026)
- Delegated Regulation (EU) 2022/30: radio equipment subject to RED Article 3(3)(d), (e) and (f) (consolidated 27 October 2023)
- Cyber Resilience Act, Regulation (EU) 2024/2847: Articles 13, 14, 18, 28, 69 and 71
- Machinery Regulation (EU) 2023/1230
- Regulation (EU) 2019/1020 on market surveillance: Article 16 (consolidated 12 August 2026)
- Regulation (EU) No 910/2014 (eIDAS): Article 25 (consolidated 18 October 2024)
FAQ
Frequently asked questions
When does a Declaration of Conformity need to be updated?
When any element stated on it changes: the product identification, the legislation or standards cited, the notified-body details, or the details of the manufacturer or authorised representative. The Commission's Blue Guide (section 4.4) says the new version is needed for products placed on the market after the change. A new edition of a standard does not by itself require a new declaration for units already placed: check its Official Journal status, the withdrawal date of the old edition and which units are affected, and keep the previous signed version.
What is the difference between amending and reissuing a DoC?
The product acts require only that the declaration is kept up to date; they do not distinguish the two. Amending means changing the existing document in place, which overwrites the record of what was declared for units already placed on the market. Reissuing means drawing up a new dated version that supersedes the earlier one, which is kept. Reissuing preserves the link between each unit and the declaration that covered it, so it is the approach this guide recommends.
How quickly must I reissue after a regulation amends?
Use the application dates and transitional provisions of the actual amending act, rather than its publication or entry-into-force date alone. Determine which units and obligations are affected, then complete any necessary assessment and declaration update before the applicable requirement becomes mandatory for those units.
Do I need to notify customers of a reissued DoC?
The declaration provisions cited in this guide contain no duty to notify customers of a new version. What they require is that the current version is in the right place: each item of radio equipment is accompanied by the full or simplified declaration (RED Article 10(9)), importers keep a copy for the authorities (RED Article 12(8)) and an authorised representative keeps it at the authorities' disposal (RED Article 11(2)(a)). Separately, Article 14(8) of the Cyber Resilience Act, applicable since 11 September 2026, requires a manufacturer to inform impacted users of an actively exploited vulnerability or a severe incident.
What if I miss a regulation amendment and continue to place product on the market?
Products must comply with the legislation applicable at the time they are placed on the market (Blue Guide, section 2.3). Units placed after a new requirement became applicable without meeting it are non-compliant, and a market surveillance authority can require corrective action under Article 16 of Regulation (EU) 2019/1020, including bringing the product into compliance. Units placed earlier are judged against the rules that applied when they were placed, subject to any transitional provision in the amending act. Establish which units are affected, complete the assessment and update the declaration.
Can the same DoC cover multiple firmware versions of the same product?
Yes, if each covered version is identified and its conformity has been demonstrated. RED Annex VI asks at point 4 for identification of the radio equipment allowing traceability and at point 8 for the software covered by the declaration. A firmware range does not replace an assessment of each release: record for every release whether it affects conformity and which declaration version covers it.
Continue reading
Related guides
reference
eIDAS and the Declaration of Conformity — which electronic signature is enough?
EU product acts require a signed declaration of conformity but prescribe no signature type. What eIDAS Article 25 gives simple, advanced and qualified signatures.
4 min read
reference
Declaration of Conformity translation requirements — which languages are required
Which languages an EU declaration of conformity needs: each Member State decides. What the RED, LVD, EMC, RoHS, CRA and MDR say, and who translates and signs.
5 min read
tutorial
Sample Declaration of Conformity — annotated walkthrough with template
The RED Annex VI model declaration, annotated point by point for a fictional radio sensor that also falls under RoHS, with what to establish before signing.
6 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.