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

# Set requests to expire automatically

> Configure automatic request expiry in ClearPolicy so unfinished attestation requests are marked expired after a set number of days.

New organizations have request expiry enabled by default with a **30-day** window. You can change the window or turn expiry off in **Settings → Document Requests**. Existing organizations keep their current settings until you change them.

With request expiry enabled, unfinished attestation requests are automatically marked as expired after your chosen number of days.

## Configure request expiry

<Steps>
  <Step title="Open document request settings">
    Click **Settings** in the sidebar, then select **Document Requests**.
  </Step>

  <Step title="Turn request expiry on or off">
    In the **Document request expiry** section, use the **Enable document request expiry** toggle.
  </Step>

  <Step title="Choose an expiry window">
    Select how many days a request should remain open before it expires. Available options are **3 days**, **5 days**, **7 days**, **14 days**, **30 days**, or **60 days**.
  </Step>
</Steps>

| Setting               | Options                     | Default for new organizations |
| --------------------- | --------------------------- | ----------------------------- |
| Enable request expiry | On / Off                    | On                            |
| Expiry window         | 3, 5, 7, 14, 30, or 60 days | 30 days                       |

<Note>
  Expiry settings apply only to new requests created after you enable or change the feature. Existing pending requests are not retroactively affected.
</Note>

## How expiry works

When request expiry is enabled, every new attestation request is assigned a deadline based on your chosen expiry window. ClearPolicy checks for expired requests daily and marks any that have passed their deadline.

Once a request expires:

* The request status changes to **Expired**.
* The request appears under **Canceled/Expired** on the **Requests** page.
* The recipient can no longer complete the attestation. If they open their link, they see a message explaining the request has expired and asking them to contact the sender for a new link.
* The expiry event is recorded in the request's activity log with the original deadline.

## How recipients see the deadline

When request expiry is enabled, ClearPolicy shows the deadline to recipients in multiple places so they know how much time they have:

* **Email notifications** — Both the initial request email and any reminder emails include a prominent notice with the exact expiration date and time.
* **Attestation page** — When a recipient opens their personal link, a warning banner appears at the top of the page showing the deadline. The expiration date also appears in the request details sidebar.

This helps recipients prioritize time-sensitive requests and complete them before the link expires.

### After a request expires

When a recipient opens an expired request link, they see a notice that the request has expired. The attestation form is not available. The message directs them to contact the person who sent the request if they need a new link.

## Re-sending after expiry

If a request expires and the recipient still needs to complete it, send a new request for the same document. The expired request remains in your records as part of the audit trail.

<Tip>
  Pair request expiry with [automatic reminders](/guides/reminders#set-up-automatic-reminders) to give recipients a nudge before their deadline passes.
</Tip>

<Tip>
  Expiry deadlines shown in emails use your organization's time zone. You can configure this in [time zone settings](/guides/timezone).
</Tip>