Version History

Where versions appear

The Version history section at the bottom of the statement page lists recent versions, each showing its number, publication date, what triggered it, and per-standard pass counts. Select View all versions to open the full version history page.

What creates a version

Publishing always creates a version, but versions are also recorded automatically as your statement's underlying data changes. Each version shows its trigger:

• You published: you selected the publish button.
• Audit completed: your audit finished.
• Action result changed: a verdict in your audit changed.
• Ticket status changed: a remediation ticket moved status.
• Organisation details changed: inherited organisation fields were updated.

Versions carry a kind badge: Intent for Statement of Intent versions, Audit for versions with full compliance data.

Reading a version card

On the version history page, each card shows the version's compliance posture per standard (Compliant, Partially compliant, or Not compliant) with passed counts, plus a diff against the previous version, for example "+2 passed". The first version reads "Initial publication", and unchanged versions read "No compliance changes". The version currently served by your public link carries a Live badge.

Pinning a version

By default, your public link always serves the latest version. To freeze it, select Pin on any version card. The statement page then shows a banner confirming the statement is pinned, and new versions will not appear on the public URL until you select Unpin or pin a newer version.

Pinning is useful when you want to review changes before they go public, or keep a known snapshot live during remediation. See sharing your statement for how the public link works.