Skip to main content
Praxikon
All obligations
Upcomingv1.0.0

Article 11: technical documentation

The technical file demonstrating before market placement that a high-risk system meets the requirements.

Article 11 requires technical documentation drawn up before market placement, kept up to date and containing the Annex IV elements, so that compliance with Section 2 is demonstrable to supervisors.

Praxikon tracks Article 11: technical documentation under the EU AI Act, checked against the official source on 8 August 2026, citing the source for every statement.

Status
Upcoming
Application date
2 December 2027
Version
1.0.0
Last reviewed
8 August 2026

Review status: placed against the official source (8 August 2026). Next check due by 4 February 2027. The check date is the knowledge date of this version; no later recheck has been recorded.

From source to evidence

Why this obligation applies, what it asks of you, and what you show for it.

Applies

Upcoming · 2 December 2027

For whom

Provider of an AI system

What you do

Build the technical file per Annex IV

What you record

Technical file (Annex IV)

Official source

Article 11(1)-(3) and Annex IV

Who this is relevant to

When this applies

  • Provider of an AI system

    A party that develops or has an AI system developed and places it on the market under its own name.

  1. 1The provider places a high-risk AI system on the market or puts it into service.

What the official source establishes

For the Annex III route this requirement applies from 2 December 2027; for high-risk AI in regulated products (Annex I) from 2 August 2028.

Our interpretation

The official source remains authoritative. This general interpretation is not legal advice.

For buying organisations, Annex IV is the checklist of what you must be able to request contractually from your supplier; without that file you cannot meet your own Article 26 duties.

What you can do now

Include the right to access the technical documentation in AI procurement and supplier contracts now.

  1. 01

    Build the technical file per Annex IV

    Document system description, development process, data, oversight measures, performance and risk management before market placement.

What to retain

Technical file (Annex IV)

Technical documentation kept current per system version, ready for a supervisor’s request.

Control and reassessment

  • Documentation update on every release

    Update the file before every release and retain earlier versions traceably.

Public tools

Conditions and exceptions

  • Small providers (SMEs) may provide the documentation in the simplified form established by the Commission.

Official sources and locators

  • EU Artificial Intelligence Act 2024/1689

    European Parliament and Council | original-oj-2024-07-12

    Source locator: Article 11(1)-(3) and Annex IV

    Open official source

  • Digital Omnibus on AI 2026/1744

    European Parliament and Council | official-journal-2026-07-24

    Source locator: Amended Article 113 application dates

    Open official source

Referring to this object

Citation block

Copy this reference into your advice, article or file. The identifier, the version and the hash keep the statement findable later, even once the dataset has moved on.

Reference

Praxikon, "Article 11: technical documentation",
praxikon:eu:ai-act:obligation:article-11-technical-documentation@1.0.0,
dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.2.0 (schema 1.5.0),
effective_at 2026-07-27T00:00:00.000Z, known_at 2026-08-08T00:00:00.000Z,
sha256 15571dc37c23ef11a79a3b7b9b7d5674ee4fc7161cc4a9bb8f62321f66294a2c,
https://www.praxikon.com/en/verplichtingen/article-11-technical-documentation
(https://www.praxikon.com/api/v1/obligations?id=praxikon%3Aeu%3Aai-act%3Aobligation%3Aarticle-11-technical-documentation&effective_at=2026-07-27&known_at=2026-08-08&lang=en, accessed 2026-09-07)

Short form

praxikon:eu:ai-act:obligation:article-11-technical-documentation@1.0.0 (sha256 15571dc3)

BibTeX

@misc{praxikon-eu-ai-act-obligation-article-11-technical-documentation-1-0-0,
  author       = {{Praxikon}},
  title        = {Article 11: technical documentation},
  year         = {2026},
  version      = {1.0.0},
  number       = {praxikon:eu:ai-act:obligation:article-11-technical-documentation},
  howpublished = {AI Act Change \& Evidence Graph, dataset 2.2.0, schema 1.5.0},
  note         = {effective_at 2026-07-27T00:00:00.000Z; known_at 2026-08-08T00:00:00.000Z; sha256 15571dc37c23ef11a79a3b7b9b7d5674ee4fc7161cc4a9bb8f62321f66294a2c},
  url          = {https://www.praxikon.com/en/verplichtingen/article-11-technical-documentation},
  urldate      = {2026-09-07},
  language     = {en}
}

CSL JSON

[
  {
    "id": "praxikon:eu:ai-act:obligation:article-11-technical-documentation@1.0.0",
    "type": "dataset",
    "title": "Article 11: technical documentation",
    "container-title": "AI Act Change & Evidence Graph",
    "publisher": "Praxikon",
    "version": "1.0.0",
    "number": "praxikon:eu:ai-act:obligation:article-11-technical-documentation",
    "URL": "https://www.praxikon.com/en/verplichtingen/article-11-technical-documentation",
    "language": "en",
    "issued": {
      "date-parts": [
        [
          2026,
          8,
          8
        ]
      ]
    },
    "accessed": {
      "date-parts": [
        [
          2026,
          9,
          7
        ]
      ]
    },
    "note": "dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.2.0; schema 1.5.0; effective_at 2026-07-27T00:00:00.000Z; known_at 2026-08-08T00:00:00.000Z; sha256 15571dc37c23ef11a79a3b7b9b7d5674ee4fc7161cc4a9bb8f62321f66294a2c; retrieved_from https://www.praxikon.com/api/v1/obligations?id=praxikon%3Aeu%3Aai-act%3Aobligation%3Aarticle-11-technical-documentation&effective_at=2026-07-27&known_at=2026-08-08&lang=en; licence https://www.praxikon.com/nl/legal/terms"
  }
]

How to verify a reference later is set out in the methodology. Terms

Version history

  1. v1.0.0

    27 July 2026

    Article 11: technical documentation

    The technical file demonstrating before market placement that a high-risk system meets the requirements.

Corrections to this obligation

No substantive correction to this object has been recorded.

Open the correction log
Zahed Ashkara, lawyer and AI governance specialist

Expert behind this page

Zahed Ashkara

Lawyer and AI governance specialist

View profileLinkedIn

Execution

From obligation to arranged and demonstrable

Knowing where you stand is step one. Embed AI translates this obligation into a concrete approach for your organisation: scope, ownership, register and evidence.

See the Embed AI approach

For AI agents and integrations

This page and the machine output derive from the same versioned object. Use the API for deterministic filters by role, topic and time.

Open as JSONOpen as JSON-LDOpen this object in the explorerRead the methodology