Skip to content
EU AI Act · EU-AI-ACT-ART-9-RISK-MANAGEMENT

EU AI Act Article 9 — Risk management system

High-risk AI systems require a continuous, documented risk management system covering the entire lifecycle — from design through post-market monitoring

HIGHProcess dutyRisk assessmentBinding regulationIn forceEnforceable from 2 August 2026

Where this comes from

Provision: Article 9 — Risk management system

Instrument: EU Artificial Intelligence Act (Regulation (EU) 2024/1689)

Citation: Article 9, Regulation (EU) 2024/1689

Text version: Regulation (EU) 2024/1689 (AI Act), OJ L, 12.7.2024

Read the official text ↗

Who it applies to

High-risk AI provider in scope — all of these:

  • Service deploys AI systems in a professional capacity
  • AI Act role is Provider or we provide some AI systems and deploy others

Annex III high-risk area (Art. 6(2)) — any one of these:

  • Annex III high-risk areas includes Biometrics
  • Annex III high-risk areas includes Critical infrastructure
  • Annex III high-risk areas includes Education and vocational training
  • Annex III high-risk areas includes Employment and worker management
  • Annex III high-risk areas includes Essential public services
  • Annex III high-risk areas includes Creditworthiness
  • Annex III high-risk areas includes Insurance
  • Annex III high-risk areas includes Law enforcement
  • Annex III high-risk areas includes Migration, asylum and border control
  • Annex III high-risk areas includes Administration of justice and democratic processes

…unless:

  • AI Act scope exclusion is used exclusively for military, defence or national-security purposes or developed and used solely for scientific research and development
  • Art. 2(3): the Regulation 'does not apply to AI systems where and in so far as they are placed on the market, put into service, or used with or without modification exclusively for military, defence or national security purposes'. (AI Act Art. 2(3))
  • Art. 2(6): the Regulation 'does not apply to AI systems or AI models, including their output, specifically developed and put into service for the sole purpose of scientific research and development'. (AI Act Art. 2(6))
  • Art. 6(3): an Annex III system is NOT high-risk where it does not pose a significant risk of harm to health, safety or fundamental rights, including by not materially influencing the outcome of decision making — which applies where the system (a) performs... (AI Act Art. 6(3))

Scope in the source's own terms

  • Art. 2(1): the AI system is placed on the market or put into service in the Union, or the provider/deployer is established in the Union, or the output produced by the system is used in the Union
  • Art. 6(2): the AI system falls within an area listed in Annex III and is therefore high-risk, no documented Art. 6(3) derogation applying (and it is ALWAYS high-risk where it performs profiling of natural persons)
  • Art. 16(a) ('Providers of high-risk AI systems shall …'), read with Art. 3(3): the actor develops the system or has it developed and places it on the market or puts it into service under its own name or trade mark — or is its authorised representative under Art. 22

What engineering work it implies

  • AI Risk Management File (Living Register with Release Thresholds)Covers it fully

    A continuously-updated risk register under Article 9, with accuracy and robustness thresholds recorded per release under Article 15 and post-market monitoring hooks...

Sample acceptance criteria Landfall generates for this obligation:

  • Each risk is a separate record naming the harm category (health, safety, fundamental rights) and the affected group
  • Reasonably foreseeable MISUSE is recorded separately from malfunction (Art. 9(2)(b))
  • Every risk has at least one mitigation with an owner and a date, linked to the control or backlog item that delivers it
  • Residual risk is stated and accepted by a named person with the authority to accept it (Art. 9(5))
  • Metrics and thresholds are defined BEFORE the first evaluation run, per subgroup as well as in aggregate (Art. 9(6))

Evidence an auditor expects

  • Assessment documentDocument reviewRetain Art. 18(1): 10 years after the system is placed on the market or put into serviceReviewed continuous and iterative throughout the lifecycle, with regular systematic review and updating (Art. 9(2))

    Risk management file for the high-risk AI system (Art. 9)

    A maintained, version-controlled file covering the four elements of Art. 9(2): (a) identification and analysis of known and reasonably foreseeable risks to health, safety and fundamental rights; (b) estimation and evaluation of risks arising in intended use and under reasonably foreseeable misuse; (c) evaluation of risks emerging from post-market monitoring data; (d) the targeted risk management measures adopted, with residual-risk acceptance decisions and the person who took them

  • Process recordDocument review

    Post-market monitoring feed into the risk management system (Art. 9(2)(c) with Art. 72)

    Evidence that post-market monitoring data is collected against the Art. 72 plan and actually re-enters risk evaluation — dated review records showing what the monitoring data changed

  • Test resultsTechnical audit

    Effectiveness testing of the adopted risk management measures (Art. 9(6)-(8))

    Test records showing the risk management measures were tested against prior-defined metrics and probabilistic thresholds appropriate to the intended purpose, before placing on the market

  • Test resultsThird-party audit

    Third-party adversarial test report (red-team / jailbreak / robustness), dated, with scope and findings

    A dated report from a party independent of the build team stating: the scope tested (models, versions, endpoints, guardrails in place), the attack classes attempted (jailbreak and prompt injection, data and model poisoning, adversarial examples and evasion, confidentiality and extraction attacks), the method and the number of attempts, the findings with severity, and what was remediated or accepted with the person who accepted it. An undated report, or one with no stated scope, does not satisfy this requirement

Questions people ask

Does EU AI Act Article 9 — Risk management system apply to my service?
It applies when Service deploys AI systems in a professional capacity; AI Act role is Provider or we provide some AI systems and deploy others; and at least one of: Annex III high-risk areas includes Biometrics; Annex III high-risk areas includes Critical infrastructure; Annex III high-risk areas includes Education and vocational training; Annex III high-risk areas includes Employment and worker management; Annex III high-risk areas includes Essential public services; Annex III high-risk areas includes Creditworthiness; Annex III high-risk areas includes Insurance; Annex III high-risk areas includes Law enforcement; Annex III high-risk areas includes Migration, asylum and border control; Annex III high-risk areas includes Administration of justice and democratic processes. It does not apply where AI Act scope exclusion is used exclusively for military, defence or national-security purposes or developed and used solely for scientific research and development.
When does this become enforceable?
EU AI Act Article 9 — Risk management system is enforceable from 2 August 2026. Its current status is: in force.
What evidence does an auditor expect?
Risk management file for the high-risk AI system (Art. 9); Post-market monitoring feed into the risk management system (Art. 9(2)(c) with Art. 72); Effectiveness testing of the adopted risk management measures (Art. 9(6)-(8)).

Find out whether this one lands on you

Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.

Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.

What Landfall Is NOT

Critical Boundaries

Understanding these boundaries is essential before using this product. Misuse of this tool for purposes outside its scope may create legal, regulatory, or commercial risk for your organization.

NOT Legal Advice

This product does not provide legal advice and does not create an attorney-client relationship.

Interpretations are informational analysis, not legal counsel. Always consult qualified legal professionals for compliance decisions.

NOT a Risk Score

We do not quantify, calculate, or certify your compliance risk level.

No numerical risk rating, compliance percentage, or safety score. Risk assessment requires human judgment about your specific context.

NOT Runtime Enforcement

This is a planning and mapping tool, not a runtime enforcement system.

Does not integrate with your production systems. Does not block, filter, or enforce compliance in real-time. Implementation is your responsibility.

NOT Regulatory Approval

Using this tool does not mean you are compliant with any regulation.

No certification, seal of approval, or compliance guarantee. Regulators will evaluate your actual implementation, not your use of this tool.

NOT Authoritative Interpretation

Our interpretations are not binding and may differ from regulatory guidance.

Only regulators and courts provide authoritative interpretation. Our analysis reflects our reading of requirements, which may be incomplete or incorrect.

NOT a Safe Harbor

This tool does not shield you from enforcement actions or liability.

Documentation of your process is valuable, but does not constitute a legal defense. Compliance is ultimately your organization's responsibility.

NOT an AI Compliance Agent

AI features assist analysis but do not make compliance decisions for you.

AI-generated interpretations require human review and approval. Automated suggestions are starting points, not final answers.

NOT Complete Coverage

We do not cover all regulations, all obligations, or all jurisdictions.

Regulatory landscape is vast and evolving. Gaps in our coverage do not mean those requirements don't apply to you.

What This Tool IS:

  • A structured workflow for mapping regulatory requirements to implementation tasks
  • A documentation system for compliance decisions (audit trail)
  • A collaboration platform for compliance, legal, and engineering teams
  • An informational resource for understanding regulatory obligations