Every change you make to a policy is tracked against the current draft. When you're ready to share it, you publish the policy, which creates a new version and generates a PDF automatically.
Review changes before publishing
When you publish, the platform shows you a summary of what's changed since the last version: sections added, removed, or modified. You can review the full diff before confirming.
Editorial vs substantive updates
When publishing, you choose what kind of update it is. This determines how the version number changes.
- Editorial – language fixes and clarifications. The minor version number increases, for example v1.0 becomes v1.1.
- Substantive – changed requirements or responsibilities. The major version number increases, for example v1.0 becomes v2.0.
You can also add a short description of what changed. This appears in the version history and makes it easier to understand the history of a policy at a glance.
What happens when you publish
Publishing a policy creates a new version and generates a PDF, which is automatically added under the Documents tab. The policy is not distributed to recipients automatically. To send it out and collect sign-offs, go to the Recipients and sign-offs tab. See Distribute policies and collect sign-offs.
Version history
The Version history tab gives you a full log of every published version. For each version you can see the published date, approver, description of changes, number of linked controls, recipients, and sign-off progress.
You can open any previous version to read the full content as it was at the time, and compare any two versions side by side or inline.