Attach evidence and verify generated documents
Attach hash-sealed evidence to obligations, and generate Annex IV, FRIA and Declaration of Conformity documents that each carry a public verify URL.
Evidence
Each obligation checklist item takes evidence — upload a file or link a document, attached directly to the requirement it supports. Evidence is fingerprinted with a SHA-256 hash so it's tamper-evident, and identical files are recognised as the same record rather than duplicated. For the full cross-portfolio view — coverage, gaps, connectors and freshness — see The Evidence hub.
Generated documents
From a system you can generate the formal documents a regulator recognises:
- Annex IV technical documentation (Art. 11)
- FRIA — fundamental-rights impact assessment (Art. 27)
- Declaration of Conformity (Art. 47)
Each is built from the obligation work you've already done, and each carries a public verify URL so a regulator or customer can confirm authenticity without an email attachment. Documents are clearly marked a working draft for your review, not a regulator submission — see Dossiers, tech docs and the regulator view and Reports and audit bundles for how these assemble into a sealed pack.