Art.11

Article 11 — Technical Documentation

High-Risk Systems SME Relevant ~2 min read · 395 words

Article 11 requires providers of high-risk AI systems to draw up comprehensive technical documentation before placing their system on the market — and to keep it updated throughout the system’s lifecycle. This documentation is what regulators and conformity assessment bodies will ask to see.

! High compliance impact for SMEs

WHAT THE ARTICLE IS ABOUT

Your compliance evidence file

Article 11 establishes the technical documentation obligation for high-risk AI systems. It ensures that the design, development, and performance of a high-risk AI system are fully documented in a way that allows regulators and auditors to assess compliance with all applicable requirements under the Act.

WHAT IT SAYS

Pre-market, comprehensive, and continuously updated

Providers must draw up technical documentation before placing a high-risk AI system on the market or putting it into service
The documentation must be kept up to date throughout the system’s lifecycle — it is not a one-time deliverable
The content of the technical documentation is specified in Annex IV and includes: a general description of the system, a detailed description of its design and development process, information on monitoring and testing, and details of the risk management system
For providers who are SMEs or startups, the Commission may provide simplified documentation forms that reduce the administrative burden while maintaining essential transparency
Technical documentation must be made available to national competent authorities on request

WHO IS AFFECTED

All high-risk AI providers before market launch

All providers of high-risk AI systems — this is a mandatory pre-market requirement
Technical and engineering teams responsible for system documentation
Quality assurance teams managing compliance records
National market surveillance authorities who may request access to documentation

WHAT IT MEANS FOR SMES

Start during development — and use the simplified pathway

The simplified documentation pathway specifically mentioned in Article 11 is a direct concession to SMEs — look for the Commission guidance on this as it is published
Start your technical documentation during development, not after — the requirements in Annex IV map closely to good engineering practice, so if you are building well you are already generating much of what is required
Think of technical documentation as your compliance evidence file — it is what you show a regulator if your system is ever questioned
Version control your documentation alongside your AI system — when the system is updated, the documentation must be updated too
If you are a deployer using a third-party high-risk AI system, request the technical documentation summary from your provider — you may need elements of it for your own compliance obligations

Article 9 — Risk management (feeds into the documentation)
Article 10 — Data governance (must be reflected in technical docs)
Article 18 — Documentation retention obligations
Annex IV — The full list of required technical documentation content

← Back to the Guide