EU AI Act Article 11 — Technical documentation
Article 11 of the EU AI Act requires that technical documentation for high-risk AI systems is drawn up before the system is placed on the market and kept up to date throughout its lifecycle. The documentation must cover the elements set out in Annex IV — system description, design specification, monitoring functioning, performance metrics, and any change-management. Enforceable from 2 August 2026.
Source: Regulation (EU) 2024/1689 (EU AI Act), CELEX:32024R1689.
In development —Agentic Document Analyser converts unstructured compliance documents — risk assessments, model cards, audit logs, contracts — into structured JSON for inclusion in an Annex IV technical documentation pack. The tool is alpha quality and Docker-only today; production hardening is on the post-launch roadmap. ADA is evidence-processing infrastructure, not a standalone Article 11 compliance product.
Practical compliance with Agentic Document Analyser
Agentic Document Analyser converts unstructured compliance documents — risk assessments, model cards, audit logs, contracts — into structured JSON for inclusion in an Annex IV technical documentation pack. The tool is alpha quality and Docker-only today; production hardening is on the post-launch roadmap. ADA is evidence-processing infrastructure, not a standalone Article 11 compliance product.
When the findings land on a governance desk
Tools surface problems. Programmes solve them.
Annex IV documentation has to survive a regulator reading it years after the system shipped. AskAjay's Liability Ledger framework walks through what documentation completeness looks like under regulator pressure — pairs with ADA and the rest of the AiExponent evidence-processing layer.
Framework: Liability Ledger — at AskAjay.ai, the advisory arm of AI Exponent LLC.
Explore the Liability Ledger framework →Other articles in the EU AI Act