Roll out a policy and prove everyone signed it
Policy rollouts end with 'please confirm by reply' and a compliance spreadsheet assembled by hand. At audit time, three confirmations are missing and one is from someone who left.
The short way: The policy, a comprehension check, and a drawn signature in one flow per person — with the not-yet-signed list updating itself until it reaches zero.
Type this — that’s your first draft
“A policy acknowledgment for our updated security policy: key points summary, confirm understanding, one comprehension question, sign”
Build it now — freeFree to start. The Pro plan adds reminder automation. Compare plans
No setup, no tutorial. The words above go with you — review what the AI builds, then share the link.
How it works — three steps
- 1
Paste the policy summary; the AI adds acknowledgment and a comprehension check.
- 2
Invite all staff by personal links; reminders run automatically.
- 3
The compliance register is the invited-vs-signed view — export it for the file.
What’s doing the work
Signature questions
Drawn-signature acknowledgment, timestamped per person.
Assess comprehension
A scored question shows the policy was read, not just clicked through.
Reminder automationPro
The rollout chases the people who have not signed yet.
Questions people ask
Can we attach the full policy document?
Link it in a descriptive block, or paste key sections directly into the flow so acknowledgment follows exposure on the same page.
New joiners after the rollout?
The link lives on — add it to onboarding, and the register keeps growing with each cohort.