Artificial Intelligence Policy Tracker
Legal requirement Post-market monitoring European Union Partially applicable

Operate a post-market monitoring system

Download: JSON · MarkdownUnder EU AI Act, Article 72

Pending review · linked to the official source, waiting for a reviewer to confirm it (a factual check against the official source, not a legal review or legal advice)
What this label means
Verified
— a named reviewer opened the official source and confirmed the record; the date and the reviewer are shown.
Pending review
— linked to the official source and in the queue for a reviewer to confirm.
Source-linked
— linked to the official source, not yet confirmed by a reviewer.
Verification policy and current standing · a factual check, not legal advice.
No change recorded as of 26 Sep 2026 · official source last checked
On this page 9 sections

In brief

Operate a post-market monitoring system is a legal requirement under the EU AI Act in the European Union (Article 72). It applies from 2 December 2027. The record carries 1 evidence example and mappings to 2 frameworks. In practice: Define performance and drift indicators, feedback channels and review cadence in a monitoring plan.

Instrument
EU AI Act
Jurisdiction
European Union
Nature
Legal requirement
Source reference
Article 72
Applies from
2 December 2027
Who it binds
Provider / developer
Evidence examples
1
Framework mappings
ISO/IEC 42001:2023, NIST AI Risk Management Framework 1.0
Controls that meet it
3
Official source
Open official text
Verification
Pending review · source-linked

What does it require?

Providers must establish and document a post-market monitoring system proportionate to the nature of the AI technology and its risks, actively and systematically collecting and analysing performance data throughout the system's lifetime, based on a monitoring plan that is part of the technical documentation. The Commission is to adopt a template for the plan.

Practical action

Define performance and drift indicators, feedback channels and review cadence in a monitoring plan.

Who does it apply to?

Providers of high-risk AI systems.

Applies from:

Which controls meet this duty?

Satisfies: the control, operated properly, does the work the duty asks for. Supports: it contributes but the duty needs more. Each control page lists every other duty it serves, so work done once can be counted once.

  • satisfiesTechnical measureAI system owner · continuous
    Post-deployment monitoring and drift detection

    Serves 10 recorded duties · evidence: Post-market monitoring plan, Monitoring dashboard or periodic monitoring report, Monitoring review decision

    Documented monitoring plan with indicators, feedback channels and review cadence.

  • supportsTechnical measureEngineering lead · continuous
    Automatic event logging and record retention

    Serves 9 recorded duties · evidence: AI system event logs, Log schema and retention standard, Log integrity and retention check

    Logs are the primary data source.

  • supportsProcessIncident coordinator · continuous
    AI incident management and regulatory reporting

    Serves 14 recorded duties · evidence: AI incident response playbook, AI incident record, Incident report to an authority

    Monitoring findings escalate into incidents.

Templates that cover this duty

Generated from the records. Free · no account · links emailed to your work address. This duty is cited in each file with its source reference and a link back here.

All 9 templates that cover it →

What evidence would a reviewer expect?

Evidence examples
EvidenceTypeNotes
Post-market monitoring plan and periodic reportsreport

Framework mappings

Original editorial crosswalks. They cite clause numbers only and reproduce no standard text; confidence reflects how direct the mapping is.

See every European Union duty mapped this way →

Framework mappings table
FrameworkReferenceNoteConfidence
ISO/IEC 42001:2023Clause 9.1 Monitoring, measurement, analysis and evaluationOriginal editorial mapping.high
NIST AI RMF 1.0MANAGE 4.1, MEASURE 3.xPost-deployment monitoring.high

Frequently asked questions

Is this a legal requirement?

Yes. It is a legal requirement under EU AI Act (Article 72).

Who must comply with this obligation?

Providers of high-risk AI systems.

When does this obligation apply?

It applies from 2 December 2027.

What evidence shows compliance?

A reviewer would expect: Post-market monitoring plan and periodic reports.

Which frameworks map to this obligation?

It is mapped to ISO/IEC 42001:2023 Clause 9.1 Monitoring, measurement, analysis and evaluation, NIST AI Risk Management Framework 1.0 MANAGE 4.1, MEASURE 3.x. These are editorial crosswalks with a stated confidence, not official mappings.

Which controls satisfy this obligation?

Automatic event logging and record retention; Post-deployment monitoring and drift detection; AI incident management and regulatory reporting.

What should an organisation do in practice?

Define performance and drift indicators, feedback channels and review cadence in a monitoring plan.

Cite this record

AIPolicyTracker (2026). “Operate a post-market monitoring system (EU AI Act)” [AIPT-OBL-0020, not yet verified]. https://aipolicytracker.org/id/AIPT-OBL-0020 (accessed 27 October 2026). Data licensed CC BY 4.0.

Permanent id AIPT-OBL-0020: it never changes or gets reused, and its address keeps working if this page moves.

Cite the official text alongside it: Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence, Official Journal of the European Union, https://eur-lex.europa.eu/eli/reg/2024/1689/oj.

BibTeX
@misc{aipolicytracker2026_operateapostmarketmonito,
  author       = {{AIPolicyTracker}},
  title        = {{Operate a post-market monitoring system (EU AI Act)}},
  year         = {2026},
  howpublished = {\url{https://aipolicytracker.org/obligations/eu-ai-act-post-market-monitoring}},
  url          = {https://aipolicytracker.org/obligations/eu-ai-act-post-market-monitoring},
  urldate      = {2026-10-27},
  note         = {Data licensed CC BY 4.0. Accessed 27 October 2026}
}

Change history

No change to this record's tracked fields has been recorded since 15 October 2026, when field-level history began.

Similar obligations in other instruments

Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.