Prove your staff read your policies.

Your policies are kept in one place, in their current version, rather than in a shared drive folder where the newest file is called FINAL v3 (actual).

Existing Word documents can be imported in bulk. The formatting mostly survives, and where it doesn't, the editor is simple.

Each policy is assigned to named people, not to "everyone", because "everyone" can't be asked a question later.

Each person reads the policy, answers any comprehension questions you've chosen to set, and signs.

Anyone who hasn't signed can be reminded with one button. Nobody enjoys chasing, but this makes it quicker.

When you update a policy, readers see exactly what changed, marked up like this like tracked changes.

Everyone who needs to signs the new version. Their signature on the old version stays on the record.

Every signature records who signed, which version, when, and a SHA-256 fingerprint of the exact text they were shown.

Once written, a signature record cannot be quietly edited afterwards, by anyone, including us.

If the text changes by so much as a comma, the fingerprint changes. There's a working one at the bottom of this page, made for you.

Any organisation that has to show a regulator, an auditor, a client's procurement team or an employment tribunal that a named person read a specific version of a specific document. That tends to mean firms without a compliance department, where the job lands on whoever is nearest.