Incident reporting deadline calculator: NIS2, EU DORA, CRA, AI Act
Enter when you became aware of an incident. The calculator shows every reporting step with date, weekday and time, plus the trigger, recipient and legal reference – for your incident playbook, drills and the real thing.
Calculator
When did you become aware?
Results update with every change. The address bar holds your inputs, so the link can be shared.
Result
Your reporting deadlines on one timeline
Became aware: Tuesday, 17 Nov 2026, 11:15. Every dated reporting stage of the selected regimes, ordered by due time.
- NIS2
Early warning (suspected unlawful/malicious, cross-border?)
within 24 h · from awareness
Section 32(1) no. 1 BSIG
- EU DORA
Initial notification
within 24 h · from awareness · upper limit from awareness
Delegated Regulation (EU) 2025/301 Art. 5(1)(a)
If classified later: 4 h from classification (Art. 5(2)).
- CRA
Incident: early warning
within 24 h · from awareness
Art. 14(4)(a)
- NIS2
Notification with initial assessment, severity, impact, IoCs
within 72 h · from awareness
Section 32(1) no. 2 BSIG
- CRA
Incident: notification
within 72 h · from awareness
Art. 14(4)(b)
- EU DORA
Intermediate report (even without status change); updated when regular activities are recovered
within 72 h · from initial notification · computed from the latest possible time of the previous stage
Delegated Regulation (EU) 2025/301 Art. 5(1)(b)
Falls on a weekend: under Art. 5(4) of Delegated Regulation (EU) 2025/301 reporting by Monday, 23 Nov 2026, 12:00 is sufficient (bank holidays not checked). This does not apply to initial notifications and intermediate reports of credit institutions, central counterparties, trading venue operators and financial entities identified as essential or important entities under NIS2 (Art. 5(5)).
- AI Act
Serious incident report
within 15 days · from awareness
Art. 73(2)
Immediately once a causal link (or its reasonable likelihood) has been established; 15 days from awareness is the upper limit.
- NIS2
Final report (progress report if ongoing, final after handling)
within 1 month · from notification · computed from the latest possible time of the previous stage
Section 32(1) no. 4, (2) BSIG
Falls on a weekend. The calculator does not move the deadline (see “How the calculator works”).
- CRA
Incident: final report
within 1 month · from incident notification · computed from the latest possible time of the previous stage
Art. 14(4)(c)
Falls on a weekend. The calculator does not move the deadline (see “How the calculator works”).
- EU DORA
Final report after root cause analysis
within 1 month · from latest intermediate report · computed from the latest possible time of the previous stage
Delegated Regulation (EU) 2025/301 Art. 5(1)(c); Art. 19(4)(c)
NIS2 / § 32 BSIG – significant incident
Recipient: joint BSI/BBK reporting point
- Intermediate report on BSI request · no fixed deadlineSection 32(1) no. 3 BSIG
The obligation applies at the earliest once the reporting channel is set up (§ 32(1) sentence 2 BSIG).
EU-DORA Art. 19 – major ICT-related incident
Recipient: competent authority (DE: BaFin)
- Classification per Del. Reg. 2024/1772 · no fixed deadlineArt. 18; Delegated Regulation (EU) 2024/1772 Art. 8
- Inform clients if their financial interests are affected · without undue delay, no fixed number of hoursArt. 19(3)
If a deadline falls on a weekend/holiday, by noon of the next working day – not for initial and intermediate reports of credit institutions, CCPs, trading venue operators and NIS2 entities (Art. 5(4), (5)). The competent authority may exclude further significant or systemic financial entities (Art. 5(6)).
If a deadline cannot be met: inform the authority before expiry with reasons (Art. 5(3)).
CRA Art. 14 – actively exploited vulnerability / severe incident
Recipient: CSIRT coordinator and ENISA via the single reporting platform
- Intermediate report at the request of the coordinating CSIRT · no fixed deadlineArt. 14(6)
- Inform affected users · without undue delay, no fixed number of hoursArt. 14(8)Text says 'after becoming aware' without fixed deadline; interpreted here as 'without undue delay'.
AI Act Art. 73 – serious incident (high-risk providers)
Recipient: market surveillance authority of the Member State where it occurred
- incomplete initial report permitted · no fixed deadlineArt. 73(5)
Practically relevant only with high-risk application (2 Dec 2027 / 2 Aug 2028).
One event can trigger several reporting duties in parallel (e.g. a CRA manufacturer that is also a NIS2 entity). The cockpit starts a separate clock per applicable regime.
Briefing
Deadline briefing by email
The calendar comes to you: the next deadlines with legal references every month and a reminder 14 days before each deadline of the selected regulations.
Comparison
Reporting deadlines compared: NIS2, EU DORA, CRA, AI Act
Every reporting stage of the four regimes with deadline, clock start and legal reference, as of 26 Oct 2026. This overview does not depend on your input.
| Reporting stage | Deadline | Clock starts at | Reference |
|---|---|---|---|
NIS2NIS2 / § 32 BSIG – significant incident Recipient: joint BSI/BBK reporting point | |||
| Early warning (suspected unlawful/malicious, cross-border?) | within 24 h | Clock starts at: awareness | Section 32(1) no. 1 BSIG |
| Notification with initial assessment, severity, impact, IoCs | within 72 h | Clock starts at: awareness | Section 32(1) no. 2 BSIG |
| Intermediate report on BSI request | no fixed deadline | Clock starts at: request by the authority | Section 32(1) no. 3 BSIG |
| Final report (progress report if ongoing, final after handling) | within 1 month | Clock starts at: notification | Section 32(1) no. 4, (2) BSIG |
EU DORAEU-DORA Art. 19 – major ICT-related incident Recipient: competent authority (DE: BaFin) | |||
| Classification per Del. Reg. 2024/1772 | no fixed deadline | Clock starts at: awareness | Art. 18; Delegated Regulation (EU) 2024/1772 Art. 8 |
| Initial notification | within 4 hno later than 24 h from awareness | Clock starts at: classification as major | Delegated Regulation (EU) 2025/301 Art. 5(1)(a) |
| Intermediate report (even without status change); updated when regular activities are recovered | within 72 h | Clock starts at: initial notification | Delegated Regulation (EU) 2025/301 Art. 5(1)(b) |
| Final report after root cause analysis | within 1 month | Clock starts at: latest intermediate report | Delegated Regulation (EU) 2025/301 Art. 5(1)(c); Art. 19(4)(c) |
| Inform clients if their financial interests are affected | without undue delay | Clock starts at: awareness | Art. 19(3) |
CRACRA Art. 14 – actively exploited vulnerability / severe incident Recipient: CSIRT coordinator and ENISA via the single reporting platform | |||
| Vulnerability: early warning | within 24 h | Clock starts at: awareness | Art. 14(2)(a) |
| Vulnerability: notification | within 72 h | Clock starts at: awareness | Art. 14(2)(b) |
| Vulnerability: final report | within 14 days | Clock starts at: corrective measure available | Art. 14(2)(c) |
| Incident: early warning | within 24 h | Clock starts at: awareness | Art. 14(4)(a) |
| Incident: notification | within 72 h | Clock starts at: awareness | Art. 14(4)(b) |
| Incident: final report | within 1 month | Clock starts at: incident notification | Art. 14(4)(c) |
| Intermediate report at the request of the coordinating CSIRT | no fixed deadline | Clock starts at: request by the authority | Art. 14(6) |
| Inform affected usersuncertain | without undue delay | Clock starts at: awareness | Art. 14(8) |
AI ActAI Act Art. 73 – serious incident (high-risk providers)uncertain Recipient: market surveillance authority of the Member State where it occurred | |||
| Serious incident report | within 15 days | Clock starts at: awareness | Art. 73(2) |
| widespread infringement / critical infrastructure (Art. 3(49)(b)) | within 2 days | Clock starts at: awareness | Art. 73(3) |
| death of a person | within 10 days | Clock starts at: awareness | Art. 73(4) |
| incomplete initial report permitted | no fixed deadline | Clock starts at: awareness | Art. 73(5) |
Method
How the calculator works
- The time zone is Europe/Berlin; summer and winter time are handled automatically.
- Deadlines in hours (4, 24 and 72 hours) run to the minute from the time entered. If a clock change falls in between, the wall-clock time shifts by one hour.
- Deadlines in days and months end at the same time of day on the target date. If that day does not exist in the target month, the deadline ends on the last day of the month (31 January plus one month gives 28 February, 29 February in a leap year).
- Later stages that depend on an earlier report are computed from the latest possible time of the previous stage. Reporting earlier also brings the next deadline forward.
- The calculator is conservative. General rules on time limits, such as Article 3 of Regulation (EEC, Euratom) No 1182/71 (the hour or day of the event is not counted; a period in days or months that ends on a weekend or public holiday is extended), can produce a later end of the deadline. They are not applied in the reporting party's favour.
- Weekends are flagged. For EU DORA the calculator also shows the time under Art. 5(4) of Delegated Regulation (EU) 2025/301; it does not check public holidays.
- Weekdays are computed from the calendar. The calculator does not assess whether an incident is reportable.
FAQ
Reporting deadlines: frequently asked questions
How long is the NIS2 reporting deadline?
Section 32 BSIG sets three fixed steps: an early warning no later than 24 h after awareness, a notification no later than 72 h after awareness and a final report no later than 1 month after the notification. Recipient: joint BSI/BBK reporting point.
When does the clock start?
For NIS2, the CRA and the AI Act at awareness. For EU DORA the initial notification runs from classification as major: within 4 h, no later than 24 h after awareness; if classified later, 4 h from classification apply. The calculator shows the trigger for every step.
Which deadlines apply to vulnerabilities under the CRA?
For actively exploited vulnerabilities, Art. 14(2) CRA requires an early warning no later than 24 h after awareness, a notification no later than 72 h and a final report no later than 14 days after a corrective measure is available. The reporting duties have applied since 11 Sept 2026. Recipient: CSIRT coordinator and ENISA via the single reporting platform.
What applies at weekends?
For EU DORA, Art. 5(4) of Delegated Regulation (EU) 2025/301 allows reporting by noon of the next working day; this does not apply to initial and intermediate notifications of certain financial entities. For NIS2, the CRA and the AI Act the calculator does not shift any deadline; it flags weekends.
Is there a template for the NIS2 notification?
What each notification must contain is set out in Section 32 BSIG; the recipient is the joint BSI/BBK reporting point. Alev-B does not provide a notification form. The calculator gives you the deadlines; the reporting drill in the regulatory cockpit walks through the process with all clocks.
Does the calculator replace legal advice?
No. It calculates the deadlines from the cited primary sources (as of 26 Oct 2026) and does not assess whether an incident is reportable. The published legal text prevails.
Primary sources
Sources and status
German implementing law for NIS2: BSI-Gesetz (BSIG) of 2 December 2025 (BGBl. 2025 I No. 301, p. 2), Art. 1 NIS2UmsuCG, in force since 06.12.2025; status: last amended by Art. 8 of the Act of 22.10.2026 (BGBl. 2026 I No. 318).
- BSI-Gesetz (BSIG) of 2 December 2025 (BGBl. 2025 I No. 301, p. 2), Art. 1 NIS2UmsuCG, in force since 06.12.2025; status: last amended by Art. 8 of the Act of 22.10.2026 (BGBl. 2026 I No. 318) · primary source · retrieved 26/10/2026
- Directive (EU) 2022/2555 (NIS 2 Directive), OJ L 333, 27.12.2022, p. 80 · primary source · retrieved 26/10/2026
- Regulation (EU) 2022/2554 on digital operational resilience for the financial sector (DORA), OJ L 333, 27.12.2022, p. 1 · primary source · retrieved 26/10/2026
- Commission Delegated Regulation (EU) 2025/301 (RTS on the content and time limits of reports on major ICT-related incidents), OJ L, 20.2.2025 · primary source · retrieved 26/10/2026
- Commission Implementing Regulation (EU) 2025/302 (ITS on standard forms, templates and procedures for reporting major ICT-related incidents), OJ L, 20.2.2025 · primary source · retrieved 26/10/2026
- Commission Delegated Regulation (EU) 2024/1772 (RTS on the classification of ICT-related incidents and cyber threats, materiality thresholds), OJ L, 25.6.2024 · primary source · retrieved 26/10/2026
- Regulation (EU) 2024/2847 (Cyber Resilience Act), OJ L, 20.11.2024 · primary source · retrieved 26/10/2026
- Regulation (EU) 2024/1689, consolidated text of 27.07.2026 (incorporating Regulation (EU) 2026/1744); documentation tool without legal effect · primary source · retrieved 26/10/2026
Orientation based on the cited primary sources (as of 26 Oct 2026) – not legal advice; the text published in the Official Journal or Federal Law Gazette prevails.