Policy acknowledgements: proving an employee read the current version

An employee is told their expense claim falls outside policy. They reply that they were never told that. Somebody goes looking and finds three versions of the travel policy — a PDF on the shared drive, an attachment circulated eighteen months ago, and the printed handbook new joiners are still handed.

Two of the three support the employee. Nobody can say which version was current when the expense was incurred, and nobody can show what the employee was given at joining. The argument is now unwinnable regardless of who is right.

Version control before acknowledgement

The instinct is to start collecting signatures. That is the wrong order — a signature against an uncontrolled document proves nothing, because you cannot establish what was signed.

1. 1

   Find every copy

   Shared drive, email attachments, the printed handbook, the induction pack, anything on a noticeboard. Most businesses find more copies than they expected, differing in ways nobody intended.

2. 2

   Declare one current version of each

   Pick or write it, mark it with a version number and an effective date, and archive the rest somewhere they cannot be mistaken for current.

3. 3

   Name an owner per policy

   One role responsible for the content being right and for reissuing it when it changes. A policy owned by everybody is owned by nobody and drifts within a year.

4. 4

   Then acknowledge

   Against a named version, with a date. Not "acknowledged the handbook" — "acknowledged Leave Policy v3, effective 1 April".

Which policies actually need acknowledgement

Not all of them. Acknowledging twenty policies at joining produces twenty unread documents and one meaningless signature, and it trains employees to click through anything you send.

ALWAYS
  Code of conduct
  Confidentiality and information security
  Anything with disciplinary consequences
  Anything the employee must act on (expenses, travel,
    claim deadlines)

ON CHANGE
  Leave and attendance rules
  Working hours and shift rules
  Any policy whose change affects entitlement

AVAILABLE, NOT ACKNOWLEDGED
  Everything else. Findable, current, but not requiring
  a signature nobody will read.

RECORD PER ACKNOWLEDGEMENT
  employee · policy · version · effective date · date
  acknowledged · how (system / signed form)

What makes the record hold up

Four things, and they are the same whether you use a system or paper.

• It names a version. Without this the record establishes nothing.
• The version is retrievable. You must be able to produce the actual document the employee acknowledged, as it was then, not the current one.
• The date is the date of acknowledgement, not the date somebody entered it.
• It survives the person who collected it. A signed form in an individual's folder is worth less than a register, because folders get reorganised.

A policy and document centre does all four by construction — one current version, the superseded ones retained, and acknowledgement recorded against the version rather than the document name. On paper it is achievable but requires discipline that usually decays within two years.

The change that catches people out

Reissuing on change is where most businesses fall down. A policy is revised, circulated by email, and the acknowledgement register still shows everyone against the old version. Six months later the register is worse than useless, because it looks complete.

Make reissue a defined step of changing a policy rather than a follow-up task: new version, effective date, notification, re-acknowledgement for the policies that require it. If the change is material, say what changed rather than only circulating the new document — an employee who reads "v4 attached" will not read v4.

At joining, and afterwards

Joining is the easy case and usually the only one handled: the new employee acknowledges the core set as part of the joining checklist, which is where it belongs as part of employee onboarding.

The harder case is everyone who joined before the current version existed. Do not try to reconstruct history. Draw a line, reissue the current set to everybody once, collect acknowledgements against the new versions, and start the register from that date. Attempting to establish what someone was given in 2021 produces an incomplete record and considerable effort.

Why this is worth doing before you need it

The value is entirely retrospective, which is why it keeps being postponed. Nobody needs the acknowledgement register until a disciplinary case, a dispute or a client audit, and at that point it cannot be created.

The work itself is small: one current version of each policy, an owner, and a register that names versions. It is the same discipline that produces one approved version of each letter format, and it usually gets done at the same time — which is why it tends to arrive as part of HR documentation work rather than on its own. If you would like to see acknowledgements tracked against versions rather than filed in folders, book a free demo of GullyHR software.

A register that fits on one screen

The output of all this is unglamorous: a table showing, for each policy, the current version, its effective date, the owner, and how many employees have acknowledged the current version. Five columns.

Read once a quarter, it tells you two things immediately. Which policies have drifted out of date — an owner who has not touched a policy in three years usually means it no longer describes how the business runs. And which acknowledgements are incomplete, which is almost always the group who joined between one version and the next.

Acknowledgement is not understanding, and saying so

A signature establishes that a document was presented. It does not establish that it was read, understood, or is capable of being followed, and businesses that treat the register as proof of the second thing are relying on something it does not support.

This matters most for the policies where it matters most. A code of conduct acknowledged by forty people in a batch, alongside eleven other documents on their first morning, has been acknowledged and not communicated. If it later needs to be relied on, the gap between those two is where the difficulty appears.

The practical response is to treat a small number of policies differently rather than to improve the register. For those, a short briefing with an opportunity to ask questions, recorded as having happened, is worth considerably more than a signature — and takes twenty minutes for a group.

Keep the acknowledgement record as well, because it is genuinely useful for establishing what was current and when. Just be clear internally about what it demonstrates. A business that believes its register proves comprehension will stop doing the things that actually produce it, which is the opposite of what the register was introduced for.

Decide which policies fall into that smaller group once, and write the list down. Left to judgement each time, it expands until everything is treated as routine again, which is precisely the drift the distinction was meant to prevent.

That second number is the one to act on, because it is the gap that will matter in a dispute. Chasing twelve outstanding acknowledgements takes an afternoon; discovering them during a disciplinary case costs considerably more. Holding the register against the versions themselves, rather than in a separate tracking sheet, is the practical reason a policy and document centre is worth more than a well-organised shared drive.