Skip to content

E-Signatures

When a contract is ready to sign, getting signatures from every party can mean emailing PDFs back and forth and chasing people manually.

Pactly handles signing directly from the contract record. You add signers, place signature fields on the document, and send. Each signer gets a link to review and sign, and you can track who has signed, who hasn’t, and send reminders.

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.

Built-in
Pactly e-Sign

Native provider. Works out of the box, no setup or licensing.

Integration
DocuSign

Admin connects the integration, users activate individually.

Integration
Adobe Sign

Admin connects the integration, users activate individually.

How E-Signatures Fit the Contract Lifecycle

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

By the time you send a contract for signatures, it has already been drafted (or uploaded), reviewed, negotiated, and approved. Collecting the signatures is the final step before the document is fully executed.

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.

Draft
In Review
Approved
Pending
Signature
Signing stage
Executed
1 Signers receive a link to review and sign
2 They sign in order, parallel or sequential
3 The 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. A contract has only one active envelope at a time: if you cancel a request and start a new one, the new envelope replaces the old, so there is always a single signing version on the contract.

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.

Parallel
All signers receive the request at once.
Request sent
Signer 1
Signer 2
Signer 3
Sequential
Each signer receives the request after the previous one signs.
Signer 1
Signer 2
Signer 3

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.

Signature field placement editor with a field palette (signature, initials, date, text, checkbox) on the left and signature fields placed on the document for each signer

Execution mode tells Pactly whether the signatures collected in a request fully execute the contract or only partially. Fully signed means every required party signs through this request, and when signing completes Pactly runs the automated next steps for an executed contract. Partially signed means only some signatures are collected here and more will be added separately, so Pactly records the signed document but holds back the post-signature automation.

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