Deployers must ensure input data they control is relevant and representative
Download: JSON · MarkdownUnder EU AI Act, Article 26(4)
What this label means
- Verified
- — a named reviewer opened the official source and confirmed the record; the date and the reviewer are shown.
- Pending review
- — linked to the official source and in the queue for a reviewer to confirm.
- Source-linked
- — linked to the official source, not yet confirmed by a reviewer.
On this page 9 sections
In brief
Deployers must ensure input data they control is relevant and representative is a legal requirement under the EU AI Act in the European Union (Article 26(4)). To the extent a deployer controls the data fed into a high-risk AI system, it must make sure that input data is relevant to, and sufficiently representative for, the system's intended purpose.
- Instrument
- EU AI Act
- Jurisdiction
- European Union
- Nature
- Legal requirement
- Source reference
- Article 26(4)
- Applies from
- 2 December 2027
- Who it binds
- Deployer / user organisation, Public authority / government body
- Evidence examples
- 2
- Framework mappings
- ISO/IEC 42001:2023, NIST AI Risk Management Framework 1.0
- Controls that meet it
- 2
- Official source
- Open official text
- Verification
- Verified against the official source 26 Sep 2026
What does it require?
To the extent a deployer controls the data fed into a high-risk AI system, it must make sure that input data is relevant to, and sufficiently representative for, the system's intended purpose. The duty sits with the deployer even though the provider designed the system, because the deployer chooses what the system is run on.
Practical action
Define input-data quality checks for each high-risk system, including population coverage and field validation, and review them with the provider's instructions.
Who does it apply to?
Deployers of high-risk AI systems that select or supply the operational input data.
Applies from:
Which controls meet this duty?
Satisfies: the control, operated properly, does the work the duty asks for. Supports: it contributes but the duty needs more. Each control page lists every other duty it serves, so work done once can be counted once.
-
satisfiesProcessData governance lead · once per ai systemData governance and dataset documentation
Serves 8 recorded duties · evidence: Dataset documentation sheet, Data quality and bias check report, Dataset approval for use
Applied to operational input data rather than training data.
-
supportsTechnical measureAI system owner · continuousPost-deployment monitoring and drift detection
Serves 10 recorded duties · evidence: Post-market monitoring plan, Monitoring dashboard or periodic monitoring report, Monitoring review decision
Detects input drift away from the intended population.
Templates that cover this duty
Generated from the records. Free · no account · links emailed to your work address. This duty is cited in each file with its source reference and a link back here.
- EU AI Act Role and Risk Classifier
Checklist · XLSX · v4
- EU AI Act Article 50 Transparency Kit
Kit · DOCX and XLSX · v44
- ISO/IEC 42001 Gap Assessment and Statement of Applicability
Assessment · XLSX · v3
- NIST AI RMF ↔ EU AI Act ↔ ISO/IEC 42001 Crosswalk
Crosswalk · XLSX · v5
What evidence would a reviewer expect?
| Evidence | Type | Notes |
|---|---|---|
| Input-data quality checklist | document | |
| Input-data validation results | record |
Framework mappings
Original editorial crosswalks. They cite clause numbers only and reproduce no standard text; confidence reflects how direct the mapping is.
See every European Union duty mapped this way →
| Framework | Reference | Note | Confidence |
|---|---|---|---|
| ISO/IEC 42001:2023 | Annex A.7.4, A.7.6 | Data quality and data preparation. | medium |
| NIST AI RMF 1.0 | MAP 2.3, MEASURE 2.2 | Data representativeness in context. | medium |
Frequently asked questions
Is this a legal requirement?
Yes. It is a legal requirement under EU AI Act (Article 26(4)).
Who must comply with this obligation?
Deployers of high-risk AI systems that select or supply the operational input data.
When does this obligation apply?
It applies from 2 December 2027.
What evidence shows compliance?
A reviewer would expect: Input-data quality checklist; Input-data validation results.
Which frameworks map to this obligation?
It is mapped to ISO/IEC 42001:2023 Annex A.7.4, A.7.6, NIST AI Risk Management Framework 1.0 MAP 2.3, MEASURE 2.2. These are editorial crosswalks with a stated confidence, not official mappings.
Which controls satisfy this obligation?
Data governance and dataset documentation; Post-deployment monitoring and drift detection.
What should an organisation do in practice?
Define input-data quality checks for each high-risk system, including population coverage and field validation, and review them with the provider's instructions.
Cite this record
AIPolicyTracker (2026). “Deployers must ensure input data they control is relevant and representative (EU AI Act)” [AIPT-OBL-0032, verified 26 September 2026]. https://aipolicytracker.org/id/AIPT-OBL-0032 (accessed 8 November 2026). Data licensed CC BY 4.0.
Permanent id AIPT-OBL-0032: it never changes or gets reused, and its address keeps working if this page moves.
Cite the official text alongside it: Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence, Official Journal of the European Union, https://eur-lex.europa.eu/eli/reg/2024/1689/oj.
BibTeX
@misc{aipolicytracker2026_deployersmustensureinput,
author = {{AIPolicyTracker}},
title = {{Deployers must ensure input data they control is relevant and representative (EU AI Act)}},
year = {2026},
howpublished = {\url{https://aipolicytracker.org/obligations/eu-ai-act-art-26-4-deployer-input-data}},
url = {https://aipolicytracker.org/obligations/eu-ai-act-art-26-4-deployer-input-data},
urldate = {2026-11-08},
note = {Data licensed CC BY 4.0. Accessed 8 November 2026}
}
Change history
No change to this record's tracked fields has been recorded since 15 October 2026, when field-level history began.
Similar obligations in other instruments
- Apply data governance and quality criteria to training, validation and testing data — EU AI Act, European Union
- Manage data quality, model development and monitoring across the lifecycle — Singapore Model AI Governance Framework, Singapore (voluntary)
Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.