Compliance tracking in ClearPolicy gives you a live picture of where each person stands on each document. Rather than digging through individual requests, you can see at a glance who has completed what, who is still pending, and who needs to re-attest because the document has been updated since they last responded.Documentation Index
Fetch the complete documentation index at: https://docs.clearpolicy.app/llms.txt
Use this file to discover all available pages before exploring further.
Compliance progress indicators
ClearPolicy shows compliance progress directly on your Documents and People lists so you can spot issues without opening individual records. Each document shows how many of its assigned people have completed the latest revision. Each person shows how many of their assigned documents they have completed. Both use a color-coded progress bar:- Red (below 50%) — needs immediate attention.
- Yellow (50%–79%) — making progress but not yet complete.
- Green (80% and above) — on track or fully compliant.
Per-document compliance view
The compliance tab on each document shows the completion status for every assigned contact. You can see:- How many people have attested to the latest revision.
- How many have an open request but have not yet completed it.
- How many attested to an older revision and are now outdated.
- How many have no request sent yet.
Per-person compliance view
Each contact’s profile has two views that help you understand their compliance:- Overview — shows a compliance gauge, document count, average response time, and the person’s contact details (email, phone, groups, and when they were added).
- Documents — lists every document assigned to the person with its status, completion date, and quick actions to send requests, nudge reminders, or view activity.
Compliance statuses
ClearPolicy tracks the following statuses for each person–document combination:Pending
Pending
A request has been sent but the person has not yet completed it. The request may be in a sent or viewed state.
Completed
Completed
The person has attested to the current, published revision of the document. No action is needed.
Outdated
Outdated
The person attested to a previous revision. A newer revision has since been published, so their completion no longer reflects the latest content.
Needs attention
Needs attention
Something requires your review — for example, a request that expired before the person completed it, or a combination of statuses that puts the person in an unclear state.
Unrequested
Unrequested
The person is assigned to the document but has never been sent a request.
Activity history
Every attestation request has an activity timeline that shows a chronological record of events: when the request was created, when it was sent, when the recipient viewed it, when they completed it, and any reminders that were sent along the way. You can view and print this timeline for audit purposes.Downloading receipts and audit trails
For each completed attestation, you can download a PDF receipt that includes:- The document content at the time of signing.
- The recipient’s name, email, and completion timestamp.
- The IP address and browser information recorded at signing.
- The typed signature name, for signature-type attestations.
Automatic renewal when a revision is published
When you publish a new revision of a document, all previous completions automatically become outdated. This is by design: the new revision reflects updated content, and you need to know who has seen the latest version.Publishing a new revision does not cancel or modify any existing open requests. Requests in flight continue to reference the revision they were sent for. Completions on those requests will be marked as outdated once they come in, because a newer revision now exists.