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

# Update a document and request new signatures

> Publish a new revision without losing earlier records, then send the updated document to people who need to sign again.

Add a new revision when a published document changes. Earlier signatures stay linked to the version each person signed.

**Who can do this:** owners and administrators.

## Publish the updated version

1. Open **Documents** and select the document.
2. Open **Revisions** and click **New Draft**. If a draft already exists, continue working on it.
3. Add the new content using the editor, an upload, or a cloud import. For a document based on an uploaded file, prepare the updated file and upload or import it into the draft.
4. Optionally fill in **What changed**. This note is for your team's revision history; it is not shown to people receiving the document.
5. Review the draft and click **Publish**.

The new revision becomes current. Previous published revisions and completed records remain available.

## Ask people to sign the update

For a document with **Requires a signature** on:

1. Open **Compliance** after publishing.
2. Review the people who need the current version. Earlier completions may show **Outdated**.
3. Send requests to those people. You can also use a group's **Send missing** for eligible missing requests.

Publishing does not email people or cancel old requests by itself. When you send a new request for the same person and document, pending requests for older revisions are canceled. Completed, expired, and previously canceled requests stay in history.

## What if someone still has the old link?

Before you send a replacement request, the old pending request continues to refer to its original revision. Completing it records a signature for that version, not the new one.

After it is canceled by a replacement request, the old request cannot be completed. Ask the person to use the new email or their [signing portal](/guides/sign-document#use-the-signing-portal).

## Update a document available to read

When **Requires a signature** is off, publishing a revision changes the file people can open through their groups. There is no signature request, availability email, or record of opening the document.

See [make documents available to read](/guides/read-documents).

## Repeat signatures without changing the document

You do not need a new revision for a recurring sign-off. Use [renewal](/guides/renewals) to ask people to sign the same published document again on a schedule.