All modules
Core HRAvailable
Policy Acknowledgements
Publish a policy, ask people to confirm they have read it, and know — version by version — who has and who has not.
The problem
Policies get emailed as attachments and the record of who read them is a thread someone half-remembers. Then the policy is updated, the old confirmations quietly stop meaning anything, and nobody can say who has seen the version that is actually in force.
What it covers
The building blocks of Policy Acknowledgements.
- Policy versions as records in their own right — republishing never rewrites what someone already confirmed
- A read-and-confirm page: the policy text, a typed full name, and an explicit confirmation
- An expiring, single-purpose link you can send to someone who has no login yet
- Confirming twice records once — the same acknowledgement comes back, never a duplicate
- An HR view of who has and has not confirmed each version, by name
- Every acknowledgement written to the audit trail, and never editable or deletable afterwards
- Plain labelling throughout: this records an acknowledgement, and says so — it is not a digital signature
- A route to Demystify Sign for documents your organisation marks as needing a signature, where signing is available
Typical use cases
A few of the ways teams use Policy Acknowledgements.
POSH policy rollout and its yearly refresh
Leave or code-of-conduct updates that everyone must read
Showing an auditor who accepted which version, and when
Collecting a confirmation from a joiner before their login exists
More in Core HR
Ready to try Policy Acknowledgements?
Start free in minutes, or book a walkthrough with our team.