In this article9 sections
The document bundle that decides your fine
When an EU market surveillance authority knocks on your door under the AI Act, they are not asking for a PowerPoint about your AI strategy. They want a specific bundle of documents proving that your high-risk AI system was assessed, monitored, and controlled before it went live. That bundle is your AI compliance evidence file, and without it, fines under Article 99 can reach €15 million or 3% of global annual turnover for a provider, whichever is higher. For SMEs and start-ups the lower of the two applies (Art 99(6)), and since the AI Omnibus small mid-caps get the lower figure for this tier too (Art 99(6a)). The high-risk rules themselves apply from 2 December 2027 for Annex III systems and from 2 August 2028 for AI in products covered by Annex I.
The good news: building this file is not a six-month legal project. A focused team at a 50-person company can do it in four to six weeks if they know what regulators are actually looking for.
What regulators check first
Market surveillance authorities work from a checklist. They want to see that you followed the obligations in Articles 9 through 17 of the AI Act, which cover risk management, data governance, technical documentation, logging, transparency, human oversight, accuracy, and quality management. Those eight areas map almost perfectly onto the six documents described below.
Only using a vendor's tool? Articles 9 to 17 and Annex IV are mostly the provider's job. If you deploy a high-risk system someone else built, your duties sit in Article 26 (from 2 December 2027): use it according to the instructions for use, assign human oversight to competent people, keep the logs, monitor its operation and inform the people affected. Your evidence file then holds the vendor's instructions for use and declaration of conformity, plus your own records of how you meet Article 26.
Authorities also check dates. A document created the week before an audit is a red flag. Each item in your evidence file needs a version history showing it was created and reviewed during normal operations, not assembled in a panic.
The six documents in a defensible evidence file
1. Risk management record
This is your written proof that you ran a systematic process to identify, estimate, and evaluate risks before deployment. Article 9 requires this to be a continuous process, not a one-off exercise. At minimum, the record should list every identified risk, the likelihood and severity of each, the mitigation measure applied, and the residual risk accepted. Two to three pages is fine. Fifty pages of boilerplate is not.
2. Technical documentation
Annex IV specifies exactly what technical documentation must contain: the system's intended purpose, the architecture, training data sources, validation results, and known limitations. Annex IV documentation is drawn up by the provider for authorities and notified bodies. If you are a deployer buying a third-party AI tool, you receive the instructions for use instead (Article 13): ask your vendor for them, and for the EU declaration of conformity, on day one. Since the AI Omnibus, SMEs and small mid-caps that are providers may supply the Annex IV elements in a simplified form that the Commission will publish (Art 11(1)).
3. Data governance log
Under Article 10, providers must make sure training and validation data meet specific quality criteria. Your data governance log records where data came from, what checks were applied, what biases were identified, and how they were addressed. For deployers using a vendor's pre-trained model, this section documents the data you feed into the system at runtime, such as employee performance scores or CV data in an HR context. Where you control that input data, Article 26(4) asks you to make sure it is relevant and sufficiently representative for the system's purpose.
4. Automatic logging records
Article 12 requires high-risk AI systems to generate logs automatically. Your evidence file should include a sample of these logs alongside your policy for how long logs are retained and who can access them. Logs must be kept for at least six months, unless other EU or national law requires something else (Arts 19, 26(6)). Check whether your sector sets a longer period.
5. Human oversight protocol
This is the document most SMEs skip. Article 14 requires providers to design high-risk systems so that natural persons can understand, monitor, and override them, and Article 26(2) requires deployers to assign that oversight to people with the necessary competence, training and authority. Your protocol should name the specific role responsible for oversight, describe how that person receives AI outputs, and document what override options exist. A one-page Standard Operating Procedure signed by a named manager is a practical format.
6. Conformity assessment report
For most high-risk AI categories listed in Annex III, the provider may use a self-assessment (internal control) conformity procedure rather than a third-party audit. The report documents your conclusion that the system meets the requirements and the evidence that supports it. It must be signed, dated, and accompanied by the EU declaration of conformity before the high-risk system is placed on the market or put into service. Since the AI Omnibus, SME providers without partner or linked enterprises may meet certain quality management system elements in a simplified manner (Art 63). If you only deploy the system, ask the vendor for its declaration.
Physical versus digital, and how long to keep it
The AI Act does not mandate a specific format, physical or digital. What it does mandate is availability. Under Article 18, providers must keep technical documentation for ten years after the high-risk AI system is placed on the market or put into service. Ten years is longer than most companies keep HR records.
A shared digital folder with access controls works perfectly. What does not work is documentation scattered across personal email inboxes, outdated SharePoint sites with broken permissions, or a single person's laptop. Use a folder structure that mirrors the six documents above. Name files with ISO 8601 dates (YYYY-MM-DD) so version history is immediately visible to any auditor.
Back up quarterly. Label each version clearly. Archive rather than delete old versions.
Who owns the file
Ownership should sit with one named role, not a committee. In practice, the right owner depends on your structure.
If you have a compliance officer, this is their file. Full stop. If you do not, the COO or a senior operations manager is the natural owner because they control processes rather than technology. The CISO or CTO can own the technical documentation section specifically, but someone outside IT must own the whole file. Regulators are skeptical when technical teams self-certify without business-side oversight.
The owner's responsibilities are concrete: ensure all six documents exist, schedule reviews, keep the version log, and be the named contact if an authority asks for the file. Write that into a job description or a formal mandate document, and put that mandate document inside the file itself.
How often to refresh
The risk management record and human oversight protocol should be reviewed every time the AI system changes significantly, and at least once every twelve months regardless. What counts as a significant change? A new training dataset, a new use case, a new integration with another system, or a change in the user population.
The technical documentation and data governance log should be updated whenever the underlying system or your data inputs change. Even if you are a deployer with a static vendor tool, your runtime data changes constantly. Review the log at least every six months.
The conformity assessment report needs to be re-run after any significant change. Many companies treat it as a one-time task. That is wrong. If you changed the system, you changed the basis of the conformity conclusion.
Set calendar reminders. Assign them to a named person. Document the outcome of each review, even if the outcome is "no changes required."
When the high-risk rules apply
The AI Omnibus (Regulation (EU) 2026/1744, in force 27 July 2026) fixed the dates. The high-risk obligations apply from 2 December 2027 for Annex III systems, such as recruitment or credit scoring, and from 2 August 2028 for AI in products covered by Annex I. These are fixed dates in the law.
Building a complete, defensible evidence file from scratch takes four to six weeks of focused work. Add time for vendor documentation requests, internal sign-off, and a dry-run self-audit. Starting well before December 2027 means the file shows a real version history rather than a last-minute bundle.
One part applies today for every company using AI: Article 4 has required providers and deployers to take measures to support the AI literacy of their staff since 2 February 2025. Keep a record of those measures in the same file: it is how you show what you did.
The one action to take this week
Print or copy the six headings above and check which documents you already have in any form. Most companies have fragments: a vendor data sheet, an IT risk log, a vague policy document. The gap analysis takes one hour. Once you know your gaps, you can sequence the work.
If you want a structured gap analysis with a clear output report, Khairos Comply offers a free 2-minute compliance check that maps your current situation against the six document requirements and tells you exactly where to start.
References
More in this guide
Not sure where your company stands?
Answer 15 questions about how your team uses AI. You get a compliance score and the gaps to close first, as a PDF.