Chapter III · Section 3 · Obligations of providers and deployers of high-risk AI systems and other parties

Article 20 — Corrective actions and duty of information

▼ Primary text, verbatim. Our annotations appear below, visibly separated.

1. Providers of high-risk AI systems which consider or have reason to consider that a high-risk AI system that they have placed on the market or put into service is not in conformity with this Regulation shall immediately take the necessary corrective actions to bring that system into conformity, to withdraw it, to disable it, or to recall it, as appropriate. They shall inform the distributors of the high-risk AI system concerned and, where applicable, the deployers, the authorised representative and importers accordingly.

2. Where the high-risk AI system presents a risk within the meaning of Article 79(1) and the provider becomes aware of that risk, it shall immediately investigate the causes, in collaboration with the reporting deployer, where applicable, and inform the market surveillance authorities competent for the high-risk AI system concerned and, where applicable, the notified body that issued a certificate for that high-risk AI system in accordance with Article 44, in particular, of the nature of the non-compliance and of any relevant corrective action taken.

This text is meant purely as a documentation tool and has no legal effect. The Union's institutions do not assume any liability for its contents. The authentic versions of the relevant acts, including their preambles, are those published in the Official Journal of the European Union and available in EUR-Lex.

What this means for you

In your terms · Corrective actions and duty of information

Withdraw, disable or recall are operational verbs: the paths to actually do them, per system, exist before the day you need them.

  • Withdraw-or-disable runbook per system
  • Downstream notification list

Failure smells likeA non-conformity is found and the only way to disable the system is a redeploy nobody dares to run.

Obligations derived from this article

If you would rather not read the law

The basics page explains the Regulation's own categories in order: scope, role, tier, date. The engineering view groups the obligations by the platform capability they demand.

Start with the basics → Open the engineering view →