Technical File for IoT devices — concrete template aligned with CRA and RED
An eight-folder Technical File structure for connected IoT products, with a coverage checklist against RED Annex V and CRA Annex VII (from 11 December 2027).
By Vladimír VicianUpdated
Fact-checked against the law as of Reviewed by Vladimír Vician on How we check
A Technical File documents the assessed product and the evidence that it meets the requirements that apply to it. The eight folders below are one way to organise that evidence. The law prescribes the content of the file, not the folder numbering.
The folders are mapped to Annex V of the Radio Equipment Directive 2014/53/EU, which applies to radio equipment and therefore to most connected IoT products, and to Annex VII of the Cyber Resilience Act, Regulation (EU) 2024/2847. One repository can support both acts, but only an item-by-item check against each annex shows that it is complete. For radio equipment, Article 3(1) of the Radio Equipment Directive covers the safety and EMC requirements, so the Low Voltage Directive and the EMC Directive are not cited separately for that equipment.
Template structure
Technical File — ConnectedSensor X1 (HW Rev C, FW v1.4.x)
═════════════════════════════════════════════════════════════
1. Product identification, description and user information
2. Design and manufacturing
3. Risk assessment
4. Standards and other specifications applied
5. Test reports and verification records
6. Cybersecurity and vulnerability-handling evidence (CRA Annex I)
7. Conformity assessment record and EU declaration of conformity
8. Post-market surveillance plan
─────────────────────────────────────────────────────────────
Annexes (as needed): photographs, schematics, full test reports
Coverage checklist
Every item the two annexes require has a folder. Tick each row for your product; where a row does not apply, record why.
| Required item | Provision | Folder |
|---|---|---|
| General description: photographs or illustrations of external features, marking and internal layout | RED Annex V(a)(i) | 1 |
| Versions of software or firmware affecting compliance | RED Annex V(a)(ii) | 1 |
| User information and installation instructions | RED Annex V(a)(iii) | 1 |
| Design and manufacturing drawings and schemes, with the explanations needed to understand them | RED Annex V(b) and (c) | 2 |
| List of harmonised standards applied in full or in part, or a description of the other solutions used | RED Annex V(d) | 4 |
| Copy of the EU declaration of conformity | RED Annex V(e) | 7 |
| EU-type examination certificate and its annexes, where Annex III was used | RED Annex V(f) | 7 |
| Results of design calculations and examinations | RED Annex V(g) | 5 |
| Test reports | RED Annex V(h) | 5 |
| Explanation of compliance with Article 10(2) (operable in at least one Member State) and of the packaging information under Article 10(10) | RED Annex V(i) | 1 |
| General description: intended purpose, software versions affecting compliance, photographs or illustrations for hardware | CRA Annex VII, point 1(a) to (c) | 1 |
| User information and instructions set out in Annex II | CRA Annex VII, point 1(d) | 1 |
| Design and development information, including the system architecture | CRA Annex VII, point 2(a) | 2 |
| Vulnerability-handling processes: software bill of materials, coordinated vulnerability disclosure policy, evidence of a contact address for vulnerability reports, secure distribution of updates | CRA Annex VII, point 2(b) | 6 |
| Production and monitoring processes and their validation | CRA Annex VII, point 2(c) | 2 |
| Cybersecurity risk assessment, including how the Annex I, Part I requirements apply | CRA Annex VII, point 3 | 3 |
| Information used to determine the support period | CRA Annex VII, point 4; Article 13(8) | 6 |
| List of harmonised standards, common specifications or certification schemes applied, or a description of the other solutions used | CRA Annex VII, point 5 | 4 |
| Reports of the tests carried out | CRA Annex VII, point 6 | 5 |
| Copy of the EU declaration of conformity | CRA Annex VII, point 7 | 7 |
| Software bill of materials, on a reasoned request from a market surveillance authority | CRA Annex VII, point 8 | 6 |
The CRA rows apply to products placed on the market from 11 December 2027. Folder 8 is not required by either annex; it holds the procedures that keep the file current after the product ships.
Section 1 — Product identification, description and user information
The first section answers what the product is and what the user is told.
For an IoT device, include:
- Product name and intended marketing description
- Type / model designation as it appears on the product label
- Hardware revision (Rev C, board v3)
- Firmware version range the Technical File covers (v1.4.x)
- Serial number range of units placed on the market under this Technical File version
- Intended use — what the product is for, in what environment, for what user type
- Reasonably foreseeable use and misuse — uses the manufacturer does not intend but can anticipate. CRA Article 13(3) bases the cybersecurity risk assessment on the intended purpose and reasonably foreseeable use, and Annex II, point 5 requires users to be told about circumstances, including reasonably foreseeable misuse, that may lead to significant cybersecurity risks
- Connectivity profile — Wi-Fi 2.4/5 GHz, BLE, LoRa, cellular bands; protocols supported (MQTT, CoAP, HTTPS, custom)
- Target markets — EU/EEA, plus any extra-EU markets sharing the conformity claim
- Photographs or illustrations showing external features, marking and internal layout
- User information and installation instructions as supplied with the product, including the frequency bands and maximum radio-frequency power required by RED Article 10(8) and, from 11 December 2027, the information listed in CRA Annex II
- Radio spectrum statement — an explanation of how the equipment can be operated in at least one Member State without infringing radio spectrum rules (RED Article 10(2)), and whether the packaging carries information on restrictions or authorisation requirements (RED Article 10(10))
Section 2 — Design and manufacturing
The engineering ground truth.
For an IoT device:
- Schematics — full electrical schematics with annotated power supply, communication interfaces, security peripherals (TPM, secure element if present)
- PCB layout — gerbers or PDF plots
- Mechanical drawings — enclosure, antenna placement, button and indicator positions
- Bill of materials with component manufacturer, part number, version, supplier
- Sub-component datasheets — radio module, microcontroller, power supply, sensor packages, secure element
- Software architecture diagram — application layers, RTOS or OS, drivers, secure boot chain, update mechanism, telemetry pipeline
- Manufacturing process description — PCB assembly, programming, calibration, testing in production
Section 3 — Risk assessment
A documented analysis of the risks the product presents and the measures that reduce them. For cybersecurity, CRA Article 13(2) and (3) requires the manufacturer to assess the cybersecurity risks of the product, to base that assessment on the intended purpose, the reasonably foreseeable use and the conditions of use, and to keep it documented and updated during the support period. Article 13(4) requires it to be included in the technical documentation.
For an IoT device, the risk assessment covers the following areas. The standards named are common references for each area; Section 4 says which of them are cited in the Official Journal and under which act.
- Electrical and thermal hazards (RED Article 3(1)(a)) — for example EN 62368-1, the safety standard for audio/video, information and communication technology equipment
- Human exposure to radio-frequency fields (RED Article 3(1)(a)) — an exposure assessment, for example to EN 62311 or EN 62479, or to a product standard such as EN 50566 for hand-held and body-mounted devices
- Electromagnetic compatibility (RED Article 3(1)(b)) — the EN 301 489 series for radio equipment, with EN 55032 for emissions and EN 55035 for immunity of multimedia equipment
- Use of radio spectrum (RED Article 3(2)) — for example EN 300 328 for wideband data transmission in the 2,4 GHz band
- Cybersecurity (RED Article 3(3)(d) to (f) where they apply, and CRA Annex I from 11 December 2027) — an asset-based analysis using a documented method. EN 18031 is cited under the Radio Equipment Directive only; it does not give a presumption of conformity with the Cyber Resilience Act
Asset-based cybersecurity risk assessment maps:
- Identified assets — what the product holds or controls that has value (user data, network functionality, update mechanism, payment functions if applicable)
- Identified threats per asset — STRIDE-style enumeration or equivalent threat-modelling approach
- Required security capabilities to mitigate each identified threat — authentication, encryption, integrity protection, secure update, logging
- Residual risks accepted by the manufacturer with rationale and any user-disclosed mitigations
See CRA Annex I explained for the security capability list aligned with this methodology.
Section 4 — Standards and other specifications applied
List every standard by full reference and edition, and say for each one whether it is a harmonised standard cited in the Official Journal under the act you rely on. Only a cited edition, applied within any restriction published with the citation, gives a presumption of conformity. Where you have not applied a harmonised standard, or have applied it only in part, RED Annex V(d) requires a description of the solution you used instead.
For radio equipment the relevant list is in Commission Implementing Decision (EU) 2022/2191. The editions below are the ones in the consolidated text of that Decision dated 15 November 2026. The lists change, so check the current consolidated Decision on the day you sign the declaration.
Cited under the Radio Equipment Directive:
- EN 18031-1:2024 — internet-connected radio equipment, for RED Article 3(3)(d). Cited with restrictions: for example, it gives no presumption of conformity if the user is allowed not to set and use any password
- EN 18031-2:2024 — radio equipment processing personal, traffic or location data, for RED Article 3(3)(e). It is relevant only where Article 1(2) of Delegated Regulation (EU) 2022/30 applies to the equipment. Cited with restrictions
- EN 18031-3:2024 — internet-connected radio equipment processing virtual money or monetary value, for RED Article 3(3)(f). It is relevant only where the equipment lets the user transfer money, monetary value or virtual currency (Article 1(3) of Delegated Regulation (EU) 2022/30). Cited with restrictions
- EN 300 328 V2.2.2 — data transmission equipment operating in the 2,4 GHz band, for access to radio spectrum
- EN 301 489-17 V3.3.1 — EMC for broadband and wideband data transmission systems. Cited with restrictions. EN 301 489-1 has no entry in the list
- EN 55035:2017 — immunity requirements for multimedia equipment
- EN 50566:2017 with amendments A1:2023 and A2:2025 — radio-frequency exposure, hand-held and body-mounted devices; EN 50360:2017 with amendment A1:2023 — devices used next to the ear
Not in the Radio Equipment Directive list. Record these as specifications applied, not as harmonised standards under that Directive:
- EN 62368-1 — safety of audio/video, information and communication technology equipment. The Low Voltage Directive list (Implementing Decision (EU) 2023/2723, consolidated text of 30 April 2026) cites EN 62368-1:2014 with AC:2015
- EN 62311:2008 and EN 62479:2010 — assessment of human exposure to electromagnetic fields. Both are cited in the Low Voltage Directive list
- EN 55032 — emissions of multimedia equipment. The EMC Directive list (Implementing Decision (EU) 2019/1326, consolidated text of 10 June 2022) cites EN 55032:2015 with amendment A11:2020
Module A remains available for the RED Article 3(1) safety and EMC requirements whether or not a harmonised standard is applied (Article 17(2)). For Article 3(2) and 3(3), the route depends on harmonised standards cited under the Radio Equipment Directive (Article 17(3) and (4)); see When you need a Notified Body.
RoHS: EN IEC 63000:2018, the standard for the technical documentation on restricted substances, was cited under Directive 2011/65/EU by Implementing Decision (EU) 2020/659.
Cyber Resilience Act: none of the standards above gives a presumption of conformity with the Cyber Resilience Act. Its list of applied standards (Annex VII, point 5) is needed for products placed on the market from 11 December 2027.
Section 5 — Test reports and verification records
The compliance evidence.
For an IoT device:
- EMC emissions test report — lab name, ISO/IEC 17025 accreditation, date, method, results vs limits
- EMC immunity test report — same structure
- Radio assessment evidence supporting the applicable RED requirements and chosen assessment route — band-of-operation, output power, spurious emissions, modulation
- Radio-frequency exposure assessment — the calculation or measurement showing compliance with the exposure limits
- Safety test report under EN 62368-1 — touch current, dielectric strength, temperature rise
- Cybersecurity assessment results per EN 18031 — the conceptual, functional completeness and functional sufficiency assessments that the standard sets for each requirement that applies to the product
- RoHS conformity declaration from each component supplier, or in-house testing for representative samples
For each test report, retain the methodology, lab credentials, date, test article description (which hardware revision and firmware version was tested), acceptance criteria, and pass/fail conclusion.
Section 6 — Cybersecurity and vulnerability-handling evidence
This folder holds the evidence for the essential cybersecurity requirements in CRA Annex I, which apply to products placed on the market from 11 December 2027. Part I of that Annex sets requirements for the product; Part II sets requirements for the manufacturer's vulnerability handling. Each subsection below names the requirement it supports. Items marked good practice are not named in the Regulation; they are common ways to meet or evidence the requirement.
6.1 — Software bill of materials
A software bill of materials in a commonly used, machine-readable format that covers at least the top-level dependencies of the product (Annex I, Part II, point 1). The Regulation does not name a format; CycloneDX and SPDX are two that are in common use. Generate one per release. See SBOM CycloneDX vs SPDX for format details.
6.2 — Secure update mechanism design
Supports Annex I, Part I, point 2(c) (vulnerabilities can be addressed through security updates) and Part II, points 7 and 8 (secure distribution of updates, disseminated without delay and free of charge).
- Distribution channel and how its security is ensured
- How users are notified of available updates, and the automatic-update setting with its opt-out
- Cryptographic signing of update packages and integrity verification on download (good practice)
- Rollback protection, and a fallback for devices that cannot receive updates over the normal channel (good practice)
6.3 — Coordinated vulnerability disclosure policy
Supports Annex I, Part II, point 5 (a policy on coordinated vulnerability disclosure) and point 6 (a contact address for reporting vulnerabilities).
- The policy and where it is published
- The contact address for vulnerability reports, with evidence that it is provided
- Acknowledgement and remediation timelines you commit to (good practice)
- A
/.well-known/security.txtfile and a channel for VEX statements (good practice)
6.4 — Vulnerability handling procedures
Supports Annex I, Part II, point 2 (address and remediate vulnerabilities without delay) and point 4 (publish information about fixed vulnerabilities once an update is available).
- Vulnerability triage process and severity classification, for example with CVSS (good practice)
- Remediation targets per severity tier (good practice)
- Advisory publication workflow
- CRA Article 14 reporting trigger and escalation; this reporting duty has applied since 11 September 2026
6.5 — Security event logging
Supports Annex I, Part I, point 2(l) (recording and monitoring relevant internal activity, with an opt-out mechanism for the user).
- What is logged (authentication, configuration changes, update events, anomalous access)
- Local retention policy
- Remote forwarding option and configuration
- User opt-out mechanism
6.6 — Cryptographic algorithm inventory
Supports Annex I, Part I, point 2(e) (confidentiality of stored, transmitted or processed data, for example by state-of-the-art encryption).
- Algorithms used, key sizes, where applied (TLS, signing, at-rest encryption)
- Deprecation plan when algorithms become weak (good practice)
6.7 — Security testing evidence
Supports Annex I, Part II, point 3 (effective and regular tests and reviews of the security of the product). The Regulation does not name test methods.
- Results of the security tests and reviews performed for each release
- Static analysis, dynamic analysis and dependency scanning results, where you use them (good practice)
- Threat-modelling summary for each major release (good practice)
6.8 — Support period
The information you took into account to determine the support period (CRA Annex VII, point 4). Article 13(8) requires the period to reflect the time the product is expected to be in use, and to be at least five years unless the expected use is shorter.
Section 7 — Conformity assessment record and EU declaration of conformity
The procedural evidence.
- Procedure applied under each act. For radio equipment, RED Article 17 allows internal production control (module A) for the Article 3(1) safety and EMC requirements. For Article 3(2) and 3(3) it allows module A only where harmonised standards cited in the Official Journal are applied; otherwise EU-type examination (modules B+C) or full quality assurance (module H) is required. Under CRA Article 32, from 11 December 2027, the route depends on whether the product is an important product of Class I or Class II or a critical product
- Reason for the choice — the product's classification under each act and the standards applied in full
- Notified body details where one was involved: name, identification number and certificate reference
- Copy of the EU-type examination certificate and its annexes where RED Annex III was used (RED Annex V(f))
- Copy of the EU declaration of conformity (RED Annex V(e); CRA Annex VII, point 7)
- Date the conformity assessment was completed
When you need a Notified Body sets out the conditions for each route.
Section 8 — Post-market surveillance plan
What happens after the product ships.
For an IoT device:
- Field data collection — customer support tickets, telemetry-derived metrics (opt-in), warranty returns
- Incident triage workflow — who classifies a customer report as a potential security incident
- CRA Article 14 reporting escalation — internal escalation criteria that map to "actively exploited vulnerability" or "severe incident" thresholds
- CVD researcher communication — how the manufacturer handles inbound researcher reports
- Regulation monitoring — how the manufacturer tracks Official Journal changes to the acts and to the cited standards lists it relies on
- Review cadence — when the Technical File and the EU declaration of conformity are formally re-assessed, for example once a year and at each major release
Review the supported scope and workflow
Related from the Library
- Technical File 101 — what the technical documentation must contain under each act
- Technical File retention requirements — how long to keep the file, and who else must hold a copy
- CRA Annex I explained — the essential requirements that Section 6 supports
- SBOM CycloneDX vs SPDX — detail for Section 6.1
- RED Delegated Act + EN 18031 walkthrough — the cybersecurity standard family
- CRA timeline and reporting obligations — the Article 14 workflow in Section 8
Further reading
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Annex VII — content of the technical documentation, EUR-Lex
- Directive 2014/53/EU (Radio Equipment Directive), Annex V — contents of technical documentation, EUR-Lex
- Implementing Decision (EU) 2022/2191 — harmonised standards cited under the Radio Equipment Directive, consolidated text of 15 November 2026, EUR-Lex
- Delegated Regulation (EU) 2022/30 — which radio equipment the cybersecurity requirements of Article 3(3)(d) to (f) apply to, EUR-Lex
- Implementing Decision (EU) 2023/2723 — harmonised standards cited under the Low Voltage Directive, EUR-Lex
- Regulation (EU) 2019/1020, Article 14(4)(a) — market surveillance powers to require documents and technical information, EUR-Lex
- The Blue Guide 2022, section 4.3 on technical documentation, EUR-Lex
- Commission overview of harmonised standards and where the cited lists are published
FAQ
Frequently asked questions
Does an IoT device need a different Technical File from any other CE-marked product?
The law does not prescribe an eight-section Technical File; the eight folders in this article are one way to organise the evidence. What is mandatory is the content: Annex V of the Radio Equipment Directive 2014/53/EU for radio equipment, Annex VII of the Cyber Resilience Act for products placed on the market from 11 December 2027, and the documentation rules of any other act that applies. For radio equipment, Article 3(1) of the Radio Equipment Directive covers the safety and EMC requirements, so the Low Voltage Directive and the EMC Directive are not cited separately for that equipment.
What goes in the IoT Technical File that does not go in a non-IoT Technical File?
The cybersecurity evidence. Under the Cyber Resilience Act, Annex VII, the file must contain the cybersecurity risk assessment, a description of the system architecture, the vulnerability-handling processes including the software bill of materials, the coordinated vulnerability disclosure policy, the contact address for vulnerability reports and the secure distribution of updates, and the information used to determine the support period. Annex I, Part II requires the software bill of materials in a commonly used, machine-readable format; it does not name CycloneDX or SPDX. These obligations apply to products placed on the market from 11 December 2027; reporting under Article 14 has applied since 11 September 2026.
Does the Technical File need to contain source code?
Neither Annex V of the Radio Equipment Directive 2014/53/EU nor Annex VII of the Cyber Resilience Act lists source code as an item of the technical documentation. Confidentiality is not an exemption, however: under Regulation (EU) 2019/1020, Article 14(4)(a), market surveillance authorities can require access to embedded software in so far as that is necessary to assess the product's compliance. If an authority or a notified body asks for implementation evidence, agree secure access and confidentiality arrangements with it rather than refusing.
How do I keep the Technical File in sync with continuous software updates?
Version-control the Technical File together with the firmware. The Radio Equipment Directive 2014/53/EU, Article 21(2), requires the technical documentation to be continuously updated, and Annex V requires it to state the software or firmware versions that affect compliance. The Cyber Resilience Act, Article 31(2), requires continuous updating where appropriate, at least during the support period, for products placed on the market from 11 December 2027. A release that changes compliance-relevant software therefore needs the affected items updated: the declared versions, the software bill of materials, the risk assessment if the threats or the architecture changed, and the test evidence. A release with no effect on compliance does not change the file's content, but recording it keeps the link between the file and the units in the field.
Where do I store the IoT Technical File electronically?
Use version-controlled storage with access control and an export route, so that the documentation can be supplied to an authority on request for the whole retention period. Article 14(4)(a) of Regulation (EU) 2019/1020 gives market surveillance authorities the power to require documents, technical specifications and data in any form or format and wherever they are stored; it does not prescribe a storage medium. Under the Radio Equipment Directive 2014/53/EU, Article 10(12), the manufacturer provides the documentation on a reasoned request in paper or electronic form, in a language the authority can easily understand.
Can my EU authorised representative hold the Technical File if my company is outside the EU?
Yes, a copy. Under the Radio Equipment Directive 2014/53/EU, Article 11(2)(a), the mandate must allow the authorised representative to keep the EU declaration of conformity and the technical documentation at the disposal of the authorities for 10 years after the radio equipment has been placed on the market. The Cyber Resilience Act, Article 18(3)(a), sets at least 10 years or the support period, whichever is longer, for products placed on the market from 11 December 2027. Drawing up the technical documentation cannot be delegated to the representative (Radio Equipment Directive Article 11(1); Cyber Resilience Act Article 18(2)), so the manufacturer stays responsible for its content and should keep the representative's copy in step with the master copy.
Continue reading
Related guides
reference
Technical File retention requirements by EU act — period, trigger and holder
How long the technical documentation and EU declaration of conformity must be kept under RED, LVD, EMC, RoHS, CRA, MDR and machinery law, from when, and by whom.
7 min read
guide
Risk assessment for CE compliance — methodology overview and standards reference
How to document product-specific safety and cybersecurity risks, choose methods within their verified scope, and connect risk controls to conformity evidence.
6 min read
guide
Technical File 101 — documentation scope and evidence overview
What EU technical documentation must contain under RED, LVD, EMC, CRA, MDR and machinery law, who keeps it and for how long, and how authorities request it.
7 min read
tutorial
Secure OTA Firmware Updates and the Evidence to Keep
Plan secure OTA test evidence for signatures, interrupted updates, recovery and downgrade controls against the CRA update requirements, with a small host demo.
6 min read
Put this into practice
Free tools & references
- EU Directive SelectorDescribe your product and find which EU directives and regulations apply.Open tool →
- CRA Readiness CheckerScore your product against the Cyber Resilience Act essential requirements.Open tool →
New to the terminology? Browse the compliance glossary — plain-English, citation-backed definitions of every term above.