3. The complete merge field list
Copy field names from here exactly. Anything not on this list will not fill in.
Recipient — who the letter is addressed to
Use these for the address block and salutation. By default these are the matter's lead client, but the fee earner can point them at any contact when generating.
Field | Example |
|---|---|
| Mrs Alexandra Smith |
| Mrs Alexandra Smith |
| Alexandra |
| Smith |
| Mrs |
| Greenfield Homes Ltd |
| Dear Mrs Smith |
| alexandra@example.com |
| +44 20 7123 4567 |
| +44 7700 900123 |
| full address, multi-line |
| their own file ref for this matter — see "The three references" below |
| 12 Baker Street |
| |
| |
| London |
| Greater London |
| W1U 3AA |
| United Kingdom |
Client — who the firm acts for
Same fields as recipient but always the lead client. Use for "we act for {{ client_name }}".
{{ client_name }} · {{ client_full_name }} · {{ client_first_name }} · {{ client_last_name }} · {{ client_title }} · {{ client_organization_name }} · {{ client_salutation }} · {{ client_email }} · {{ client_phone }} · {{ client_mobile }} · {{ client_address }} · {{ client_address_line_1 }} · {{ client_address_line_2 }} · {{ client_address_line_3 }} · {{ client_city }} · {{ client_county }} · {{ client_postcode }} · {{ client_country }}
Matter
Field | Example |
|---|---|
| SMI/LIT/2025/0021 |
| Smith v Greenfield Homes |
| |
| 16/11/2025 |
| |
| Active |
| Litigation |
| the client's own reference |
Short aliases also work: {{ reference }}, {{ title }}, {{ our_ref }}, {{ your_ref }}.
The three references — they are not the same thing
This trips people up, because all three are "a reference" and two of them are
spelled similarly. On a letter to another firm you may well need all three:
Field | Whose reference | Comes from |
|---|---|---|
| Your firm's own file reference | the matter's reference |
| Your client's reference for this matter | the matter's "client reference" field |
| The person you're writing to — their file ref, a court ref, an expert's ref | the reference recorded against that contact on this matter |
Each row lists interchangeable aliases; pick one and be consistent. The first
name in each row is the clearest to read in a template.
{{ recipient_reference }} follows whoever you pick in the Address To
column when generating, so one template works whether you're writing to the
client or to the other side. It stays blank if that contact has no reference
recorded on the matter.
Writing to the opponent's solicitor, the conventional heading is
Our ref: {{ our_ref }}/Your ref: {{ recipient_reference }}— not{{ your_ref }}, which is your own client's reference and will look wrong to
the recipient.
Firm
Field | Example |
|---|---|
| CaseConnect Solicitors LLP |
| full address, multi-line |
| 73 King William Street |
| London |
| EC4N 7BE |
| +44 20 7000 1111 |
| info@example.com |
| www.example.com |
| 8001234 |
| GB123456789 |
| 12345678 |
| trading name, if different from the registered name |
| web address of the firm's uploaded logo |
Where this data comes from: SRA number, VAT number, company number, trading name and logo are set once by a Firm Admin in Settings → Firm Settings → Branding. If one of these prints blank in a test document, the firm hasn't entered that value yet — it isn't a template problem. Ask a Firm Admin to fill it in, then regenerate.
Solicitor (the responsible fee earner)
Field | Example |
|---|---|
| Jordan Patel |
| jordan.patel@example.com |
| Jordan |
| Patel |
| +44 20 7000 1111 |
| +44 7700 900111 |
| 654321 |
Where this data comes from: the solicitor's own phone, mobile, job title and SRA number are set on their CaseConnect user profile. A user who hasn't filled these in will show a blank field — again, a data gap, not a template fault.
Other parties (the other side)
For the parties on a matter, matched by their role:
Field | Example |
|---|---|
| James Greenfield |
| |
| Alexandra Smith |
| |
| |
| |
| positional (up to 20) |
| James Greenfield, Sarah Greenfield |
| every party, comma-separated |
Each party{N}_ slot also has _email, _phone, _address, _role.
Dates and system
Field | Example |
|---|---|
| 23/07/2026 |
| 23 July 2026 |
| 23/07/2026 |
| 15:45 |