EU AI Act Art. 26(5): deployer monitoring, suspension and informing the provider

Deployers monitor operation per the instructions; on reason to consider a risk they inform the provider or distributor and the authority and suspend use; a serious incident goes to the provider first, and Art. 73 applies to the deployer if the provider cannot be reached

By Jorge García Aibar Reviewed 2026-09-24

From clause to evidence Build the artefact, then file every output it produces as a record that names AIGE-OBL-EUAIA-ART26-5. Drawn from chapter 08.

Text alternative

Clause: EU AI Act, Art. 26.
Duty holder: Deployer.
Applies from: 2027-12-02, Deferred.
Artefact: Monitoring plan with signal….
Layers: Layer 02, Layer 04, Layer 05.
Evidence record: AI incident record, +7 more.
Record schemas: AI incident record , Deployment decision record , Vendor due-diligence response , Agent register entry , AI system register entry , Training record , Instructions for use , Decommissioning runbook .
No crosswalk topic files this clause yet.

When this obligation applies The first date in the row's status, then each later step: filled once its date has passed, outlined while it is still ahead of the review date.

Data table: the dates

Dates of AIGE-OBL-EUAIA-ART26-5
Date	Step	Detail
2027-12-02	Deferred	Annex III
2028-08-02	High-risk (Annex I)	Applies to Annex I embedded (product safety-component) systems
2030-08-02	Later step	Deadline for legacy high-risk systems intended for use by public authorities (Art. 111(2))

Id

AIGE-OBL-EUAIA-ART26-5

Instrument

EU AI Act (post-Omnibus) law

Compared side by side

ISO 42001 vs EU AI Act · NIST AI RMF vs EU AI Act

Clause

Art. 26(5)

Duty holder

Deployer

Authority

National MSA

Applies from

2027-12-02 Deferred · Annex III

Later dates

2028-08-02 Applies to Annex I embedded (product safety-component) systems
2030-08-02 Deadline for legacy high-risk systems intended for use by public authorities (Art. 111(2))

System class

High-risk (Annex III) · High-risk (Annex I)

The artefact that evidences it

Monitoring plan with signal owners; tested suspension path (feature flag, traffic switch); provider incident contact in the registry; pre-filled risk and serious-incident notices.

What this obligation connects to Solid edges are direct relations, dashed ones looser (a case that cites the same article, a framework whose clauses only touch the topic); patterns and controls take the colour of their stack layer. Select a node to open it; the lists below give every relation in full.

Data table: every relation

Relations of AIGE-OBL-EUAIA-ART26-5
Family	Item	Relation
Patterns	Deactivation, Localisation & Retirement Runbook	Direct
Patterns	Decision Notice & Contest Path	Direct
Patterns	Disclosure & Notification Pipeline	Direct
Patterns	Drift & Fairness Monitor	Direct
Patterns	Explanation Artefact	Direct
Patterns	Rights Requests Against Models	Direct
Patterns	Staged Rollout with Rollback Criteria	Direct
Patterns	Vendor / Model Due-Diligence Gate	Direct
Open controls	AIGE-CTL-DEPLOY-012 Deactivation triggers, degraded modes and suspension	Direct
Open controls	AIGE-CTL-DEPLOY-008 Monitoring plan with thresholds, owners and consequences	Direct
Open controls	AIGE-CTL-DEPLOY-011 Serious incident reporting clocks	Direct
Open controls	AIGE-CTL-DEPLOY-005 Staged rollout with pre-registered rollback criteria	Direct

Patterns that build it

Vendor / Model Due-Diligence Gate (layer 2 and 5)
Explanation Artefact (layer 4 and 5)
Decision Notice & Contest Path (layer 4 and 5)
Rights Requests Against Models (layer 2 and 5)
Staged Rollout with Rollback Criteria (layer 4)
Drift & Fairness Monitor (layer 4 and 5)
Disclosure & Notification Pipeline (layer 5 and 2)
Deactivation, Localisation & Retirement Runbook (layer 4 and 2)

Open controls that evidence it

Draft controls in the open control profiles that map to this row: each states a requirement and the evidence it must leave behind.

AIGE-CTL-DEPLOY-005 Staged rollout with pre-registered rollback criteria (Deployment and monitoring profile)
AIGE-CTL-DEPLOY-008 Monitoring plan with thresholds, owners and consequences (Deployment and monitoring profile)
AIGE-CTL-DEPLOY-011 Serious incident reporting clocks (Deployment and monitoring profile)
AIGE-CTL-DEPLOY-012 Deactivation triggers, degraded modes and suspension (Deployment and monitoring profile)

Source

Chapter 08, section EU AI Act, post-Omnibus, checked against its sources on the review date above.

Machine-readable

This obligation: /api/v1/obligations/aige-obl-euaia-art26-5.json
The register: /api/v1/obligations.json · CSV
Schema and stability promise: open data and API

Cite this obligation

García Aibar, J. (2026). EU AI Act Art. 26(5): deployer monitoring, suspension and informing the provider (AIGE-OBL-EUAIA-ART26-5). In AI Governance Engineering: The Thesis & Body of Knowledge (v0.5.0). https://doi.org/10.5281/zenodo.22956197. https://aigovernanceengineer.com/obligations/aige-obl-euaia-art26-5. CC BY 4.0

BibTeX

@misc{aige2026obligation,
  author       = {Jorge García Aibar},
  title        = {{EU AI Act Art. 26(5): deployer monitoring, suspension and informing the provider (AIGE-OBL-EUAIA-ART26-5)}},
  howpublished = {In AI Governance Engineering: The Thesis \& Body of Knowledge},
  year         = {2026},
  version      = {0.5.0},
  doi          = {10.5281/zenodo.22956197},
  url          = {https://aigovernanceengineer.com/obligations/aige-obl-euaia-art26-5},
  note         = {Version 0.5.0}
}