2. The exact syntax — read this twice

✅ Correct:

{{ client_name }}
{{ matter_reference }}
{{ firm_address }}

❌ Wrong — these will NOT work:

Wrong	Why it fails
`<<CLIENT_NAME>>`	Angle-bracket codes are not the generation syntax. They will print literally.
`{{ client.name }}`	Dotted names do not work. Use an underscore: `{{ client_name }}`.
`{{client_name}}`	This works, but always put a single space inside the braces for readability: `{{ client_name }}`.
`{{ Client_Name }}`	Field names are lowercase.
`{ client_name }`	Single braces do nothing. You need two on each side.

Where to copy field names from — and one trap. The safest source is Settings → Merge Fields in CaseConnect: click any field and it copies the correct {{ field_name }} straight to your clipboard. If you insert fields using the Word add-in panel, it also inserts the correct {{ token }} for you. Do NOT hand-type from the CSV/PDF export of the field directory — that export currently lists the old <<CODE>> form, which does not work. Always translate <<CLIENT_NAME>> to {{ client_name }} (lowercase, underscores, double braces).

Typing braces in Word — avoid the #1 mistake

Word's AutoCorrect and AutoFormat can silently break merge fields:

Smart quotes / special characters: braces themselves are fine, but if you copy fields from a web page or email, hidden formatting can come with them. Type the braces manually or paste as plain text (Ctrl+Shift+V).
Do not let a field get split across formatting. If half of {{ client_name }} is bold and half isn't, Word stores it as fragments and the field won't be recognised. The safest habit: type the whole field in one go, in normal formatting, then apply formatting to the whole field afterwards.
Check for stray spaces inside the name: {{ client _name }} (space in the middle) will fail.

Golden test: after building a template, upload it and generate one test document. If a field prints as literal {{ something }} text in the output, that field name is either misspelled or not in the list below.