Policy acknowledgement
Policy acknowledgement is a named person confirming that they have read a specific version of a policy, at a recorded time, in a way that can be shown to someone else later.
That last part is what separates it from sending a policy out. An email was sent, a file was opened, a row was ticked in a spreadsheet: none of those is a confirmation by the person. This section defines the term, shows what the process looks like in practice, and explains how it can be shaped around an organization without the record getting weaker.
What a valid acknowledgement needs
- 1. A specific policy, at a specific version
- 2. A specific person, whose identity was checked
- 3. An explicit action by that person, not by an administrator
- 4. A record of when, kept where it cannot be edited
What it looks like in practice
Three screens from Policy Confirm, one for each side of the process: the person confirming, the administrator following up, and the record that is left behind.

The person confirms
A personal link or the policy portal, a one-time code or Microsoft sign-in, the policies to read, and one click. A quiz or signature if the policy requires it.

The administrator follows up
Who has confirmed, who is pending, who is overdue. Reminders go out on their own, and someone who joins mid-cycle gets their own deadline.

The record stays
Who confirmed which version, when and how. As a PDF or CSV, per person, per group or for the whole organization, for the auditor or the customer who asks.
The process is yours. The record is the same.
No two organizations run acknowledgement the same way, and a system that forces one way gets worked around. What can vary is below. What cannot vary is the four elements above: whatever the route, the confirmation is by a named person, against a version, at a time, and kept.
Different groups, different policies
A department, a site, a role, contractors, or one named person. Each policy applies to the groups you choose, and a cycle can cover one group or the whole organization.
Scheduled, recurring, or by hand
An annual round, a cycle every time a policy changes, or one that runs all year and picks up new joiners with their own deadline. Or send it yourself when you decide.
Documents where they already live
Link a policy to its page in SharePoint or the intranet, upload the PDF, or write where it is kept. The confirmation is recorded against the version either way.
The confirmation you require
A click after a one-time code or Microsoft sign-in. Questions to answer correctly first, for the policies that have them. A drawn or typed signature where the organization requires one.
Each element, and where it is in Policy Confirm
Closeups from the app, one for each part of a valid acknowledgement.
1 of 4
The policy, at a version
Every policy keeps its versions: an uploaded PDF, a link to SharePoint or the intranet, or a note of where it is kept. Recipients open the current one, and the confirmation names it.

2 of 4
An identified person, by their own action
People sign in with a one-time code or Microsoft, open each policy with View, tick it and confirm. The box cannot be ticked before the policy has been opened.

3 of 4
Followed up until everyone has confirmed
Each person has their own deadline. Reminders go out before and after it, and the cycle shows who has confirmed all, some or none of their policies.

4 of 4
A record that stays
Each person's confirmations across every cycle, with the version, whether it is still the latest, whether they confirmed or signed, and when. As a PDF, Excel, or a proof per cycle.

Reference pages
4 pagesIn depth, with examples from Policy Confirm: what acknowledgement is, why a read receipt is not one, how to run the sign-off, and how to choose a system.

What is policy acknowledgement?
The four elements a valid acknowledgement needs, the levels from a click to a signature, and when to ask again.
Read more
Read receipt vs policy acknowledgement
Why read receipts, open tracking and view logs fall short as evidence, and what a confirmation records instead.
Read more
Best practices for employee sign-off
Ten practices people complete and auditors accept: targeting, deadlines, reminders, quizzes, signatures, records.
Read more
Policy acknowledgement software
What it does, how it differs from SharePoint, Excel, HR systems and e-signature, and what to ask before choosing.
Read moreCompared with what you use today
Most organizations already keep policies somewhere and ask people to read them somehow. These pages say where each approach stops, and what is added on top.
SharePoint vs Policy Confirm
Keep the policies in SharePoint. What a library does on its own, and what is added when Policy Confirm links to it.
Excel vs Policy Confirm
A spreadsheet can list who should confirm. It cannot ask them, chase them, or prove what they confirmed.
Policy Confirm vs HRIS acknowledgement modules
HR systems cover employees and one workflow. Versions, contractors and audit retrieval are where they stop.
All comparisons
E-signature tools and GRC platforms too, and why the real alternative is usually no process at all.
When someone asks for proof
The audit side: what counts as evidence, and what ISO 27001 and SOC 2 expect to see.
Audit proof
What auditors and customers accept as evidence that a policy was acknowledged, and what they do not.
ISO 27001 policy acknowledgement
Clause 7.3 awareness and clause 7.5 documented information, and what an auditor asks to see.
SOC 2 policy acknowledgement
How the Trust Services Criteria treat communication of policies and retention of evidence.
Frequently asked questions
What is policy acknowledgement?
Policy acknowledgement is a named person confirming that they have read a specific version of a policy, at a recorded time, in a way that can be shown to someone else later. It needs the policy at a version, an identified person, an explicit action by that person, and a record that cannot be edited.
Why do organizations need policy acknowledgement?
So that people know the policies that apply to them, and so the organization can show it. Auditors for ISO 27001 and SOC 2, customers in supplier questionnaires and regulators ask for evidence that staff were made aware of the policies.
What is the difference between policy acknowledgement and an e-signature?
An e-signature signs one document once. Policy acknowledgement tracks many people against many policies and their versions over time, with rounds, deadlines and reminders. A signature can be part of an acknowledgement where one is required.
How do you prove employees have read a policy?
With a record of an explicit confirmation by each identified person against the version they read, with the time. A read receipt or a file view log shows delivery, not confirmation.
Policy acknowledgement that fits how you work
Your groups, your rhythm, your documents where they are. And for every confirmation, a record you can hand over.