Market surveillance powers and the escalation ladder

Lesson 2 of 6 in Governance, Enforcement, Penalties, and Sandboxes.

Enforcement runs on Regulation 2019/1020 — the EU’s general market-surveillance machinery — imported and adapted by Article 74. The powers are extensive: authorities can demand any documentation and data (training, validation, and testing datasets included), obtain access to the system itself through APIs or other remote means, run inspections and tests, and — under the strict two-condition rule you met in the conformity module — reach source code by reasoned request (Art 74(13)). Providers of GPAI-built systems get a bridge: where a system built on a GPAI model is directly usable by deployers, the AI Office and national authorities cooperate and exchange what enforcement needs (Art 75).

What happens when an authority finds something wrong is a graduated escalation ladder — evaluation, corrective order, national restriction, Union-level resolution. It matters commercially because a dispute that starts with one inspector in one Member State can end with your product banned across the whole single market.

Enforcement escalation (Arts 79–81)

  1. Sufficient reason to believe an AI system presents a risk

    Risk to health, safety, or fundamental rights — triggered by monitoring, a complaint (Art 85), an incident report, or a fundamental-rights authority.

  2. Authority evaluates the system (Art 79)

    Full evaluation against the Act, with special attention where fundamental rights are at stake; operator must cooperate.

  3. Non-compliance found?
  4. Corrective order: comply, withdraw, or recall within a set period

    The operator must take all appropriate corrective action for ALL affected systems it has made available across the Union market.

  5. Operator takes adequate action?
  6. National measures: prohibit, restrict, withdraw, or recall

    The authority acts itself when the operator will not — and notifies the Commission and all other Member States without delay.

  7. Objection from another Member State or the Commission within 3 months?

    30 days where the case concerns a prohibited practice.

  8. Measures deemed justified — all Member States must ensure equivalent action

    One national finding scales Union-wide by default. Silence is agreement.

  9. Union safeguard procedure: Commission decides (Art 81)

    The Commission consults and rules on whether the national measure is justified; its decision binds all Member States.

  10. Case resolved at Union level
  11. Compliant but still risky? → Art 82; formal defects? → Art 83

    Art 82: even a fully compliant system presenting a risk can be forced into corrective measures. Art 83: missing CE mark, declaration, or registration triggers an order to cure, then restriction.

Art 79 — AI presenting a risk at national level

The workhorse procedure: evaluate, order corrective action, escalate to national restriction if the operator balks, and notify the Commission and every other Member State. Corrective duties cover all affected systems Union-wide, not just the ones in the investigating State.

Art 80 — the misclassification procedure

Aimed squarely at the Annex III Article 6(3) filter: where an authority has sufficient reason to consider that a system the provider classified as non-high-risk actually is high-risk, it evaluates and, if it agrees, orders the provider to bring the system into full high-risk compliance — and providers who misclassified to circumvent the rules face fines. The filter is a bet the provider can lose retroactively.

Art 81 — the Union safeguard procedure

When one Member State restricts a system and another Member State (or the Commission) objects, the Commission consults the parties and decides whether the national measure is justified — binding everyone. It is the tie-breaker that keeps 27 enforcement regimes from fracturing the single market.

Art 82 — compliant but still risky

The uncomfortable one: a system can pass every conformity test and still present a risk to health, safety, or fundamental rights. The authority can require corrective measures anyway. Compliance is a floor, not a safe harbour.

Art 83 — formal non-compliance

Missing CE mark, missing declaration of conformity, registration not done, authorised representative not appointed, documentation unavailable: cure it within the deadline or face restriction and withdrawal. Paperwork failures are enforcement events in their own right — no harm required.

Art 84 — Union AI testing support

The Commission designates Union testing facilities that give authorities independent technical firepower — labs that can actually probe a model’s behaviour rather than take the provider’s test reports on faith.

Interactive checkpoint quiz (2 questions) — open this page in a browser to take it.