Attach evidence and verify generated documents
Attach fingerprinted evidence to obligations and checklist items, and generate the Annex IV, FRIA and declaration documents that each carry a public verify URL.
Evidence on an obligation
Each obligation and each of its checklist items takes evidence — upload a file or record a link, attached directly to the requirement it supports. Evidence is fingerprinted with a SHA-256 hash so it is tamper-evident, and identical files are recognised as the same record rather than duplicated. One record can be linked to many obligations across many systems. For the cross-portfolio view — seals, links, connectors and freshness — see The Evidence hub.
Generated documents
From a system you can generate the formal documents a regulator recognises, each assembled from the obligation work you have already done rather than retyped:
- Annex IV technical documentation (Art. 11)
- FRIA — the fundamental-rights impact assessment (Art. 27)
- EU Declaration of Conformity (Art. 47, Annex V)
- the Annex VIII registration sheet (Art. 49)
- the instructions for use package (Art. 13)
Each is filed as generated evidence with the hash of its exact bytes, and each carries a public verify URL so a regulator or customer can confirm the document is unaltered without an email attachment. Generated documents are clearly marked a working draft for your review, not a regulator submission. Their register — what is owed, drafted, approved and issued — is Documents; how they assemble into a sealed pack is in Dossiers, tech docs and the regulator view and Reports, CSV export and audit bundles.