eSign itself does not store reusable templates. Templating is handled by the calling product — Legal, Build, CRM, AMS, or your own workflow. This article explains how templates work in the context of eSign and how to structure repeatable envelope creation.
Who This Is For
Staff who send the same type of document frequently and want a consistent, repeatable process — for example, a standard service agreement or onboarding form sent to every new client.
How eSign Handles Repeated Documents
When you send an envelope, eSign accepts whatever documents, fields, and signers you provide. It does not apply its own template logic. To create envelopes consistently from the same document structure, you build the template in the product or workflow that calls eSign.
For Legal documents: Legal has its own contract template management. When a contract is ready to sign, Legal creates the eSign envelope with the correct documents and fields automatically.
For other products (Build, CRM, AMS): Each product manages its own template library. When a document needs signing, the product creates the envelope via the eSign API and passes in the standard structure.
For direct eSign users: If you are not using another product's template feature, create a consistent process by saving a master copy of your document with fields already laid out. Each time you need to send it, create a new envelope and upload the prepared document.
Structuring a Consistent Envelope
If you regularly send the same type of document, do the following once and repeat:
- Prepare the document (PDF) with all content finalized except for the signer-specific fields.
- Create a new envelope, upload the document, and place all signature and field positions.
- Save the envelope in Draft.
- Before sending, verify the signer details are correct for this recipient.
- Click Send.
By keeping a documented record of your standard field layout (which page, which position, which field type for each common document), you can recreate the layout quickly each time without starting from scratch.
Source Tracking
When a calling product creates an envelope, it sets a source_service and source_id on the envelope. This links the eSign envelope back to the original record in the calling product (for example, a contract ID in Legal or a deal ID in CRM). If you are building an integration, always pass these fields so you can trace completed envelopes back to their origin.
Frequently Asked Questions
Can I save a draft envelope as a template inside eSign? Not as a named reusable template — eSign does not have a template library. You work from your own document files and recreate the field layout when needed, or rely on a calling product's template system.
What if I send the same document to dozens of people? For high-volume repeated sends, use a calling product (CRM, AMS) that has template support and will create the eSign envelopes automatically. Doing it manually for large volumes is not practical.
Can the calling product pre-fill text fields? The envelope documents and field values are set when the envelope is created. A calling product can pre-fill field values at creation time before the envelope is sent.