Writing a policy is the easy half. The auditor’s question is the other half: show me that the people it applies to have read the current version. A PDF on a shared drive cannot answer that.
Policies as controlled documents
- Each policy has a number under your own scheme, an owner and an approval.
- Each change creates a new version. Earlier versions are kept.
- The current version is the one staff see.
Sign-off, per person, per version
An employee opens the policy, reads it and signs. The sign-off is recorded against that person and that version, with the date. When a new version is issued, the earlier sign-off no longer counts for it and the policy returns to the person’s list.
What a manager sees
- Which policies are outstanding, and for whom.
- Who has signed each policy, and when.
- A list that can be shown to an auditor as it stands.
New joiners
Policies to sign are part of induction. A joiner’s first-day list already contains them, alongside their induction training.
Sharing outside the company
A customer’s security team or an auditor sometimes needs to read a policy without having an account. A policy can be shared through a link for that purpose.
Where it connects
| Connected to | How |
|---|---|
| HR | The list of who must sign comes from the employee record |
| Training | Policies and induction training are assigned together |
| Compliance | Sign-offs count as evidence for the control that requires the policy |
| Audits | The auditor samples sign-offs straight from the record |
- What happens to sign-offs when a policy changes?
- A new version needs a new sign-off. The earlier one stays on record against the earlier version.
- Can an auditor see who has signed?
- Yes. The sign-off list is the evidence.
- Can someone outside the company read a policy?
- Yes, through a share link.