Policy Acknowledgement Needs a Completion Percentage, Not an Email Trail

Sending a policy round by email creates the appearance of distribution. It's a much weaker stand-in for evidence of receipt. When an inspector or an internal review later asks who has seen the current version, an email send log rarely answers the question with any confidence.

A policy library that tracks acknowledgement per person, per version, turns distribution into something that can actually be checked and defended.

Policies change, and a staff member who acknowledged version one has said nothing about version two. Without version-aware tracking, an organisation can end up relying on stale acknowledgements to answer a current-state question.

Each new published version should reset the acknowledgement expectation, so the completion percentage always reflects agreement with what is actually in force today rather than with whatever was current when someone last read it.

A policy that is no longer in force still has evidentiary value. It shows what staff were expected to follow at a given point in time, and that matters if an incident is later reviewed against historic practice. Deleting it destroys that context.

Archiving instead of deleting keeps the acknowledgement history intact while making clear the policy is no longer active, which is the more defensible position if the record is ever examined retrospectively.