Send a policy to the right people, watch the confirmations come in, and keep a version-linked record of who acknowledged what. When somebody asks for it later, it is already there.
In some organizations one person owns this alongside four other jobs. In others it is a compliance function answering for every site and every framework. What comes out is the same record.
Policies and their versions live in one place, not in a folder, an email thread and somebody's memory. Every send is tied to one version and one recipient list, so there is never a question about which document a person was given.
Each person makes an explicit acknowledgement of their own, tied to them and to the version they were sent. Groups pick up the right people automatically, so you are not keeping a list of who still owes you a reply.
Every confirmation is timestamped and locked to the version that was current when it was made. When a customer, head office or an auditor asks, the evidence is assembled already and nothing has to be reconstructed.
Upload the PDF and pick who gets it, by department, location or role. The upload creates a version-linked record, so every confirmation that follows points at this exact document.
Everyone gets a secure personal link by email. They open the policy, read it and confirm. No account, no password, nothing to install, which is what keeps completion rates up among people who do not live in software.
Watch who has confirmed and who has not, as it happens. When you need to hand the evidence over, export a PDF certificate or a CSV log with the timestamps, versions and individual actions already in it.
Turn passive distribution into verified acknowledgement. Full control for administrators, direct access for recipients.
Coverage stays complete without anyone chasing it. New joiners are picked up automatically, and policies come back round on the schedule you set, so nothing lapses quietly.
Import recipients in bulk from CSV, Excel or Active Directory sync (Microsoft Entra ID), then group them by role, department or location-based policy targeting. When new employees join a group, they inherit all active policies automatically, with no manual admin work.
Every policy is versioned explicitly. When a document changes, you decide whether to start a new confirmation round or update the file for recordkeeping only. Each version is locked at dispatch and fully traceable.
Group policies into a single, controlled confirmation cycle across teams and departments. Confirmations stay synchronized, deadlines aligned, and proofs unified.
Handle exceptions without stalling progress. Decide whether to extend deadlines or finalize cycles as-is, while keeping confirmations consistent and cycles under control.
Recipients confirm policies via a secure, personal link. No accounts or passwords are required, while every confirmation remains uniquely identified and timestamped.
Add your own logo, message, and color to everything recipients see, from the first request to the moment they confirm.
Sign in using an existing Microsoft work account. No separate credentials required for administrators or recipients.
Assign supervisors to recipient groups and let them follow up with their own teams. Outstanding confirmations are handled close to the people who owe them, not by one central admin.
Add questions to a policy and every recipient has to answer them before they can confirm. Set once, enforced for everyone.
If preferred, require recipients to draw their signature before confirming policies. An optional add-on for use cases where a more formal acknowledgement is needed.
Formal PDF certificates and detailed CSV logs, with timestamped records for every single recipient.
All events, including uploads, version changes, dispatches, confirmations, and closures, are logged. Nothing is implicit. Nothing is lost.
Set how long confirmation records are kept for inactive recipients. Records are automatically deleted when the retention period expires, supporting GDPR and industry compliance requirements.
A secure personal link takes each recipient straight to the policies assigned to them. Nothing to sign up for, nothing to remember, nothing to install. That is why the people who are hardest to chase still confirm.
Two formats, both produced the moment you ask for them. A certificate when someone needs one document showing the policy was confirmed, and a CSV log when they want to work through every recipient, version and timestamp themselves.
Click to switch format
From evaluation to organization-wide rollout.
Priced by how many people you send to, so a team of forty is not paying for a platform built for four thousand.
Test and evaluate the system
Everything you need to run policy confirmations and produce proof.
For organizations that require delegated governance, multiple entities, or tailored compliance workflows.
Clear answers about acknowledgements, confirmations, and the records they leave behind.
Guides, templates, and best practices for policy management and compliance.
How to automate policy distribution when onboarding new employees
New hires should receive their policies because they were hired, not because someone remembered. Here is how to wire policy distribution to the moment an account is created, and what the record looks like afterwards.
Read more: How to automate policy distribution when onboarding new employeesEssential IT policies: the documents to have, and how to prove they were read
A working set of IT policies is smaller than most templates suggest. This is the list, what each document has to cover, who has to acknowledge it, and what the evidence looks like afterwards.
Read more: Essential IT policies: the documents to have, and how to prove they were readSecond July release: Your message, your logo, your colors
Recipient emails and confirmation pages can now carry your message, logo, and brand color, while the acknowledgement record and audit trail stay unchanged.
Read more: Second July release: Your message, your logo, your colorsThe UK Cyber Security and Resilience Bill: what organizations must be able to document
The UK Cyber Security and Resilience Bill expands regulatory scope and enforcement powers. Here is what in-scope organizations, and their suppliers, need to be able to document about security governance and policy awareness.
Read more: The UK Cyber Security and Resilience Bill: what organizations must be able to documentJune 2026 release: Microsoft sign-in, cycle insights, and bulk editing
A detailed look at what shipped in Policy Confirm during June 2026: Microsoft sign-in for administrators, a per-policy breakdown at cycle creation, typed eSign signatures, bulk editing for recipients and groups, Excel export for cycles, a recipient details view, and a new support page.
Read more: June 2026 release: Microsoft sign-in, cycle insights, and bulk editingAcknowledgement vs comprehension: when to add a quiz to a policy
An acknowledgement proves someone confirmed they read a policy. It does not prove they understood it. Quiz questions close that gap, but only some policies need them.
Read more: Acknowledgement vs comprehension: when to add a quiz to a policyFor a demo or specific questions about your compliance requirements, get in touch at: