> For the complete documentation index, see [llms.txt](https://help.hippoly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hippoly.com/using-hippoly/e-signing/manage-signing-process.md).

# Manage signing process

Once a document has been sent for e-signing, you can track its progress, remind signers, or cancel the signing if needed.

## Track signing status

Every document with an ongoing or completed signing shows a status indicator. The possible statuses are:

| Status        | Meaning                                                              |
| ------------- | -------------------------------------------------------------------- |
| **Signing**   | The signing is in progress. One or more signers have not yet signed. |
| **Completed** | All signers have signed. The signed PDF has been stored.             |
| **Rejected**  | A signer has declined to sign. The signing is cancelled.             |
| **Cancelled** | The signing was manually cancelled by the sender.                    |
| **Timed out** | The signing was not completed within 90 days and has expired.        |

Open the signing details on the document to see the full list of signers, their individual status, and when they signed.

## Send reminders

If one or more signers have not yet completed their signing, you can send them a reminder.

{% stepper %}
{% step %}
Open the signing details on the document.
{% endstep %}

{% step %}
Click `Remind signers`. All signers who have not yet signed receive a new notification.
{% endstep %}
{% endstepper %}

## Cancel a signing

If the signing is no longer needed, for example the document needs to be updated before signing, you can cancel it as long as it's still in the **Signing** status.

{% stepper %}
{% step %}
Open the signing details on the document.
{% endstep %}

{% step %}
Click `Cancel signing` and confirm the action.
{% endstep %}

{% step %}
The signing is cancelled and all pending signers are notified. The document returns to its previous state, and a new signing can be initiated when ready.
{% endstep %}
{% endstepper %}

## Signatory statuses

Each individual signer in a signing process has their own status:

| Status               | Meaning                                                                           |
| -------------------- | --------------------------------------------------------------------------------- |
| **Pending**          | The signer has been invited but has not yet signed.                               |
| **Signed**           | The signer has completed their signature.                                         |
| **Rejected**         | The signer has declined to sign.                                                  |
| **Waiting**          | The signer is waiting for a prior signer to complete (when signing order is set). |
| **Delivery problem** | The signing invitation could not be delivered to the signer.                      |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.hippoly.com/using-hippoly/e-signing/manage-signing-process.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.