Provider — EU obligations
What the obligations mean for the role of provider: the obligations, the articles carrying them, the workflows that get you there and what most often fails. Every row carries article, reading date and hash.
Share this page
Obligations
- AI Act — 16: Obligations of providers of high-risk AI systems — Meet the provider obligations for high-risk AI systems.
- AI Act — 9: Risk management system — Establish and maintain a risk management system.
- AI Act — 10: Data and data governance — Apply data and data governance requirements to training, validation and testing data.
- AI Act — 11: Technical documentation — Draw up and keep technical documentation.
- AI Act — 12: Record-keeping — Enable automatic recording of events (logging).
- AI Act — 17: Quality management system — Operate a quality management system.
- AI Act — 43: Conformity assessment — Carry out the applicable conformity assessment before placing on the market.
- AI Act — 72: Post-market monitoring by providers and post-market monitoring plan for high-risk AI systems — Run post-market monitoring of the system in use.
- AI Act — 73: Reporting of serious incidents — Report serious incidents to the market surveillance authority.
Risk points
- Documentation lags behind the product: the version in use is not the one described.
What forces a redo
- The node hash changes — the text behind the row is no longer the same.
- The reading date moves forward — the row has been re-read against the source.
- A timeline passes — the requirement starts to apply or tightens.
As data
- The same node as data: add ?format=json to the address, or ?format=agent for receipt and dependencies.
Workflows
Articles
- AI Act — 16: Obligations of providers of high-risk AI systems
- AI Act — 9: Risk management system
- AI Act — 10: Data and data governance
- AI Act — 11: Technical documentation
- AI Act — 12: Record-keeping
- AI Act — 17: Quality management system
- AI Act — 43: Conformity assessment
- AI Act — 72: Post-market monitoring by providers and post-market monitoring plan for high-risk AI systems
- AI Act — 73: Reporting of serious incidents
Relations
Metadata
- Acts
- AI Act
- Articles
- 9
- Reading date
- 2026-08-31
- Freshness
- 74/100
- Hash
- 6760964b5f0b3bd7
- Corpus version
- legal-2026-08-25
- Next check
- —
Next step
Three ways to put the register to work in your own practice.
Start with your task
Litigation
Find support in a judgment
Search guiding decisions, see what became final and follow changes in the law.
In-house, deals
Map the rules in a transaction
Move from theme to act and on to the article that carries the duty.
Compliance
Assess the risk in a process
Risk scoring per legal area, with the sources behind every score.