Comparison

Article 72 versus Article 73: monitoring and incident reporting

Article 72 is continuous and internal: the provider gathers and assesses how the system behaves in practice. Article 73 is an event and external: as soon as a serious incident occurs, a report goes to the market surveillance authority.

The official source remains authoritative. This is general interpretation and not legal advice about your situation.

The fields side by side

Every row comes from the objects themselves. Where a field is empty, it says so; we do not fill in an assumption where the source is silent.

Article 72 versus Article 73: monitoring and incident reporting
Field	Article 72, continuous	Article 73, event
Status	Upcoming	Upcoming
Applies from	2 December 2027	2 December 2027
Who carries the duty	Provider of an AI system	Provider of an AI system
Who is affected	Deployer	Deployer
Who supervises	Not recorded	Market surveillance authority
When this applies	The provider has a high-risk system on the market; deployers supply the real-world data via monitoring and signals.	A serious incident occurs with a high-risk system: death or serious harm to health, serious and irreversible disruption of critical infrastructure, infringement of fundamental-rights protections or serious damage to property or environment.
Exceptions	The plan may be proportionate to the nature of the system and align with existing sectoral monitoring regimes.	For systems under sectoral reporting regimes with equivalent duties, reporting may run through that regime to avoid duplication.
First actions	Draw up a post-market monitoring plan	Set up an incident process with reporting routes
Evidence that belongs with it	Monitoring plan and reports	Incident register and reports
Control	Signal-to-action loop	Incident drill and deadline watch
Version and review status	v1.0.0, placed against the official source	v1.0.0, placed against the official source

Status

Article 72, continuous: Upcoming
Article 73, event: Upcoming

Applies from

Article 72, continuous: 2 December 2027
Article 73, event: 2 December 2027

Who carries the duty

Article 72, continuous: Provider of an AI system
Article 73, event: Provider of an AI system

Who is affected

Article 72, continuous: Deployer
Article 73, event: Deployer

Who supervises

Article 72, continuous: Not recorded
Article 73, event: Market surveillance authority

When this applies

Article 72, continuous: The provider has a high-risk system on the market; deployers supply the real-world data via monitoring and signals.
Article 73, event: A serious incident occurs with a high-risk system: death or serious harm to health, serious and irreversible disruption of critical infrastructure, infringement of fundamental-rights protections or serious damage to property or environment.

Exceptions

Article 72, continuous: The plan may be proportionate to the nature of the system and align with existing sectoral monitoring regimes.
Article 73, event: For systems under sectoral reporting regimes with equivalent duties, reporting may run through that regime to avoid duplication.

First actions

Article 72, continuous: Draw up a post-market monitoring plan
Article 73, event: Set up an incident process with reporting routes

Evidence that belongs with it

Article 72, continuous: Monitoring plan and reports
Article 73, event: Incident register and reports

Control

Article 72, continuous: Signal-to-action loop
Article 73, event: Incident drill and deadline watch

Version and review status

Article 72, continuous: v1.0.0, placed against the official source
Article 73, event: v1.0.0, placed against the official source

Article 72: post-market monitoring Article 73: serious incident reporting

Official sources and locators

Per side, the provisions the statements above rest on.

Article 72, continuous

EU Artificial Intelligence Act 2024/1689
Locator: Article 72(1)-(4)
Open official source
Digital Omnibus on AI 2026/1744
Locator: Amended Article 113 application dates
Open official source

Article 73, event

EU Artificial Intelligence Act 2024/1689
Locator: Article 73(1)-(11)
Open official source
Digital Omnibus on AI 2026/1744
Locator: Amended Article 113 application dates
Open official source

Referring to these two objects

Each side has its own stable identifier, version and hash. Take them separately; you cite a comparison by citing the two objects.

Referring to this object

Citation block

Copy this reference into your advice, article or file. The identifier, the version and the hash keep the statement findable later, even once the dataset has moved on.

Reference

Praxikon, "Article 72: post-market monitoring",
praxikon:eu:ai-act:obligation:article-72-post-market-monitoring@1.0.0,
dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.1.0 (schema 1.4.0),
effective_at 2026-07-27T00:00:00.000Z, known_at 2026-08-08T00:00:00.000Z,
sha256 b635803b8ca4eff99ebd690c91d90d1ffbbe107fee55345d457d855f2340e2a5,
https://www.praxikon.com/en/verplichtingen/article-72-post-market-monitoring
(https://www.praxikon.com/api/v1/obligations?id=praxikon%3Aeu%3Aai-act%3Aobligation%3Aarticle-72-post-market-monitoring&effective_at=2026-07-27&known_at=2026-08-08&lang=en, accessed 2026-08-24)

Short form

praxikon:eu:ai-act:obligation:article-72-post-market-monitoring@1.0.0 (sha256 b635803b)

BibTeX

@misc{praxikon-eu-ai-act-obligation-article-72-post-market-monitoring-1-0-0,
  author       = {{Praxikon}},
  title        = {Article 72: post-market monitoring},
  year         = {2026},
  version      = {1.0.0},
  number       = {praxikon:eu:ai-act:obligation:article-72-post-market-monitoring},
  howpublished = {AI Act Change \& Evidence Graph, dataset 2.1.0, schema 1.4.0},
  note         = {effective_at 2026-07-27T00:00:00.000Z; known_at 2026-08-08T00:00:00.000Z; sha256 b635803b8ca4eff99ebd690c91d90d1ffbbe107fee55345d457d855f2340e2a5},
  url          = {https://www.praxikon.com/en/verplichtingen/article-72-post-market-monitoring},
  urldate      = {2026-08-24},
  language     = {en}
}

CSL JSON

[
  {
    "id": "praxikon:eu:ai-act:obligation:article-72-post-market-monitoring@1.0.0",
    "type": "dataset",
    "title": "Article 72: post-market monitoring",
    "container-title": "AI Act Change & Evidence Graph",
    "publisher": "Praxikon",
    "version": "1.0.0",
    "number": "praxikon:eu:ai-act:obligation:article-72-post-market-monitoring",
    "URL": "https://www.praxikon.com/en/verplichtingen/article-72-post-market-monitoring",
    "language": "en",
    "issued": {
      "date-parts": [
        [
          2026,
          8,
          8
        ]
      ]
    },
    "accessed": {
      "date-parts": [
        [
          2026,
          8,
          24
        ]
      ]
    },
    "note": "dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.1.0; schema 1.4.0; effective_at 2026-07-27T00:00:00.000Z; known_at 2026-08-08T00:00:00.000Z; sha256 b635803b8ca4eff99ebd690c91d90d1ffbbe107fee55345d457d855f2340e2a5; retrieved_from https://www.praxikon.com/api/v1/obligations?id=praxikon%3Aeu%3Aai-act%3Aobligation%3Aarticle-72-post-market-monitoring&effective_at=2026-07-27&known_at=2026-08-08&lang=en; licence https://www.praxikon.com/nl/legal/terms"
  }
]

How to verify a reference later is set out in the methodology. Terms

Referring to this object

Citation block

Copy this reference into your advice, article or file. The identifier, the version and the hash keep the statement findable later, even once the dataset has moved on.

Reference

Praxikon, "Article 73: serious incident reporting",
praxikon:eu:ai-act:obligation:article-73-incident-reporting@1.0.0,
dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.1.0 (schema 1.4.0),
effective_at 2026-07-27T00:00:00.000Z, known_at 2026-08-08T00:00:00.000Z,
sha256 50ff870bf326acf58085d7a7c88cc7b5f38663837e21ac44d10ce88c5ee65eff,
https://www.praxikon.com/en/verplichtingen/article-73-incident-reporting
(https://www.praxikon.com/api/v1/obligations?id=praxikon%3Aeu%3Aai-act%3Aobligation%3Aarticle-73-incident-reporting&effective_at=2026-07-27&known_at=2026-08-08&lang=en, accessed 2026-08-24)

Short form

praxikon:eu:ai-act:obligation:article-73-incident-reporting@1.0.0 (sha256 50ff870b)

BibTeX

@misc{praxikon-eu-ai-act-obligation-article-73-incident-reporting-1-0-0,
  author       = {{Praxikon}},
  title        = {Article 73: serious incident reporting},
  year         = {2026},
  version      = {1.0.0},
  number       = {praxikon:eu:ai-act:obligation:article-73-incident-reporting},
  howpublished = {AI Act Change \& Evidence Graph, dataset 2.1.0, schema 1.4.0},
  note         = {effective_at 2026-07-27T00:00:00.000Z; known_at 2026-08-08T00:00:00.000Z; sha256 50ff870bf326acf58085d7a7c88cc7b5f38663837e21ac44d10ce88c5ee65eff},
  url          = {https://www.praxikon.com/en/verplichtingen/article-73-incident-reporting},
  urldate      = {2026-08-24},
  language     = {en}
}

CSL JSON

[
  {
    "id": "praxikon:eu:ai-act:obligation:article-73-incident-reporting@1.0.0",
    "type": "dataset",
    "title": "Article 73: serious incident reporting",
    "container-title": "AI Act Change & Evidence Graph",
    "publisher": "Praxikon",
    "version": "1.0.0",
    "number": "praxikon:eu:ai-act:obligation:article-73-incident-reporting",
    "URL": "https://www.praxikon.com/en/verplichtingen/article-73-incident-reporting",
    "language": "en",
    "issued": {
      "date-parts": [
        [
          2026,
          8,
          8
        ]
      ]
    },
    "accessed": {
      "date-parts": [
        [
          2026,
          8,
          24
        ]
      ]
    },
    "note": "dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.1.0; schema 1.4.0; effective_at 2026-07-27T00:00:00.000Z; known_at 2026-08-08T00:00:00.000Z; sha256 50ff870bf326acf58085d7a7c88cc7b5f38663837e21ac44d10ce88c5ee65eff; retrieved_from https://www.praxikon.com/api/v1/obligations?id=praxikon%3Aeu%3Aai-act%3Aobligation%3Aarticle-73-incident-reporting&effective_at=2026-07-27&known_at=2026-08-08&lang=en; licence https://www.praxikon.com/nl/legal/terms"
  }
]

How to verify a reference later is set out in the methodology. Terms

Execution

Put the evidence where it will be asked for

Two duties that look alike rarely produce the same piece of evidence, and you notice that difference only once a supervisory authority or a client asks. Praxikon does not carry that out; Embed AI maps scope, ownership and recording per system.

See the Embed AI approach

Unsure about your role itself rather than the duties that come with it? Work out whether you are a provider or a deployer

The fields side by side

Official sources and locators

Article 72, continuous

Article 73, event

Referring to these two objects

Citation block

Citation block

Put the evidence where it will be asked for

Other comparisons