LO
Policy mandateProcess & self-service2024-08-01
The EU AI Act requires a deployer that controls a high-risk system's input data to ensure it is relevant and sufficiently representative (Article 26(4)), from 2 December 2027
Business systems owneroccupation page →
Event date / reported
2024-08-01 · reported 2026-07-27
Evidence stage
Policy mandateRegulation, subsidy or public procurement is requiring or funding adoption — the mirror of a constraint. It shows adoption is being required, not that it has happened, so one mandate is never enough on its own; two independent ones are.
Tasks this bears on
Keeping the records worth trusting
Duplicates, half-filled fields, statuses nobody updates, three spellings of the same customer — finding them and deciding which version is the real one.
Automating✓ Evidence-backed
Deciding what the system may decide alone
Which actions the automation takes without a person — assigning an owner, scoring a lead, sending a message, closing a record — and what happens when it is unsure.
New task✓ Evidence-backed
Where this applies
The EU, and only for deployers of high-risk AI systems. What it establishes is that on the input side of these systems, clean data moves from an internal good habit to a legal obligation — and in most companies the party controlling that input data is the person who owns the system. Article 26(1) additionally requires deployers to use such systems in accordance with their instructions for use. Regulation (EU) 2026/1744 (the Digital Omnibus on AI, published 24 July 2026) moved the application of these obligations from 2 August 2026 to 2 December 2027 for systems that are high-risk under Annex III, and to 2 August 2028 for those that are high-risk under Article 6(1) and Annex I; so this is a rule on the books that does not yet apply. The law names no job title and does not require a dedicated data owner, so attaching the duty to this occupation is our inference; it covers only systems classified as high-risk.
What this means
A duty that used to be nobody's is written into law and attached to the deployer: where your organisation controls what goes into a high-risk system, it must ensure that input data is relevant and sufficiently representative. The person who knows what goes in is usually whoever owns the system's configuration — this job. The duty is enacted, and applies from December 2027.
What it does not yet show
It does not yet apply, and nothing here shows an inspection, a penalty or a company changing what it does. It binds the deployer as an entity; which desk it lands on is an internal decision. Outside the EU market it does not apply at all.
What you can check
Open EUR-Lex's consolidated text of Regulation (EU) 2024/1689 (version of 27 July 2026) and find Article 26(4), "sufficiently representative in view of the intended purpose", then Article 113, point (c).
Does it change the assessment?
No. The impact index is never moved by a single event. Of the 2 linked judgements above, 0 moved from inference to evidence with this record; the other 1 already rested on earlier evidence.
Source
Regulation (EU) 2024/1689 (Artificial Intelligence Act), Article 26(1) and 26(4) and Article 113, as amended by Regulation (EU) 2026/1744 — EUR-Lex consolidated text of 27 July 2026 · verified 2026-09-27 · Claude (VOLO agent) · interpreted 2026-09-27 · Claude (VOLO agent)
Primary source — published by the party that did this, or the authority of record. No co-signature needed.
This record is cited in