CRA technical documentation (Annex VII) and EU declaration of conformity (Annex V): what small makers must write
Last verified: 2026-11-13.
Information, not legal advice. Our reading of the official sources, not reviewed by a lawyer. You decide how the CRA applies to your product; for an opinion you can rely on, ask a lawyer; for a third-party conformity assessment, a notified body. This guide helps you work with the EU Cyber Resilience Act (Regulation (EU) 2024/2847) but does not certify, assess or guarantee the compliance of any product. You remain responsible for your product's conformity assessment, CE marking and reporting. Last verified against official sources: 2026-11-13.
Short answer
- For in-scope products placed on the EU market from 11 December 2027, the manufacturer must write the technical documentation before release, with at least the eight elements of Annex VII, and keep it updated at least during the support period (CRA Art. 13(12), 31(1)–(2), 71(2); Annex VII).
- After the conformity assessment shows the essential requirements are met, the manufacturer draws up the EU declaration of conformity (Annex V structure), affixes the CE marking, and gives users either a copy of the declaration or the short simplified declaration (Annex VI) with the exact web address of the full one (CRA Art. 13(12), 13(20), 28; Annexes V–VI).
- Both documents are kept at the disposal of market surveillance authorities for at least 10 years after the product is placed on the market, or for the support period if that is longer (CRA Art. 13(13)).
Key terms
- Technical documentation: all relevant data or details of the means the manufacturer used to make sure the product and its processes meet the essential cybersecurity requirements of Annex I; at least the Annex VII elements (CRA Art. 31(1)). People often call it the "technical file".
- EU declaration of conformity: the manufacturer's statement that fulfilment of the applicable Annex I requirements has been demonstrated (CRA Art. 28(1)). By drawing it up, the manufacturer assumes responsibility for the product's compliance with the CRA (CRA Art. 28(4)).
- Simplified EU declaration of conformity: a two-sentence version that points to the full text online (CRA Art. 13(20); Annex VI).
- Support period: the period you set under Article 13(8), at least five years unless the product is expected to be in use for less (CRA Art. 13(8)).
When this applies
The CRA applies from 11 December 2027, except Article 14 reporting (from 11 September 2026) and the notified-body chapter (from 11 June 2026) (CRA Art. 71(2)). Products placed on the market before 11 December 2027 are subject to the CRA's requirements, including these documents, only if they are substantially modified from that date (CRA Art. 69(2)). Reporting under Article 14 applies to them regardless (CRA Art. 69(3)).
What the technical documentation must contain (Annex VII)
Annex VII lists the minimum content "as applicable to the relevant product" (CRA Annex VII):
| # | Element | What a small team typically writes | Source |
|---|
| 1 | General description: intended purpose; software versions affecting compliance with the essential requirements; for hardware, photographs or illustrations of external features, marking and internal layout; user information and instructions under Annex II | A one-page product sheet, a version list, photos (hardware) and a copy of your user and security instructions | Annex VII(1)(a)–(d); Annex II |
| 2 | Design, development and production, and vulnerability handling: design and architecture (how software components build on or feed into each other); vulnerability-handling processes, including the SBOM, the coordinated vulnerability disclosure policy, evidence of a contact address for reports and the technical solution for secure distribution of updates; production and monitoring processes and their validation | An architecture diagram, your vulnerability-handling and disclosure policies, the SBOM per release, your update-delivery design, and your build and release process | Annex VII(2)(a)–(c) |
| 3 | The cybersecurity risk assessment, including how the Annex I Part I requirements apply | The risk assessment document; a clear justification for any requirement you consider not applicable | Annex VII(3); Art. 13(3)–(4) |
| 4 | Information used to determine the support period | Your support-period reasoning (expected use time, user expectations, comparable products, component support) | Annex VII(4); Art. 13(8) |
| 5 | Harmonised standards, common specifications or European cybersecurity certification schemes applied (in full or in part); where none were applied, the solutions adopted to meet Annex I Parts I and II and other technical specifications used | A list of standards or specifications used, or a requirement-by-requirement description of your own solutions | Annex VII(5) |
| 6 | Reports of tests carried out to verify conformity of the product and the vulnerability-handling processes with Annex I Parts I and II | Test and review reports (for example security tests, code review records, process checks) | Annex VII(6) |
| 7 | A copy of the EU declaration of conformity | The signed declaration | Annex VII(7) |
| 8 | Where applicable, the SBOM, further to a reasoned request from a market surveillance authority where needed to check compliance | Be ready to hand over the SBOM on request | Annex VII(8) |
The middle column is our suggestion of typical evidence, not wording from the Regulation.
Obligations by article
| What you must do | Who | From | Article |
|---|
| Draw up the technical documentation before placing the product on the market | Manufacturer | 11 Dec 2027 | Art. 13(12), 31(2) |
| Include the documented, updated cybersecurity risk assessment in the technical documentation; justify any essential requirement you treat as not applicable | Manufacturer | 11 Dec 2027 | Art. 13(3)–(4) |
| Include the information used to set the support period | Manufacturer | 11 Dec 2027 | Art. 13(8); Annex VII(4) |
| Keep the technical documentation continuously updated, where appropriate, at least during the support period | Manufacturer | 11 Dec 2027 | Art. 31(2) |
| If other EU acts also require technical documentation (for products referred to in Art. 12, high-risk AI systems), draw up a single set | Manufacturer | 11 Dec 2027 | Art. 31(3) |
| Write the technical documentation and notified-body correspondence in a language of the notified body's Member State or one the body accepts | Manufacturer using a notified body | 11 Dec 2027 | Art. 31(4) |
| Carry out the chosen conformity assessment procedure; once conformity is demonstrated, draw up the EU declaration and affix the CE marking | Manufacturer | 11 Dec 2027 | Art. 13(12), 32 |
| Use the Annex V model structure for the declaration, include the elements of the relevant Annex VIII procedure, update it as appropriate, and make it available in the languages the Member State requires | Manufacturer | 11 Dec 2027 | Art. 28(2) |
| One declaration for all EU acts that require one for the same product, naming each act and its publication reference | Manufacturer | 11 Dec 2027 | Art. 28(3) |
| Provide users with a copy of the declaration, or the simplified declaration with the exact web address of the full one | Manufacturer | 11 Dec 2027 | Art. 13(20); Annex VI |
| For software, affix the CE marking on the declaration or on the website accompanying the product | Manufacturer | 11 Dec 2027 | Art. 30(1) |
| Keep the technical documentation and the declaration at the authorities' disposal for at least 10 years, or the support period if longer | Manufacturer (or authorised representative, if mandated) | 11 Dec 2027 | Art. 13(13); Annex VIII Part I(4.2), (5) |
| On a reasoned request, give a market surveillance authority all information and documentation needed to demonstrate conformity, in a language it easily understands | Manufacturer | 11 Dec 2027 | Art. 13(22) |
Annex V requires all of the following information (CRA Annex V):
- Name and type and any additional information enabling unique identification of the product.
- Name and address of the manufacturer or its authorised representative.
- A statement that the declaration is issued under the sole responsibility of the provider.
- Object of the declaration: identification allowing traceability, which may include a photograph where appropriate.
- A statement that the object of the declaration is in conformity with the relevant Union harmonisation legislation.
- References to any relevant harmonised standards used, or any other common specification or cybersecurity certification, in relation to which conformity is declared.
- Where applicable, the name and number of the notified body, a description of the conformity assessment procedure performed and identification of the certificate issued.
- Additional information, then "Signed for and on behalf of", place and date of issue, name, function and signature.
Under the internal control procedure (module A), the declaration is drawn up for each product, identifies the product it covers, is kept together with the technical documentation, and a copy goes to the relevant authorities on request (CRA Annex VIII Part I(4.2)).
The simplified declaration (Annex VI)
If you give users the simplified version, Annex VI sets the wording (CRA Annex VI):
Hereby, … [name of manufacturer] declares that the product with digital elements type … [designation of type of product with digital element] is in compliance with Regulation (EU) 2024/2847. The full text of the EU declaration of conformity is available at the following internet address: …
The simplified declaration must contain the exact web address of the full one (CRA Art. 13(20)), and your Annex II user information must give, where applicable, the internet address where the declaration can be accessed (CRA Annex II(6)). The simplified declaration is also subject to the Member State's language requirements (CRA Art. 28(2)). In our reading, a simplified declaration does not replace the full one: it points to it.
Practical approach for a small team
Our suggestions, not requirements:
- Start the risk assessment first. Annex VII(3), (5) and (6) all depend on it, and Article 13(3) asks it to say how each Annex I requirement applies.
- Tie the file to releases. Annex VII(1)(b) asks for the software versions affecting compliance; keep the SBOM, test reports and declaration per release in the same repository or folder.
- Write once, reuse. The Annex II user information appears inside the technical documentation (Annex VII(1)(d)), so keep one source text.
- Plan for 10+ years. Archive in formats you can still open in a decade, with dates and version numbers (CRA Art. 13(13)).
- Keep it confidential, but ready. We found no general duty in the CRA to publish the technical documentation; authorities can ask for it (CRA Art. 13(22)) and must respect the confidentiality of trade secrets, including source code (CRA Art. 63(1)(a)). The exception: free and open-source software in Annex III categories may use internal control only if its technical documentation is made public when placed on the market (CRA Art. 32(5)).
Penalties
Breaches of Article 13, which includes drawing up these documents and keeping them for 10 years, can be fined up to EUR 15 million or 2.5% of worldwide annual turnover (CRA Art. 64(2)). Breaches of Article 28 (declaration), Article 30(1)–(4) (CE marking) and Article 31(1)–(4) (technical documentation) can be fined up to EUR 10 million or 2% (CRA Art. 64(3)). Supplying incorrect, incomplete or misleading information to authorities in reply to a request: up to EUR 5 million or 1% (CRA Art. 64(4)). Member States set the rules, and the size of micro, small and medium-sized enterprises is a factor (CRA Art. 64(1), (5)(c)).
What may still change
- Simplified technical documentation for micro and small enterprises: they may provide the Annex VII elements in a simplified format, using a form the Commission is to specify by implementing act; notified bodies must accept it (CRA Art. 33(5)). The Commission's CRA page (last update 7 September 2026) mentions no such implementing act; we did not find one adopted as of 2026-11-13 (
unverified: no complete register search). Until the form exists, plan for the full Annex VII content. - Delegated acts may add elements to Annex V (CRA Art. 28(5)) and to Annex VII (CRA Art. 31(5)).
- Harmonised standards: the Commission's standardisation page (last update 12 November 2026) describes standardisation request M/606 and an amendment of 10 November 2026 extending some delivery deadlines by three months; it lists no CRA harmonised standard cited in the Official Journal (Commission). Annex VII(5) then requires you to describe your own solutions.
- Next re-check of this guide: 2027-01-04.
How Shieldbook helps
Shieldbook is a set of templates and tools to help you prepare for the EU Cyber Resilience Act (Regulation (EU) 2024/2847). The kit includes a technical documentation skeleton (structure for the technical file, including the risk assessment and the information for users) and templates for the full and the simplified EU declaration of conformity, with a note on CE marking. Each template cites the article it supports. You carry out the conformity assessment and sign the declaration yourself.
Start with the free 5-question scope checker for a provisional indication: https://shieldbook.ppftec.com/check. See the kit: https://shieldbook.ppftec.com/kit.
FAQ
When must the technical documentation exist?
Before the product is placed on the market, for products placed on the market from 11 December 2027 (CRA Art. 13(12), 31(2), 71(2)). It is then kept updated, where appropriate, at least during the support period (CRA Art. 31(2)).
Do I have to publish my technical documentation?
We found no general duty to publish it. You keep it for market surveillance authorities and provide it on a reasoned request (CRA Art. 13(13), 13(22)). Free and open-source software in Annex III categories that uses internal control must make it public (CRA Art. 32(5)).
Must the SBOM be in the technical documentation?
Annex VII(2)(b) lists the SBOM among the vulnerability-handling information, and Annex VII(8) covers handing it to an authority on a reasoned request (CRA Annex VII). Publishing it to users is your choice; if you do, Annex II(9) asks you to say where it can be accessed (CRA Annex II(9)).
Can I give users only the simplified declaration?
Yes, provided it contains the exact internet address of the full declaration (CRA Art. 13(20)). The full declaration still has to be drawn up and kept (CRA Art. 13(12)–(13)).
Where does the CE marking go for software?
On the EU declaration of conformity or on the website accompanying the software; on the website, the relevant section must be easily and directly accessible to consumers (CRA Art. 30(1)).
My product also falls under another EU law that needs a declaration. Two declarations?
No. One declaration covering all those acts, naming each act and its publication reference (CRA Art. 28(3)).
In which language?
The declaration (full and simplified): the languages required by the Member State where the product is placed or made available (CRA Art. 28(2)). Technical documentation for a notified body: a language of the body's Member State or one it accepts (CRA Art. 31(4)). For authorities' requests: a language they easily understand (CRA Art. 13(22)).
Is there a lighter version for micro and small companies?
The CRA provides for a simplified format using a Commission form (CRA Art. 33(5)). We found no adopted form as of 2026-11-13 (unverified); re-check before relying on it.
Sources
Opened by the compliance analyst; dates are when each source was last read.
- Regulation (EU) 2024/2847 (Cyber Resilience Act), OJ L, 20.11.2024. Citation URL: https://eur-lex.europa.eu/eli/reg/2024/2847/oj/eng. File read (authentic OJ PDF via the Publications Office): https://publications.europa.eu/resource/cellar/21b7d4eb-a6e2-11ef-85f0-01aa75ed71a1.0006.01/DOC_1. Art. 13, 28, 30–33, 63–64, 69, 71 and Annexes II, V, VI, VII, VIII Part I read 2026-11-13.
- European Commission, Cyber Resilience Act policy page, last update 7 September 2026: https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act (2026-11-13).
- European Commission, CRA standardisation page, last update 12 November 2026: https://digital-strategy.ec.europa.eu/en/policies/cra-standardisation (2026-11-13).
The Shieldbook kit: templates and worked examples
This site needs JavaScript for the scope checker and the waitlist form.