Skip to content

Signing tags

Signing tags turn blank areas in a Word template into fields for Pactly e-Sign. A generated contract keeps its template’s field settings, so you do not need to place the same fields for every signature request.

Type each tag on one line in its own paragraph or table cell. Word text boxes are not supported. Use ordinary text with a white background. Leave enough blank space below and to the right for the field and its answer.

TagField
{{signature:1}}Signature for template signer 1
{{initials:1}}Initials for template signer 1
{{name:1}}Editable text initially filled with that recipient’s name
{{text:1:address}}Text answer named address for template signer 1
{{checkbox:1:accepted}}Checkbox named accepted for template signer 1
{{date:1}}Automatic date when template signer 1 signs
{{date:completion}}Automatic date of the last required signature

Change 1 to another signer number as needed. Names such as address identify answers. Repeating the same tag repeats the same answer throughout the document. A tag for signer 2 has a separate answer from the corresponding tag for signer 1.

Signing tags remain in generated Word documents until you prepare the signature request. In the signing PDF, Pactly covers the marker text with white boxes before placing fields. The marker text may remain in extracted PDF text; it is not redacted. Ordinary template variables such as {{contractValue}} are filled earlier, during contract generation.

  1. Upload the tagged Word template using your usual template authoring process.
  2. Open the template in Manage Templates, then choose Signing fields. You need permission to edit templates.
  3. Choose a field under Field to configure, then set its label, width, height and required status. Dimensions use points, with 72 points per inch. Field preview updates as you change the settings.
  4. For an address, select Allow multiple lines and reserve a taller box in Word. Set a character limit that suits the space available.
  5. For dates, choose the display format and timezone. These dates come from signing events and cannot be entered or backdated by recipients.
  6. Optionally select a compatible contract property under Update contract property after signing.
  7. Save the settings and generate a new contract.

For text fields, enter a Sample answer to check wrapping and fit. Samples are only used in the preview and are not saved or sent to signers. The preview shows field size, not placement in the document. Check placement in the generated PDF before sending.

Changes apply to contracts generated after saving. Editing the template does not change an existing generated contract or a request already sent.

Choose the recipients in signing settings. By default, signer order matches the numbered tags. To change the assignment, open the gear beside Recipient 1 or another recipient and set Template signer slot. An overridden slot appears beside the recipient heading. Selecting an occupied slot swaps the two assignments.

For a manual send, check the generated fields in the document preview. Template fields have fixed positions and settings. To change them, edit the template and generate another contract. You can still add ordinary fields in the preview.

If a revised document no longer has the tags, choose Place fields manually for this request in signing settings. Remove visible tags from the document first. This turns off template fields and property mappings for that request and records the choice in its audit trail. Check every field in the preview. Automated workflows continue to require valid template tags.

A workflow uses the same saved field settings and requires a list of signers only. For requests with viewers or copy recipients, send from the contract signing dialog. Every signer needs a signature field. Missing recipients, invalid tags, fields outside the page or fields overlapping document text stop preparation with an error.

If a field overlaps text, increase the blank area in Word. Do not reduce the field until long names or addresses become unreadable. Check the PDF preview because conversion can change Word spacing. If a tag wraps onto two lines, widen its cell or shorten the answer name.

Text fields can update text or multiline properties. Checkboxes can update boolean properties. Automatic dates can update date properties. Shared Party records are not changed.

Later signers can see completed tagged text, checkbox and date values as read-only details. Unfinished answers are not shared.

Mappings run after the signing request completes. Pactly keeps the signed answer on the request and records its source on the contract property. Other contract properties are preserved.

If someone changes a mapped property after the signing preview was prepared, Pactly keeps that person’s edit and records a mapping conflict for review. A deleted or changed property definition also requires review. The signed document remains valid and retains the collected answer.

ProviderSupport
Pactly e-SignThe tags and property mappings in this guide
DocuSign, AdobeSign and SignWellExisting workflow translation of numbered signature and name tags, for signers 1 through 5

The additional tags and property mappings require Pactly e-Sign. Choosing another provider for a contract that uses them stops the send with an explanation. External provider settings and anchor placement still apply to their existing workflow integrations.

If the actual signer is not yet known, choose a Delivery contact in the recipient settings. The contact receives a link they can forward. The person signing enters their own name and email before filling the tagged fields. Use text fields and property mappings to collect organization details during signing. This works for manual requests and workflow sends; a delivery contact is still required, and the request must use Link only access.