This is governance evidence, the workforce side of the Practice Standards rather than the training side: proof that a policy reached the people it applies to, by name, by version, with a date.
What an acknowledgement actually records
An acknowledgement in CORA records four things: a worker's name, a policy, the exact version number they had open, and the date and time they pressed acknowledge. That's a precise record of contact with a specific version of a specific document, attributed to one person, timestamped. It's a different claim from understanding what the policy says, and being exact about which one you're holding is exactly the kind of precision an auditor respects.
Every new version, asked again
Upload a new version of a policy and CORA doesn't quietly assume last year's acknowledgement still counts for it. Every worker in scope goes back to outstanding for the new version the moment it's published, and their acknowledgement of the old one stays on record as exactly what it was: proof they read version 3, not version 4.
That's the property most providers lose the moment a policy library lives in a shared drive. A file gets replaced, and there's no way to tell who read the new one and who's working from a version that no longer applies.
Scoped to the whole organisation, or to named teams
A policy can apply to everyone, or to specific teams only. A medication management policy scoped to the teams that actually administer medication reaches exactly those workers. A code of conduct scoped to the whole organisation reaches everyone. Either way, the same outstanding derivation applies: an active worker inside a policy's scope, with no acknowledgement of its current version, shows up as outstanding until they acknowledge it.
The register shows what's outstanding, not just what's done
Open the policy register and every active policy shows its current version and a count: how many workers are in scope, how many have acknowledged the current version. Outstanding workers sort first, because that's what a provider opens the register to chase, not a list of who's already finished.
Exports, per policy or organisation-wide
A single policy exports as its own record: every worker in scope, whether they've acknowledged the current version, which version they last acknowledged if it wasn't the current one, and the date. An organisation-wide export covers every policy at once, the same shape repeated down the page, ready to hand to an assessor who wants the whole picture rather than one document at a time.
Where policy titles come from
CORA's policy library suggests titles grouped against the Practice Standards' own divisions inside the Core Module: rights and responsibilities, governance and operational management, provision of supports, and support environment, alongside common ones like the Code of Conduct that sit outside those groups. A provider still writes and owns the content. The suggestions exist so a new policy gets filed against a category an auditor will actually recognise, rather than however it happened to be named in the shared drive it came from.
Every claim on this page is written the same way every claim on the site is written: about a named artefact, checkable in a demo. See the standard CORA holds every claim to.
Archiving keeps the history
Retiring a policy takes it off the active register. Every acknowledgement ever recorded against it stays on the worker's own history and stays reachable, because a policy going out of use is not the same fact as a record of who read it while it was current.
Common questions
What does a policy acknowledgement record?
A worker's name, the policy, the exact version number, and the date and time they acknowledged it. That's what's on file for every acknowledgement in the register.
What happens when a policy gets a new version?
Every worker in the policy's scope goes back to outstanding for the new version. Their acknowledgement of the previous version stays on record, attributed to that version specifically.
Can I export acknowledgements for one policy, or for everything at once?
Both. A per-policy export lists every worker in scope against that one policy. An organisation-wide export covers every policy at once, in the same format.
Does archiving a policy delete the acknowledgement history?
No. Archiving removes a policy from the active register. Every acknowledgement already recorded against it stays on the worker's history.