Skip to main content
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.

​
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.
This view lets you take action directly — send missing requests, send reminders, or review individual activity — without leaving the document.

​
Per-person compliance view

The requests tab on each contact’s profile shows the full picture from their perspective: every document they have been sent a request for, the status of each request, and when they completed or last interacted with it. This is useful when a contact reaches out with a question, or when you need to confirm that a specific person has completed all required documents.

​
Compliance statuses

ClearPolicy tracks the following statuses for each person–document combination:
A request has been sent but the person has not yet completed it. The request may be in a sent or viewed state.
The person has attested to the current, published revision of the document. No action is needed.
The person attested to a previous revision. A newer revision has since been published, so their completion no longer reflects the latest content.
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.
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.
You can also print the full activity timeline for a request, which provides an end-to-end record suitable for audits or internal review.

​
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.
After publishing an update, use the document compliance view to send missing requests to everyone who needs to re-attest. You can send to all people without a current completion in a single action.

​
Compliance is scoped to your organization

All compliance data — contacts, documents, requests, and attestation records — is scoped to your organization. Other organizations cannot see your data, and your team members only see records within your organization’s account.
Last modified on April 12, 2026