Document Studio: every required document, one register
The unified register of every EU AI Act document your organisation must produce — status per document per system, drafts composed from your obligation data, and sealing for the ones that matter.
Documentation → Document Studio answers the question every audit begins with: which documents does the Act require from us, and do we have them? It's a register of ~30 document types — Annex IV technical documentation, FRIA, Declaration of Conformity, transparency notices, monitoring plans, data-governance policies and the rest — with a live status for each, per system.
Reading the register
Every row is one required document for one system (or the organisation), keyed to the article that requires it. The status tells you exactly where it stands:
- To add — nothing exists yet.
- In progress — the source obligations are partially complete.
- Ready — every obligation the document draws from is complete; generating now produces a full draft.
- Generated — a draft exists.
- Sealed — the finished document is fingerprinted (SHA-256) into your evidence and dossier chain, so what you show an auditor is provably the file you generated.
Tracking is free on every plan. The register always shows what's required and what's missing — the gap analysis costs nothing. Generating and sealing documents is a Growth-plan feature.
Composition — your data becomes the draft
Open any row and you land in an editor for that document. Veritome composes a draft from the obligation data you've already entered — classification details, checklist answers, form fields, risk records. Composition is deliberately prefill, never overwrite: only genuinely empty fields are seeded, anything you've written by hand stays yours, and composed drafts are labelled as such.
Some document types get a bespoke structured editor (the FRIA wizard, the importer pre-market form); everything else opens in the generic editor. Every row in the register resolves to a working editor — there is no document type you can see but not produce.
Sealing and verification
Sealing a finished document computes its fingerprint and writes it into the system's dossier chain-of-custody. Anyone you hand the document to can check it against the public verify page — see Attach evidence and verify generated documents for how verification reads.