Policy Acknowledgements: Proving Employees Saw the Handbook
A signed acknowledgement is only useful if it names the exact version, the date and the person. How to collect policy acknowledgements you can actually rely on later.
When a dispute turns on a policy, the first question is not what the policy says. It is whether this employee ever saw it, and which version. A folder of signed "I have read the handbook" slips rarely answers that, because the slips do not say which handbook. A useful acknowledgement proves three things: who acknowledged, what exact document they acknowledged, and when.
Version the policy before you ask anyone to sign
Every policy needs a version number or effective date printed on the document itself, not only in the file name. "Remote Working Policy v3, effective 1 March" is something you can point to. "Remote_policy_FINAL2.pdf" is not. Keep every superseded version too, even after it stops applying. If an employee signed v2 and the dispute concerns events under v2, you need v2, not today's text.
What the acknowledgement should say
Keep the wording short and specific:
- The policy title and version or effective date.
- A plain statement: "I have received and read this policy and understand that it applies to me."
- Where to ask questions, and that the policy may be updated with notice.
- The employee's name, signature and the date of signing.
Avoid bundling twenty policies into one signature. If the grievance policy changes, you want a fresh acknowledgement for that policy alone, not a re-signature of the whole handbook. One acknowledgement per policy version is more paperwork to collect and far less to argue about.
Paper, click-through or e-signature
Wet signatures work but are slow to collect and easy to lose. Click-through boxes on an intranet are fast, but only as good as the log behind them: if nobody can later show which account clicked, on which date, against which version, the record is thin. An electronic signature on the actual PDF is usually the strongest practical option, because the signed file carries the document text, the signer and the date together. Whether an electronic signature is sufficient for your purpose depends on local law; we summarised the general position in is an electronic signature legally binding.
In Herarx, the pattern is one case per employee file. HR sends the policy PDF for e-signature from that case's Files tab; the recipient verifies with a one-time email code, signs, and the signed PDF with its audit trail is stored back in the same case. The case timeline shows when it went out and when it came back.
Chase, then record the refusal
Some people never sign. Set a due date when you send the request and follow up once or twice. If someone still has not acknowledged, record that fact and the dates you asked. A documented refusal or non-response is itself evidence that the policy was provided, even without the signature. Do not quietly leave the gap unrecorded.
When policies change
- Publish the new version with a new effective date.
- Send it to everyone it applies to, with a short summary of what changed.
- Collect new acknowledgements against the new version.
- Keep the old version and the old acknowledgements; they still cover the old period.
How long to keep them
Acknowledgements belong in the employee's file and follow its retention period, which usually runs for some years after the person leaves; check your jurisdiction. We cover setting those periods in how long to keep HR records after an employee leaves. The policy versions themselves should be kept at least as long as any acknowledgement that refers to them.
