Practical template
Firmware release conformity impact review
Use this template with your own product details and evidence. Copy the text into your document to complete the fields and add rows as needed.
- Old/new image hashes: [fill in]
- Hardware/variants: [fill in]
- Release date/scope: [fill in]
| Change | Existing evidence assumption | Impact and uncertainty | Reuse rationale or verification needed | Actual evidence | Owner/approval |
|---|---|---|---|---|---|
| Radio settings | [fill in] | [fill in] | [fill in] | [fill in] | [fill in] |
| Power/thermal/charging | [fill in] | [fill in] | [fill in] | [fill in] | [fill in] |
| Interfaces/intended use | [fill in] | [fill in] | [fill in] | [fill in] | [fill in] |
| Security behaviour/dependencies | [fill in] | [fill in] | [fill in] | [fill in] | [fill in] |
Substantial modification analysis under Article 3(30) of the Cyber Resilience Act (Regulation (EU) 2024/2847), legal basis and timing: [fill in]. This is separate from radio/safety/EMC evidence reuse. Notified body to inform (EU-type examination certificate or approved quality system, for example Radio Equipment Directive 2014/53/EU, Annex III, Module B, point 7)? Basis, date sent and reply: [fill in]. Declaration/instruction/label changes required: [fill in]. Unresolved release blockers: [fill in]. Conformity and security reviewer/date: [fill in].
Read the accompanying guide
When a Firmware Update Needs New CE Evidence or Retesting