Merge fields are the parts of an agreement template that fill themselves in from each inspection — the client's name, the property address, your fee. Getting one into a template used to be a small chore.
Clicking a merge field appended it to the bottom of the agreement. Not where your cursor was — the bottom. So the real workflow was: click the field, scroll to the end, cut it, scroll back, paste it.
Now it goes in at the cursor. If you've highlighted some text first, the merge field replaces it.
{{property_address}} was indistinguishable from the sentence around it, easy to
typo into something that silently never filled in, and easy to half-delete into
{{property_addres}}.
Each merge field is now a chip showing its plain-English label:
This agreement is made between Inspector name of Company name ("Inspector") and Client name(s) ("Client") for the inspection of the property located at Property address.
You can see at a glance which parts of the document fill themselves in. A chip is a single object: one backspace removes the whole thing, and you can't accidentally break it in half.
The / command menu — the one that gives you headings, lists and dividers — now
has a Merge fields group at the bottom. Type /fee and you get the
inspection fee.
Or type { and you get just the merge fields, nothing else.
Open any template you already have and its merge fields turn into chips. Save it
and they go back out as the same {{…}} tokens they always were, so the
agreement your clients read and sign is unchanged.
One quiet fix came with this: a merge field wrapped in bold or italics used to lose that formatting when the template was re-saved, which is why the sample agreement's bolded opening paragraph would flatten out over time. It doesn't anymore.