When does a Declaration of Conformity need to be updated?

Review the declaration when product identification, scope, applicable requirements, applied standards, assessment evidence or other declared facts change. A new standard does not automatically require retrospective reissuance for every unit: assess its OJ status, covered requirements, transition and affected units. Keep any revised declaration traceable to its supporting evidence and preserve the previous signed version.

What is the difference between amending and reissuing a DoC?

Amending is rare and risky — it changes the historical record of what was declared. Reissuing produces a new DoC with a new document number and date, and supersedes the prior version. The prior version remains in the Technical File alongside its associated Technical File version, so the historical record of what was declared at the time of original placement on the market remains intact. Reissuing is the standard approach.

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?

There is no general obligation to actively notify customers, but distributors and importers can request the current DoC on demand and the manufacturer must provide it. For products under MDR, vigilance and post-market obligations may require notification. For products under CRA, if the amendment relates to a security issue, the Article 13 vulnerability disclosure obligations apply in parallel and may require user notification.

What if I miss a regulation amendment and continue to place product on the market?

A failure to meet applicable requirements can lead to corrective action and authority enforcement. Assess the current act, transition, units affected and evidence; Article 14 of Regulation 2019/1020 concerns authority powers and does not itself define a blanket rule that every previously placed unit must meet every later amendment.

Can the same DoC cover multiple firmware versions of the same product?

A declaration may cover identified variants when the applicable act permits this and traceability and conformity are demonstrated for each covered configuration. Do not use a firmware range as a substitute for impact assessment. Link each release to the scope decision, evidence and declaration version.

guideCRA, RED9 min read

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 Vician14 June 2026Updated 5 October 2026

A signed Declaration of Conformity is not a static document. EU regulations are amended, harmonised standards are replaced and withdrawn, products are modified, and manufacturers reorganise. Each change can trigger a need to reissue the DoC.

This article explains when reissuing is mandatory, when it is recommended, the difference between amending and reissuing, and how to maintain the historical record in the Technical File.

When the DoC must be reissued

Reissuing is required when a fact stated on the DoC has changed in a way that affects the underlying legal claim. The four most common triggers:

1. A cited directive or regulation is amended

When a cited directive is amended such that the product no longer conforms to the new text:

CRA amendment to Annex I essential requirements — check the amending act, its application date, transitional provisions and the particular units affected
RED Delegated Act updates — when Commission Delegated Regulation 2022/30 is updated
MDR amendment to clinical evaluation or post-market surveillance requirements
New directive replacing an old one — e.g. the Machinery Regulation 2023/1230 replacing the Machinery Directive 2006/42/EC from January 2027

The new DoC cites the amended text of the regulation; the old DoC remains in the Technical File covering units placed on the market before the amendment date.

2. A cited harmonised standard is replaced

When a harmonised standard is replaced and the old version is withdrawn from the Official Journal:

A new version of EN 18031 is cited; the old version is withdrawn after a transition period
EN 55032 is amended; the new version replaces the old in the Official Journal listing
A draft standard becomes a final harmonised standard and replaces interim self-assessment

The presumption of conformity from the withdrawn standard expires on the withdrawal date set in the Official Journal. The new DoC cites the new standard version; the manufacturer must reassess evidence against the applicable essential requirements. Applying the newly cited standard is one route; alternative evidence or a different assessment procedure may be available under the applicable act.

3. The product is materially modified

When a hardware revision, firmware update, or component change materially affects the product's compliance posture:

A new radio module that brings RED Article 3(3)(d) into scope
A new feature that processes personal data, bringing GDPR and the relevant CRA Annex I Part I point 2 requirements into scope
A new component that takes the product into a different RoHS category
An AI feature that brings the product into AI Act scope

Cosmetic changes (colour, branding, packaging) typically do not trigger reissue. Functional changes that affect the directive scope or the harmonised standard test methods do.

4. Administrative changes

When non-technical facts on the DoC change:

Manufacturer identity — merger, acquisition, name change, registered address change
Signatory — the named signing officer leaves or changes role
EU Authorised Representative — the EC REP relationship ends or changes
Notified Body — the NB designation changes or the certificate expires

These changes do not affect the product's technical conformity but they do affect the legal claim — and an outdated DoC names entities or individuals no longer authorised.

Amending versus reissuing

Two approaches exist, only one is recommended:

	Amend the existing DoC	Reissue as new DoC
Effect on prior record	Changes the historical document	Supersedes; prior version preserved
Document numbering	Same DoC number	New DoC number, new date
Traceability	Difficult — which version of the DoC was in force when?	Clean — each unit shipped corresponds to a specific DoC version
Auditor reaction	Suspicious; raises questions about provenance	Standard practice; no audit risk
Recommended use	Almost never	Default

Reissue, do not amend. The prior DoC version stays in the Technical File alongside the firmware version, hardware revision, and Technical File version it corresponded to. When market surveillance asks "what version of the DoC was in force when this unit was placed on the market?", the manufacturer can answer with certainty.

The reissue workflow

A practical workflow for reissuing:

Detect the trigger — regulation amendment in the Official Journal, harmonised standard withdrawal, product change, or administrative change
Assess the impact — does the product still conform under the new text? What changes in the Technical File?
Update the Technical File — add the new directive version, new harmonised standard version, updated test reports, updated risk assessment
Draft the new DoC — with a new document number (typically incrementing: DoC-2026-0042 → DoC-2026-0043) and the current date
Sign the new DoC — fresh handwritten or qualified electronic signature
Archive the old DoC — into the Technical File for the retention period, with a clear note of which units it covered
Update distribution channels — distributors and importers asking for the DoC receive the new version going forward
Update product packaging or accompanying documents if the DoC version is referenced there
Notify the EC REP if applicable — they hold a copy and must have the current version

For products under the Cyber Resilience Act with continuous monitoring obligations, this workflow runs in addition to the Article 13 vulnerability handling processes.

Detecting amendments — the monitoring problem

Reissuing only works if you know an amendment has happened. The Official Journal of the European Union publishes amendments and harmonised standard updates continuously. Manual monitoring is impractical at scale.

Practical detection options:

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.

The most common cause of belated reissue is manufacturer didn't know the regulation amended. A distributor asks for the DoC, the distributor's compliance team notices the cited directive is the old version, the manufacturer scrambles. By that point the new directive has been in force for months.

What to retain in the Technical File

For each DoC version reissued, the Technical File retains:

The prior DoC document (PDF or paper)
The document numbering record showing the supersession sequence (DoC-2026-0042 superseded by DoC-2026-0043 on 25 June 2026)
The trigger event that prompted the reissue (regulation amendment date, standard withdrawal date, product change record)
The applicability period of each DoC version — which serial number ranges and which shipping dates each version covered
The updated Technical File version that supports the new DoC

Under CRA Annex VII and parallel annexes in other directives, set retention by the applicable act: CRA Article 13(13) requires at least ten years after placing on the market or the support period, whichever is longer; MDR has separate last-device and implantable-device rules — regardless of how many DoC versions were issued in between.

Common reissue mistakes

Reissue triggered by amendment but Technical File not updated. The new DoC cites the new directive version but the Technical File still references the old version. Auditors immediately spot the gap.
Amend in place rather than reissue. Same DoC number, same date, different cited regulations. Loses traceability.
Update the DoC but forget the EC REP copy. The EC REP holds a copy under the applicable written mandate, including CRA Article 18 where relevant; that copy must be the current version.
Update the DoC but ship product with old DoC packaged. Stock-on-hand of accompanying documents must be reviewed when a reissue happens.
No record of which units shipped under which DoC. When market surveillance asks "which DoC version covered the unit serial 0042?", the manufacturer must be able to answer.
Treating routine harmonised standard amendment as a no-op. A version-date change in EN 18031 is a real change with real test-method implications.

Using Cenitia for this work

Cenitia helps prepare evidence-linked working drafts within its supported regulatory catalogue. Confirm the product scope, actual applied standards and completed assessments, and review the result before issuance. Source-change alerts prompt a review; they do not certify conformity, automatically reissue a signed declaration or guarantee monitoring of every national rule and standard edition.

Explore Cenitia’s compliance workflow

Review the supported scope and workflow

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 continuous-monitoring obligations under CRA

Frequently asked questions

When does a Declaration of Conformity need to be updated?
Review the declaration when product identification, scope, applicable requirements, applied standards, assessment evidence or other declared facts change. A new standard does not automatically require retrospective reissuance for every unit: assess its OJ status, covered requirements, transition and affected units. Keep any revised declaration traceable to its supporting evidence and preserve the previous signed version.
What is the difference between amending and reissuing a DoC?
Amending is rare and risky — it changes the historical record of what was declared. Reissuing produces a new DoC with a new document number and date, and supersedes the prior version. The prior version remains in the Technical File alongside its associated Technical File version, so the historical record of what was declared at the time of original placement on the market remains intact. Reissuing is the standard approach.
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?
There is no general obligation to actively notify customers, but distributors and importers can request the current DoC on demand and the manufacturer must provide it. For products under MDR, vigilance and post-market obligations may require notification. For products under CRA, if the amendment relates to a security issue, the Article 13 vulnerability disclosure obligations apply in parallel and may require user notification.
What if I miss a regulation amendment and continue to place product on the market?
A failure to meet applicable requirements can lead to corrective action and authority enforcement. Assess the current act, transition, units affected and evidence; Article 14 of Regulation 2019/1020 concerns authority powers and does not itself define a blanket rule that every previously placed unit must meet every later amendment.
Can the same DoC cover multiple firmware versions of the same product?
A declaration may cover identified variants when the applicable act permits this and traceability and conformity are demonstrated for each covered configuration. Do not use a firmware range as a substitute for impact assessment. Link each release to the scope decision, evidence and declaration version.

Related guides

Put this into practice

Free tools & references

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

guideCRA, RED9 min read

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 Vician14 June 2026Updated 5 October 2026

This article explains when reissuing is mandatory, when it is recommended, the difference between amending and reissuing, and how to maintain the historical record in the Technical File.

When the DoC must be reissued

Reissuing is required when a fact stated on the DoC has changed in a way that affects the underlying legal claim. The four most common triggers:

1. A cited directive or regulation is amended

When a cited directive is amended such that the product no longer conforms to the new text:

CRA amendment to Annex I essential requirements — check the amending act, its application date, transitional provisions and the particular units affected
RED Delegated Act updates — when Commission Delegated Regulation 2022/30 is updated
MDR amendment to clinical evaluation or post-market surveillance requirements
New directive replacing an old one — e.g. the Machinery Regulation 2023/1230 replacing the Machinery Directive 2006/42/EC from January 2027

The new DoC cites the amended text of the regulation; the old DoC remains in the Technical File covering units placed on the market before the amendment date.

2. A cited harmonised standard is replaced

When a harmonised standard is replaced and the old version is withdrawn from the Official Journal:

A new version of EN 18031 is cited; the old version is withdrawn after a transition period
EN 55032 is amended; the new version replaces the old in the Official Journal listing
A draft standard becomes a final harmonised standard and replaces interim self-assessment

3. The product is materially modified

When a hardware revision, firmware update, or component change materially affects the product's compliance posture:

A new radio module that brings RED Article 3(3)(d) into scope
A new feature that processes personal data, bringing GDPR and the relevant CRA Annex I Part I point 2 requirements into scope
A new component that takes the product into a different RoHS category
An AI feature that brings the product into AI Act scope

Cosmetic changes (colour, branding, packaging) typically do not trigger reissue. Functional changes that affect the directive scope or the harmonised standard test methods do.

4. Administrative changes

When non-technical facts on the DoC change:

Manufacturer identity — merger, acquisition, name change, registered address change
Signatory — the named signing officer leaves or changes role
EU Authorised Representative — the EC REP relationship ends or changes
Notified Body — the NB designation changes or the certificate expires

These changes do not affect the product's technical conformity but they do affect the legal claim — and an outdated DoC names entities or individuals no longer authorised.

Amending versus reissuing

Two approaches exist, only one is recommended:

	Amend the existing DoC	Reissue as new DoC
Effect on prior record	Changes the historical document	Supersedes; prior version preserved
Document numbering	Same DoC number	New DoC number, new date
Traceability	Difficult — which version of the DoC was in force when?	Clean — each unit shipped corresponds to a specific DoC version
Auditor reaction	Suspicious; raises questions about provenance	Standard practice; no audit risk
Recommended use	Almost never	Default

The reissue workflow

A practical workflow for reissuing:

Detect the trigger — regulation amendment in the Official Journal, harmonised standard withdrawal, product change, or administrative change
Assess the impact — does the product still conform under the new text? What changes in the Technical File?
Update the Technical File — add the new directive version, new harmonised standard version, updated test reports, updated risk assessment
Draft the new DoC — with a new document number (typically incrementing: DoC-2026-0042 → DoC-2026-0043) and the current date
Sign the new DoC — fresh handwritten or qualified electronic signature
Archive the old DoC — into the Technical File for the retention period, with a clear note of which units it covered
Update distribution channels — distributors and importers asking for the DoC receive the new version going forward
Update product packaging or accompanying documents if the DoC version is referenced there
Notify the EC REP if applicable — they hold a copy and must have the current version

For products under the Cyber Resilience Act with continuous monitoring obligations, this workflow runs in addition to the Article 13 vulnerability handling processes.

Detecting amendments — the monitoring problem

Practical detection options:

What to retain in the Technical File

For each DoC version reissued, the Technical File retains:

The prior DoC document (PDF or paper)
The document numbering record showing the supersession sequence (DoC-2026-0042 superseded by DoC-2026-0043 on 25 June 2026)
The trigger event that prompted the reissue (regulation amendment date, standard withdrawal date, product change record)
The applicability period of each DoC version — which serial number ranges and which shipping dates each version covered
The updated Technical File version that supports the new DoC

Common reissue mistakes

Reissue triggered by amendment but Technical File not updated. The new DoC cites the new directive version but the Technical File still references the old version. Auditors immediately spot the gap.
Amend in place rather than reissue. Same DoC number, same date, different cited regulations. Loses traceability.
Update the DoC but forget the EC REP copy. The EC REP holds a copy under the applicable written mandate, including CRA Article 18 where relevant; that copy must be the current version.
Update the DoC but ship product with old DoC packaged. Stock-on-hand of accompanying documents must be reviewed when a reissue happens.
No record of which units shipped under which DoC. When market surveillance asks "which DoC version covered the unit serial 0042?", the manufacturer must be able to answer.
Treating routine harmonised standard amendment as a no-op. A version-date change in EN 18031 is a real change with real test-method implications.

Using Cenitia for this work

Explore Cenitia’s compliance workflow

Review the supported scope and workflow

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 continuous-monitoring obligations under CRA

Frequently asked questions

When does a Declaration of Conformity need to be updated?
Review the declaration when product identification, scope, applicable requirements, applied standards, assessment evidence or other declared facts change. A new standard does not automatically require retrospective reissuance for every unit: assess its OJ status, covered requirements, transition and affected units. Keep any revised declaration traceable to its supporting evidence and preserve the previous signed version.
What is the difference between amending and reissuing a DoC?
Amending is rare and risky — it changes the historical record of what was declared. Reissuing produces a new DoC with a new document number and date, and supersedes the prior version. The prior version remains in the Technical File alongside its associated Technical File version, so the historical record of what was declared at the time of original placement on the market remains intact. Reissuing is the standard approach.
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?
There is no general obligation to actively notify customers, but distributors and importers can request the current DoC on demand and the manufacturer must provide it. For products under MDR, vigilance and post-market obligations may require notification. For products under CRA, if the amendment relates to a security issue, the Article 13 vulnerability disclosure obligations apply in parallel and may require user notification.
What if I miss a regulation amendment and continue to place product on the market?
A failure to meet applicable requirements can lead to corrective action and authority enforcement. Assess the current act, transition, units affected and evidence; Article 14 of Regulation 2019/1020 concerns authority powers and does not itself define a blanket rule that every previously placed unit must meet every later amendment.
Can the same DoC cover multiple firmware versions of the same product?
A declaration may cover identified variants when the applicable act permits this and traceability and conformity are demonstrated for each covered configuration. Do not use a firmware range as a substitute for impact assessment. Link each release to the scope decision, evidence and declaration version.

Related guides

Put this into practice

Free tools & references

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

Updating a Declaration of Conformity after a regulation amendment

When the DoC must be reissued

1. A cited directive or regulation is amended

2. A cited harmonised standard is replaced

3. The product is materially modified

4. Administrative changes

Amending versus reissuing

The reissue workflow

Detecting amendments — the monitoring problem

What to retain in the Technical File

Common reissue mistakes

Using Cenitia for this work

Further reading

Frequently asked questions

Related guides

eIDAS and Declarations of Conformity — signature claims and evidence

Declaration of Conformity translation requirements — every EU language explained

Sample Declaration of Conformity — annotated walkthrough with template

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

Free tools & references

Updating a Declaration of Conformity after a regulation amendment

When the DoC must be reissued

1. A cited directive or regulation is amended

2. A cited harmonised standard is replaced

3. The product is materially modified

4. Administrative changes

Amending versus reissuing

The reissue workflow

Detecting amendments — the monitoring problem

What to retain in the Technical File

Common reissue mistakes

Using Cenitia for this work

Further reading

Frequently asked questions

Related guides

eIDAS and Declarations of Conformity — signature claims and evidence

Declaration of Conformity translation requirements — every EU language explained

Sample Declaration of Conformity — annotated walkthrough with template

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

Free tools & references