Policy acknowledgment tracker

Register

Who was asked to read which policy, which version it was, when it was due, and what they told you.

Superseded is not the same as done

When a new version replaces an old one, the old acknowledgment does not become false — it becomes an acknowledgment of a document nobody uses any more. That is why Superseded is a state rather than a deletion: the record of what somebody agreed to in March is exactly the record you would want in September, and a tracker that quietly overwrote it would destroy the only thing it was keeping.

It is not a signature, and it says so on the form

The words are on the field, not in a footnote: this captures no signature and is not one. If your rules require a signed acknowledgment, keep the signed copy where you keep signed copies and use this to know who still owes you one. Confusing the index for the evidence is the failure mode this tool is built to avoid.

Where the policies themselves live

This holds no documents. It records which one, which version and who said what. The training somebody owes goes on the training matrix, the documents you expect to have on file go on the document checklist, and what a new starter has to get through in week one is the onboarding checklist.

A record of what people told you. CompliMaint captures no signature and is not an electronic signature; it is not evidence that anybody read or understood anything; and it states no requirement that any policy be acknowledged, issued or retained. It gives no employment-law advice. Everything runs on your device.

Questions people ask

Does this capture a signature?
No, and it is important that you know that. There is no signature field, no signature pad and no electronic signature of any kind, and nothing here is one. What the record holds is a line you typed saying how somebody told you they had read a document — signed the paper copy, replied by email, said so in the Tuesday meeting. If you need a signature, you need whatever your own rules say a signature is.
Why does the version matter so much?
Because an acknowledgment without a version is an acknowledgment of nothing. People acknowledge a handbook in March, the handbook changes in June, and a record that says only handbook cannot tell you who has seen the current one. The version is the first field on the form for that reason, and Superseded is a state of its own so the old record survives when a new version replaces it.
Does it prove somebody read the policy?
No. It records that they said so. Nobody can prove a document was read, and a tool that implied it could would be the most confident lie in this product. What the record is good for is knowing who you asked, when, about which version, and who has not come back to you.
Does it tell me what policies I have to issue?
No, deliberately. There is no starter list of required policies and no acknowledgment interval, because what you must issue and what proof you must keep comes from your own rules, your regulator, your insurer and your advisors. A list presented as the required list would be wrong for most people who read it.