Draw up technical documentation before placing a high-risk system on the market

Practical action

Maintain an Annex IV-structured technical file under version control.

Who does it apply to?

Providers of high-risk AI systems.

Actors

Provider / developer

Sectors

Cross-sector / all sectors

Use cases

AI in hiring and employmentAI in finance, credit and insuranceSafety-critical and infrastructure

Applies from: 2 December 2027

Which controls meet this duty?

Satisfies: the control, operated properly, does the work the duty asks for. Supports: it contributes but the duty needs more. Each control page lists every other duty it serves, so work done once can be counted once.

• satisfiesProcessProduct or model owner · at launch and on material change
  Technical documentation, model cards and instructions for use

  Serves 14 recorded duties · evidence: Technical documentation file, Model card or deployer information pack, Instructions for use

  Versioned technical file structured to the required elements.

• supportsProcessData governance lead · once per ai system
  Data governance and dataset documentation

  Serves 8 recorded duties · evidence: Dataset documentation sheet, Data quality and bias check report, Dataset approval for use

  Dataset sheets supply the data sections.

Templates that cover this duty

Generated from the records. Free · no account · links emailed to your work address. This duty is cited in each file with its source reference and a link back here.

• AI System Inventory

  Register · XLSX and DOCX · v6

• EU AI Act Role and Risk Classifier

  Checklist · XLSX · v4

• EU AI Act Article 50 Transparency Kit

  Kit · DOCX and XLSX · v32

• ISO/IEC 42001 Gap Assessment and Statement of Applicability

  Assessment · XLSX · v3

All 10 templates that cover it →

What evidence would a reviewer expect?

Framework mappings

Original editorial crosswalks. They cite clause numbers only and reproduce no standard text; confidence reflects how direct the mapping is.

See every European Union duty mapped this way →

Frequently asked questions

Cite this record

AIPolicyTracker (2026). “Draw up technical documentation before placing a high-risk system on the market (EU AI Act)” [AIPT-OBL-0008, not yet verified]. https://aipolicytracker.org/id/AIPT-OBL-0008 (accessed 27 October 2026). Data licensed CC BY 4.0.

Permanent id AIPT-OBL-0008: it never changes or gets reused, and its address keeps working if this page moves.

Cite the official text alongside it: Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence, Official Journal of the European Union, https://eur-lex.europa.eu/eli/reg/2024/1689/oj.

@misc{aipolicytracker2026_drawuptechnicaldocumenta,
  author       = {{AIPolicyTracker}},
  title        = {{Draw up technical documentation before placing a high-risk system on the market (EU AI Act)}},
  year         = {2026},
  howpublished = {\url{https://aipolicytracker.org/obligations/eu-ai-act-technical-documentation}},
  url          = {https://aipolicytracker.org/obligations/eu-ai-act-technical-documentation},
  urldate      = {2026-10-27},
  note         = {Data licensed CC BY 4.0. Accessed 27 October 2026}
}

Change history

Similar obligations in other instruments

• Providers must document and register a conclusion that an Annex III system is not high-risk — EU AI Act, European Union
• Providers of GPAI models must maintain technical documentation and inform downstream providers — EU AI Act, European Union
• Developers must document high-risk systems and disclose known risks — Colorado AI Act, Colorado (United States)
• Developers must supply deployers with documentation of the technology — Colorado ADMT law (SB 26-189), Colorado (United States)