Overview
Sign Signature tokens in Finalize agreements allow for the automatic placement of signature and initial fields within your documents. When placeholder tokens are inserted directly into the document text, the system recognizes and converts them into the correct signing fields. This enhances the efficiency of the signing process, ensures consistency across agreements, and minimizes the risk of missing essential fields.
Benefits:
- Faster document preparation
- Fewer manual errors
- Consistent field placement across documents
Process
1. Start with a new template document or an existing template document.
2. Insert tokens where you want the signers to interact
For example:
- #[SIGN::SIGNATURE_1]# – Automatically places a signature field for Signer 1
- #[SIGN::NAME_1]# – Automatically places a name field for Signer 1
- #[SIGN::TITLE_1]# – Automatically places a title field for Signer 1
- #[SIGN::INITIALS_2]# - Automatically places initials for Signer 2
- #[SIGN::DATE_1]# - Automatically places the date for Signer 1
Token Formats
Supported Token Formats
| Token | Description |
| #[SIGN::NAME_1]# | Inserts the name field for Signer 1 |
| #[SIGN::TITLE_1]# | Inserts the title field for Signer 1 |
| #[SIGN::INITIALS_1]# | Inserts the initials field for Signer 1 |
| #[SIGN::SIGNATURE_1]# | Inserts the signature field for Signer 1 |
| #[SIGN::DATE_1]# | Inserts the date field for Signer 1 |
| #[SIGN::NAME_2]# | Inserts the name field for Signer 2 |
| #[SIGN::TITLE_2]# | Inserts the title field for Signer 2 |
| #[SIGN::INITIALS_2]# | Inserts the initials field for Signer 2 |
| #[SIGN::SIGNATURE_2]# | Inserts the signature field for Signer 2 |
| #[SIGN::DATE_2]# | Inserts the date field for Signer 2 |
Note: Once the tokens are placed in the document, set the font color to white.
This will prevent the tokens from appearing visibly in the final signed document.
3. Save and upload the document
Once the document is uploaded to your Finalize template, Finalize will automatically detect the signature tokens and assign the appropriate signatory group.
Remap signature tokens the same as you would with Template tokens, in edit mode.
To learn more about creating tokens in a template: HERE
4. Assign Signers
Once the signature tokens have been completed and the Finalize agreement is Ready for Signature, choose Sign as your e-signature method. Upon opening, the signature tokens automatically convert the tokens into the appropriate signature fields where added.
Next assign the signer roles by choosing the kebab and edit.
Note: Assigned signers are not limited to two people, as seen in the example.
Include any information needed for the recipient. The information provided will populate the appropriate signature blocks. Signers can also populate any missing information at the time of signing.
Once completed, save.
There is always the option to manually add additional signature blocks or any required predefined data needed to complete the signature request.
5. Send for signature
Once all signature requests have been added, choose: Send Request
6. Review and Track
After sending the agreement for signature, track the signing process and review the completed agreement once all parties have signed.
Note:
- Tokens are case-sensitive; they must be typed exactly as specified, including '#[ ]#' at the beginning and end of the token
- If tokens are misspelled or left incomplete, the system will skip them during the field generation.
- Prevent the tokens from appearing visible in the final signed document, set the token text color to white. This will ensure they are not visible during the signing phase.