What does Article 11 require for EU AI Act technical documentation?
For a high-risk AI system, Article 11 makes a pre-market or pre-service requirement. The file must be drawn up before the system is placed on the market or put into service, kept up to date, and written to demonstrate compliance with the high-risk requirements in Chapter III, Section 2.
The documentation should let a national competent authority or notified body understand the system without reverse-engineering the product. A usable file therefore starts with system identity and , then shows how design, data, testing, risk controls, human oversight, cybersecurity, conformity, and post-market monitoring support that intended purpose.
Article 11 applies the Annex IV content as relevant to the system. It does not excuse a missing item without analysis: mark an item not applicable only when the system facts support that conclusion, and keep the reason in the controlled file.
- Identify the AI system, provider, version, deployment form, , and relevant software, firmware, hardware, API, or embedded-product context.
- Explain the system architecture, development process, algorithms, design choices, assumptions, expected outputs, output quality, and any third-party pre-trained systems or tools used.
- Document training, validation, and testing data where relevant, including provenance, scope, main characteristics, selection, labelling, cleaning, and data-governance choices.
- Include validation and testing procedures, metrics for accuracy and robustness, discrimination-impact checks where relevant, test logs, and dated reports signed by responsible persons.
- Tie the file to the Article 9 risk-management system, Article 14 human-oversight measures, cybersecurity measures, conformity evidence, and post-market monitoring plan.
Does every EU AI Act file need to follow Annex IV?
For high-risk AI systems subject to Article 11, Annex IV is the minimum content baseline, applied as relevant to the system. From 27 July 2026, amended Article 11 allows SMEs, including start-ups, and small mid-cap enterprises to supply the Annex IV elements in a simplified manner through a Commission-established form. The simplified route changes presentation, not the underlying duty to provide the applicable Annex IV information.
Is EU AI Act only a legal compliance memo?
No. Annex IV expects engineering and product evidence: system description, , interfaces, architecture, development methods, data requirements, validation and testing procedures, performance metrics, cybersecurity measures, risk management, lifecycle changes, standards or technical specifications, conformity declaration, and post-market monitoring.
When does Article 11 become mandatory?
Regulation (EU) 2026/1744, published on 24 July 2026 and entering into force on 27 July 2026, moves Chapter III Sections 1 to 3 to 2 December 2027 for Article 6(2) Annex III systems and 2 August 2028 for Article 6(1) Annex I systems. Article 111 separately limits how the high-risk rules apply to a type and model first placed on the market or put into service before the relevant date, with a 2 August 2030 deadline for high-risk systems intended for use by public authorities.
Primary legal text for the Article 11 timing rule and Annex IV minimum technical-documentation contents for high-risk AI systems.
Commission overview confirming that high-risk AI providers must address documentation, human oversight, robustness, cybersecurity, conformity assessment, registration, declaration of conformity, and CE marking.