Alethexis
  • Pricing
  • Trust

Stay ahead of the AI Act

Regulatory analysis, AI news and product updates. No noise.

I agree to receive communications from Alethexis: content about AI and regulation, and product news. I can unsubscribe at any time.

Data protection — newsletter

Controller: ALETHEXIS, S.L. (NIF B88758057). Purpose: to send you the Alethexis newsletter (content about AI and regulation, and product news). Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time. Recipients and transfers: we use providers acting on behalf of Alethexis for hosting, security and email delivery. No disclosure of your data to third parties for their own purposes is planned, except where required by law. Some providers may process data outside the EEA with the safeguards set out in the additional information. Rights of access, rectification, erasure, objection, restriction and portability: privacidad@alethexis.com. You may lodge a complaint with the Spanish Data Protection Authority (AEPD, www.aepd.es) or with the supervisory authority of your Member State (Article 77 GDPR). More information in the privacy policy.

Alethexis
Take the AI Act assessment (3 minutes)14-day free trial

Product

  • M1 Visibility
  • M2 Governance
  • M3 High-Risk Ready
  • Agentic Add-on
  • How it works
  • All features
  • Pricing
  • AI governance software

Solutions

  • For DPOs and consultants
  • Shadow AI
  • If you develop AI

Sectors

  • Dental Clinics
  • B2B Distribution
  • Food Distribution
  • Recruitment and HR
  • Private Education
  • Private Healthcare
  • Financial Services
  • Logistics and Transport
  • Professional Services and Consulting
  • Other sectors
  • All sectors

Resources

  • The Route: AI governance in 30 days
  • AI Act assessment
  • Templates
  • EU AI Act guide
  • Glossary
  • AI Act timeline
  • Blog
  • Changelog

Trust

  • Overview
  • Trust Center
  • Security
  • Accessibility

Company

  • About us
  • Contact
  • hello@alethexis.com
  • Partners

Legal

  • Legal Notice
  • Privacy Policy
  • Terms of Service
  • DPA (Data Processing Agreement)
  • Cookie Policy
  • Subprocessors & Service Providers Register
© 2026 Alethexis, S.L. · NIF B88758057 · C/ Tirso de Molina 36, 08940 Cornellà de Llobregat (Barcelona) · The enterprise standard. Built for SMEs.

Alethexis structures the governance, risk, operation and evidence of AI use. Using the platform does not constitute legal advice, nor does it by itself establish regulatory compliance.

LinkedIn · Contact · Product data in the EU 🇪🇺 · See the subprocessors & service providers register
By Rafael Luque Ocaña·10 August 2026

Post-market monitoring: the system belongs to the provider, the information is yours

Article 72 requires the provider to establish a post-market monitoring system. The deploying company doesn't build it, but Article 26(5) requires it to monitor operation, inform in accordance with that article and, where applicable, suspend use.

The three previous articles in this series are cleanly ruled out for the deploying company: it doesn't build, it doesn't have what needs to be kept and Annex IV doesn't even impose anything.

With post-market monitoring the split stops being clean, and it's worth saying that up front: here the easy conclusion doesn't hold. Article 72 belongs to the provider, yes. But the deploying company has related duties, they sit in another article, and one of them is among the most demanding in the whole Regulation.

Article 26 series → This article covers paragraph 5; the map of all twelve paragraphs says which post covers each one.

Who owes what: provider and deployerRegulation (EU) 2024/1689, as amended by Regulation (EU) 2026/1744Obligationand the articles it rests onProviderArt.3(3)DeployerArt.3(4)Technical requirements ofthe systemArts.9, 10, 13 and 15 · viaArt.16(a)Obligationrisk management, data,instructions for use,accuracy and cybersecurity—Technical documentation,QMS, conformityArts.11, 17, 18 and 43 · AnnexIVObligationdraw it up, keep it and putthe system through conformityassessment—Registration in the EUdatabaseArt.49 · Annex III, exceptpoint 2Obligationregister itself and thesystem before placing on themarket or into serviceObligationonly public authorities andEU bodies, or persons actingon their behalfAutomatically generatedlogsArts.12, 19 and 26(6)Obligationdesign the system to generatethem; keep those under itscontrolObligationkeep those under its controlHuman oversightArts.14 and 26(2)Obligationdesign the system so it canbe effectively overseenObligationassign it to people with thecompetence, training andauthority, and supportUse per instructions; inputdataArt.26(1) and (4)—Obligationinput data: to the extent itexercises control over itMonitoring the system inoperationArts.72 and 26(5)Obligationpost-market monitoring system(Art.72)Obligationmonitor per the instructions,inform the provider; if atrisk, suspend useSerious incidentsArts.73 and 26(5)Obligationreport them to the marketsurveillance authority(Art.73)Obligationprovider → importer ordistributor → authorities; nocontact, 73 mutatis mutandisInforming workers andaffected personsArt.26(7) and (11)—Obligationworkers, if an employer;affected persons, if itdecides on them (Annex III)Fundamental rights impact(FRIA)Art.27—ObligationFRIA (Article 27): Annex IIIsystems only, except point 2,for public bodies, privateentities providing publicservices and the uses inpoint 5(b) and (c)Transparency of certain AIsystemsArt.50Obligation50(1) interaction notice50(2) marking · with itsexceptionsObligation50(3) emotion recognition,biometric categorisation ·50(4) deep fakes, textAI literacyArt.4Obligationtake measures; no specificlevel of AI literacy of anyindividualObligationtake measures; no specificlevel of AI literacy of anyindividualAI Officerno article · a method roleInternal controlno direct legal basisInternal controlno direct legal basisObligation: the article imposes it on that roleInternal control: no direct legal basis—: not an obligation of that roleRegulation (EU) 2024/1689, as amended by Regulation (EU) 2026/1744 · who owes each duty, not from when
Obligations by role, not by date: when each one applies is on the calendar. The high-risk rows only reach high-risk systems. The FRIA applies to bodies governed by public law and private entities providing public services — except Annex III, point 2 — and to deployers of Annex III, point 5(b) and (c) systems. The paragraphs of Article 50 carry exceptions, among them text that has undergone human review or editorial control.

The figure divides the AI Act's obligations between the provider and the deployer, one per row. The highlighted row is monitoring the system in operation (Articles 72 and 26(5)): the provider runs the post-market monitoring system; the deployer monitors operation on the basis of the instructions for use, informs the provider and, if there is a risk, suspends use.

What Article 72 requires, and of whom

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

Paragraph 2 describes what that system does: it collects, documents and analyses data on the system's performance "actively and systematically" throughout its lifetime, so that the provider can assess whether it continues to meet the requirements.

And that's where the piece that decides the split shows up. The data that system analyses is, in the words of the text, "relevant data which may be provided by deployers or which may be collected through other sources".

The deploying company doesn't build the monitoring system: it's one of its sources. And that position isn't decorative, because the Regulation imposes it elsewhere.

What Article 26(5) does require of you

Paragraph 5 of Article 26 is short and contains three distinct duties. It deserves a full read before ruling anything out. And, like the whole of Article 26, it applies from 2 December 2027 for high-risk systems under Annex III and from 2 August 2028 for those under Annex I; it does not reach products under Annex I, Section B.

First, monitor. "Deployers shall monitor the operation of the high-risk AI system on the basis of the instructions for use and, where relevant, inform providers in accordance with Article 72."

Note the cross-reference: your duty to inform is defined by reference to the provider's system. These aren't two separate worlds — you are the designated informant of the mechanism the provider is required to maintain.

Second, warn and suspend. Where you have reason to consider that using the system in accordance with its instructions may result in it presenting a risk within the meaning of Article 79(1), you must inform the provider or distributor and the market surveillance authority "without undue delay", and suspend use.

That last obligation rarely makes it onto any task list, and it's the toughest one in the paragraph: it isn't informing and waiting for instructions. It's stopping using it.

Third, escalate serious incidents. If you identify a serious incident, you must inform "immediately" — and the article fixes the order: first the provider, then the importer or distributor and the market surveillance authority. And if you cannot reach the provider, Article 73 applies to you mutatis mutandis.

Why the easy reading is dangerous here

In the three previous articles, "this belongs to the provider" settled the matter. Not here, and getting that confused has real consequences.

A company that concludes "post-market monitoring isn't mine" and files it away will have got the subject of Article 72 right and got everything else wrong: it will still have the duty to monitor operation, to inform, to notify the authority, and to suspend use in the face of a risk.

The difference between "this obligation isn't mine" and "I have no related obligation" is exactly where compliance plans fall apart. And it's an error you won't catch by reading Article 72 alone: you have to go to Article 26.

What it takes to be able to comply with Article 26(5)

Three things, and none of them is a new document.

Know who monitors each system. "Monitoring operation on the basis of the instructions for use" needs a specific person to do it and to know it's theirs to do. Without a name, the duty isn't assigned — it's just stated.

Have the instructions for use on hand. The paragraph anchors monitoring to them. If nobody knows where they are, the reference has nothing to point to.

Know who to notify, and in what order. Provider first. Then the importer or distributor, and the market surveillance authority. Working out those contacts on the day of the incident wastes the time the paragraph itself asks you not to lose, because the warning has to be given immediately. And the underlying reason is explained in the post on Article 73: the one who reports the serious incident to the authority is the provider, and its general deadline is "not later than 15 days after the provider or, where applicable, the deployer, becomes aware of the serious incident".

What this case teaches about the others

This block has been ruling out provider articles one by one, each for a different substantive reason. Article 72 is the one that shows the limit of the method: ruling out the subject of an article doesn't rule out the matter.

And it's a good reminder of why the real work isn't reading the Regulation — it's having written down, system by system and dated, who monitors it, where its instructions are, and who gets called if something goes wrong. That isn't something you improvise on the day it's needed, which is precisely the only day it's needed.

Content in accordance with Articles 26, 72 and 73 of Regulation (EU) 2024/1689.

This article is for informational purposes only and does not constitute legal advice.

Frequently asked questions

Does the deployer have to set up a post-market monitoring system?

No. Article 72 requires providers to establish and document it. The deployer monitors the operation of the system on the basis of the instructions for use and, where relevant, informs providers in accordance with Article 72 (Article 26(5)).

When must use of the system be suspended?

When there is reason to consider that using it in accordance with its instructions may result in it presenting a risk within the meaning of Article 79(1). The deployer then informs the provider or distributor and the relevant market surveillance authority without undue delay, and suspends use (Article 26(5)).

Who reports a serious incident under Article 73?

The provider. The deployer immediately informs first the provider, and then the importer or distributor and the relevant market surveillance authorities; if it cannot reach the provider, Article 73 applies to it mutatis mutandis (Article 26(5)).

Sources

  • Regulation (EU) 2024/1689, Article 26
  • Regulation (EU) 2024/1689, Article 72(1) and (2)
  • Regulation (EU) 2024/1689, Article 73(1) to (6)

Last substantive review: 6 October 2026

Scope: Deployers of high-risk systems. Contrasts Article 72, which binds the provider, with Article 26(5), which binds the deployer; Article 73 appears only to attribute reporting to the provider.

Reviewed by Rafael Luque

Want to start from the beginning? The Route: AI governance in seven steps →

Drafted with AI support and published after human review. Editorial responsibility: Alethexis SL.

Related

  • Article 26, paragraph by paragraph: what binds the deployer of high-risk AI, and which post covers each
  • Serious incidents: the provider reports, but the clock starts when you find out
  • The Article 17 quality management system isn't yours to set up
  • Keeping ten years of documentation you don't generate

Where to go next

Next read

Article 26, paragraph by paragraph: what binds the deployer of high-risk AI, and which post covers each

Next step

Take the AI Act assessment (3 minutes)

Get analysis like this in your inbox

Alethexis regulatory and product news. No noise.

I agree to receive communications from Alethexis: content about AI and regulation, and product news. I can unsubscribe at any time.

Data protection — newsletter

Controller: ALETHEXIS, S.L. (NIF B88758057). Purpose: to send you the Alethexis newsletter (content about AI and regulation, and product news). Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time. Recipients and transfers: we use providers acting on behalf of Alethexis for hosting, security and email delivery. No disclosure of your data to third parties for their own purposes is planned, except where required by law. Some providers may process data outside the EEA with the safeguards set out in the additional information. Rights of access, rectification, erasure, objection, restriction and portability: privacidad@alethexis.com. You may lodge a complaint with the Spanish Data Protection Authority (AEPD, www.aepd.es) or with the supervisory authority of your Member State (Article 77 GDPR). More information in the privacy policy.