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. When you need to work through unfinished requests one by one, use the organization-wide Requests page. It brings together the active document requests that still need follow-up.

​
What compliance metrics mean

In ClearPolicy, compliance means completion of assigned document requests (policy acknowledgments captured with electronic signature) on the current published version of each document — not whether someone is legally compliant or following your policies in practice. Dashboard scores, progress bars, and status badges reflect administrative sign-off tracking inside your organization account. They do not account for:
  • People who are not added to ClearPolicy
  • Policies or documents you have not uploaded and assigned
  • Whether someone read, understood, or is behaving according to the policy after signing
Use these metrics to see who still needs to complete a request and to maintain audit-ready acknowledgment records.

​
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.
These indicators update automatically as people complete requests or as you publish new revisions. For more details on how to use them, see track compliance.

​
Per-document compliance view

Opening a document takes you to the Compliance tab by default. It shows the completion status for every assigned person. 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.
If there is no published revision yet, Compliance prompts you to publish first (use the Revisions tab). Use Add People to assign people to the document without sending a request. You can filter the list by compliance status and search by name or email. When the document is assigned to groups (configured in Settings, via the gear in the header), a Groups filter also appears so you can narrow results to a team or department without leaving the document. From this view you can take action directly — send missing requests, send reminders, or review individual activity — without leaving the document.

​
Per-person compliance view

Open a person from People to land on their Documents tab. The header shows their name and groups; use the gear for email, phone, and other settings.
  • Documents — lists every document assigned to the person with its status, completion date, and quick actions to send requests, nudge reminders, or view activity. Switch between currently and previously assigned documents, print a compliance report, or add documents.
  • Requests — every request sent to the person, including status, timing, and delivery follow-up when an email failed.
These views are useful when a person 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 open this timeline from Requests, from a document’s compliance view, or from a person’s request history. You can view and print this timeline for audit purposes.

​
Downloading receipts and audit trails

For each attestation completed online, 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.
  • An electronic certificate of attestation.
For completions recorded as paper on file, choose Download uploaded file instead. That file is the signed paper copy your team uploaded. Paper completions do not include an electronic certificate. See paper on file. ClearPolicy digitally signs electronic certificate PDFs before download. A valid signature helps confirm that the PDF was issued by ClearPolicy and has not been changed after it was sealed. This seal is separate from the person’s electronic signature on the attestation record. Some PDF readers may show ClearPolicy’s signing certificate as self-issued or not trusted by a public certificate authority; that alone does not mean the file was altered. For more detail, see Security. You can also print the full activity timeline for a request, which provides an end-to-end record suitable for audits or internal review. To keep printed timelines concise, consecutive “viewed” events that occur within ten minutes of each other are grouped into a single line showing the total number of views — for example, “Viewed (3 times).”

​
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 — people, 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 August 7, 2026