Quick answer
Open Policies → Acknowledgements (/policies/admin). Each row is one version of one policy, showing how many people have confirmed it and naming everyone who has not.
Version is a column, not a footnote
The view is organised around policy versions because that is the only way the numbers mean anything.
When you republish a policy, ASHR.work retires the old version and publishes a new one as a separate record. Acknowledgements already collected stay attached to the version they were made against. So the report can tell you two different things at once — that thirty people accepted version 2, and that only eleven of them have yet accepted version 3 — instead of collapsing both into one misleading figure.
What the outstanding column is for
It lists names, not a completion percentage. "82% complete" is not something you can act on; "Priya and Arun have not confirmed v3" is.
Sending a link to someone who has no login
Not everyone who needs to acknowledge a policy has an account yet — a joiner, most often. Issue an acknowledgement link for them and it opens the policy text and the same confirmation without requiring a sign-in.
The link is a credential in its own right, so it behaves like one: it expires, it is valid for exactly one person and one policy version, and it is shown to you once. ASHR.work stores only a hash of it, so the record can show which link was used without the link itself being recoverable.
What this is, and what it is not
Every acknowledgement here is a recorded confirmation that a person read a specific version of a policy. It is not a digital signature and the product never describes it as one.
For documents that must actually be signed, your organisation can mark them so, and they route to Demystify Sign rather than being acknowledged here — once signing is available to you.
Frequently asked questions
- Why does the same policy appear on more than one row?
- Because each version is its own record. Republishing a policy does not overwrite the previous version — it retires it and publishes a new one — so the earlier acknowledgements stay true statements about the text those people actually read. Showing them merged would tell you that people had accepted words they never saw.
- Someone acknowledged the old version. Do I have to chase them?
- That is your call, and the view is built so you can make it. They appear as confirmed against the version they read, and outstanding against the current one. If the change was material you chase them; if it was a typo fix you may not.
- Can I correct or remove an acknowledgement?
- No. Acknowledgements are append-only — there is no edit and no delete, for anyone, including HR and platform administrators. A record of a past act that could be quietly rewritten would not be worth keeping. If something was recorded in error, publish a new version and collect fresh acknowledgements against it.
- Is an acknowledgement the same as a signature?
- No. It records that a named person opened a named version of a policy and confirmed they had read it. That is evidence of assent to an internal document, not a digital signature. Documents that must genuinely be signed — offer letters, contracts — route through Demystify Sign, where signing is switched on for your organisation.
- What is stored about the link I send?
- Only a one-way hash of it, and its expiry — never the link itself, because anyone holding it could use it. The record shows which link was redeemed without the link being recoverable from the record.
- Can a manager see this?
- No. This view is HR-admin only. It names people who have not done something, which is a people-management fact rather than a directory one.
This guide also lives in the help centre at /help/policy-acks/how-to-see-who-has-acknowledged-a-policy, which is its canonical home.