- WHAT THE EXAMINER ASKS FOR
Three Moments This Is Built For
The first day, the changed policy, and the moment proof is requested
- 01
The new hire's first day
Tag a new employee into their team and they inherit the whole reading list automatically, bundled with a deadline. Reminders chase; HR does not.
- 02
The mid-year policy change
The updated policy re-runs approval, goes back to everyone it covers, and the word-by-word compare makes re-acknowledging a two-minute job, not a reread.
- 03
The day someone asks for proof
A dispute, an audit, a lawyer's letter: the answer is an export. Who acknowledged which version, when, with the exact statement they agreed to.
- THE MACHINERY
What does the work
Onboarding, approval, acknowledgment, and signature—each on the right record.

Packaged guides carry day-one onboarding
Bundle the reading list in order, assign it by team, and set the deadline.

Approval workflows put named sign-off on every policy
Each decision, comment, person, and timestamp stays attached to the version.

Acknowledgment records bind people to exact versions
The record remains permanent and survives employee turnover.

NDAs and IP assignments run e-signature instead
Use your provider or AllyMatter’s built-in signing flow.

Editors pay; every employee who reads and signs is free
Headcount can grow without turning policy access into a per-person charge.
- FAQS
Frequently asked questions
What if an employee refuses to sign?
They can decline with a comment. The refusal and reason land on the record, so the conversation happens with context.
Isn't our HRIS enough for handbook signatures?
At onboarding, often yes. The gaps are mid-cycle: provable re-acknowledgment after changes, policies owned outside HR, records that outlive the tool.
We're multi-state. Can policies differ by location?
Yes. Tags scope policies by state, role, or team, with separate records for each.
- KEEP READING