$TagName syntax and a core set of names, but each engine has its own resolver. A tag from one engine does not work in the other. This page is the full reference, organized by engine, with a column that calls out tags shared across both.
Send-time behavior differs. Contract sends are blocked if a required tag would come out blank, and are blocked if the template contains any unrecognized
$Tag. Communication templates refuse to save with an unknown tag, and any unknown tag is dropped at send time. Nothing prints as typed.License tags (both engines)
Every license type your company offers in Business Ops › Users › License Types has its own tag, and the same tags work in contracts, emails and on report covers. See Licenses and certifications.
A
$License… tag prints blank when the inspector doesn’t hold that license. In a contract, that blocks the send: an agreement that prints a $License… tag goes out only when the assigned inspector holds it. A $License… tag must match a license type exactly. A misspelt one ($LicenseTRECX) blocks a contract send and can’t be saved in an email template.
Both pickers list these under Licenses: All Licenses first, then one entry per license type your company offers.
Contracts tags
Used in agreements built in Business Ops › Contracts. Values are filled in by the Contracts send pipeline.Order fields
Reinspection only
These resolve to a value only on reinspection agreements. On any other agreement they are blank, so the tag simply disappears from the printed PDF.Inspector and company
Signature fields (double-bracket syntax)
Use these to drop a signature, date or initials block into the agreement. Single-bracket syntax is also accepted. In the Contracts Insert Tag picker these sit in the groups Signature — Client and Signature — Co-Client, each including Date and Initials. (The other groups are Order Fields, Reinspection, Inspector / Company and Licenses.)Co-client (
signer2) tags render as a “Pending Signature” box both before and after signing, because the signing step today only fills in signer1. Use co-client signature tags for agreements that need the second signer, with the understanding they stay pending.Communications tags
Used in email templates built in Business Ops › Communications › Email Templates, inserted with the Insert Variable button (contracts use Insert Tag). Values are filled in by the email send pipeline.People
Inspection and company
Refunds
For the Refund Issued trigger. Both describe the most recent refund on the inspection.Links
Manual payment handles
Quote delivery
Hidden from the picker (advanced)
Recognized by the backend but not listed in the Insert Variable picker. Available if you type them in by hand.Which tags cross engines
As a quick lookup: Only in Contracts: every fee tag ($TripFee, $InspectionFee, $BaseFee, $ServiceFee), every fee table ($TripFeeTable, $AllOrderFeesTable, $InspectionFeeTable), the schedule table ($InspectionScheduleTable), the reinspection tags, $CompanyLogo, $ContractDate, and every signature field ([[sig|...]], [[date|...]]).
Only in Communications: every agent tag ($BuyerAgent*, $ListingAgent*), every link tag ($ContractLink, $PaymentLink, $ReportLink, $AgentReportLink, $PortalLink, $ClientPortalLink, $BookingLink, $GoogleReviewLink, $YelpLink), every manual payment handle, every quote tag, the refund tags ($RefundAmount, $RefundReason), and the three hidden tags above.
Available in both: $ClientNames, $ClientFirstNames, $ClientFirstName, $ClientLastName, $Client2FirstName, $Client2LastName, $InspectionAddress, $InspectionDate, $InspectionTime, $InspectorName, $InspectorLicense, $InspectorLicenses, every $License… tag, $CompanyName.