RED software update impact for radio equipment

Treat each update as a product-change assessment, not as a routine engineering label. The first question is whether the change can alter an Article 3 requirement: health and safety, EMC, efficient spectrum use, an activated Article 3(3) requirement, or the common-charger information and charging-capability rules for covered equipment.

The RED technical documentation must identify software or firmware versions that affect compliance with essential requirements. The release-control record should also monitor hardware and software changes, standards, legal developments, and state of the art. That makes the record important even when the conclusion is that no retest or declaration change is needed.

The update record should let a reviewer connect the software release to the radio equipment type placed on the EU market. Keep the release identifier, affected models, affected hardware variants, changed radio or security functions, standards impact, test impact, DoC impact, notified-body impact, approval owner, and release decision.

Annex V is the anchor for the file: it calls for a general product description, conceptual design and manufacturing materials, software or firmware versions affecting compliance, user and installation information, harmonised standards or other technical specifications, EU declaration, EU-type examination material where applicable, calculations, examinations, and test reports. If the update affects any of those records, update the technical documentation instead of relying on release notes alone.

A software update can reopen the conformity-assessment route if the change affects a requirement that was covered by a harmonised standard, a partly applied standard, a technical specification, an EU-type examination certificate, or a full-quality-assurance approval. RED gives presumption of conformity only for the essential requirements covered by OJEU-published harmonised standards or parts of standards.

For Article 3(2) and Article 3(3), the notified-body question is especially important. If relevant OJEU-cited harmonised standards are not applied, are applied only in part, or no such standards exist for the requirement being assessed, Article 17 points the manufacturer to Annex III or Annex IV rather than Annex II for those requirements. For Annex III, modifications to the approved type that may affect conformity or certificate validity require additional approval.

The main mistake is treating firmware as outside RED because no physical component changed. That is too narrow: software can affect radio parameters, EMC behavior, safety functions, cybersecurity controls, restrictions, charging behavior, instructions, and the evidence package used to place the equipment on the EU market.

The second mistake is treating every update as a brand-new conformity assessment. A documented impact decision can be proportionate, but it must explain why the existing Article 3 matrix, standards evidence, technical documentation, DoC, and notified-body records still cover the released configuration.