Reusable eSignature templates for the documents you send again and again
With BoldSign, you set up a document once with its signer roles and fields, then send it to new signers whenever you need it.
- Signer roles and fields saved with the template
- Your team sends from it, and only the teams you pick can edit it
Setting up the same document from scratch slows every send
-
Same setup, every send
Placing signature, date, and text fields for each signer repeats work you already did for the last contract.
With a templateYou place the fields once and reuse them on every send.
-
Copies drift apart
When every sender rebuilds a document, the wording, field order, and signer settings start to differ. Those differences later come back as questions.
With a templateYou lock the files, fields, signers, and message, so every copy matches.
-
New senders start over
Without a shared starting point, each new team member learns where fields go and who signs first. A template carries those decisions for them.
With a templateYou share it with your team, so new senders start from a finished setup.
How do you create and send an eSignature template?
A BoldSign template takes 3 steps: upload a document, assign its fields to signer roles, and send it to real people whenever you need it.
-
Upload a document and name the roles
Add a PDF, Word, Excel, PowerPoint, or image file. Then name a role for each person who signs, such as Employer and Employee. A role is a placeholder until you send.
Roles1 Employer Signer2 Employee SignerEnable signing orderExample with sample data: a template with two signer roles named Employer and Employee -
Place fields for each role
Add signature, date, text, checkbox, and other fields, and assign each one to a role. Signing order and signer authentication saved here apply to every send. AI-powered field detection can place the fields for you.
Employment agreementThis agreement is made between Cubeflakes and Employee name.Start date: DateEmployer signatureEmployee signatureEmployerEmployeeExample with sample data: fields on an employment agreement, each assigned to the Employer or Employee role -
Send to real signers
Pick the template, enter the name and email for each role, and send. Each signer gets a link and completes the fields assigned to their role.
RecipientsEmployer Michael Brooksmichael.brooks@cubeflakes.comEmployee Emily Carteremily.carter@cubeflakes.comExample with sample data: each template role matched to a real signer's name and email before sending
Which documents work well as eSignature templates?
Any document you send more than once with the same layout works well as a BoldSign template. A few common ones are below.
| Document | Roles in the template | Fields set once |
|---|---|---|
| Mutual nondisclosure agreement | Company, Counterparty | Signatures, names, company names, dates |
| Employee onboarding forms | HR, New hire | Signatures, start date, address, emergency contact |
| Service agreement | Provider, Client | Signatures, client name, start date, fee |
| Lease or rental agreement | Landlord, Tenant | Signatures, initials on each page, move-in date |
| Consent or permission form | Organizer, and a parent or guardian | Signature, date, a checkbox for each permission |
Can you stop senders from changing a template?
Yes, BoldSign lets you decide what senders can change when they use a template you built.
-
Lock the files
Senders use only the documents you added, with no new or replaced files.
-
Control the fields
Allow senders to add fields, to edit or delete them, or only to set default values.
-
Fix the signers
Stop senders from adding signers beyond your roles, or from editing or removing a role.
-
Keep the message
Require the message you wrote, so every signer reads the same instructions.
Can you create and share templates from your phone?
Yes, the BoldSign iOS and Android apps let you create a template and send from it. Sharing it with your team works there too.
BoldSign mobile app
Build a template from a file on your phone, choose what senders can change, and send it to new signers between meetings. BoldSign has an iOS and Android app, and signers without it open the link in any phone browser.
How are your templates and signed documents kept secure?
BoldSign encrypts every document twice with AES-256. Its security controls are independently audited for SOC 2 Type 2, and each standard is listed in your account’s Compliance page, shown below.
Compliance
BoldSign meets global security and compliance standards to protect your documents and data. Manage the settings below to align with your organization’s requirements.
Data Residency
Active (US - Global)Your documents and signer data are securely stored in your selected region to meet data sovereignty and local regulatory requirements.
HIPAA Compliance
EnabledEnable HIPAA mode to protect PHI using administrative, technical, and physical safeguards aligned with HIPAA regulations.
PCI DSS
CompliantPayments are securely processed through Stripe, a PCI DSS Level 1-certified provider, ensuring the safe handling and encryption of all payment data.
CCPA & CPRA
CompliantEnsures compliance with California privacy laws, giving residents transparency and control over their personal data, including rights to access, delete, and opt out.
SOC 2 Type II
CompliantBoldSign has successfully completed a SOC 2 Type II audit, validating our controls for security, availability, confidentiality, and data integrity.
UETA & ESIGN
CompliantBoldSign ensures that all e-signatures are legally binding and compliant with the U.S. ESIGN Act and the Uniform Electronic Transactions Act (UETA).
eIDAS (SES)
CompliantBoldSign complies with the EU eIDAS Regulation (910/2014) and supports Simple Electronic Signatures (SES) by default.
eIDAS (QES)
EnabledEnable Qualified Electronic Signatures (QES) for contracts requiring the highest legal assurance under eIDAS.
Security and procurement documents for eSignature
IT and procurement teams can read BoldSign’s security policy, data processing agreement, and subprocessor list online. They can also request the SOC 2 Type 2 report.
- Sign-in
Single sign-on and user provisioning
Works with Microsoft Entra ID.
See features by plan - Audit report
SOC 2 Type 2 report
Available on request from BoldSign.
Request the SOC 2 report - Data protection
Data processing agreement
Includes the EU Standard Contractual Clauses and the UK Addendum by reference.
Read the data processing agreement - Data protection
Subprocessor list
Every third party BoldSign uses to process data.
See the subprocessor list - Service
Service level agreement
Uptime, support response times, and service commitments.
Find it in the Legal Center
Why choose BoldSign for eSignature templates
BoldSign lets your team build each document once and keep every copy it sends the same.
BoldSign is rated 4.7 out of 5 from 474 reviews on the BoldSign G2 profile.
-
No template limit
Unlimited templates, so you never delete an old template to make room for a new one.
-
Free help while you set up
Reach the BoldSign team by chat, email, or support ticket while you set up your first templates.
-
Build once, send from anywhere
A template you build once needs no second setup to send it from your phone, your own software, or Claude.
Customer stories from teams that send from templates
Innovation Philosophy, Ethical Mortgage, and Redcat send their documents from BoldSign templates.
-
Innovation Philosophy
Reusable templates cut document errors
Read story -
Ethical Mortgage Faster mortgage signing from templates
Read story -
Redcat
Branded templates set up quickly
Read story
Limits and costs to know before you use eSignature templates with BoldSign
BoldSign stores your templates and sends them for signature. It does not write or draft the documents inside them.
- 2 templates on the Essential plan Sharing and locking templates are not on this plan.
- 10 templates on the Growth plan $5 per user a month, billed yearly (pricing).
- $0.25 per envelope sent by Bulk Send or Bulk Links Add-ons on the Business plan and higher.
Prices are in USD.
Before your first template
- 25 files per template Each file up to 25MB and 1,000 pages (template documentation).
- Template links, custom fields, and AI-powered field detection are not on the Essential or Growth plans.
- Live API calls and templates embedded in your own app need the Enterprise API plan, from $30 a month with 40 envelopes, then $0.75 each.
How do you share templates with teams through the API?
BoldSign’s template API creates, edits, lists, and shares templates, and sends documents from them. The samples below come from the share template documentation and grant or revoke team access to one template.
curl -X PATCH 'https://api.boldsign.com/v1/template/share?templateId=54e67b1a-af13-4370-91ed-031343170578' \
-H 'Content-Type: application/json' \
-H 'X-API-KEY: {API-KEY}' \
-d '{
"teams": [
{
"teamId": "54e67b1a-af13-4370-91ed-031343170578",
"action": "Grant",
"accessLevel": "Edit"
},
{
"teamId": "41b498c3-cbee-488d-8c7c-4dc97a7f31e7",
"action": "Grant",
"accessLevel": "Use"
},
{
"teamId": "96d38f94-d636-4215-9f50-ff21d90baba8",
"action": "Revoke"
}
]
}' var apiClient = new ApiClient("YOUR_API_KEY");
var templateClient = new TemplateClient(apiClient);
var shareTemplateRequest = new ShareTemplateRequest
{
Teams =
[
new TemplateTeamShare
{
TeamId = "54e67b1a-af13-4370-91ed-031343170578",
Action = TemplateShareAction.Grant,
AccessLevel = TemplateAccessLevel.Edit
},
new TemplateTeamShare
{
TeamId = "41b498c3-cbee-488d-8c7c-4dc97a7f31e7",
Action = TemplateShareAction.Grant,
AccessLevel = TemplateAccessLevel.Use
},
new TemplateTeamShare
{
TeamId = "96d38f94-d636-4215-9f50-ff21d90baba8",
Action = TemplateShareAction.Revoke
}
]
};
templateClient.ShareTemplate("YOUR_TEMPLATE_ID", shareTemplateRequest); import boldsign
configuration = boldsign.Configuration(host = "https://api.boldsign.com", api_key="YOUR_API_KEY")
with boldsign.ApiClient(configuration) as api_client:
template_api = boldsign.TemplateApi(api_client)
team1 = boldsign.TemplateTeamShareRequest(
team_id="YOUR_TEAM_ID",
action="Grant",
access_level="Use"
)
team2 = boldsign.TemplateTeamShareRequest(
team_id="YOUR_TEAM_ID",
action="Revoke",
access_level="Use"
)
template_share_request = boldsign.TemplateShareRequest(
teams=[team1,team2]
)
template_api.share_template(
template_id="YOUR_TEMPLATE_ID",
template_share_request=template_share_request
) <?php require_once "vendor/autoload.php";
use BoldSign\Configuration;
use BoldSign\Api\TemplateApi;
$config = new Configuration();
$config->setHost('https://api.boldsign.com');
$config->setApiKey('YOUR_API_KEY');
$template_api = new TemplateApi($config);
$team = new BoldSign\Model\TemplateTeamShareRequest();
$team->setAccessLevel("Use");
$team->setAction("Grant");
$team->setTeamId("YOUR_TEAM_ID");
$template_request = new BoldSign\Model\TemplateShareRequest();
$template_request->setTeams([$team]);
$template_api->shareTemplate("YOUR_TEMPLATE_ID",$template_request); import { TemplateApi } from "boldsign";
const templateApi = new TemplateApi("https://api.boldsign.com");
templateApi.setApiKey("YOUR_API_KEY");
var templateTeamShareRequest = new TemplateTeamShareRequest();
templateTeamShareRequest.teamId = "YOUR_TEAM_ID";
templateTeamShareRequest.accessLevel = TemplateTeamShareRequest.AccessLevelEnum.Use;
templateTeamShareRequest.action = TemplateTeamShareRequest.ActionEnum.Grant;
var templateShareRequest = new TemplateShareRequest();
templateShareRequest.teams = [templateTeamShareRequest];
templateApi.shareTemplate("YOUR_TEMPLATE_ID", templateShareRequest); ApiClient client = Configuration.getDefaultApiClient();
client.setBasePath("https://api.boldsign.com");
client.setApiKey("YOUR_API_KEY");
TemplateApi templateApi = new TemplateApi(client);
TemplateTeamShareRequest team1 = new TemplateTeamShareRequest();
team1.setTeamId("YOUR_TEAM_ID");
team1.setAction(TemplateTeamShareRequest.ActionEnum.GRANT);
team1.setAccessLevel(TemplateTeamShareRequest.AccessLevelEnum.EDIT);
TemplateShareRequest shareRequest = new TemplateShareRequest();
shareRequest.setTeams(Arrays.asList(team1));
templateApi.shareTemplate("YOUR_TEMPLATE_ID", shareRequest); More guides for eSignature templates
BoldSign guides cover template permissions, team sharing, sending to many people, and a library of document templates.
- Guide
Roles and permissions
Who creates, shares, and sends templates.
Read the guide - Guide
Share with other teams
Help centre steps for sharing a template with other teams.
Read the guide - Page
Bulk Links
One signing link from a template, for many signers.
See the page - Page
Bulk Send
Send one template to a list of named signers.
See the page - Guide
Send from Claude
Connect Claude Desktop and send from your templates.
Read the guide - Templates
Template library
Agreements and forms to upload as a starting point.
Browse the library
Switching from another eSignature tool
Docusign templates import into BoldSign at no charge with BoldSign’s import tool, and BoldSign support helps teams make the switch.
- Guide
Import your Docusign templates
Step-by-step help for moving Docusign templates into BoldSign.
Read the import guide - Comparison
BoldSign compared with Docusign
Features and prices side by side, for teams moving from Docusign.
See the Docusign comparison - Comparison
BoldSign compared with Dropbox Sign
For teams moving from Dropbox Sign, formerly HelloSign.
See the Dropbox Sign comparison - Comparison
BoldSign compared with Adobe Acrobat Sign
For teams moving from Adobe Acrobat Sign.
See the Adobe comparison - Comparison
BoldSign compared with PandaDoc
For teams moving from PandaDoc.
See the PandaDoc comparison - Comparison
SignNow and other tools
Every eSignature tool BoldSign is compared with.
See all comparisons
Questions about eSignature templates
Do signers need a BoldSign account to sign a document sent from a template?
No. BoldSign sends each signer a link, and they sign without an account, an app or any payment.
Can you turn an existing PDF or Word file into a template?
Yes. Upload the file when you create a BoldSign template, then place the fields. If a PDF already has fillable fields, automatic field detection turns its text boxes, checkboxes, radio buttons and signature fields into BoldSign fields.
Can you send one template to many people at once?
Yes. BoldSign’s Bulk Send feature sends a template to a list of named signers from a CSV file. Its Bulk Links feature creates one link that many people can sign. Both are add-ons on the Business plan, at the rate shown in the limits above.
Can you prefill field values when you send from a template?
Yes. A BoldSign template can let senders set default values for its fields before they send. Through the API, you fill existing fields by their field ID when you send from the template.
Can a template make signers sign in a set order?
Yes. Turn on signing order when you build the BoldSign template, and each signer is notified only after the one before them has signed.
Are documents sent from a template legally binding?
Yes. Signatures you collect with BoldSign are legally binding under the ESIGN Act, UETA, and eIDAS.
Last updated: October 15, 2026