[Home](/)/[Resources](/resources)/Updating CE Documentation

EUDocumentation Guide

# Updating CE Documentation After Product Changes

Complete guide to updating CE documentation when products change. Learn when changes require updated DoC, test reports, and technical file revisions.

Copy Link[Share on WhatsApp](https://wa.me/?text=https%3A%2F%2Fkrono-labs.com%2Fguides%2Fupdating-ce-documentation)

At a glance

Change types

4

Update triggers

5

FAQs

5

## Types of product changes

### Minor changes

Label artwork updates, user manual revisions, cosmetic changes

Update technical file, no new testing typically required

### Component changes

Substituting equivalent components, supplier changes

Update BOM and supplier documentation, verify equivalence

### Design changes

PCB layout changes, firmware updates, mechanical modifications

Re-assess impact, may require re-testing depending on scope

### Major changes

New features, different radio modules, significant hardware changes

Full re-assessment and likely re-testing required

## Triggers for documentation updates

*   Changes to applicable directives or standards
*   Component substitutions that affect compliance
*   Firmware updates that change functionality
*   Hardware design modifications
*   Changes to intended use or target market

## Frequently Asked Questions

### Do all product changes require updated CE documentation?

Not all changes require updates. Minor cosmetic or documentation changes may only require updating the technical file. However, any change that affects compliance — components, firmware, design, or intended use — requires assessment and potential documentation updates.

### When do I need to sign a new Declaration of Conformity?

Sign a new DoC when changes affect the compliance status. This includes new directives becoming applicable, significant design changes, or changes to harmonised standards referenced. Document the rationale for the new DoC in the technical file.

### Do firmware updates require re-testing?

It depends. If firmware changes affect emissions, safety, or functionality covered by testing, re-testing may be required. Minor bug fixes that don't affect compliance may not need re-testing but should be documented in the technical file.

### How do I document product changes?

Maintain a change control log in your technical file. Document the change, its rationale, compliance impact assessment, and any testing performed. This provides an audit trail for market surveillance authorities.

### What if a harmonised standard is updated?

When a harmonised standard is updated or withdrawn, you must update your DoC to reference the current standard. Products already on the market before the transition may continue under the old standard, but new production must reference the new standard.

**Disclaimer:** This page is an educational resource based on official EU sources. It is not legal or engineering advice. Always verify current directive and standard status in the Official Journal before placing any product on the EU market.

[

Map your product, free

Every standard, document, and test that applies — free, no account required.

Start mapping](/platform/new)[

Want an expert to handle your compliance for you?

One consultant from Krono's compliance team takes your product from requirements to legal sale, with a fixed quote before any work starts.

See compliance services](/services)

Related guides

*   [CE technical file retentionComplete guide to CE documentation retention requirements.](/guides/ce-technical-file-retention)
*   [How to build a CE technical fileComplete guide to building a CE technical file: template structure, required sections, evidence organization, and review-ready …](/guides/how-to-build-ce-technical-file)
*   [Technical documentation for CE markingComplete guide to CE technical documentation: required elements, file structure, evidence requirements, and how to build an rev…](/guides/technical-documentation-for-ce-marking)
*   [CE Declaration of Conformity: common mistakesComplete guide to avoiding common DoC mistakes.](/guides/ce-doc-common-mistakes)