How do I use the Art. 73 Incident Notification Generator?

Log the incident date, type, and severity Record affected persons and immediate remediation actions taken Calculate the notification deadline automatically Fill in the mandatory Art. 73(3) notification content Export the formal notification document for submission Save to vault as part of your Art. 72 post-market monitoring record

Omnibus update (7 May 2026): Annex III high-risk provisionally shifted from 2 Aug 2026 to 2 Dec 2027. Art. 50 transparency (chatbots, deepfakes, emotion, biometric) still 2 Aug 2026. Art. 4 / Art. 5 / GPAI live now. Details.

Why this matters

Art. 73 requires providers and deployers to formally notify the relevant market surveillance authority within defined deadlines (2, 10, or 15 working days). The notification must contain specific mandatory content. This tool generates the submission-ready notification document.

How to use it

1Log the incident date, type, and severity
2Record affected persons and immediate remediation actions taken
3Calculate the notification deadline automatically
4Fill in the mandatory Art. 73(3) notification content
5Export the formal notification document for submission
6Save to vault as part of your Art. 72 post-market monitoring record

Legal basis

Art. 73
Art. 73(3)
Art. 72

Notification deadline: 2026-06-05 (15 working days)

Art. 73(2) — serious incident, general default

Art. 73(1) requires notification “without undue delay” from the moment a causal link is established. The deadline above is the statutory maximum, not a target.

Art. 73 Incident Notification Generator

AI System Name

System Version

EU Database Registration Number

Date of Incident

Incident Type

Internal Severity Assessment

For internal records only. This does NOT determine the legal notification deadline, which is set by the statutory triggers below (Art. 73(2) / (3) / (4)).

Competent Market Surveillance Authority (Art. 73 addressee)

VERIFY BEFORE SENDING. The MSA designation register is still consolidating in May 2026. Confirm the current responsible body in the EU AI Office authority register and the relevant national portal before submitting an Art. 73 / Art. 27(3) / Art. 49 notification.

Statutory deadline triggers (tick all that apply)

The incident has resulted in the death of a person (Art. 73(4) — 10 working days).The incident is a widespread infringement (Art. 3(61): affecting persons in three or more Member States, or affecting collective interests of consumers) (Art. 73(3) — 2 working days).The incident has caused serious and irreversible disruption to critical infrastructure (Art. 73(3) — 2 working days).

If none apply, the 15 working day default under Art. 73(2) applies. Incident type and severity above do not by themselves shorten the deadline.

Incident Description

Art. 73(3)(a)

Affected Person Categories

Art. 73(3)(b)

Estimated Number of Persons Affected

Art. 73(3)(b)

Immediate Action Taken

Art. 73(3)(c)

Root Cause Analysis (Preliminary)

Art. 73(3)(d)

Corrective Measures Planned

Art. 73(3)(d)

Notifying Person

Important Legal Disclaimer

This tool is a self-assessment aid only and does not constitute legal advice, a formally certified compliance assessment, or an independently audited report.

Outputs — including reports, scores, checklists, and generated documents — are for internal use and should be reviewed by a qualified legal representative or independent AI compliance auditor before being relied upon for regulatory, procurement, or public-disclosure purposes.

This tool does not replace a notified body conformity assessment where one is required under Art. 43(1) of the EU AI Act (e.g. biometric identification systems for law enforcement).

All assessment risk lies with the user. AIAuditRef, its developers, and staff accept no liability for losses arising from use of or reliance on these outputs. Always verify against official sources: the EU AI Act (Regulation 2024/1689) and your national enforcement authority.