EU AI Act Article 11: Technical Documentation Requirements

What Article 11 Covers

Article 11 of Regulation (EU) 2024/1689 establishes the technical documentation obligation for high-risk AI systems. The documentation is the central evidence file of the entire compliance regime: it is what national competent authorities will inspect, what notified bodies will assess where third-party conformity assessment applies, and what the provider relies on when drawing up the EU declaration of conformity under Article 47.

Two timing rules matter. First, the documentation must be drawn up before the high-risk AI system is placed on the market or put into service. It is not a retrospective write-up; it must exist when the system reaches the market. Second, it must be kept up to date throughout the system's life, which links Article 11 directly to post-market monitoring under Article 72 and to the management of substantial modifications.

What the Documentation Must Demonstrate

Article 11(1) sets a functional test: the technical documentation shall be drawn up in such a way as to demonstrate that the high-risk AI system complies with the requirements of Section 2 of Chapter III, and to provide national competent authorities and notified bodies with the necessary information in a clear and comprehensive form to assess that compliance. In other words, the document is judged by whether an informed outsider could verify compliance from it, not by its length.

The minimum contents are set out in Annex IV. In summary, Annex IV requires:

• A general description of the AI system, including its intended purpose, the provider's name, the system version and how it interacts with hardware or other software.
• A detailed description of the elements of the system and its development process, including design specifications, system architecture, the data requirements and the provenance and characteristics of training, validation and testing datasets.
• An assessment of the human oversight measures needed under Article 14 and of the technical measures that help deployers interpret outputs.
• A description of any predetermined changes to the system and its performance, together with the continued-compliance approach.
• Details of validation and testing procedures, including metrics for accuracy, robustness and cybersecurity, test logs and test reports.
• A description of the risk management system established under Article 9.
• A description of relevant changes made through the lifecycle.
• A list of harmonised standards applied in full or in part, or a description of the alternative solutions adopted.
• A copy of the EU declaration of conformity referred to in Article 47.
• A detailed description of the post-market monitoring system and plan under Article 72.

Simplified Documentation for SMEs

Article 11(1) contains an important proportionality measure. Small and medium-sized enterprises, including startups, may provide the elements of the Annex IV technical documentation in a simplified manner. The European Commission is tasked with establishing a simplified technical documentation form targeted at the needs of small and microenterprises. Where an SME opts for the simplified approach, it must use that form, and notified bodies must accept it for the purposes of conformity assessment. The substance of the obligation does not disappear; the format becomes lighter.

One File for Embedded AI

Article 11(2) deals with high-risk AI systems related to products covered by the Union harmonisation legislation listed in Section A of Annex I, such as medical devices or machinery. In that case, a single set of technical documentation is drawn up containing both the AI Act information and the information required under the sectoral legislation. This mirrors the anti-duplication logic of Article 8(2) and means manufacturers should extend their existing technical files rather than creating a parallel AI dossier.

Article 11(3) empowers the Commission to amend Annex IV by delegated act where necessary to keep the documentation requirements aligned with technical progress, so providers should monitor for updates.

How to Build the Documentation in Practice

1. Start from Annex IV as a checklist and create a skeleton document with one section per Annex IV point.
2. Assign each section to the team that owns the underlying work: data science for dataset descriptions, engineering for architecture, quality for risk management and testing records.
3. Write the intended purpose statement first, since almost every other section, from data relevance to oversight design, is evaluated against it.
4. Capture evidence as you build, including test logs, dataset datasheets and design decisions. Reconstructing this after release is the most common and most expensive failure mode.
5. Version-control the documentation and define a trigger list for updates, such as model retraining, dataset changes or new deployment contexts.
6. Cross-reference rather than copy. Where the quality management system under Article 17 already contains a procedure, the technical documentation can reference it precisely.

A Concrete Example

A provider of an AI system used for shortlisting job candidates, which is high-risk under point 4(a) of Annex III, would document the intended purpose as candidate shortlisting for specified roles, describe the model architecture and training pipeline, characterise its training data including how representativeness across demographic groups was examined under Article 10, record accuracy and error-rate testing disaggregated where relevant, describe the recruiter-facing oversight controls, and attach its post-market monitoring plan. If a regulator later questions the system, this file is the provider's primary account of its diligence.

How Article 11 Connects to Other Provisions

The technical documentation is referenced across the regulation. Article 18 requires it to be kept for ten years after market placement. Article 22 requires the authorised representative of a non-EU provider to verify it was drawn up and keep it available to authorities. Article 23 requires importers to verify it exists. It is the object of the conformity assessment under Article 43 and Annexes VI and VII, and the post-market monitoring plan under Article 72 forms part of it. Penalties for non-compliance with provider obligations can reach 15 million euros or 3 percent of worldwide annual turnover under Article 99.

Actions to Take Before August 2, 2026

Providers intending to have high-risk systems on the EU market from August 2, 2026 should draft their Annex IV documentation now, not in mid-2026. A realistic internal milestone is a complete first draft at least six months before the system is placed on the market, leaving time for the conformity assessment, the EU declaration of conformity and registration in the EU database under Article 49. SMEs should watch for the Commission's simplified form and decide early whether to adopt it. This article provides general information about Regulation (EU) 2024/1689 and does not constitute advice on any specific system.

This article is for informational purposes only and does not constitute legal advice. Regulatory requirements change frequently — verify current rules with official sources. Built by Sawai Gyoseishoshi Office, Hiroshima, Japan.