US Employee Handbook
Distribute HR handbook policies (at-will, anti-harassment, PTO, code of conduct) to employees and capture an e-signed acknowledgment with a full evidentiary audit trail, automatic re-attestation on new policy versions, reminders, overdue flagging and a compliance completion report.
Distribute HR handbook policies (at-will, anti-harassment, PTO, code of conduct) to employees and capture an e-signed acknowledgment with a full evidentiary audit trail, automatic re-attestation on new policy versions, reminders, overdue flagging and a compliance completion report.
Key Features
Author a policy with a title, free-form rich-text
Author a policy with a title, free-form rich-text body and/or a file attachment, an effective date and a policy type (at-will, anti-harassment, PTO, code of conduct, safety, ...).
Each policy carries a version number
Publishing a brand-new version automatically supersedes the prior one and copies forward its targeting.
Choose whether a policy requires annual (or custom
Choose whether a policy requires annual (or custom interval) re-attestation so acknowledgments expire and re-open on schedule.
Target everyone, a set of departments, specific job
Target everyone, a set of departments, specific job positions, or employees in selected US states / jurisdictions -- or hand-pick individual employees.
One click fans the assignment out into one
One click fans the assignment out into one outstanding attestation task per matching employee, with a due date derived from the policy effective date plus a configurable grace period. Re-running the fan-out is idempotent: existing open task
The employee (or an HR user on their
The employee (or an HR user on their behalf via the portal/back-office) signs by typing their full legal name; the system records the signed timestamp, the typed-name signature, and -- for evidentiary value -- the IP address and user agent
A signature is always bound to the exact
A signature is always bound to the exact policy version, so when a newer version is published the old acknowledgment no longer counts and a fresh task is opened automatically.
A scheduled job flags outstanding tasks as overdue
A scheduled job flags outstanding tasks as overdue once past due and flags previously-signed tasks as expired when their re-attestation interval elapses, re-opening them.
Send reminder emails for everything still outstanding, or
Send reminder emails for everything still outstanding, or target the overdue subset, straight from the policy or from a manager dashboard.
Live completion percentage per policy version
assigned, signed, outstanding and overdue counts.
A drill-down of exactly who signed which version,
A drill-down of exactly who signed which version, when, and from where, and a filterable outstanding list for follow-up.
Screenshots
Assignments
Jurisdictions
Attestations
Send Reminders
Outstanding Acknowledgments
Policies
Jurisdictions
Send Reminders
Compliance Report
Why Choose This Module
Why it matters "At-will employment", anti-harassment, PTO, code of conduct, social-media, remote-work and safety policies are only enforceable if you can show the employee actually received and acknowledged them. A signed acknowledgment with a timestamp, the exact policy version, and evidentiary metadata (IP address and user agent at the moment of signing) is what stands up when a policy is later disputed.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: English
- Author: Pokutsoft
- Dependencies: hr, mail
- Support: support@pokutsoft.com
Update date: 2026-07-02
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) |
| Lines of code | 1852 |
| Technical Name |
us_employee_handbook_acknowledgment_policy_att |
| License | OPL-1 |
| Website | https://pokutsoft.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module