GUIDE DE LA SOCIÉTÉ

EU AI Act Post-Market Monitoring and Serious Incident Reporting

The EU AI Act requires providers of high-risk AI systems to operate a post-market monitoring system and report specified serious incidents.

  • 3 minutes de lecture
  • Dernière mise à jour
Sur cette page3 minutes de lecture
  1. Aperçu
  2. Plongée profonde
  3. Impact stratégique
  4. The Future of EU AI Act Post-Market Monitoring and Serious Incident Reporting
  5. Mise en œuvre dans le monde réel
  6. Risques et garde-fous
  7. Feuille de route de mise en œuvre
  8. Continuez à explorer
  9. Questions fréquemment posées

Aperçu

Providers and deployers have distinct duties, and serious-incident reporting is not the same as routine customer support or general model drift monitoring.

Plongée profonde

Article 72 requires providers to establish and document a post-market monitoring system proportionate to the nature of the AI technology and the risks of the high-risk system. It should actively and systematically collect, document, and analyse relevant data provided by deployers or collected through other sources about performance throughout the system’s lifetime. The system feeds updates to risk assessment and may lead to corrective action. It complements, rather than replaces, provider quality management, deployer monitoring, and other sectoral safety obligations. Article 73 covers reporting of serious incidents. Providers must report to the market surveillance authorities of the Member States where the incident occurred, subject to the Regulation’s timelines and process. The Act includes a special deadline for incidents involving death: report as soon as a causal relationship is established or suspected, and no later than ten days after awareness. Other incidents have different deadlines based on severity and awareness. Do not compress these into one rule; consult the operative article for the specific event. Deployers have duties to inform providers or relevant authorities when they identify risks or serious incidents in operation, following the channels required by the Act. They should preserve relevant logs and cooperate with investigations. A provider should establish usable reporting routes, triage evidence, protect personal data, and maintain a record of decisions. An internal ticket or user complaint may be an early signal but does not automatically meet the legal definition of a serious incident. The practical system links post-market evidence to action: detect a signal, assess whether it relates to the AI system, determine severity and reporting duties, notify the right authority within the applicable period, and take corrective measures when needed. Assign named responsibility and escalation coverage outside business hours. Make sure vendors and deployers can supply information quickly, while avoiding unsupported conclusions about causation before investigation.

Impact stratégique

Risques et sécurité

Les dommages catastrophiques et quotidiens causés par l’IA dépendent tous deux de la personne qui comprend les risques et qui peut agir.

Décisions plus claires

Les connaissances du public et des professionnels déterminent si une politique de sécurité forte est politiquement possible.

Passer à travers le battage médiatique

Des explications claires réduisent la capture par le battage médiatique, les relations publiques en laboratoire et le théâtre d'éthique vague.

The Future of EU AI Act Post-Market Monitoring and Serious Incident Reporting

The European Commission’s current timeline makes most AI Act requirements applicable from 2 August 2026, with Annex III high-risk rules delayed to 2 December 2027 and product-embedded high-risk rules to 2 August 2028. Some requirements and duties already apply earlier or under other laws, so teams must check the system category and applicable date. As oversight capacity and standards develop, organizations should update incident playbooks and authority contacts rather than assume a single calendar applies to all systems. Keep dated records of the applicable text, guidance, and decisions so teams can explain their reasoning when rules or system purposes change.

Mise en œuvre dans le monde réel

A provider detects a safety-relevant output pattern and checks the affected system versions and users.

A deployer preserves logs and notifies the provider after an AI-supported workflow contributes to a serious injury.

An incident lead records the first awareness timestamp and consults Article 73 for the applicable deadline.

A post-market review identifies a drift trend and documents corrective action before further harm occurs.

Risques et garde-fous

  • Traiter le risque existentiel comme de la science-fiction alors que les capacités s’accroissent.

  • Confondre sécurité des produits de surface et alignement sous haute autonomie.

  • Laisser le public non anglophone et non expert avec uniquement des sources de mauvaise qualité.

Feuille de route de mise en œuvre

  1. Séparez les dommages causés aux produits, leur mauvaise utilisation et les risques de perte de contrôle/désalignement.

  2. Demandez quelles preuves pourraient changer votre point de vue sur les délais et la gravité.

  3. Préférez les sources primaires et les évaluations concrètes aux allégations marketing.

  4. Identifiez une voie d’action : carrière, politique, financement ou compétences – et pas seulement la sensibilisation.

Continuez à explorer

Free newsletter

Get the daily AI briefing

Three verified AI stories every weekday morning, written in plain English. Free forever, no ads.

One email each weekday. Unsubscribe in one click. We never sell or share your address.

Test yourself

Take the EU AI Act Post-Market Monitoring and Serious Incident Reporting quiz

Instant feedback on every answer, and a shareable certificate with a verifiable ID once you pass a course.

Démarrer le quiz

Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation

Questions fréquemment posées

What is EU AI Act Post-Market Monitoring and Serious Incident Reporting?

The EU AI Act requires providers of high-risk AI systems to operate a post-market monitoring system and report specified serious incidents. Providers and deployers have distinct duties, and serious-incident reporting is not the same as routine customer support or general model drift monitoring.

How does Article 72 support oversight after a high-risk system enters service?

The provider’s system collects and analyses lifetime performance information.

Where does Article 73 direct a provider to report a serious incident?

The article identifies national market surveillance authorities.

What special deadline applies to a death-related serious incident?

The Regulation sets a specific ten-day outer limit for death cases.

Does every complaint automatically qualify as a serious incident?

Complaints can trigger triage but are not automatically legally classified.