Regulation (EU) 2024/2847 · Article 14 · Applies from 11 September 2026

CRA reporting deadlines and notification generator

Official Journal texts last checked for changes:

Article 71 states that the CRA applies from 11 December 2027, and then makes Article 14 an exception, bringing the reporting duties forward to 11 September 2026, fifteen months earlier. From that date a manufacturer that becomes aware of an actively exploited vulnerability, or of a severe incident affecting the security of a product with digital elements, has 24 hours to send an early warning and 72 hours to send the notification. This free tool shows the periods that Article 14 sets and generates what Article 14 requires to be stated at each stage. It does not file anything, and it does not decide whether an incident is severe.

This tool reproduces what the act prescribes. It does not assess your product, and it does not decide which obligations apply to you or whether a document satisfies them.

One free document per tool · Runs in your browser · Nothing uploaded

What are you reporting

Product and deadline

Runs in your browser. Nothing you enter is uploaded to or stored on a server.

This drafts content. It does not file anything. Article 14(7) requires notifications to go through the single reporting platform of Article 16, to the electronic notification end-point of the CSIRT designated as coordinator in the Member State of your main establishment, and to be simultaneously accessible to ENISA — and which CSIRT that is turns on facts only you hold. Article 14(6) lets that CSIRT ask you for an intermediate report, so three stages is the floor and not the ceiling. Article 14(8) is a separate duty to inform impacted users. Article 14(10) lets the Commission fix the format of these notifications by implementing act; none is reflected here, so this follows the Article’s own wording.
Live preview · Notification draft

Before you rely on this document

  • Check it against the act. The tool assembles the model wording set out in the legislation. It does not check that your entries are true, complete or correct for your product, so read the document against the act itself before you sign it.
  • This is one required document, not your compliance. The risk assessment, the technical documentation you must keep and be able to produce on request, the EU-based responsible person where the act requires one, any registration, and the marking and labelling on the product itself all remain yours. Generating a declaration discharges none of them.
  • Where an assessment or a notified body is required, it must actually have happened. A declaration stating that it did is a statement you make. RulesOf.EU cannot and does not verify it.
  • Keep your own copy, with the evidence behind it. The document is generated in your browser and RulesOf.EU keeps nothing, so if you do not save it, nobody holds a copy.
  • Have anything high-stakes reviewed by a qualified adviser. A first placing on the market, a submission to customs or an authority, a recall or a customer audit each justifies a qualified adviser’s time. This tool is a drafting aid.