Providers of GPAI models must maintain technical documentation and inform downstream providers
Context fileUnder EU AI Act, Article 53(1)(a) and 53(1)(b); Annexes XI and XII
What does it require?
Providers of general-purpose AI models must draw up and keep up to date technical documentation covering the training and testing process and evaluation results, as set in Annex XI, and supply it to the AI Office or national authorities on request. They must also keep current the Annex XII information for providers that integrate the model into their own AI systems, so those providers understand its capabilities and limitations and can meet their own duties. Free and open-source models without systemic risk are exempt from both duties.
Practical action
Maintain a model card and technical file aligned to Annexes XI and XII with version control tied to each model release.
Who does it apply to?
Providers placing general-purpose AI models on the EU market, other than free and open-source models that do not present systemic risk. Models placed on the market before 2 August 2025 have until 2 August 2027 under Article 111(3).
- Sectors
- Cross-sector / all sectors
- Use cases
- Generative AI and foundation models
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.
-
satisfiesProcessProduct or model owner · at launch and on material changeTechnical documentation, model cards and instructions for use
Serves 13 recorded duties · evidence: Technical documentation file, Model card or deployer information pack, Instructions for use
Model card and technical file structured to Annexes XI and XII.
-
supportsProcessRelease manager · at launch and on material changeModel release and change-management gate
Serves 5 recorded duties · evidence: Release or change approval record, Release and change-classification procedure
Release requires the documentation to be current.
What evidence would a reviewer expect?
| Evidence | Type | Notes |
|---|---|---|
| Annex XI technical documentation | document | |
| Annex XII downstream integration documentation | document |
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.6.2.7, A.8.2, A.10.4 | Technical documentation, system documentation and information for customers. | high |
| NIST AI RMF 1.0 | GOVERN 1.4, MAP 2.2, MEASURE 2.1 | Documentation of design, testing and evaluation. | medium |
Cite this record
AIPolicyTracker (2026). “Providers of GPAI models must maintain technical documentation and inform downstream providers (EU AI Act)”. https://aipolicytracker.org/obligations/eu-ai-act-art-53-gpai-technical-and-downstream-documentation (accessed 24 September 2026). Data licensed CC BY 4.0.
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.
Similar obligations in other instruments
- Draw up technical documentation before placing a high-risk system on the market — EU AI Act, European Union
- Providers must document and register a conclusion that an Annex III system is not high-risk — EU AI Act, European Union
- Developers must document high-risk systems and disclose known risks — Colorado AI Act, Colorado (United States)
Informational only, not legal advice. Verify every claim against the linked official sources and consult qualified counsel before acting.