Login Get a Demo
01 Glossary · Compliance

What Is Post‑Market Monitoring?

What Article 72 of the EU AI Act requires from providers once a high-risk AI system is in use, and how it feeds serious incident reporting under Article 73.

The short answer

What is post-market monitoring under the EU AI Act?

Last updated
Read time
4 min read
From
Cranium AI
Share on LinkedIn

Post-market monitoring is the set of activities a provider carries out to collect and review experience from AI systems it has placed on the market or put into service, so it can identify any need for corrective or preventive action.

Article 72 of the EU AI Act requires it for every high-risk AI system.

Key takeaways
  • Providers of high-risk AI systems must establish and document a monitoring system proportionate to the risks.
  • It collects performance data across the system’s lifetime, including data supplied by deployers.
  • It rests on a post-market monitoring plan that forms part of the Annex IV technical documentation.
  • Serious incidents are reported under Article 73 within 15 days at most, and sooner in the gravest cases.
02 Requirements

What does Article 72 require?

01

A documented system

Providers establish and document a post-market monitoring system in a manner proportionate to the nature of the AI technologies and the risks of the high-risk AI system.

02

Active data collection

The system actively and systematically collects, documents and analyzes data on performance throughout the system’s lifetime, so the provider can evaluate continuous compliance with the Chapter III, Section 2 requirements.

03

Interaction with other AI

Where relevant, monitoring includes an analysis of the interaction with other AI systems. Sensitive operational data of law enforcement deployers is excluded.

04

A plan and a template

The system is based on a plan within the technical documentation. As amended in 2026, the Commission is to adopt guidance with a template for the plan by September 2, 2027.

03 Incidents

How does it link to serious incident reporting?

Article 3(49) defines a serious incident as one that leads to death or serious harm to health, serious and irreversible disruption of critical infrastructure, infringement of fundamental rights obligations, or serious harm to property or the environment. Providers report to the market surveillance authority where it occurred.

SituationReporting deadline under Article 73
Any serious incidentImmediately after a causal link, or its reasonable likelihood, is established, and no later than 15 days after becoming aware
Widespread infringement, or serious and irreversible disruption of critical infrastructureImmediately, and no later than two days after becoming aware
Death of a personImmediately after a causal relationship is established or suspected, and no later than 10 days after becoming aware
04 Deployers

What is the deployer’s part?

  1. Monitor in use

    Deployers monitor the operation of the high-risk AI system on the basis of the instructions for use and, where relevant, inform the provider in line with Article 72.

  2. Escalate risks and incidents

    Where use may present a risk, the deployer informs the provider or distributor and the market surveillance authority and suspends use. A serious incident goes to the provider immediately.

  3. Keep the logs

    Deployers keep the logs the system generates automatically, to the extent under their control, for at least six months.

05 Keep going

Related reading.

06 Questions

Frequently asked questions.

Straight answers, kept current. Last updated .

Ask us anything →
Who is responsible for post-market monitoring?

The provider of the high-risk AI system. Article 72 places the duty to establish and document the system on providers, and Annex VI makes post-market monitoring one of the things verified during conformity assessment. Deployers supply data and have their own monitoring duty under Article 26(5), but they do not take over the provider’s obligation unless Article 25 makes them the provider.

Does a runtime monitoring tool satisfy Article 72?

Not by itself. Article 72 asks for a documented system and plan covering data collection, analysis and continuous compliance, which is an organizational process. Runtime records are one input. Cranium Guardian, for example, inspects traffic between an AI application and the LLM for each interaction and keeps event records a team can use as evidence. No tool is a legal compliance guarantee.

When does the obligation apply?

Article 72 applies to providers of high-risk AI systems. As amended in 2026, the classification rules and requirements for those systems apply from December 2, 2027 for Annex III systems and August 2, 2028 for Annex I products, and the Commission’s guidance and template for the monitoring plan are due by September 2, 2027. This page is general information, not legal advice.

How does it differ from market surveillance?

Post-market monitoring is done by the provider on its own systems. Market surveillance is done by public authorities, which receive serious incident reports under Article 73 and must take appropriate measures within seven days of receiving one. The two connect: the provider’s monitoring is where reportable incidents surface, and the authority then decides what measures to take.

07 See it for yourself

From the definition
to the evidence.

See how Cranium AI discovers, observes, governs, secures and proves every AI model, agent and vendor in your enterprise.