> ## 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.

# Understand completion statuses

> Distinguish document completion, person status, request activity, and delivery status so you know what to do next.

ClearPolicy's compliance views track whether people have completed their assigned documents on the current published version and whether renewal is due. They do not measure legal compliance or whether people follow a policy in practice.

## What compliance metrics mean

Only the people and required documents you track in ClearPolicy contribute to these views. Documents **Available to read** do not require a signature and do not record opening activity.

Online signatures and paper on file both count as completion for the relevant revision. Historical acknowledgments remain part of the record.

## Compliance statuses

Document status answers: **What does this person need to do for this document now?**

| Status | Meaning | Next step |
| - | - | - |
| **Signed** or **Acknowledged** | Completed on the current revision and not due for renewal. | No new signature needed. Download the record if needed. |
| **Pending signature** | A request for the current revision is open. | Send a reminder or resolve delivery problems. |
| **Outdated** | The latest completion covers an older revision. | Send the current revision. |
| **Renewal due** | The renewal interval has passed since completion. | Send another request, or use Auto-renew. |
| **Unrequested** | No current completion or pending request satisfies the assignment. | Publish if needed, then send a request. |

A completed request stays completed even when its document becomes outdated or due for renewal. These are different views of the same history.

## Person statuses

Person status summarizes current assignments:

| Status | Meaning |
| - | - |
| **Compliant** | All current assignments are complete and current. |
| **Pending** | At least one assignment has an open request, with no unrequested, outdated, or renewal-due assignment taking priority. |
| **Needs Attention** | At least one assignment is unrequested, outdated, or renewal due. Other requests may also be pending. |
| **Not Started** | No current document assignments contribute to the person's status. |

Open the person's **Documents** tab to see the underlying document statuses rather than relying only on the summary.

## Request and delivery statuses

A request's status describes its own lifecycle: sent, viewed, completed, canceled, or expired. A new revision does not rewrite that request's history.

Email delivery is separate. **Bounced**, **Delivery failed**, and **Complained** flag requests that need delivery follow-up. “Sent” does not guarantee inbox delivery, and “Viewed” does not mean signed.

See [manage requests](/guides/manage-requests) and [delivery failures](/guides/delivery-failures).

## Compliance progress indicators

Documents show completion among their assigned people. People show completion among their assigned documents. Group views use that group's scope.

Progress bars are red below 50%, yellow from 50% to 79%, and green from 80%. A green bar can still include unfinished work; read the count or percentage.

The dashboard's person-based completion score and a document's signature count measure different things.

## Per-document compliance view

Use **Documents → Compliance** to find people who need a particular document. See [track completion](/guides/track-compliance#document-compliance-view).

## Per-person compliance view

Use **People → Documents** to review a person's current and previous assignments. See [person details](/guides/track-compliance#person-detail-view).

## Activity history

Open **Activity** on a request for its timeline. The organization-wide [Activity page](/guides/activity-feed) provides a broader history.

## Downloading receipts and audit trails

Use [download records](/guides/download-records) for electronic certificates, paper evidence, and printed timelines.

<h2 id="automatic-renewal-when-a-revision-is-published">
  After publishing a revision
</h2>

Publishing a new revision makes earlier completions outdated for current-version tracking. It does not send replacement requests or cancel pending ones by itself. See [update a document](/guides/update-document).

Scheduled renewal is a separate setting. Use [recurring renewals](/guides/renewals) when people should sign again after an interval even without a content change.

## Compliance is scoped to your organization

Completion views reflect your selected organization. Group Managers see their assigned groups; owners and administrators can review organization-wide results.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.