Article 11 — Technical documentation (EU AI Act)

Article 11 of Regulation (EU) 2024/1689 — Technical documentation. Official text, practical interpretation, key obligations and compliance implications.

Official Text Summary

Article 11 of Regulation (EU) 2024/1689 (the EU AI Act) establishes the obligation for providers of high-risk AI systems to draw up technical documentation before placing such a system on the market or putting it into service, and to keep that documentation up to date throughout the system's lifecycle.

The article directs that technical documentation must be compiled in a manner that demonstrates the system's compliance with the requirements laid down in Title III, Chapter 2 of the Regulation — the full set of requirements applicable to high-risk AI systems. The documentation must contain, at minimum, all the information specified in Annex IV of the Regulation.

Annex IV enumerates eight categories of required information: (1) a general description of the system and its intended purpose; (2) a detailed description of the system's elements and the development process; (3) information on the monitoring, functioning, and control of the system; (4) a description of the risk management process followed pursuant to Article 9; (5) a description of changes made to the system over its lifecycle; (6) a list of harmonised standards applied and other technical standards relied upon; (7) a copy of the EU declaration of conformity required under Article 47; and (8) post-market monitoring plans as required by Article 72.

The article also provides that the Commission may adopt delegated acts to amend Annex IV where technological developments make it necessary, ensuring that documentation requirements remain current and relevant as the technology evolves.

What This Means in Practice

Article 11 requires providers — not deployers, not distributors — to produce and maintain a structured technical file for every high-risk AI system they bring to market or put into service within the EU. This is a pre-market obligation: the documentation must exist before the system is released, not assembled after the fact.

For an AI provider building, for example, a credit-scoring tool used by a bank (an Annex III, point 5(b) system), this means producing a living document that captures not only what the model does and how it was trained, but also how risks were identified and mitigated (Article 9), how the system was tested and validated (Article 9(8)), what data governance measures apply (Article 10), and how the system can be monitored and audited post-deployment (Article 72).

The "up to date" requirement is operationally significant. Any material change to the system — a model retrain, a significant update to training data, a change in intended purpose, or an expansion to a new deployment context — must be reflected in revised documentation. Providers should therefore treat technical documentation not as a one-time compliance artefact but as a version-controlled record that tracks the system's development history.

For providers established outside the EU, the authorised representative designated under Article 22 must hold the documentation and be able to present it to national market surveillance authorities or notified bodies on request. National authorities may demand access to technical documentation during conformity assessments and post-market surveillance activities, including in the context of serious incident investigations under Article 73.

Notified bodies involved in third-party conformity assessment (required for certain high-risk categories, as set out in Article 43) will scrutinise technical documentation as the primary evidentiary basis for issuing an EU technical documentation assessment certificate.

Key Obligations

• Draw up complete technical documentation in accordance with Annex IV before the high-risk AI system is placed on the market or put into service.
• Keep documentation up to date throughout the system's operational lifecycle, reflecting any significant changes to the system, its training data, or its deployment context.
• Ensure documentation is sufficiently detailed to allow national competent authorities and notified bodies to assess conformity with all Title III, Chapter 2 requirements.
• Include a description of the risk management process (Article 9), data governance measures (Article 10), and post-market monitoring plans (Article 72) as integral components of the documentation.
• Make documentation available to market surveillance authorities, notified bodies, and other designated national authorities upon request, within the timeframes those bodies specify.
• Retain technical documentation for ten years after the system is placed on the market or put into service, in accordance with Article 18.

Relationship to Other Articles

Article 11 sits at the centre of the conformity infrastructure for high-risk AI systems and cannot be read in isolation. It draws directly on Article 9 (risk management system), as the risk management process and its outcomes must be documented in the technical file. Article 10 (data and data governance) contributes the data-related elements required under Annex IV. Article 12 (record-keeping) complements Article 11 by requiring automatic logging of events throughout the system's operation, logs that themselves form part of the broader documentation landscape.

Article 43 (conformity assessment) is the primary downstream consumer of Article 11: notified bodies conducting third-party assessments rely on technical documentation as their core evidentiary input. Article 47 (EU declaration of conformity) requires a copy of that declaration to be incorporated into the technical file itself. Article 18 sets the ten-year retention period for technical documentation. Article 72 (post-market monitoring) and Article 73 (serious incident reporting) generate information that must flow back into updated documentation over the system's life.

Compliance Timeline

The EU AI Act entered into force on 1 August 2024 (twenty days after publication in the Official Journal on 12 July 2024). Application of the Act is phased:

• February 2, 2025 — Prohibitions on unacceptable-risk AI practices (Article 5) became applicable. Article 11 does not apply at this stage.
• August 2, 2025 — Obligations relating to general-purpose AI models (Title VIII) became applicable. Article 11 obligations do not yet apply to providers of high-risk AI systems at this date.
• August 2, 2026 — High-risk AI systems listed in Annex III (points 1 to 7, excluding point 5(b)) become subject to the full Title III requirements, including Article 11. Providers must have complete technical documentation in place by this date.
• August 2, 2027 — High-risk AI systems listed in Annex I (safety components of products already subject to Union harmonisation legislation) become subject to Article 11, with some additional time allowed for systems already on the market before August 2, 2026.

Providers who have not yet initiated their technical documentation processes should treat August 2026 as a hard deadline and build documentation drafting into their development workflows immediately. The complexity of Annex IV and the iterative nature of AI development mean that documentation assembled retrospectively rarely meets the standard authorities will apply.