Document Tags - Full List

Introduction

Below is a list of all of SignatureSense tags (sometimes called "codes") you can add to your templates to request signatures (and more) at specific locations.  Watch a video demonstration.

Some are as simple as "sign here"; others are more complex, such as "mutually exclusive ticks" or "append a document".

Signatory ID

The signatory ID  in the examples below has been set to "LL1"  (Landlord 1).   However this part of the code will change depending on who it's for.  For example it might be "TT1" (tenant 1) or "employee1".

Reapit users must use a specific codes for the signatory IDs.

Add these codes so that they don't show on the final document:

You can just cut and paste the codes into your template, but you should apply a "style" to the tags so that you can turn them on (coloured)/ off (white) as needed.  You need to make sure the code are hidden (coloured white) before using the template.

Table of Tags

Action


Code / Tag

Notes





Signing




Signature

Required

{ss:SG_LL1}

Signature required here

Dated

Required

{ss:SD_LL1}

Date of signing

Signatory Name

Required

{ss:SN_LL1}

Name of the signatory

Initial

Required

{ss:IN_LL1}

Signatory must initial at this location

Tick (Mandatory)

Required

{ss:TK_LL1}

Signature must tick at this location.

Sign and Date

Required

{ss:FS_LL1}

Signature and Date inserted at the same location





Form Fields




Tick (tick / untick)

Required

{ss:TR_LL1}

User can check or uncheck, but a response is required

Tick (tick / untick)

Optional

{ss:TN_LL1}

As above but can be ignored.

Tick box group 

(Mutually Exclusive) 

Required

{ss:TR_LL1:g1}




Group ticks by adding :g1 or :g2 or any unique identifier, for example :pet.
Only one in the group can be ticked.

Tick box group 

(Mutually Exclusive) 

Optional

{ss:TN_LL1:g1}



As above but the tick group can be ignored.





Textbox 1 Line

Required

{ss:1R_LL1_________}

The trailing underscores dictate the size of the text box.  Make sure the tag font is Arial 10pt for accurate sizing.

Textbox 1 Line

Optional

{ss:1N_LL1_________}





Yes / No

Required

{ss:YR_LL1}

Inserts the word Yes or No.  User clicks to change.

Yes / No

Optional

{ss:YN_LL1}

As above but can be ignored.


 






Document Execution

Set to auto execution


{ss:FC_AutoExec=True}

Document automatically executes when the last person signs.  Tag can go anywhere on document.

Set to manual execution


{ss:FC_AutoExec=False}

Execution will happen when triggered by the document sender.  Tag can go anywhere on document.





Witness Codes




Link Witness 1 to LL1


{ss:WT_LL1:WT1}

These can go anywhere on the document.  They tell the system that LL1 requires a witness and the witness for LL1 is “WT1”.  The witness signature is then inserted using the following codes.

Link Witness 2 to LL2


{ss:WT_LL2:WT2}

Witness Name


{ss:SN_WT1}

Signing codes for the witness are as above in this table.  Just make sure the SignatoryID is set appropriately for the witness, for example WT1

Witness Signature


{ss:SG_WT1}

Witness Date


{ss:SD_WT1}

Witness Occupation


{ss:OC_WT1}

Occupation, as provided during the witnessing process

Witness Address


{ss:AD_WT1}

Address, as provided during the witnessing process





Upload Requests




Document upload request


{ss:UR_LL1:Proof of ID}

The signatory will be prompted to upload a document called “Proof of ID”.  The wording can change according but cannot exceed 38 letters.  The tag can go anywhere on the document.








Document Behavior


Initial All Pages


{ss:FC_InitialPage=True}

All parties will need to initial all pages.  No need to use individual codes.  This one code does this automatically and spreads the initials along the bottom of each page.

Append a document


{ss:DA_library file name}

Automatically append a PDF to the end of this document before sending.  Leave the “.pdf” part of the filename off.  Replace “library file name” with the name of a PDF in the library area of your account.