Publish a policy, and know who has signed it.
Upload a policy, mark whether it needs signing, and see who has signed which version. Every acknowledgement is saved with the person's name, signature, the time and where it was signed from.
Upload it, mark that it needs acknowledging, and everyone who has not signed sees it waiting on their own record. Each signature records who, when and from where.
The policy screen
Every policy, and how many people have signed it.
Policies are grouped by category, each showing its current version and whether it needs a signature. Open one to see who has signed it and who has not.
Every signature records the person, the time and the address it came from.
Every signature is recorded.
Publish a policy, and decide whether it needs signing.
Group policies into categories so they stay easy to find as the list grows.
- Upload a document, or link to one you host
- Put it in a category and give it a version
- Mark whether it needs a signature
- Set a review date so you revisit it before it goes out of date
- Keep the previous version and its signatures
Access
Who can do what.
Everyone can read the policies that apply to them and sign the ones that need it. Publishing a new version and chasing signatures are kept to the people who own the policy.
Read the policies that apply to you.
Sign a policy and keep proof that you did.
Publish policies and chase outstanding signatures.
Set review dates and retire a policy.
Admin is the highest role and can do everything, so give it only to the small group of people who really need it.
One policy, start to finish
Published on Monday, forty-four signatures by Friday.
The policy went out to everyone it applied to and appeared on each person's own record. Every signature came back with a name and a time against it, and the three people who had not signed were shown by name.
Uploaded, filed under a category and marked as needing a signature.