> ## 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. # Track who still needs to sign > Choose the person, document, or group view that answers your question, then act on the outstanding work. Start with the question you need to answer. Owners and administrators can use organization-wide views. Group Managers work inside their assigned groups. | Question | View | | - | - | | Which open requests need follow-up? | **Requests** | | Who still needs one document? | **Documents → Compliance** | | What does one person need? | **People → Documents** | | How is a department or team doing? | **Groups → People** or **Documents** | | What needs attention across the organization? | **Dashboard** | | How can I share the results? | **Reports** | ## Requests page Open **Requests** for unfinished requests. Search and filter, then send reminders, resolve delivery failures, or close requests no longer needed. See [manage requests](/guides/manage-requests). ## Document compliance view Open a signature-required document on **Compliance**. Filter by status or search for a person. Review who has completed the current revision, who has a pending request, and who needs a new request. Select a person to open the **Document compliance** side panel. When they have request history, you can switch between: * **Requests:** review each request, the version it covers, and its activity. Use the request's actions to send a reminder or download a completed record. * **Signed:** review the versions the person has completed, including paper on file. When a new request is needed, **Send request** appears near the top. You can send the latest version even if a request for an older version is pending. Sending the new request cancels the older pending request. See [update a document](/guides/update-document). If the document has no published revision, finish it under **Revisions** first. ### Add people **Add People** assigns people to the document. It does not email them unless **Also send a document request** is on. Use **Send request** when your goal is to email a signing link. ### Filter by group When the document belongs to groups, use **Groups** to narrow the completion view. You can combine this with status and search. ## Person detail view Open a person on **People**. **Documents** shows what they need; **Requests** shows what has been sent. **Settings** holds their details and groups. ### Documents tab The table shows each required document's status and **Next step**. Select a document to open **Document compliance** and review its requests and completed versions. For current assignments, you can also send a request or remind someone who still needs to sign. Open **Filters → Assignment history** to choose **Currently Assigned** or **Previously Assigned**. Previous assignments let you review history and download completed records. You can also filter by status. Use **Add Document** to assign an existing document, or **Print** for a single-person report. Assignment alone does not send a request unless you enable the send option. The **Available to read** section lists published documents accessible through the person's groups. Those documents do not require completion and have no opening record. See [reading access](/guides/read-documents). ### Requests tab Review request status, sending and reminder dates, and delivery problems. Open an individual request's activity when you need its full history. ## Group compliance view Open a group and choose **People** to check what one person still needs, or **Documents** to check who still needs one document. Selecting a row opens a side panel without leaving the group. ### Compliance on the group documents tab Under **Requires a signature**, select a published document to open **Group compliance**. Search for a person or filter by status to see who has signed and who still needs to sign. Use **Send missing** when it appears to send this document's missing requests to group members. Searching or filtering the list does not narrow that send. **View document** opens the document page for more detail. Documents under **Available to read** show how many group members can read them in the signing portal. Opening a document is not recorded. A document without a published version shows **Not published yet**. ### Compliance on the group people tab Select a person to open **Group compliance** and see their required documents. Expand a document to review its activity. Use **Send request** beside a document when a new signature is needed. **Nudge** at the bottom reminds that person's eligible pending requests for documents in this group. On the **People** tab, **Send missing** sends missing requests across the group. See [send missing requests](/guides/manage-groups#send-missing-requests). Group progress counts only the documents required by that group. A person may be up to date here but still need to sign documents assigned elsewhere. ## Compliance progress on the documents list Document cards show the current version, draft status, groups, and completion count. Documents available to read show **Available to read** instead of a completion meter. ## Compliance progress on the people list Person cards show overall status and completion among assigned documents. Use filters to find specific needs. Color is a quick guide, not proof that every document is complete; check the count. ## Request statuses For exact meanings, see [completion statuses](/concepts/compliance). Request completion, current-document status, and delivery status answer different questions. ## Paper on file in compliance views Paper on file counts as completion for its revision. The **Paper on file** label identifies how it was completed. See [record a paper signature](/guides/record-paper-signature). ## Downloading a completion receipt Use the completed request's actions. See [download records](/guides/download-records). ## Activity history Open **Activity** on a request to review and print its history. Use the [organization Activity page](/guides/activity-feed) to look across requests. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.