← Vetro Attest · High-risk classifier · Log retention calculator · Penalty calculator · Disclosure generator · Incident report · Log checker · Deutsch · Français · Italiano · Español
EU AI Act Article 73 serious incident report: deadline and draft
If a high-risk AI system causes a serious incident, the provider must report it to the market surveillance authority within 2, 10 or 15 days of becoming aware. Enter what happened and when you found out: you get the deadline and a report draft to complete. Runs entirely in your browser; nothing is sent anywhere.
After an incident, the authority asks for the file
An Art. 73 report is usually followed by a request for the technical documentation and risk assessment. The compliance pack drafts Annex IV, the FRIA (Art. 27), the AI literacy plan (Art. 4) and Art. 50 notices from one questionnaire and signs them with ed25519. No ledger or code needed.
Get the compliance pack, 99 USDThe authority will ask for the evidence. Make it evidence nobody can doubt.
Article 73(6) forbids altering the system before you inform the authorities in a way that could affect the investigation. A log you can edit invites the question of whether you did. Record every model call, tool call and policy decision in a signed, hash-chained ledger, check your current logs with the free log checker, and attach a Vetro Attest report: an ed25519 counter-signature over the affected runs plus an EU AI Act evidence mapping. 29 USD, one-off.
Get the countersigned report or check whether your system is high-riskOrientation tool, not legal advice. Article 73 applies to high-risk AI systems, on the timeline of the high-risk rules that the Digital Omnibus postponed (deadlines); the European Commission publishes the official reporting guidance and template. Full walkthrough: Article 73 serious incident reporting.