A document no longer matches my register
A generated document captures your details at the moment you made it. If your register changes later, the document does not change with it. The fix is to regenerate.
Updated May 2026
Why it happens
When you generate a document, Veillo fills it from your company and system details at that moment, then keeps it as a version you can edit. It does not silently rewrite a document you may have already reviewed or shared. So if you rename your company, confirm a new high-risk system, or change a use, an existing document keeps the old details until you regenerate it.
Regenerate it
Go to Documents and generate the document again. The new version picks up the current details, and the previous version is kept in the document's history, so you do not lose the record of what said what. For small wording tweaks, you can also edit the document directly in the editor. See generate your first document.
Keeping documents in sync
The cleanest habit is to regenerate any affected document as soon as you change the register, especially the per-system ones that name a specific tool. The quarterly review exists to catch anything that slipped through. For which documents name a system, see org-wide vs per-system documents.
Generate a compliance document from your register: pick a template, choose the system if needed, then edit, export to PDF or DOCX, and keep versions.
Why some Veillo documents are generated once for the whole company and others once per high-risk system, and what that means when your register changes.
What the quarterly review is, the three statements you confirm, who can sign it off, and how it keeps your register honest.
Still need help?
Get in touch and a human will answer, or book a short walkthrough.