Loading page
All-in-one HR platform · v2.0
14-day free trial · No credit cardhello@HrMagix.com
All-in-one HR platform · v2.0
14-day free trial · No credit cardhello@HrMagix.com
A policy that nobody can show was received is a weak policy. When a disciplinary case turns on whether an employee knew the rule, the first question is usually: what proof is there that they were told? An email sent to a distribution list two years ago is not much of an answer.
Acknowledgement is the record that a specific person received a specific version of a specific policy on a specific date. This guide covers how to issue policies so that record exists for everyone, including the people who join after the launch.
01
An acknowledgement means nothing unless you can say which text was acknowledged. Give each policy a version number and an effective date, and keep every superseded version rather than overwriting it.
When a policy changes significantly, issue the new version and collect a fresh acknowledgement. A typo correction does not need one; a change to a rule, an entitlement or a consequence does.
Watch for itChanges to terms of employment, as opposed to workplace rules, may need more than acknowledgement, and in some establishments standing orders have their own certification procedure. Take advice before treating a policy update as a change to contract terms.
02
A policy should live in one place that every employee can open at any time, not only in the email that announced it. If people cannot find the current version, they will rely on what a colleague remembers.
HRMagix keeps company policies in one list (All Policies) that employees can open in the app. Whatever tool you use, the test is the same: can an employee find the current version in under a minute without asking HR?
03
The acknowledgement statement should be short and specific. It names the policy and the version, and says the employee has received it, read it, and had the chance to ask questions. It should not pretend to be a contract.
04
Set a window for acknowledgement, a couple of weeks is typical, and decide in advance who follows up with people who have not responded. Managers are usually better at this than HR, because they can ask in person.
Run a list of outstanding acknowledgements at the deadline. Long leave, field staff without regular access to a device and people who have resigned will show up here. For workers without devices, a supervised sign-off on paper, later recorded in the system, is a legitimate route.
05
The launch is the easy part. The record breaks when people join afterwards and nobody asks them to acknowledge the policies that were issued before they arrived.
Make the core set, code of conduct, harassment, leave, attendance, data handling, part of the joining checklist, so a new joiner's acknowledgements are complete before their first month ends.
06
The question you will be asked is narrow: did this person acknowledge this policy, which version, and when. You should be able to answer that in minutes, for any employee, including those who have left.
Keep acknowledgements for at least as long as you keep the rest of the employee file. Check the retention period your advisers recommend, since claims can arise after someone leaves.
Every guide ends here rather than in a summary. If a line below is not true yet, that is the next thing to do.
It shows the email was opened, not that the policy was read or which version was attached. A recorded acknowledgement against a named version is a much stronger record.
For material changes to a rule, entitlement or consequence, yes. Minor corrections to wording or formatting usually do not need one, but keep the new version on record.
Record that the policy was issued to them, when and how, and that they declined to acknowledge it. Ask what their concern is. If the policy affects terms of employment, take advice before proceeding.
Brief them in person, in a language they understand, and take a signed acknowledgement on paper. Then record it against their employee record so the evidence is in one place.
The checklist above is generic by necessity. Bring your own structures, states and rota and we will tell you which lines are already true and which are not.
14-day free trial · Full access to all 12 modules · Zero implementation fee · Cancel anytime