Overview
Browse all articles

Merge fields in your own documents

Every {{merge_field}} you can use in a custom document, what each one fills in, and why an unknown one is rejected.

Updated July 31, 2026ForSolo creatorsProducers & studios
On this page

A custom document is an HTML document with placeholders in double curly braces. When a performer opens it, each placeholder is swapped for that performer's real details, so one document serves everyone you send it to.

Custom documents are sent in addition to the standard ones. The Personal Identifying Worksheet and Model Release always go out.

How a placeholder works

Write the field name in double curly braces, lowercase, with underscores:

  • <p>This agreement is between {{producer_name}} and {{talent_legal_name}}.</p>
  • <p>Signed: {{SIGNATURE}} on {{DATE}}</p>

At signing time that becomes the producer's company name, the performer's legal name, their signature image, and the date.

The three special placeholders

These are not filled from your records. They are handled at the moment of signing.

PlaceholderWhat it does
{{SIGNATURE}}Where the signature image is placed. Every document needs at least one, or there is nowhere to sign and the upload is rejected. Use it more than once and the same signature image appears at each spot.
{{DATE}}The date the document is signed.
{{INITIALS}}An initials box, taken from the signer's name. For several boxes in one document, name each one: {{INITIALS:section1}}, {{INITIALS:section2}}.

Producer and custodian

FieldFills in
{{producer_name}}Your company name, falling back to your account name
{{custodian_name}}Your custodian of records name
{{custodian_address}}Your custodian of records address

The performer

FieldFills in
{{talent_legal_name}}First, middle and last name together
{{talent_first_name}}First name
{{talent_middle_name}}Middle name
{{talent_last_name}}Last name
{{talent_maiden_name}}Maiden name
{{talent_stage_name}}Stage name
{{talent_aliases}}Any other names on file
{{talent_dob}}Date of birth
{{talent_age}}Age, worked out from date of birth
{{talent_email}}Email address
{{talent_phone}}Phone number
{{talent_address}}Address

The production and scene

FieldFills in
{{production_title}}Production title
{{scene_number}}Scene number
{{scene_title}}Scene title
{{production_date}}Scene date
{{production_location}}Scene location
{{participant_role}}How this person is credited on the scene

The identity document

These come from the ID the performer verified with.

FieldFills in
{{id_type}}Kind of ID, such as a driver's licence or passport
{{id_number}}ID number, masked to the last four characters
{{id_issuing_state}}Issuing state
{{id_issuing_country}}Issuing country
{{id_expiration}}Expiry date

What happens if a field is empty

A placeholder whose record is blank renders as nothing at all. If your document says Stage name: {{talent_stage_name}} for a performer with no stage name, the line prints as Stage name: with nothing after it. Where that would read badly, keep the detail in a sentence that still makes sense when it is absent, or use a field you know is always filled in, such as {{talent_legal_name}}.

Which HTML survives

Documents are cleaned on upload, and you are shown what was removed. What is kept is the plain document furniture:

  • Text and structure: p, br, hr, div, span, h1 to h6
  • Emphasis: strong, b, em, i, u, s, sub, sup, small
  • Lists and quotes: ul, ol, li, blockquote, pre, code
  • Tables: table, thead, tbody, tfoot, tr, td, th, caption, colgroup, col

Scripts, styles and embedded frames are removed along with their contents. Links and images are removed too: a signed contract has no business fetching anything from elsewhere, and a document that changes after signing is not evidence of what was agreed.

Before it reaches anyone

Every custom document is reviewed before a performer sees one. Upload it, and it sits in your list until that review is done.

Still stuck?

Tell us what you were looking for and we will work it out with you.

Contact support