Compliance
How to track staff policy reading and follow up on acknowledgements
Track who was assigned a policy, which version they confirmed and who needs follow-up. Then add the right support for understanding and everyday use.
To track staff policy reading, record which policy version each person was assigned, collect an explicit acknowledgement and keep an up-to-date view of outstanding responses. Use questions or learning activities where you also need to check understanding.
Be precise about what the record tells you. A file view shows activity. An acknowledgement records a person's confirmation. Neither proves that every sentence was read or that the policy will always be followed.
1. Define the audience before sending
Start with who needs the policy for their work. A rule may apply to everyone, a department, a location, a role or another group you define.
Give someone responsibility for keeping that audience current. A person who never received the policy will not appear on a list of unanswered requests, so check for missing assignments as well as missing responses.
Your initial register can be simple: person, group, policy, version, assignment date, deadline and current status. If you are starting manually, the policy acknowledgement tracker gives you a place to organise the work.
2. Send a clear request tied to a version
Tell people what to read, why it matters, what action to take, when to complete it and where to ask a question. Use a specific version so that the record remains meaningful after the document changes.
Make sure the person can actually open the policy, including any file held in SharePoint or another internal system. A reminder cannot solve an access problem.
The request and reminder email templates can help you put those details into a message.
3. Keep status useful for follow-up
A list of confirmations is only part of the picture. You also need to know which assigned people are still waiting and why.
Illustrative follow-up view, not a product screenshot:
| Situation | What to do next |
|---|---|
| Confirmed the assigned version | Keep the response with its version and timestamp |
| Assigned, still within the deadline | Leave the request visible and follow your reminder schedule |
| Past the deadline | Check access, availability and questions before escalating |
| Joined after the first distribution | Add them to the appropriate workflow with a suitable deadline |
| Policy no longer applies | Document the correction or exception without inventing a confirmation |
This avoids treating every outstanding response as unwillingness to comply. People may be on leave, unable to open the document or waiting for clarification.
4. Design for new hires and team changes
Decide how people enter and leave the process. You might send manually during onboarding, include new group members in a running cycle or use a recurring schedule.
Policy Confirm supports these different approaches. With the relevant settings enabled, new group members can join active cycles, and follow-up can be delegated to supervisors. These are choices the organisation configures, rather than a universal annual-signing rule. The onboarding distribution guide covers this workflow in more detail.
5. Check understanding where it matters
For a straightforward update, a clear explanation and an acknowledgement may be enough for your chosen process. A more difficult rule may benefit from a scenario: “What would you do if a customer sent personal information to the wrong address?”
Policy Confirm's policy questions can sit before confirmation. Its optional paid Learning add-on offers short interactive courses completed alongside policies. These provide additional learning activities and records; completing them is not a guarantee of understanding or behaviour.
Choose the method for the policy and the people. Do not add a quiz to every document merely to make the record look more substantial.
6. Keep the policies available after the email
People often need a policy weeks after acknowledging it. Give them a dependable place to return to the applicable documents, outstanding requests and contact details.
The employee policy portal is one way to provide that access. For organisations using the optional Policy Intelligence add-on, employees can also ask questions answered from selected, uploaded policy documents, with sources to check. Unclear or consequential questions still need the responsible person's attention.
Test the whole process with a small group
Choose one policy and test three situations: a normal confirmation, a missed deadline and a new person joining. Then retrieve one person's record and the outstanding list for that policy.
Whether you use a spreadsheet, a configured Microsoft 365 workflow or dedicated software, the useful test is the same: can you see who needs to act, help them complete it and explain the resulting record?
Try the follow-up process with your own policy.
Send to a small group, check what recipients see and follow the outstanding responses. Policy Confirm is free for up to 10 recipients, with no credit card required.