Do you want to get the same contract electronically signed multiple times by different signers? In that case, it’s a hassle to add fields to the contract every time. Therefore, it’s possible to create a contract (template) in which the fields are automatically added. It takes a few minutes to create and test the template, but when done it makes working with SignRequest easier and faster.
SignRequest offers two ways to create a template:
- Templates with tags in a base document
- Templates within SignRequest
This help article shows you how to create a Template with tags in a base document.
To create a template of a document within SignRequest, click here.
Templates with tags in a base document
Template tags are a way in which you can add data to a base document in your chosen word-processing program (Word, Google Docs) that is automatically recognised by SignRequest.
The above video shows how to create a template with tags in a base document.
How to add tags to a base document
In this example, we use two signers, if fewer signers are added to the SignRequest by default these will not be shown. So to test and view all tags, we advise you to add at least 2 email addresses.
You can open the tag with " [[ " and close the tag with " ]] ". To create a text field use " t ", for a date field use " d " and for a signature field use " s ". Then, add a " | " and a number for every different user.
- You can change the size of the text, date and signature fields by adjusting the size of the font and adding spaces.
- The font color of the tags should be made white, so they aren't visible in the contract. (If you select the text, ctrl all, they should be visible, or when using the latest Word & Office 365, temporarily change the color of the page to grey, so the white text is visible.)
- You should keep a distance between the tags. Preferably an enter or a proper line-height. While making a template please be sure to test, before sending to contacts.
- For our "Bulk send" feature you'll need to create a Template within SignRequest.
Signer 0: this is the first person that needs to sign (including you).
Signer 1: this is the second person that needs to sign (including you).
The result in SignRequest:
Which tag is for which signer?
The numbers in the tags are used to make distinctions between the signers and group multiple tags (input fields) to one specific signer.
The template tags are assigned to the order at which the email addresses are added to the contact field and are not the same as the order of signing. This means that for example “s|1” can be the first or last signer depending on what you specified in the order of signing (if used of course).
More or fewer signers than tags?
This document has template tags for 3 signers. If you only add 2 signers then the last tags (in this example t|2, d|2 and s|2) will not be used. If you add more signers then tags then those signers will still be able to sign the document, but will not be directed to the locations in the document and have the ability to add text, dates and signatures wherever they want in the document.
Example 1: You need to sign yourself and have 2 external signers
In this case, you’ll be assigned to the t|0, d|0 and s|0 tags as by default the sender is always the first added email address. The t|1, d|1 and s|1 tags will be for the next added email address and the t|2, d|2 and s|2 tags will be for the other email address.
Example 2: You don’t need to sign yourself and have 2 external signers
In this case, the t|0, d|0 and s|0 tags will be assigned to the first added external email address. The t|1, d|1 and s|1 tags will be for the next added email address and the t|2, d|2 and s|2 tags will not be shown at all.
Tip: to easily test documents with tags you don’t really need to send them out, after uploading and adding the email addresses you can easily view the result by clicking on “Prepare document”.
How to make a field optional or required
By default, the text fields and signature fields are required. The checkbox field can be skipped by default.
To make the text or date fields optional instead of required you can add “r:0” to the tags, as follows:
Text field: [[t|1|r:0]]
Date field: [[d|1|r:0]]
To make the checkbox fields mandatory, you can add “r:1” to the tags, as follows:
Checkbox field: [[c|1|r:1]]
How to add a name to the fields
You can also add a name to the fields by adding “n:examplename”. Currently, that name is only visible in the pop-up window after clicking on the field. In the future, we will also add that name to the field thus replacing “Text”.
Text field: [[t|1|n:examplename]]
Text field: [[t|1|r:0|n:examplename]]
Automatic pre-fill of a date field
By default, the date field will be pre-filled automatically with the date of signing. In some cases, however, this is not useful, for example with a date of birth. In that case, you can use "p:0" to prevent it from being pre-filled.
Date field: [[d|1|p:0]]
Add an ID to a field
You can add an ID to the fields by adding “id:examplename”. This ID can be used to export data in an excel file or by using the API to pre-fill or export these fields.
Text field: [[t|1|id:examplename]]
How to make a text field "multi-line"
By default, text fields are "single-line". If you'd like the text field to support "multi-line" capacity, then you'll need to add "m:1" to your text field tags. It should look as follows:
Start testing yourself
You can quickly test this feature with our example documents:
These are shared Google Docs documents with example tags. If you have our Google Docs Add-on you can directly send a SignRequest!
If you don't have our Google Docs Add-on for electronic signatures, go to "Add-ons" in the Google Docs menu bar and install the Add-on for free. Then, go back to "Add-ons" and click "SignRequest".