Skip to content

Build

Technical documentation: what AI regulations require

Documentation, instructions for use, model card, retention.

26 requirements · 10 regulations · 12 checks

Requirements by regulation

EUAI Act8

EX-005

Technical documentation Art. 11 + Annexe IV

EX-007

Transparency to deployers Art. 13

EX-011

10-year retention Art. 18

EX-014

Cooperation with authorities Art. 21 + Art. 26§12

EX-015

EU declaration of conformity Art. 47

EX-019

DPIA Art. 26§9

EX-027

Compliant use Art. 26§1

EX-031

GPAI obligations Art. 53

EUCRA1

CRA-31

Technical documentation and user information Art. 31, Annex VII

EUPLD1

PLD-09

Evidence disclosure and presumptions: keep documentation and logs Art. 9, 10

USNIST AI RMF8

MAP-1.1

Intended purposes, potentially beneficial uses, context-specific laws, norms and expectations, and prospective settings in which the AI system will be deployed are understood and documented. Considerations include: the specific set or types of users along with their expectations; potential positive and negative impacts of system uses to individuals, communities, organizations, society, and the planet; assumptions and related limitations about AI system purposes, uses, and risks across the development or product AI lifecycle; and related TEVV and system metrics. MAP

MAP-1.3

The organization's mission and relevant goals for AI technology are understood and documented. MAP

MAP-1.4

The business value or context of business use has been clearly defined or - in the case of assessing existing AI systems - re-evaluated. MAP

MAP-1.6

System requirements (e.g., 'the system shall respect the privacy of its users') are elicited from and understood by relevant AI actors. Design decisions take socio-technical implications into account to address AI risks. MAP

MAP-2.2

Information about the AI system's knowledge limits and how system output may be utilized and overseen by humans is documented. Documentation provides sufficient information to assist relevant AI actors when making decisions and taking subsequent actions. MAP

MAP-3.1

Potential benefits of intended AI system functionality and performance are examined and documented. MAP

MAP-3.3

Targeted application scope is specified and documented based on the system's capability, established context, and AI system categorization. MAP

MEASURE-2.9

The AI model is explained, validated, and documented, and AI system output is interpreted within its context - as identified in the map function - to inform responsible use and governance. MEASURE

COColorado AI Act1

CO-02

Documentation to deployers (risks, data, evaluations) §6-1-1702(2)

TXTRAIGA1

TX-03

Answer an AG civil investigative demand (purpose, data, metrics, limits, monitoring) §552.103

CASB 531

SB53-02

Transparency report before each new model §22757.12(c)

BRPL 23383

BR-09

Applier documentation Art. 18 I.a, I.c, I.f

BR-10

Developer documentation and explainability Art. 18 II.a, II.d

BR-17

General-purpose and generative AI Arts. 29, 30

KRAI Basic Act1

KR-04

High-impact measures: risk management, explainability, user protection, oversight, documentation Art. 34

INTLISO 420011

ISO-A.6

Lifecycle: design, verification, deployment, operation, event logs A.6

Checks in this theme

Most shared first

Code	Check	Used by
VER-005-01	Complete technical documentation compliant with Annex IV	AI Act PL 2338 CRA ISO 42001 AI Basic Act PLD TRAIGA
VER-007-01	Instructions for use complete and compliant with Art. 13	AI Act PL 2338 CRA ISO 42001 Colorado AI Act
VER-031-G-02	Documentation for downstream providers compliant with Annex XII	AI Act PL 2338 SB 53
VER-011-01	10-year document retention policy documented and implemented	AI Act PLD
VER-005-02	Instructions for use obtained and read by the deployer	AI Act PL 2338
VER-005-03	Use consistent with the intended purpose documented	AI Act PL 2338
VER-027-D-01	Use compliant with the purpose intended by the provider verified	AI Act ISO 42001
VER-031-G-01	GPAI model technical documentation compliant with Annex XI	AI Act PL 2338
CHK-USECASE-SCOPING	Intended purpose, context, applicable laws, business value and application scope are documented	NIST AI RMF
CHK-REQ-SPEC	System requirements are elicited with socio-technical implications addressed	NIST AI RMF
CHK-DOC-TECH	Technical documentation incl. knowledge limits, human oversight and usage instructions is maintained	NIST AI RMF
CHK-MODEL-CARD	The model is explained, validated and documented (model card)	NIST AI RMF

Related themes

Data governance Logging & traceability Accuracy & robustness Cybersecurity Environmental impact

Run these requirements across all your AI systems

TrustFlow inventories your systems, qualifies them under each regulation and collects evidence once for every referential.