Skip to content
Free Employee Handbook Template

Guide, 10 Nov 2026, read 10 Nov 2026

A policy is acknowledged when the rollout is short, dated, personal and followed up

See the rankingAll guides

Decide what needs an acknowledgement

Not every update needs one. Ask people to confirm the handbook at hire, and again for a policy where a breach could lead to discipline or a legal claim: conduct, harassment, acceptable use, data privacy, time off and any new rule that changes pay or hours. Typo fixes and link updates do not need a new confirmation.

An acknowledgement shows that the employee received the rule. It is not agreement to waive any right, and the wording should say so by saying only what it does: that they received and read this version.

Write a change note people will read

The announcement is where most rollouts fail. Keep it to a short message that says what changed, who it affects, when it starts and what to do. Put the change in the first two lines. Link to the full policy and mark the changed paragraph.

For a UK change that affects contract terms, give notice in line with the contract. Where a change is to the written statement of employment particulars, the employer should tell the employee in writing.

  • What changed, in one sentence.
  • Who it affects and from which date.
  • What you need them to do, and by when.
  • Where to ask a question.
  • A link to the previous version for comparison.

Capture the acknowledgement properly

Record the person, the policy, the version, the date and time and the method. An electronic confirmation works: in the UK, the Electronic Communications Act 2000 allows electronic signatures to be admitted in evidence. Tie the record to the version number, not the policy title, so you can show which text the person saw.

Do not collect acknowledgements in an email inbox. A shared inbox or spreadsheet cannot be searched by version, and the person who ran it will leave.

Chase the gaps without nagging

Set a date, usually two to three weeks. Send one reminder to individuals, then give managers a list of people on their team who have not responded. Escalate to the department head only after a second miss. Track the completion rate and send the number to leadership, since a 96 percent rate at day 21 is normal and 60 percent is a sign the message was unclear.

Treat people on leave as a separate group. They should have the chance to read the update on return, and the acknowledgement date is theirs, not the group's.

Keep the record

Keep the acknowledgement for as long as the employee's file is kept, and keep every version. US federal regulations require personnel records to be kept for one year, and many employers keep them for the life of the employment plus a set period. When a dispute arises, the record shows what was communicated and when.

Review the process once a year: how long it took, who did not respond and why, and whether any policy was acknowledged but still broken.

A worked example

Take a new remote work policy. Week one: announce it with a four-line note and a link, and open a short question session for managers. Week two: send the acknowledgement request with the version number and a due date three weeks out. Week three: send a single reminder to those who have not responded. Week four: give managers a list of the gaps and close the campaign with a report of the completion rate and the questions raised.

The questions raised are as valuable as the signatures. They show which sentence in the policy was unclear, and they feed the next version.

Sources

  1. Electronic Communications Act 2000, section 7, legislation.gov.uk, read 10 Nov 2026
  2. Recordkeeping requirements, EEOC, read 10 Nov 2026
  3. Employment contracts, GOV.UK, read 10 Nov 2026
  4. Acas Code of Practice on disciplinary and grievance procedures, read 10 Nov 2026

Last reviewed 10 Nov 2026.