Artificial Intelligence Policy Tracker
Legal requirement Data governance and quality European Union Partially applicable

Apply data governance and quality criteria to training, validation and testing data

Download: JSON · MarkdownUnder EU AI Act, Article 10

Pending review · linked to the official source, waiting for a reviewer to confirm it (a factual check against the official source, not a legal review or legal advice)
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.
Verification policy and current standing · a factual check, not legal advice.
No change recorded as of 26 Sep 2026 · official source last checked
On this page 9 sections

In brief

Apply data governance and quality criteria to training, validation and testing data is a legal requirement under the EU AI Act in the European Union (Article 10). It applies from 2 December 2027. The record carries 2 evidence examples and mappings to 2 frameworks.

Instrument
EU AI Act
Jurisdiction
European Union
Nature
Legal requirement
Source reference
Article 10
Applies from
2 December 2027
Who it binds
Provider / developer
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
Pending review · source-linked

What does it require?

High-risk AI systems that use data-driven techniques must be developed on training, validation and testing data sets meeting quality criteria: appropriate governance practices covering design choices, data collection and origin, preparation, assumptions, availability and suitability, examination for possible biases, and measures to detect, prevent and mitigate bias. Data must be relevant, sufficiently representative and, to the best extent possible, free of errors and complete for the intended purpose.

Practical action

Produce a data-provenance and bias-assessment record for each data set used to build the system.

Who does it apply to?

Providers of high-risk AI systems that involve model training.

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 system
    Data governance and dataset documentation

    Serves 8 recorded duties · evidence: Dataset documentation sheet, Data quality and bias check report, Dataset approval for use

    Dataset documentation, representativeness and bias checks per dataset.

  • supportsProcessModel development lead · at launch and on material change
    Training-data provenance and copyright register

    Serves 4 recorded duties · evidence: Training source register, Copyright and rights-reservation policy, Public summary of training content

    Origin and collection records for each source.

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.

All 7 templates that cover it →

What evidence would a reviewer expect?

Evidence examples
EvidenceTypeNotes
Dataset documentation (datasheet)document
Bias examination reportreport

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 mappings table
FrameworkReferenceNoteConfidence
ISO/IEC 42001:2023Annex A controls on data for AI systemsOriginal editorial mapping.medium
NIST AI RMF 1.0MAP 2.3, MEASURE 2.1, MEASURE 2.11Data quality and bias measurement.medium

Frequently asked questions

Is this a legal requirement?

Yes. It is a legal requirement under EU AI Act (Article 10).

Who must comply with this obligation?

Providers of high-risk AI systems that involve model training.

When does this obligation apply?

It applies from 2 December 2027.

What evidence shows compliance?

A reviewer would expect: Dataset documentation (datasheet); Bias examination report.

Which frameworks map to this obligation?

It is mapped to ISO/IEC 42001:2023 Annex A controls on data for AI systems, NIST AI Risk Management Framework 1.0 MAP 2.3, MEASURE 2.1, MEASURE 2.11. These are editorial crosswalks with a stated confidence, not official mappings.

Which controls satisfy this obligation?

Data governance and dataset documentation; Training-data provenance and copyright register.

What should an organisation do in practice?

Produce a data-provenance and bias-assessment record for each data set used to build the system.

Cite this record

AIPolicyTracker (2026). “Apply data governance and quality criteria to training, validation and testing data (EU AI Act)” [AIPT-OBL-0007, not yet verified]. https://aipolicytracker.org/id/AIPT-OBL-0007 (accessed 27 October 2026). Data licensed CC BY 4.0.

Permanent id AIPT-OBL-0007: 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_applydatagovernanceandqu,
  author       = {{AIPolicyTracker}},
  title        = {{Apply data governance and quality criteria to training, validation and testing data (EU AI Act)}},
  year         = {2026},
  howpublished = {\url{https://aipolicytracker.org/obligations/eu-ai-act-data-governance}},
  url          = {https://aipolicytracker.org/obligations/eu-ai-act-data-governance},
  urldate      = {2026-10-27},
  note         = {Data licensed CC BY 4.0. Accessed 27 October 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

Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.