Three ways compliance paperwork fails an audit.
One catalogue, 104 documents, four ways to build them.
Three documents, from first draft to issued.
A provider preparing the Annex IV technical file for a high-risk hiring tool.
- The file opens as an outline: each section names the Art. 9, 10, 14 or 15 obligation that feeds it.
- Sections fill from the risk plan, the oversight plan and the training-data record already in the workspace.
- Issued as a PDF pack, sealed, with a verify link for the notified body.
A deployer of an Annex III system writing its fundamental rights impact assessment.
- Art. 27(4) lets the FRIA build on an existing DPIA.
- Its answers are laid under the DPIA's Art. 35(7) headings, so each record shows what the other covers.
- The completed assessment is filed against the Art. 27 obligation as its evidence.
A 30-person company that needs an AI acceptable use policy this month.
- The policy opens from its template as a clause outline.
- Aria drafts the empty clauses; nothing is saved until a person keeps or edits each one.
- An approver signs it off and every member acknowledges it in the app.
- The owner is reminded four weeks before the annual review.
Documents come last, after the work they describe.
EU AI Act technical documentation: your questions
Which documents does Veritome produce?
104 in the catalogue today: 20 for each AI system and 84 for the organisation. By framework: EU AI Act 30, ISO 42001 26, ISO 27001 29, GDPR 18, NIST AI RMF 1. They include the Annex IV technical documentation, the EU declaration of conformity, the EU database registration sheet, the fundamental rights impact assessment, the post-market monitoring plan and the policies an auditor asks for first.
Do I start from a blank page?
No. Prescribed documents such as the declaration of conformity have a fixed field set in the order the Annex gives. Composed documents such as the Annex IV file have no fields of their own: they are assembled from the obligation work you have already done, and each section names the obligation that feeds it. Policies start from a clause outline, and Aria can draft the empty clauses for a person to keep or edit.
Can a regulator or a customer check a document is genuine?
For the technical dossier and the documents completed as smart forms, yes. Each is sealed with a SHA-256 fingerprint when it is generated, and its public verify page checks the seal without an account, so whoever receives the file can confirm it is the one you issued and that nothing changed since. Policies are different: they carry an approver, a version history and per-person acknowledgement inside the workspace, but no public verify page.
Does Veritome file documents with a regulator?
No. It prepares them, including the Annex VIII registration sheet ready to paste into the EU database, and you make the submission. Nothing is filed on your behalf and nothing here is legal advice.