Skip to main content
Praxikon
Comparisons

Comparison

Article 12 versus Article 72: logging and post-market monitoring

The difference

Article 12 is about the recording itself: a high-risk AI system has to log events automatically so that its behaviour can be traced afterwards. Article 72 is about what happens with that recording: after placing the system on the market the provider has to keep actively monitoring it and use what that produces.

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.

Status

Article 12, recording
Upcoming
Article 72, monitoring
Applicable

Applies from

Article 12, recording
2 December 2027
Article 72, monitoring
2 August 2026

Who carries the duty

Article 12, recording
Provider of an AI system
Article 72, monitoring
Provider of an AI system

Who is affected

Article 12, recording
Deployer
Article 72, monitoring
Deployer

Who supervises

Article 12, recording
Not recorded
Article 72, monitoring
Not recorded

When this applies

Article 12, recording
The system is high-risk; the provider designs the logging, provider and deployer retain the logs under their control.
Article 72, monitoring
The provider has a high-risk system on the market; deployers supply the real-world data via monitoring and signals.

Exceptions

Article 12, recording
The retention period may be limited by Union or national law, including data protection.
Article 72, monitoring
The plan may be proportionate to the nature of the system and align with existing sectoral monitoring regimes.

First actions

Article 12, recording
Design logging into the system
Article 72, monitoring
Draw up a post-market monitoring plan

Evidence that belongs with it

Article 12, recording
Logs and retention regime
Article 72, monitoring
Monitoring plan and reports

Control

Article 12, recording
Periodic log review
Article 72, monitoring
Signal-to-action loop

Version and review status

Article 12, recording
v1.0.0, placed against the official source
Article 72, monitoring
v2.0.0, placed against the official source
Article 12: logging and traceabilityArticle 72: post-market monitoring

Official sources and locators

Per side, the provisions the statements above rest on.

Article 12, recording

  • EU Artificial Intelligence Act 2024/1689

    Locator: Article 12, Article 19 and Article 26(6)

    Open official source

  • Digital Omnibus on AI 2026/1744

    Locator: Amended Article 113 application dates

    Open official source

Article 72, monitoring

  • EU Artificial Intelligence Act 2024/1689

    Locator: Article 72(1)-(4)

    Open official source

  • EU Artificial Intelligence Act 2024/1689

    Locator: Article 113, second paragraph

    Open official source

  • Digital Omnibus on AI 2026/1744

    Locator: Article 1, point (40)(b), replacing Article 113, third paragraph, point (c)

    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 12: logging and traceability",
praxikon:eu:ai-act:obligation:article-12-logging@1.0.0,
dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.2.0 (schema 1.5.0),
effective_at 2026-07-27T00:00:00.000Z, known_at 2026-08-08T00:00:00.000Z,
sha256 92daf8448d3471e5014ea66a2dc2731909f2689e5e3bdb243f49a75572002f20,
https://www.praxikon.com/en/verplichtingen/article-12-logging
(https://www.praxikon.com/api/v1/obligations?id=praxikon%3Aeu%3Aai-act%3Aobligation%3Aarticle-12-logging&effective_at=2026-07-27&known_at=2026-08-08&lang=en, accessed 2026-10-08)

Short form

praxikon:eu:ai-act:obligation:article-12-logging@1.0.0 (sha256 92daf844)

BibTeX

@misc{praxikon-eu-ai-act-obligation-article-12-logging-1-0-0,
  author       = {{Praxikon}},
  title        = {Article 12: logging and traceability},
  year         = {2026},
  version      = {1.0.0},
  number       = {praxikon:eu:ai-act:obligation:article-12-logging},
  howpublished = {AI Act Change \& Evidence Graph, dataset 2.2.0, schema 1.5.0},
  note         = {effective_at 2026-07-27T00:00:00.000Z; known_at 2026-08-08T00:00:00.000Z; sha256 92daf8448d3471e5014ea66a2dc2731909f2689e5e3bdb243f49a75572002f20},
  url          = {https://www.praxikon.com/en/verplichtingen/article-12-logging},
  urldate      = {2026-10-08},
  language     = {en}
}

CSL JSON

[
  {
    "id": "praxikon:eu:ai-act:obligation:article-12-logging@1.0.0",
    "type": "dataset",
    "title": "Article 12: logging and traceability",
    "container-title": "AI Act Change & Evidence Graph",
    "publisher": "Praxikon",
    "version": "1.0.0",
    "number": "praxikon:eu:ai-act:obligation:article-12-logging",
    "URL": "https://www.praxikon.com/en/verplichtingen/article-12-logging",
    "language": "en",
    "issued": {
      "date-parts": [
        [
          2026,
          8,
          8
        ]
      ]
    },
    "accessed": {
      "date-parts": [
        [
          2026,
          10,
          8
        ]
      ]
    },
    "note": "dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.2.0; schema 1.5.0; effective_at 2026-07-27T00:00:00.000Z; known_at 2026-08-08T00:00:00.000Z; sha256 92daf8448d3471e5014ea66a2dc2731909f2689e5e3bdb243f49a75572002f20; retrieved_from https://www.praxikon.com/api/v1/obligations?id=praxikon%3Aeu%3Aai-act%3Aobligation%3Aarticle-12-logging&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 72: post-market monitoring",
praxikon:eu:ai-act:obligation:article-72-post-market-monitoring@2.0.0,
dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.2.0 (schema 1.5.0),
effective_at 2026-07-27T00:00:00.000Z, known_at 2026-09-06T00:00:00.000Z,
sha256 6fe04840ffe25ded5e84488a9486d4fa3f46720b9c66ce47d2244110d9e33098,
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-09-06&lang=en, accessed 2026-10-08)

Short form

praxikon:eu:ai-act:obligation:article-72-post-market-monitoring@2.0.0 (sha256 6fe04840)

BibTeX

@misc{praxikon-eu-ai-act-obligation-article-72-post-market-monitoring-2-0-0,
  author       = {{Praxikon}},
  title        = {Article 72: post-market monitoring},
  year         = {2026},
  version      = {2.0.0},
  number       = {praxikon:eu:ai-act:obligation:article-72-post-market-monitoring},
  howpublished = {AI Act Change \& Evidence Graph, dataset 2.2.0, schema 1.5.0},
  note         = {effective_at 2026-07-27T00:00:00.000Z; known_at 2026-09-06T00:00:00.000Z; sha256 6fe04840ffe25ded5e84488a9486d4fa3f46720b9c66ce47d2244110d9e33098},
  url          = {https://www.praxikon.com/en/verplichtingen/article-72-post-market-monitoring},
  urldate      = {2026-10-08},
  language     = {en}
}

CSL JSON

[
  {
    "id": "praxikon:eu:ai-act:obligation:article-72-post-market-monitoring@2.0.0",
    "type": "dataset",
    "title": "Article 72: post-market monitoring",
    "container-title": "AI Act Change & Evidence Graph",
    "publisher": "Praxikon",
    "version": "2.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,
          9,
          6
        ]
      ]
    },
    "accessed": {
      "date-parts": [
        [
          2026,
          10,
          8
        ]
      ]
    },
    "note": "dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.2.0; schema 1.5.0; effective_at 2026-07-27T00:00:00.000Z; known_at 2026-09-06T00:00:00.000Z; sha256 6fe04840ffe25ded5e84488a9486d4fa3f46720b9c66ce47d2244110d9e33098; 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-09-06&lang=en; licence https://www.praxikon.com/nl/legal/terms"
  }
]

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

Have it done

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. The AI Act scan maps your role, the classification and the record per system.

AI Act scan · from €3,950 · up to 10 applications · 3 weeks

See the AI Act scan

Carried out by Zahed Ashkara, the lawyer behind this explanation.

Other comparisons

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