- POLICY ACKNOWLEDGMENT & ATTESTATION
Proof that the right people read the right version
A verbal “I read it” won't survive an audit & last year's sign-off is not this year's policy
Read receipts prove nothing
Email receipts prove delivery, not that anyone agreed.
Spreadsheets go stale
The who-signed-what sheet is out of date the day a policy changes.
Versions drift apart
The version signed last year may be nothing like the one live now.
Stragglers never close
Completion stalls short of the full list and nobody chases the rest.
- Capabilities
Sign-Off That's Bound To A Version, And Refreshes Itself.
Version-bound acknowledgment
Every sign-off is tied to the exact version it was made against. The record stores the attestation statement the person saw, their email identity, and the timestamp.
Re-acknowledgment on every change
Change the policy and everyone is asked to sign again, even for a one-word edit. Yesterday's sign-off never passes for today's.
Targeted assignment
Send each policy to the people it applies to, by the tags you define: location, department, anything. Not the whole company by default.
Reminders & completion
Track who's done and who's outstanding. Automatic reminders chase the stragglers on a cadence, and owners can re-nudge anyone by hand.
- Proof
The proof is gathered as you go
Every acknowledgment is a record, not a tick. Completion, per-person history, the statement they saw, and a scoped export - assembled as sign-offs come in, not the week before the audit.
01
Completion dashboard
Live completion and outstanding lists across every policy & audience.
02
Per-person record
One record per person and version, with the attestation text stored on it.
03
Identity and timestamp
Email identity and time of sign-off held on the record.
04
Scoped export
Tamper-evident PDF or CSV, scoped to the audience asked about.
05
Permanent records
Completed acknowledgments survive the person's account being deleted.
- Fit
For Every Policy Someone Has To Attest They Read
Wherever a sign-off has to be produced on demand - and tied to the version that was actually in force at the time.
BUILT FOR:
Annual attestations
Yearly policy sign-off across the whole company.
Code of conduct
Conduct sign-off at onboarding and on every revision.
Security policies
Acceptable use, access, and data handling, by team.
One-off campaigns
A single attestation push on one document, tracked to done
- FAQS
Frequently asked questions
What's the difference between a notification and an acknowledgment?
A notification tells people something changed. An acknowledgment records that they read and agreed, tied to a version, with the statement they saw stored on the record.
Can I prove who acknowledged which version?
Yes. Every record is bound to a specific version, with identity and timestamp, and exports as tamper-evident PDF or CSV.
What about people who never sign?
The dashboard shows outstanding sign-offs, automatic reminders keep going out, and owners can re-nudge anyone directly.
What happens when the policy changes?
Everyone it covers is asked to acknowledge the new version. Every change re-collects acknowledgment; there is no minor-edit exception.
Get Acknowledgments You Can Prove
Send, track, re-ask, and export — on one system.
30-day free trial · No credit card · Cancel anytime