Providers must keep high-risk AI documentation for ten years
Download: JSON · MarkdownUnder EU AI Act, Article 18
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
Providers must keep high-risk AI documentation for ten years is a legal requirement under the EU AI Act in the European Union (Article 18). 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 18
- 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
- Verified against the official source 26 Sep 2026
What does it require?
For ten years after a high-risk AI system is placed on the market or put into service, the provider must keep at the disposal of national competent authorities the technical documentation, the quality management system documentation, any changes approved by a notified body, the notified body's decisions and other documents, and the EU declaration of conformity. Financial institutions keep these as part of their sector record-keeping.
Practical action
Set a ten-year retention class for the technical file, QMS records and conformity documents of each high-risk system.
Who does it apply to?
Providers of high-risk AI systems; retention runs from the date the system was placed on the market or put into service.
- Actors
- Provider / developer
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.
-
satisfiesTechnical measureEngineering lead · continuousAutomatic event logging and record retention
Serves 9 recorded duties · evidence: AI system event logs, Log schema and retention standard, Log integrity and retention check
Retention classes and archive controls for the listed documents.
-
supportsProcessProduct or model owner · at launch and on material changeTechnical documentation, model cards and instructions for use
Serves 14 recorded duties · evidence: Technical documentation file, Model card or deployer information pack, Instructions for use
Produces the technical file that must be retained.
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.
- AI System Inventory
Register · XLSX and DOCX · v6
- EU AI Act Role and Risk Classifier
Checklist · XLSX · v4
- AI Agent Registry and Permission Matrix
Register · XLSX and DOCX · v6
- EU AI Act Article 50 Transparency Kit
Kit · DOCX and XLSX · v44
What evidence would a reviewer expect?
| Evidence | Type | Notes |
|---|---|---|
| Retention schedule for AI conformity records | document | Retention class, storage location and disposal date per document type. |
| Technical file archive index | register |
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 | Clause 7.5.3; Annex A.6.2.7 | Control of documented information and technical documentation. | high |
| NIST AI RMF 1.0 | GOVERN 1.4 | Documentation of governance and risk decisions retained. | medium |
Frequently asked questions
Is this a legal requirement?
Yes. It is a legal requirement under EU AI Act (Article 18).
Who must comply with this obligation?
Providers of high-risk AI systems; retention runs from the date the system was placed on the market or put into service.
When does this obligation apply?
It applies from 2 December 2027.
What evidence shows compliance?
A reviewer would expect: Retention schedule for AI conformity records; Technical file archive index.
Which frameworks map to this obligation?
It is mapped to ISO/IEC 42001:2023 Clause 7.5.3; Annex A.6.2.7, NIST AI Risk Management Framework 1.0 GOVERN 1.4. These are editorial crosswalks with a stated confidence, not official mappings.
Which controls satisfy this obligation?
Automatic event logging and record retention; Technical documentation, model cards and instructions for use.
What should an organisation do in practice?
Set a ten-year retention class for the technical file, QMS records and conformity documents of each high-risk system.
Cite this record
AIPolicyTracker (2026). “Providers must keep high-risk AI documentation for ten years (EU AI Act)” [AIPT-OBL-0024, verified 26 September 2026]. https://aipolicytracker.org/id/AIPT-OBL-0024 (accessed 8 November 2026). Data licensed CC BY 4.0.
Permanent id AIPT-OBL-0024: 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_providersmustkeephighris,
author = {{AIPolicyTracker}},
title = {{Providers must keep high-risk AI documentation for ten years (EU AI Act)}},
year = {2026},
howpublished = {\url{https://aipolicytracker.org/obligations/eu-ai-act-art-18-documentation-keeping}},
url = {https://aipolicytracker.org/obligations/eu-ai-act-art-18-documentation-keeping},
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
- Design high-risk systems to log events automatically — EU AI Act, European Union
- Providers must retain automatically generated logs under their control — EU AI Act, European Union
- Keep records of consequential decisions influenced by the technology for three years — Colorado ADMT law (SB 26-189), Colorado (United States)
Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.