How do I format my own custom documents on Savvi?

Learn how to format your own custom documents using our software

What document types work with Savvi?

Our software works some of the most popular document extension types, including doc, docx, pdf, wpd, txt, rtf, and odt. 

What are Tokens?

Tokens are the symbols you place in a document that inform our software where the custom fields (such as signatures and date blocks) should go. 

How do I format a Token?

Tokens are created by placing curly braces “{}” in the document. Within the curly brackets, you can place three different fields of information: the type of information, the role of the party, and the name of the token. Each information field is separated by a colon. Here’s an example:


So remember these points when creating your tokens:

  • The type is the sort of information the token will display.
  • The role is the party who is responsible for filling out the information in the token.
  • The name identifies the token so it can be filled in on our questionnaire page prior to being sent out for signature. It applies to tokens that are texts and is optional for those that are texfields and checkboxes. 

How do I change the physical size of a token?

The physical size of tokens can be expanded by adding underscores “__” before the end of the curly brackets and after the token’s information. In the chart below, we list the different types of fields that can be used in the document with examples of how to fill them in.

Field Type Code Examples
signature s

{signature:employee} {s:employee:________}  {s:emp:_____}

date d {date:employee} {d:emp______}
initials i {initials:employee} {i:emp____}
textfield t {t:employee:phone.number___}
text* tx {tx:employer:job.description__}
checkbox c {c:emp}



This is where each party will place their electronic signatures. The length of the token will also affect the signature block’s height. For most documents, we recommend leaving 2 or 3 otherwise empty vertical spaces for the token to fill (including the line the token itself is on). If not, the signature will appear very small. We understand that some document formats may not allow for multiple empty spaces above the token. It is possible to use a single vertical space signature if necessary, but the signature will appear small in its final form.

 Vertical spaces available for a signature  Recommended Size
1 {s:emp}
2 {s:emp:_____}
3 {s:employee:________}



This block will let the person enter in a date. This may be the date the document is signed, the date the agreement becomes effective, or the date the document was drafted. Our software includes a “today” button, making it easy for the signer to insert the current date. The date token should be roughly this size. While a date can likewise be small, if you use a smaller token, part of the date may be cut off in the document.

Recommended Size: {d:emp______}



This block will put a user's initials in the spot provided. We should note, making the token small will make the initials look small when signed.

Recommended Size: {i:employee__}



This will insert a textfield to be filled out when the document is sent out for signature. Textfields are helpful for things like a title or email where the signer might need to put in something. They only take a single line, and will have a maximum amount of information that is based on the width of the token. We recommend erring on the side of making the token too large for the information you expect to fill it with.

Recommended Size: this depends on the information you expect. Users often need to make it larger than expected.



This token will allow the creator to add text to the document before it is sent out for signature. The text must be provided when the document is created and cannot be edited once it is sent out for signature. If the text provided takes up more space than is permitted by the token, it will wrap at the length of the token. Because of this, we recommend that you err on the side of creating token space that is greater than the text you are expecting to add. Otherwise, we recommend allowing for enough vertical space for the text to wrap.

*As Text is required to be filled out prior to submission, it is the only token that requires a "Name" property.

Recommended Size: this depends on the information you provide. We suggest making it larger than you think you need.



This will insert a checkbox that the signer can toggle. The token size has no effect on how the checkbox will appear when sent to the parties for signature.

Recommended Size: Irrelevant. The size of this token does not affect how it will appear.

What are some common errors I should be aware of?

There are some things to be aware of when creating tokens.  

  • Roles and names may only contain letters, numbers, and periods. Other symbols create errors.
  • While roles and names may contain numbers, they cannot start with a number.
  • Tokens should not have any character directly next to them. The tokens should instead be separated by spaces and/or periods.
  • Because the role of each party must remain consistent throughout the document, you should avoid referring to the same signer using more than one role. For example, if you use the role "Employee" in one token, you should use it with the exact spelling in all the tokens assigned to the same party. But if for one token you use "Emp" instead of "Employee," the software will recognize "Emp" as a completely different party. So if you need to use a smaller symbol for one token, then change the roles of the other tokens as well to make them consistent. If you need to expand the sizes of other tokens, use underscores to extend the token dimensions.




    {s:new employee}


    This token contains a space within the curly brackets.



    Underscores are only allowed at the end of a token.


    No Error

    Periods may be used to separate parts of a role.


    No Error

    Numbers may be used in roles.



    While numbers may be used in roles, roles cannot start with a number.



    No role is provided. A token must contain a role.



    There is no space before the token and after the characters preceding it.



    There should be a space between the tokens.

    Signature: {s:emp}

    No Error

    There is spacing between the token and the characters preceding it.

    {s:emp1} {s:emp2}

    No Error

    There is spacing between the tokens.

    Savvi Technologies, Inc. is not an attorney or a law firm, and can only provide self-help services at your specific direction. Do not rely on any documents or information from Savvi without consulting an attorney. Savvi may partner with or refer clients to licensed attorneys, but such referral does not constitute an attorney-client relationship until the attorney is officially engaged by the client.