Creating EchoSign Smart Forms using Text Tags

EchoSign allows you to easily place signatures, initial boxes and forms fields in your document simply by
adding special text tags in your document. Tags may appear in any document type such as PDF, Microsoft
Word, Powerpoint, Excel and simple text files (*.txt)
EchoSign will convert any text-based document containing those tags into a powerful EchoSign Smart
Form, allowing allow you to collect data from your signers, position signature and initials fields in your
documents, collect multi-party information from sender and signers and more.

EchoSign Smart Forms allow you to enjoy the following benefits:

• The best signing experience – EchoSign’s signing wizard guides
signers through the documents so they can easily sign any form.
• 100% web-based. Allow your customers to sign without requiring
them to have Adobe Reader installed.
• Set locations for customers to initial documents
• Enables EchoSign’s Advanced and Biometric signature options
 Creating EchoSign Smart Forms using Text Tags

EchoSign Text Tags

EchoSign Text Tags are simply text strings that may appear anywhere within the content of your
document specifying the location and type of field included in the document presented to your
signers.

EchoSign Text Tags appears between a set of two curly braces and contain the name of the field.
This name specifies the role associated with the field (e.g. sender, signer, etc.), the field type
(signature, initials or a regular text field) and whether the field is optional or mandatory.

For example:
{{address_es_signer}} – an text field to be filled by the signer
{{_es_signer_signature}} – a signature field to be signed by the signer

EchoSign Text Tags will be converted into EchoSign Smart Form fields when the document is sent or
uploaded into the EchoSign document library.

For example:

In Microsoft Word:

When signing:

And in the
signed document:
 Creating EchoSign Smart Forms using Text Tags

Collecting Data From Specific Signers

Fields can be assigned to specific signers by appending an EchoSign-specific suffix to their names.
A field that does not have such a suffix (e.g. {{address}}) can be filled by any signer.
After it has been filled, the field will be locked to prevent subsequent signers from changing its value.

Associating a Field With a Specific Signer.

You can instruct EchoSign to distinguish between fields that need to be filled by the sender or the
signer by adding a suffix to their names. For senders, add _es_sender. For signers, _es_signer.

If you have a document that needs to be signer by multiple signers document in sequential order, you
may associate fields with up to 6 signers using _es_signer1, _es_signer2 to _es_signer6.

For example:
{{price_es_sender}} – an text field to be filled by the sender
{{street_es_signer}} – a text field to be filled by the signer
{{city_es_signer2}} – a text field to be filled by the 2nd signer

Sender Pre-Fills Data, Only Signer Sign

In some cases, the sender is not required to sign the document but needs to enter data before the
document is sent out for signature.

By adding the _es_prefill suffix to the names of relevant fields, EchoSign allows the sender to
complete (pre-fill) those fields before sending the document for signature.

For example, {{price_es_prefill}} would create a text field to be pre-filled by the sender before the
document is sent for signature.
 Creating EchoSign Smart Forms using Text Tags

EchoSign Signature Fields

You may position EchoSign signature or initial fields by adding a suffix to designate the type of the
signature field and whether it should be signed by the sender of signer.

To position a signature field by appending _signature to the field name.

To position an initials field, append _initials

For example:
{{signHere_es_signer_signature}}, {{clause1_es_signer_initials}}, {{senderSign_es_sender_signature}}

When sending a document containing those fields for signature, signature and initials fields would
require the signers to enter their signature or initials at the designated locations:

For example:

When Signing:

And, in the signed document

 Creating EchoSign Smart Forms using Text Tags

Additional EchoSign Fields

You may position these EchoSign fields in your document by appending their names to the field name

Data Entry fields Read Only fields

_title – The signer’s job title. _date – signature date
_company – The signer’s company. _email – the signer’s email address
_fullname – The signer’s full name

For example: {{_es_signer_title}}, {{_es_signer_company}}, {{_es_sender_fullname}} etc.

The EchoSign Signature Block

If no signature field was placed in the document for a specific signer, EchoSign will automatically place
a signature block at the bottom of the document.

Depending on your account configuration, signers may also be required to provide their title and
company. In that case, EchoSign will present a signature block containing those fields in case they
were not place in the document.

You may position the entire EchoSign signature block in your document by appending _signatureblock
to the end of the field name

For example: {{_es_signer_signatureblock}}, {{_es_sender_signatureblock}}

 Creating EchoSign Smart Forms using Text Tags

Marking Mandatory Fields

Signature and Initial fields are mandatory by default.
Title and Company are mandatory if your account preferences require them to be part of
the signature block.

Other text fields are optional by default. You may explicitly mark a field to make it
mandatory by adding an asterisk (*) prefix to the field name.

For example:
{{*price_es_sender}} – a mandatory text field to be filled by the sender
{{address_es_signer}} – an optional text field to be filled by the signer

Required fields will be outlined in red when signing.

 Creating EchoSign Smart Forms using Text Tags

Summary
Signature fields
{{_es_signer_signature}}
{{_es_signer_initials}}
{{_es_signer_signatureblock}}
– A signature field assigned to the signer
– An initials field assigned to the signer
– A signature block assigned to the signer

Special EchoSign fields

{{_es_signer_title}} – A field for the signer to enter their title.
{{_es_signer_company}} – A field for the signer to enter their company name.
{{_es_signer_fullname}} – A field for the signer to enter their full name.
{{_es_signer_date}} – A read-only field containing the date of the signer’s signature
{{_es_signer_email}} – A read-only field containing the signer’s email address

signer may be replaced by other roles such as sender, signer2, signer3, … signer6
The text inside the tag can be preceded by some name – e.g. {{accept_es_signer_initials}}

Text fields
{{address_es_signer}} – An optional for the signer’s to enter theiraddress.

The text inside the tag can be preceded by an asterisk (*) to make the field mandatory – e.g.
{{*phone_es_signer}} – A mandatory field for the signer to enter their phone number

Prefill
{{*price_es_prefill}} – A mandatory field where the sender enters the price before
sending the document out for signature.