Skip to content

E-Signatures

When a contract is ready to sign, you need signatures from multiple parties, often across different organizations and time zones. Without e-signatures, you are emailing PDFs back and forth, losing track of who has signed, and chasing people manually. A single missed signer can delay execution by days.

Pactly’s e-signature capability handles this. You create a signature request directly from the contract record, add signers, place signature fields on the document, and send. Each signer receives a link to review and sign. You can track progress, send reminders, and see exactly who has signed and who has not.

📷 Screenshot
Signature request creation dialog showing signers list, signing order toggle (parallel/sequential), and execution mode selector

Pactly supports three e-signature providers. You choose which provider to use when creating a signature request.

Pactly e-Sign is the built-in provider. It works out of the box with no additional setup or licensing. Signers receive an email with a link to review and sign the document in their browser.

DocuSign is available as an enterprise integration. Your organization’s admin connects DocuSign at the account level, then each user activates their own DocuSign account in their profile settings. When you create a signature request, you can select DocuSign as the provider.

Adobe Sign works the same way as DocuSign. Admin connects the integration, users activate individually, and you select Adobe Sign when creating a request.

All three providers follow the same workflow in Pactly: add signers, place fields, send. The signing experience for the signer differs depending on the provider, but tracking and status updates in Pactly are consistent across all three.

🎨 Illustration
Creative/conceptual: Three provider cards side by side - Pactly e-Sign (built-in, no setup), DocuSign (enterprise integration), Adobe Sign (enterprise integration) - each with their logo/icon and a brief differentiator

How E-Signatures Fit the Contract Lifecycle

Section titled “How E-Signatures Fit the Contract Lifecycle”

E-signatures handle the signing stage. By the time you send a contract for signatures, it has already been drafted (or uploaded), reviewed, negotiated, and approved. The signature phase is the final step before execution.

When all required signatures are collected, Pactly automatically moves the contract to Executed status. The signed document is stored on the contract record alongside the full timeline of signature events: who signed, when, and in what order.

If your organization uses workflows, you can configure rules that trigger after execution, such as notifications, archival, or renewal reminders.

📐 Diagram
Contract status flow highlighting the signature stage: Draft → In Review → Approved → Pending Signature → Executed. Show the signing process expanding from 'Pending Signature': signers receive links, sign in order, contract moves to Executed.

A signing envelope is the container for a single signature request. It tracks the document being signed, the list of signers, their completion status, and the signing order. One contract can have multiple envelopes over its lifetime, for example if the first request was cancelled and a new one created.

When you create a signature request, you choose between two signing orders. Parallel sends the request to all signers at the same time. Sequential sends it to one signer at a time, in a defined order. The next signer only receives their request after the previous signer completes theirs.

🎨 Illustration
UI-faithful: Side-by-side comparison of parallel signing (all 3 signers receive simultaneously, arrows pointing to all at once) vs sequential signing (signer 1 → signer 2 → signer 3, arrows in sequence)

Signature fields are zones you place on the document before sending. Each field is assigned to a specific signer. Field types include signature, initials, date signed, text input, and checkbox. Signers can only interact with fields assigned to them.

📷 Screenshot
Signature field placement editor showing a PDF document with draggable signature, initials, date, and text fields positioned on the page, each color-coded by signer

Execution mode controls when the contract moves to Executed status. Fully signed means all signers must complete their signatures before the contract is considered executed. Partially signed means the contract moves to Executed as soon as the first signer signs, which is useful for acknowledgements or one-sided agreements where counter-signature is not required.

See Fully Signed vs Partially Signed for details on when to use each mode.