If a harmonised standard referenced in your Declaration of Conformity (DoC) gets updated, your existing DoC does not automatically become invalid. However, you must check whether the updated standard affects your product’s compliance and whether you can still claim presumption of conformity under the relevant EU product compliance rules.
In practice, a harmonised standard update can introduce new tests, revised safety limits, or changed documentation expectations. If those changes are relevant to your product, you may need to update your technical documentation and, in some cases, revise your DoC to keep your compliance position clear and defensible.
The questions below explain what changes, when you should update your DoC, and how to manage harmonised standard updates in your technical file.
What changes when a harmonised standard is updated,
When a harmonised standard is updated, the technical route you use to demonstrate EU product compliance can change, especially the requirements that support presumption of conformity. The update may add or modify essential safety tests, clarify scope, change normative references, or introduce transition dates that affect which version is recognized for compliance purposes.
A harmonised standard update typically matters in three practical ways:
- Technical requirements shift: new clauses, revised limits, or different test methods can change whether your existing evidence still matches the standard.
- Scope and definitions change: the updated version may include or exclude product types, accessories, software functions, or foreseeable use cases that were unclear before.
- Compliance signaling changes: if the newer version becomes the preferred harmonised reference, using the older version may weaken your presumption of conformity position over time.
Not every update forces action. Some revisions are editorial or clarifying. The key is whether the changes affect the hazards, performance, or conditions of use that apply to your product.
Do you need to update your Declaration of Conformity,
You need to update your Declaration of Conformity (DoC) when the harmonised standard update changes the compliance basis you are claiming, or when you switch to citing the newer standard version to maintain presumption of conformity. If your product still meets the essential requirements and your evidence remains valid, an immediate DoC change may not be necessary.
Use a simple decision check:
- Did you adopt the new version? If you test or assess to the updated standard, update the DoC references to match.
- Did the update introduce new or stricter requirements relevant to your product? If yes, reassess and likely update supporting evidence and the DoC.
- Is there a transition period or end date for the old version? If the older version is no longer the recognized route to presumption of conformity, you should plan an update.
- Did your product change? If you changed materials, components, firmware, suppliers, or intended use, you may need to align with the latest standard and update the DoC accordingly.
Also separate product safety obligations from paperwork habits. The General Product Safety Regulation (EU) 2023/988 (GPSR) sets broad consumer product safety expectations, but a DoC is not universally required under GPSR. DoCs are typically tied to specific harmonization legislation and product categories, so always confirm what applies to your product type.
How to manage updates in technical documentation,
Manage a harmonised standard update by treating it as a controlled technical documentation update: identify what changed, assess the impact on your product, update evidence where needed, and keep a clear record of decisions. This approach protects your EU product compliance position and helps you respond quickly if authorities ask how you ensured ongoing conformity.
A practical workflow that scales for both small sellers and large manufacturers:
- Track the change: record the standard number, version, and publication date you currently cite, then obtain the updated version and its change summary.
- Perform a delta assessment: map new or revised clauses to your product design, labeling, instructions, and foreseeable use.
- Decide on actions: determine whether you can justify continued use of the older version during any transition, or whether you should move to the new version.
- Update evidence: refresh test reports, risk assessment, design rationale, and user information where the update affects hazards or performance.
- Update controlled documents: revise the DoC if the cited standard changes, and ensure version control across the technical file.
- Document the decision: keep a short internal memo explaining why you updated or why you did not, including dates and responsible roles.
Keep in mind that market surveillance authorities can request documentation to verify compliance. Under the Market Surveillance Regulation (EU) 2019/1020 (MSR), the Responsible Person role is carried out by an economic operator established in the EU, and that economic operator must be able to cooperate with authorities and, under Article 4, inform the manufacturer when risks are identified. If an accident or complaint triggers scrutiny, a clean documentation history makes responses faster and more consistent.
How EARP helps with harmonised standard updates,
We help you stay on top of harmonised standard updates by putting a clear, repeatable process around monitoring, impact assessment, and technical documentation update actions that support EU product compliance and presumption of conformity. We also act as your independent EU-based regulatory operator so documentation can be made available to authorities when requested.
- Standard update triage to identify what changed and whether it affects your product and DoC references
- Documentation completeness checks so your technical file stays organized, current, and ready for authority requests
- Controlled update support for revising DoC references and aligning test evidence and risk documentation
- EU regulatory operator services designed for non-EU manufacturers and online marketplace sellers who need continuity and neutrality
If you want a structured review of your current DoC and technical file against the latest harmonised standard update, contact us via our contact page or review our compliance services to get started.
Related Articles
- What safety and warning information must appear on online product listings under GPSR?
- Are handmade and artisan products subject to the GPSR?
- What is the difference between a product safety information sheet and a full GPSR technical file?
- Is FCC approval in the US sufficient to sell electronics in the European Union?
- Could the recipient or buyer in their own country just count as the responsible person for my product?
