Feature 1
Set acknowledgement requirements
Choose which roles or staff must acknowledge a policy and how long they have to respond.
- Select a policy
- Assign roles
- Set the due period
Capability
Policy Acknowledgements
Assign published policies to the relevant staff and maintain records of reading, acknowledgement and follow-up.
The outcome
Know who was asked to read each policy version, who acknowledged it and where follow-up remains.
How it helps
How Policy Acknowledgements works
This capability connects with the wider Apollo platform, so information can support action, evidence and reporting without being entered again.
Feature 2
Track the exact version staff received
Connect every acknowledgement record to the published wording that applied to that person.
- Review records
- Find overdue work
- Report completion
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
- Role-based requirements
- Published-version tasks
- Staff reading and acknowledgement
- Due and overdue status
- Acknowledgement records
- Reporting matrix
Connected platform
Keep exploring Apollo
See where this capability is available and the related capabilities and solutions that use the same connected information.
Questions and answers
Questions about Policy Acknowledgements
Practical answers to common questions about managing this responsibility well.
Why does policy acknowledgements matter?
Know who was asked to read each policy version, who acknowledged it and where follow-up remains.
What should policy acknowledgements include?
It should cover role-based requirements, published-version tasks, staff reading and acknowledgement, due and overdue status and acknowledgement records, with enough context to support action and explain decisions.
Who should be responsible for policy acknowledgements?
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 acknowledgements 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 acknowledgements?
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 Acknowledgements in Apollo
Book a focused demonstration and we will show how the capability fits your current responsibilities, existing information and next practical priorities.