> For the complete documentation index, see [llms.txt](https://docs.enapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enapi.com/roaming/how-to-pre-sign-an-offer.md).

# How to Pre-sign an Offer

Collect your own signatures before your counterparty accepts, so the connection activates the moment they do. If you send offers to all partners, this is the recommended way to do it.

## **Why**

Signing is normally sequential: your partner accepts and signs, you get an email, you sign, and the agreement activates. Every step waits on a person. Pre-signing moves your half to the front, so acceptance becomes the last step instead of the middle one.

It matters most for general offers sent to all partners. One presign covers the whole offer: your signatures are applied to every partner who accepts it, and each acceptance becomes a live connection with no further action from you.

## **How it works**

{% stepper %}
{% step %}
**Create the offer.** 

Choose a standard or custom contract, then select the signatories. The ENAPI standard contract preselects your first contact. Change this selection as you would for a custom template.
{% endstep %}

{% step %}
**Select Presign.** 

ENAPI sends each signatory a one-time signing link.
{% endstep %}

{% step %}
**Sign the offer.**

Each signatory opens their link and types or draws a signature. An ENAPI account is not required. Links expire one hour after ENAPI sends them, or immediately after use.
{% endstep %}

{% step %}
**Wait for acceptance.** 

When your counterparty accepts, ENAPI applies the stored signatures. The connection becomes *Active* immediately, or on the future activation date you set.
{% endstep %}
{% endstepper %}

## **Good to know**

* **One presign covers every partner.** On an offer sent to all partners, you sign once and your signatures apply to each acceptance.
* **It works on offers you've already sent.** Presign isn't limited to new offers. Open an existing one and pre-sign it.
* **You can resend as often as you need.** Each new email invalidates the previous links, so if someone lets an hour lapse, just send again.
* **Partial signatures are safe.** If your counterparty accepts before every signatory has signed, nothing is lost. The offer falls back to the normal flow, and signing links go out by email at that point.
* **Your counterparty doesn't see your signatures** while reviewing the offer. They appear on the contract once the agreement is complete.
* **Standard and custom agreements both support it.** Externally signed contracts don't need signatures on ENAPI, so no Presign button appears on them.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.enapi.com/roaming/how-to-pre-sign-an-offer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.