EU AI Act Art. 73: serious-incident reporting

Serious-incident reporting for high-risk systems, on the deadlines of chapter 08's reporting-clock table

By Jorge García Aibar Reviewed 2026-09-24

From clause to evidence Build the artefact, then file every output it produces as a record that names AIGE-OBL-EUAIA-ART73. Drawn from chapter 08.

Text alternative

Clause: EU AI Act, Art. 73.
Duty holder: Provider.
Applies from: 2027-12-02, Deferred.
Artefact: Incident detection and triage….
Layers: Layer 05, Layer 04.
Evidence record: AI incident record.
Record schemas: AI incident record .
The same topic in 15 other frameworks; the crosswalk section below links each clause.

When this obligation applies The first date in the row's status, then each later step: filled once its date has passed, outlined while it is still ahead of the review date.

Data table: the dates

Dates of AIGE-OBL-EUAIA-ART73
Date	Step	Detail
2027-12-02	Deferred	Annex III
2028-08-02	High-risk (Annex I)	Applies to Annex I embedded (product safety-component) systems
2030-08-02	Later step	Deadline for legacy high-risk systems intended for use by public authorities (Art. 111(2))

Id

AIGE-OBL-EUAIA-ART73

Instrument

EU AI Act (post-Omnibus) law

Compared side by side

ISO 42001 vs EU AI Act · NIST AI RMF vs EU AI Act

Clause

Art. 73

Duty holder

Provider

Authority

National MSA

Applies from

2027-12-02 Deferred · Annex III

Later dates

2028-08-02 Applies to Annex I embedded (product safety-component) systems
2030-08-02 Deadline for legacy high-risk systems intended for use by public authorities (Art. 111(2))

System class

High-risk (Annex III) · High-risk (Annex I)

The artefact that evidences it

Incident detection and triage pipeline; reporting-clock automation; evidence capture.

What this obligation connects to Solid edges are direct relations, dashed ones looser (a case that cites the same article, a framework whose clauses only touch the topic); patterns and controls take the colour of their stack layer. Select a node to open it; the lists below give every relation in full.

Data table: every relation

Relations of AIGE-OBL-EUAIA-ART73
Family	Item	Relation
Patterns	Incident Pipeline	Direct
Open controls	AIGE-CTL-EVAL-007 Incident Evidence Preservation	Direct
Open controls	AIGE-CTL-DEPLOY-011 Serious incident reporting clocks	Direct
Same crosswalk topic	AI Verify 9.5.4, 1.5.1, 1.6.1, 5.11.1	Core clause
Same crosswalk topic	CSA AICM SEF-07, SEF-08	Core clause
Same crosswalk topic	China GenAI Measures GenAI Art. 14, GenAI Art. 15	Core clause
Same crosswalk topic	EU AI Act Art. 72, Art. 26(5), Art. 55, Art. 3(49), Art. 20	Core clause
Same crosswalk topic	G7 Code G7 Action 2, G7 Action 4	Core clause
Same crosswalk topic	GAO AI Accountability 4.1, 4.2	Core clause
Same crosswalk topic	GDPR Arts. 33–34	Core clause
Same crosswalk topic	GPAI Code Safety C9, Safety 3.5	Core clause
Same crosswalk topic	ISO 42001 A.8, 10.2	Core clause
Same crosswalk topic	Korea AI Act Art. 32(1)	Core clause
Same crosswalk topic	NIST AI RMF MANAGE 4, MANAGE 4.3, MANAGE 2.4, GOVERN 4.3	Core clause
Same crosswalk topic	Singapore Agentic Agentic 2.3.3	Core clause
Same crosswalk topic	Singapore GenAI GenAI 4	Core clause
Same crosswalk topic	TC260 Framework 3.0 TC260 5.3.7, TC260 5.3.18, TC260 App. 2 II.6	Core clause
Same crosswalk topic	China Algo. Rec. AlgoRec Art. 7	Related clause

Patterns that build it

Incident Pipeline (layer 5)

The same topic in other frameworks

From the topic crosswalk: the clauses filed under the same topics as this one. Mappings are illustrative, not a claim of conformity.

Incident response and monitoring

EU AI Act Art. 72 Post-market monitoring by providers and post-market monitoring plan (core)
ISO 42001 A.8 Information for interested parties (core)
ISO 42001 10.2 Nonconformity and corrective action (core)
NIST AI RMF MANAGE 4 MANAGE 4: Risk treatments, including response and recovery, and communication plans for the identified and measured AI risks are documented and monitored (core)
TC260 Framework 3.0 TC260 5.3.7 Real-time risk monitoring (core)
TC260 Framework 3.0 TC260 5.3.18 Incident reporting (core)
China GenAI Measures GenAI Art. 14 Handle and report unlawful content (core)
China GenAI Measures GenAI Art. 15 Complaint and reporting mechanism (core)
EU AI Act Art. 26(5) Deployer monitoring, informing the provider and suspending use (core)
GPAI Code Safety C9 Commitment 9: Serious incident reporting (core)
GDPR Arts. 33–34 Notification and communication of a personal data breach (core)
NIST AI RMF MANAGE 4.3 MANAGE 4.3: Incidents and errors are communicated to relevant AI actors, including affected communities. Processes for tracking, responding to, and recovering from incidents and errors are followed and documented (core)
CSA AICM SEF-07 Incident Management and Response (core)
CSA AICM SEF-08 Security Breach Notification (core)
Korea AI Act Art. 32(1) Safety duties for AI above the compute threshold (core)
Singapore GenAI GenAI 4 Incident Reporting (core)
Singapore Agentic Agentic 2.3.3 When deploying, continuously monitor and test (core)
G7 Code G7 Action 2 Identify and mitigate vulnerabilities, incidents and misuse after deployment (core)
G7 Code G7 Action 4 Responsible information sharing and reporting of incidents (core)
GAO AI Accountability 4.1 Planning: develop plans for continuous or routine monitoring of the AI system (core)
GAO AI Accountability 4.2 Drift: establish the range of data and model drift that is acceptable (core)
AI Verify 9.5.4 Accountability: enable an incident management process to report and respond to actions or decisions that affect the AI system's outcome (core)
AI Verify 1.5.1 Transparency: communicate to end users whenever an incident has occurred (core)
EU AI Act Art. 55 Obligations for providers of general-purpose AI models with systemic risk
TC260 Framework 3.0 TC260 App. 2 II.6 Emergency plans
China Algo. Rec. AlgoRec Art. 7 Security management and emergency response
EU AI Act Art. 3(49) Definition of serious incident
EU AI Act Art. 20 Corrective actions and duty of information
GPAI Code Safety 3.5 Measure 3.5: Post-market monitoring
NIST AI RMF MANAGE 2.4 MANAGE 2.4: Mechanisms are in place and applied, and responsibilities are assigned and understood, to supersede, disengage, or deactivate AI systems that demonstrate performance or outcomes inconsistent with intended use
NIST AI RMF GOVERN 4.3 GOVERN 4.3: Organizational practices are in place to enable AI testing, identification of incidents, and information sharing
AI Verify 1.6.1 Transparency: give end users and external parties the means to report adverse impacts, with whistleblower protection
AI Verify 5.11.1 Security: monitor AI system outputs and behaviour after deployment and alert system owners to issues

Open controls that evidence it

Draft controls in the open control profiles that map to this row: each states a requirement and the evidence it must leave behind.

AIGE-CTL-EVAL-007 Incident Evidence Preservation (Evaluation environment profile)
AIGE-CTL-DEPLOY-011 Serious incident reporting clocks (Deployment and monitoring profile)

Source

Chapter 08, section EU AI Act, post-Omnibus, checked against its sources on the review date above.

Machine-readable

This obligation: /api/v1/obligations/aige-obl-euaia-art73.json
The register: /api/v1/obligations.json · CSV
Schema and stability promise: open data and API

Cite this obligation

García Aibar, J. (2026). EU AI Act Art. 73: serious-incident reporting (AIGE-OBL-EUAIA-ART73). In AI Governance Engineering: The Thesis & Body of Knowledge (v0.5.0). https://doi.org/10.5281/zenodo.22956197. https://aigovernanceengineer.com/obligations/aige-obl-euaia-art73. CC BY 4.0

BibTeX

@misc{aige2026obligation,
  author       = {Jorge García Aibar},
  title        = {{EU AI Act Art. 73: serious-incident reporting (AIGE-OBL-EUAIA-ART73)}},
  howpublished = {In AI Governance Engineering: The Thesis \& Body of Knowledge},
  year         = {2026},
  version      = {0.5.0},
  doi          = {10.5281/zenodo.22956197},
  url          = {https://aigovernanceengineer.com/obligations/aige-obl-euaia-art73},
  note         = {Version 0.5.0}
}