WHAT FACTS SUPPORT THE CLASSIFICATION?
Preserve the system identity, intended purpose, operator role, applicable risk route, exclusions relied on, versions, dependencies, deployment context and the evidence supporting those facts.
WHAT DO YOU ACTUALLY NEED
TO HAVE ON FILE?
EU AI Act governance becomes real when a business can show the evidence behind its system identity, classification, obligations, controls, changes and continuing reliance. The goal is not a bigger document folder. It is a current, attributable evidence record.
BOUNDARYThis page is educational and operational guidance. It is not legal advice, certification, conformity assessment or regulatory approval.
CURRENT SOURCE ANCHOR
OPEN OFFICIAL EU SOURCE ↗EUR-Lex · Regulation (EU) 2024/1689 · Articles 11, 12, 18 and 19
For high-risk AI systems, Article 11 requires technical documentation before market placement or use and requires it to be kept up to date. Article 12 requires automatic logging capability. Article 18 sets a 10-year provider documentation-retention period for specified records, while Article 19 generally requires controlled logs to be kept for at least six months unless other law provides otherwise.
WHAT BUSINESSES NEED TO ESTABLISH
Do not start with a generic checklist.
Start with the actual system, role, use case and evidence boundary. The same regulation can produce different obligations for different actors and systems.
WHAT DOCUMENTATION SUPPORTS THE SYSTEM REQUIREMENTS?
For high-risk systems this can include technical documentation, risk-management records, data-governance evidence, testing, instructions for use, human-oversight measures, accuracy, robustness and cybersecurity evidence.
WHAT OPERATIONAL RECORDS MUST SURVIVE OVER TIME?
Logs, monitoring records, incidents, corrective actions, post-market evidence, approved changes, declarations, notices and review history matter because the compliance position must survive beyond a one-time assessment.
CAN YOU SHOW WHAT CHANGED AND WHAT WAS REVALIDATED?
Evidence is not durable if old files silently support a new system state. Preserve version changes, model swaps, intended-purpose changes, authority changes, source-state changes and the revalidation decision.
THE TA-14 OPERATING ROUTE
Turn the question into a governed record.
The goal is not merely to reach an answer. It is to preserve what facts, evidence, scope and limitations supported that answer at that time.
Define the proposition before collecting files
Start with the claim being supported: system identity, actor role, classification, transparency duty, high-risk requirement, human oversight, or another obligation. A file is only useful if it supports a bounded proposition.
Bind each evidence object to source, version, scope and owner
Preserve who produced the evidence, what system/version it concerns, when it was valid, what scope it covers, and which accountable person or authority relies on it.
Separate supported, missing, stale and unresolved evidence
A governed record should show evidence gaps and stale evidence explicitly instead of allowing an incomplete folder to look complete.
Revalidate after material change
When the system, intended purpose, model, authority, deployment, legal source or control environment changes, question whether the previous evidence can still be relied upon.
READY TO OPERATE · START PAID ACCESS NOW
Move from reading about the EU AI Act to maintaining the record.
Choose the smallest operating tier that fits the portfolio today. Upgrade when system count, team size or governance scope actually requires it.
Evidence Passport
$19/MOKeep a living system-level evidence record with obligations, gaps, versions and revalidation state.
START EVIDENCE PASSPORT →Compliance Workspace
$49/MOCoordinate evidence, owners, documentation, incidents and team compliance work in one governed workspace.
START COMPLIANCE WORKSPACE →Governance Pro
$99/MOOperate broader high-risk, GPAI, FRIA, post-market and material-change governance across a growing portfolio.
START GOVERNANCE PRO →Institution
$499/MORun institutional governance with expanded users, authority workflows, examiner rooms and portfolio reporting.
START INSTITUTION →Need an independent human readiness examination?A governed readiness review is separate from software access and starts at $750.
REQUEST READINESS REVIEW →Not ready to subscribe? Classify first.
Use the free classifier to establish the system, intended purpose, possible actor role, EU exposure and unresolved facts. When continuing evidence infrastructure is needed, paid access begins at $19 per month. Independent human readiness review remains a separate service.
COMMON QUESTIONS
Questions businesses are asking now.
Does the EU AI Act require technical documentation?
Yes for high-risk AI systems. Article 11 requires technical documentation to be drawn up before the system is placed on the market or put into service, kept up to date, and structured to demonstrate compliance with the high-risk requirements.
What does high-risk technical documentation contain?
Article 11 points to Annex IV. In practice, the documentation covers the system description, development process, monitoring and control, performance, risk-management measures, changes and other information needed to assess conformity.
Does the EU AI Act require logs?
High-risk AI systems must technically allow automatic logging over their lifetime under Article 12. Providers and deployers must keep logs under their control for an appropriate period, generally at least six months unless other law provides differently.
How long must providers keep high-risk documentation?
Article 18 requires providers to keep specified documentation available to competent authorities for 10 years after the high-risk AI system has been placed on the market or put into service.
Is every EU AI Act evidence requirement the same for every company?
No. The evidence set depends on the system, operator role, risk classification, intended purpose, sector, customer use, transparency duties and other applicable Union or national law.
Does uploading documents to TA-14 prove compliance?
No. TA-14 can preserve evidence identity, scope, provenance, gaps, change and revalidation state. The existence of a document—or its presence in a workspace—does not by itself establish legal compliance.