> ## 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. # Manage document requests > Find outstanding requests by person or by request, review activity, send reminders, and cancel requests that are no longer needed. Use **Requests** to work through unfinished document requests across your organization. Each request is one person being asked to sign one document revision. **Who can use this page:** owners and administrators. Group Managers handle follow-up from their assigned group pages. ## Choose a view Open **Requests**. It starts on **By person** and **Outstanding**. ClearPolicy remembers the view you last chose. | View | Use it to | | - | - | | **By person** | Follow up with someone who has one or more matching requests. | | **By request** | Act on a single request. | Search by person name, email, or document name, or choose a filter. The filter applies to both views. | Filter | What it shows | | - | - | | **Failures** | Pending requests flagged for delivery follow-up. Appears when there are failures. | | **Outstanding** | Active, unfinished requests. | | **Not viewed** | Requests whose signing link has not been opened. | | **Viewed** | Requests opened but not completed. | | **Reminded** | Open requests that have received a reminder. | | **Completed** | Completed requests, including historical acknowledgments and paper on file. | | **Canceled/Expired** | Requests that can no longer be completed. | | **All** | Full request history. | ### By person Each row shows the person, how many matching requests they have, the oldest, the last activity, and when the next automatic reminder will go out. Click the row to open that person's requests. The sheet lists that person's requests in the current filter, such as **Outstanding documents**, with a count. Search on the page applies here. When an automatic reminder is scheduled, the sheet says ClearPolicy is taking care of follow-up and shows the next send time. If a request bounced or otherwise needs delivery follow-up, that notice is replaced with the provider error and a link to update the person’s email. Reminders stay paused for those requests. The people list shows **Fix delivery** instead of the next reminder. Open a request in the sheet to see when it was sent, viewed, reminded, completed, canceled, or expired. **View profile** opens the person. **Nudge** in the sheet reminds that person's eligible requests in the current filter, including requests on later pages. A request that is still sending, or one flagged for delivery follow-up, is not included. Add a note in the composer if you want to replace the note on those requests. ### By request Each row shows the person, document, status, requested date, and latest reminder date. Use this view for one reminder, activity, delivery review, cancel, expire, paper on file, or download. ## Follow up on a request On **By request**: * **Nudge** sends a reminder using the existing request link. * **Nudge with note…** lets you replace the request's note before reminding. * **Activity** opens the history of sending, delivery, views, reminders, and completion or closure. * **Review** on a failed request helps you retry delivery or correct the address. See [send reminders](/guides/reminders) for single and bulk actions. ## Fix a delivery failure Use **Failures → Review** to inspect the latest delivery details. Choose **Email is correct — try again**, or [correct the person's email](/guides/delivery-failures#correct-an-email-address) and save so open requests send to the new address. Ordinary reminders pause for a flagged request. Other successfully delivered requests to that person can still receive reminders. See [fix missing or failed emails](/guides/delivery-failures). ## Follow up on a group of requests Click **Nudge** and choose **All outstanding**, **Not viewed**, **Viewed**, or **Reminded**. Search can narrow the audience; the current status tab does not set the reminder scope. Check the count in the composer before sending. See [bulk reminders](/guides/reminders#send-bulk-reminders-with-nudge). ## Send a new request Click **Send request**, select people and one or more documents, preview, and send. Each person gets one email listing those documents. Use a new request for a new signature; use **Nudge** for an existing open request. See [send document requests](/guides/send-requests). ## Close a request that should not be completed On **By request**, open the active request's actions menu and choose: * **Cancel request** when the person no longer needs to complete it. * **Expire request** to close it immediately as expired. The personal link no longer allows completion. The request and its activity stay in history. A canceled or expired request is not reopened; send a new request if the person still needs to sign. ## Record paper on file On **By request**, use **Record paper signature** on a pending request when the person signed a paper copy. A PDF or image upload is required. See [record a paper signature](/guides/record-paper-signature). ## Download completed documents On **By request**, use **Download signed document** for an online completion or **Download uploaded file** for paper on file. See [download documents and completion records](/guides/download-records). ## When to use Requests, People, Documents, and Reports | Question | Where to go | | - | - | | Who needs follow-up today? | **Requests → By person** | | What does one person still need to sign? | **People → Documents** | | Who has signed a particular document? | **Documents → Compliance** | | How do I share completion summaries? | **Reports** | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.