Skip to main content
Praxikon
Comparisons

Comparison

Article 11 versus Article 13: technical documentation and instructions for use

The difference

The technical documentation of Article 11 is internal and meant for the supervisory authority: it shows how the system was built and why it meets the requirements. The instructions for use of Article 13 are external and meant for the deployer: they have to enable that party to use the system correctly and to actually exercise human oversight.

The official source remains authoritative. This is general interpretation and not legal advice about your situation.

The fields side by side

Every row comes from the objects themselves. Where a field is empty, it says so; we do not fill in an assumption where the source is silent.

Status

Article 11, technical documentation
Upcoming
Article 13, instructions for use
Upcoming

Applies from

Article 11, technical documentation
2 December 2027
Article 13, instructions for use
2 December 2027

Who carries the duty

Article 11, technical documentation
Provider of an AI system
Article 13, instructions for use
Provider of an AI system

Who is affected

Article 11, technical documentation
Not recorded
Article 13, instructions for use
Deployer

Who supervises

Article 11, technical documentation
Not recorded
Article 13, instructions for use
Not recorded

When this applies

Article 11, technical documentation
The provider places a high-risk AI system on the market or puts it into service.
Article 13, instructions for use
The provider supplies a high-risk system; the deployer uses it according to the instructions.

Exceptions

Article 11, technical documentation
Small providers (SMEs) may provide the documentation in the simplified form established by the Commission.
Article 13, instructions for use
The level of detail may match the intended deployer’s knowledge; trade secrets need not be disclosed.

First actions

Article 11, technical documentation
Build the technical file per Annex IV
Article 13, instructions for use
Provide complete instructions for use

Evidence that belongs with it

Article 11, technical documentation
Technical file (Annex IV)
Article 13, instructions for use
Instructions and interpretation file

Control

Article 11, technical documentation
Documentation update on every release
Article 13, instructions for use
Instructions check at deployment

Version and review status

Article 11, technical documentation
v1.0.0, placed against the official source
Article 13, instructions for use
v1.0.0, placed against the official source

Official sources and locators

Per side, the provisions the statements above rest on.

Article 11, technical documentation

Article 13, instructions for use

Referring to these two objects

Each side has its own stable identifier, version and hash. Take them separately; you cite a comparison by citing the two objects.

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.1.0 (schema 1.4.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-08-24)

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.1.0, schema 1.4.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-08-24},
  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,
          8,
          24
        ]
      ]
    },
    "note": "dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.1.0; schema 1.4.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

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 13: transparency towards deployers",
praxikon:eu:ai-act:obligation:article-13-instructions@1.0.0,
dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.1.0 (schema 1.4.0),
effective_at 2026-07-27T00:00:00.000Z, known_at 2026-08-08T00:00:00.000Z,
sha256 818266e8912de0d2c95a38a4a16c67b1aad02d10359b3571710fd757c678819b,
https://www.praxikon.com/en/verplichtingen/article-13-instructions
(https://www.praxikon.com/api/v1/obligations?id=praxikon%3Aeu%3Aai-act%3Aobligation%3Aarticle-13-instructions&effective_at=2026-07-27&known_at=2026-08-08&lang=en, accessed 2026-08-24)

Short form

praxikon:eu:ai-act:obligation:article-13-instructions@1.0.0 (sha256 818266e8)

BibTeX

@misc{praxikon-eu-ai-act-obligation-article-13-instructions-1-0-0,
  author       = {{Praxikon}},
  title        = {Article 13: transparency towards deployers},
  year         = {2026},
  version      = {1.0.0},
  number       = {praxikon:eu:ai-act:obligation:article-13-instructions},
  howpublished = {AI Act Change \& Evidence Graph, dataset 2.1.0, schema 1.4.0},
  note         = {effective_at 2026-07-27T00:00:00.000Z; known_at 2026-08-08T00:00:00.000Z; sha256 818266e8912de0d2c95a38a4a16c67b1aad02d10359b3571710fd757c678819b},
  url          = {https://www.praxikon.com/en/verplichtingen/article-13-instructions},
  urldate      = {2026-08-24},
  language     = {en}
}

CSL JSON

[
  {
    "id": "praxikon:eu:ai-act:obligation:article-13-instructions@1.0.0",
    "type": "dataset",
    "title": "Article 13: transparency towards deployers",
    "container-title": "AI Act Change & Evidence Graph",
    "publisher": "Praxikon",
    "version": "1.0.0",
    "number": "praxikon:eu:ai-act:obligation:article-13-instructions",
    "URL": "https://www.praxikon.com/en/verplichtingen/article-13-instructions",
    "language": "en",
    "issued": {
      "date-parts": [
        [
          2026,
          8,
          8
        ]
      ]
    },
    "accessed": {
      "date-parts": [
        [
          2026,
          8,
          24
        ]
      ]
    },
    "note": "dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.1.0; schema 1.4.0; effective_at 2026-07-27T00:00:00.000Z; known_at 2026-08-08T00:00:00.000Z; sha256 818266e8912de0d2c95a38a4a16c67b1aad02d10359b3571710fd757c678819b; retrieved_from https://www.praxikon.com/api/v1/obligations?id=praxikon%3Aeu%3Aai-act%3Aobligation%3Aarticle-13-instructions&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

Execution

Put the evidence where it will be asked for

Two duties that look alike rarely produce the same piece of evidence, and you notice that difference only once a supervisory authority or a client asks. Praxikon does not carry that out; Embed AI maps scope, ownership and recording per system.

See the Embed AI approach

Unsure about your role itself rather than the duties that come with it? Work out whether you are a provider or a deployer