eSignature templates
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.
Example with sample data and demo names.
Setting up the same document from scratch slows every send
-
More fields, more work, every send
Every new contract means placing the same signature, date, and text fields again.
See how templates solve it -
Copies drift apart
When every sender rebuilds a document, wording, field order, and signer settings start to differ.
See how template locking solves it -
New senders start over
Without a shared starting point, each new sender relearns where fields go and who signs first.
See how template sharing solves it
How do you create a template once and use it repeatedly?
A BoldSign template takes 3 steps: upload, place fields and roles once, then reuse it.
-
Upload a document and name the roles
Add a PDF, Word, or image file. Name a role for each signer, such as Employer and Employee.
-
Place fields and roles once
Add fields and assign each to a role. Signing order and authentication apply to every send. AI-powered field detection can place them for you.
-
Use it repeatedly
Pick the template, enter each role’s name and email, and send.
Which documents work well as eSignature templates?
Any document you send often with the same layout. Common ones:
| 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 |
What else can a BoldSign template do?
A template can also be built faster, keep each role’s rules, and go out in more ways.
- 01 · Build
Fields placed with AI
AI places signature and date fields; a PDF’s form fields become BoldSign fields.
- 02 · Build
Copy a template
Clone a template, with or without values, for a variation.
- 03 · Control
Rules for each role
Control recipient edits and ask a role for a code or an ID check.
- 04 · Organise
Tags and filters
Tag templates, then filter by tag, creator, team, or date.
- 05 · Send
Bulk Send and Bulk Links
Send to a CSV list, or turn it into one shared link.
- 06 · Send
From your phone
Pick and send a template from the iOS or Android app.
Can you stop senders from changing a template?
Yes. You decide what senders can change.
How are your templates and signed documents kept secure?
BoldSign encrypts every document twice with AES-256, and its controls are audited for SOC 2 Type 2.
IT and procurement teams can read the data processing agreement and the subprocessor list online, and request the SOC 2 Type 2 report.
View security policyCustomer stories from teams that send from templates
Innovation Philosophy, Ethical Mortgage, and Redcat send their documents from BoldSign templates.
All customer storiesInnovation Philosophy
Information Technology & Services
Reusable templates cut document errors
“BoldSign is easy to use and eliminates the headache that often comes with managing large volumes of signed documents across multiple products and teams.”
Manos Katris · CEO of Innovation Philosophy
- Product used
- BoldSign
- Region
- Australia
Limits and costs to know before you use eSignature templates with BoldSign
BoldSign stores and sends templates; it does not draft the documents in 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 embedded templates need Enterprise API, 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.
Read the developer docscurl -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); 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 it when you create a template, then place the fields. A PDF’s fillable fields become BoldSign fields automatically.
Can you send one template to many people at once?
Yes. Bulk Send sends a template to a CSV list of named signers, and Bulk Links make one link many people can sign. Both are add-ons on the Business plan.
Can you prefill field values when you send from a template?
Yes. Senders can set default field values before they send, and the API fills fields by their field ID.
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
