Placeholders

Placeholders are the template's merge fields. Named slots in the document that fill with real data at send time. {{company_name}} in the template becomes "Acme Ltd" on the envelope.

What placeholders do

• Personalize the document. Names, dates, amounts, and terms injected before signing, so the signer sees their finished agreement, not a form letter.
• Feed bulk send. Each spreadsheet column maps to a placeholder; bulk send produces envelopes with every row's data baked in.
• Drive agreement actions, CLM actions fill placeholders from the signed agreement's own field values, a signed order form auto-creates the onboarding envelope with the client's name already inside.

Defining placeholders

In the template builder, a placeholder is inserted as a named token. Give placeholders stable, descriptive names. They are the contract between your template and whatever fills it:

• Bulk-send spreadsheets map columns → placeholder names.
• Agreement actions map source field → placeholder name.
• Manual sends show a fill-in prompt per placeholder before the envelope is created.

Placeholders vs signing fields

• A placeholder fills before sending. The value comes from you (or a spreadsheet, or an upstream envelope) and is fixed in the document.
• A signing field fills during signing. The value comes from the recipient.

Use placeholders for what you already know (the client's name, the quoted price); use fields for what the signer must provide (their signature, their start date choice).

Empty placeholders

A placeholder without data at send time stays empty in the document. The send flow warns about unfilled placeholders so a {{salary}} never silently reaches a signer as a blank.