Feature 1
Publish the approved version
Confirm publication metadata and make the reviewed version current for the intended audience.
- Set effective details
- Confirm visibility
- Publish the version
Capability
Policy Publishing and Versions
Publish approved policy versions with effective dates, visibility, distribution and complete version history.
The outcome
Give people the correct policy while preserving the history behind every approved version.
How it helps
How Policy Publishing and Versions works
This capability connects with the wider Apollo platform, so information can support action, evidence and reporting without being entered again.
Feature 2
Preserve policy history
Retain drafts and previous versions so the organisation can explain what applied at any point in time.
- Review version history
- Inspect prior wording
- Print the applicable version
What is included
One capability, connected to the wider platform
Use the capability you need now while keeping its records, work and evidence ready for related capabilities across Apollo.
Included features
- Draft and published versions
- Effective dates
- Publishing details
- Version history
- Visibility and distribution
- Web, print and Trust Centre presentation
Connected platform
Keep exploring Apollo
See where this capability is available and the related capabilities and solutions that use the same connected information.
Policy Authoring
Create and maintain policy content from files, URLs, templates or Apollo's structured document editor.
Explore capabilityPolicy Review and Approval
Send policy drafts through independent review, proposed changes and accountable approval before publication.
Explore capabilityPolicy Acknowledgements
Assign published policies to the relevant staff and maintain records of reading, acknowledgement and follow-up.
Explore capabilityProduct
Policy Management
Use policy management software to manage content, ownership, review, approval, publication and version history in one governed lifecycle.
Explore productProduct
Trust Centre
Publish approved security, privacy and compliance information through a branded customer-facing site.
Explore productQuestions and answers
Questions about Policy Publishing and Versions
Practical answers to common questions about managing this responsibility well.
Why does policy publishing and versions matter?
Give people the correct policy while preserving the history behind every approved version.
What should policy publishing and versions include?
It should cover draft and published versions, effective dates, publishing details, version history and visibility and distribution, with enough context to support action and explain decisions.
Who should be responsible for policy publishing and versions?
Ownership should sit with the person who can make decisions and keep the information current. A specialist or governance team may provide the method, but accountability should not be left with an unnamed group.
How do you keep policy publishing and versions current?
Set review dates according to risk and reassess after relevant incidents, material change, new evidence or overdue follow-up work. Preserve the history so changes remain explainable.
What evidence should be retained for policy publishing and versions?
Keep the source information, owner, review and approval history, supporting documents and resulting actions needed to show what was considered and what happened next.
See Policy Publishing and Versions in Apollo
Book a focused demonstration and we will show how the capability fits your current responsibilities, existing information and next practical priorities.