Custom Document Templates
Upload your own Word document templates with Carbone tokens for automated document generation.
AwardLettr ships templates for award letters, panel declarations, reports, and invoices. But your business runs on more than those four documents. You have engagement letters, status update letters, demand letters, retention agreements, certified mail cover sheets, and a dozen other Word files you have refined over years and want to keep using.
Custom templates let you upload those Word documents directly. You add Carbone tokens like {d.insuredName} where data should drop in, upload the .docx once, and from then on you generate filled-out PDFs from any case in two clicks. No retyping, no copy-paste errors, no maintaining a separate folder of "master" Word files you have to keep in sync.
This article shows you how to author the tokens, upload the template, generate documents, and (if applicable) wire up e-signature fields. The token reference at the bottom is the lookup table you will come back to whenever you author a new template.
How It Works
Create Your Template
Design a Word document (.docx) and insert Carbone tokens where you want dynamic data. For example, type {d.insuredName} where you want the insured's name to appear.
Upload to AwardLettr
Go to Settings > Document Templates and click "Upload Your Own". Drop your .docx file and give it a name.
Generate Documents
On any appraisal, click Generate Document and select your custom template from the "Custom Templates" section. AwardLettr replaces all tokens with the appraisal's data and creates a PDF.
Available Tokens
Use these tokens in your Word document. Each token must be wrapped in curly braces with the {d.} prefix.
Claim Information
| Token | Description | Example Output |
|---|---|---|
| {d.claimNumber} | Claim number | CLM-2026-001 |
| {d.policyNumber} | Policy number | POL-123456 |
| {d.insuredName} | Insured's full name | John Smith |
| {d.dateOfLoss} | Date of loss (short) | 01/15/2026 |
| {d.dateOfLossLong} | Date of loss (long) | January 15, 2026 |
| {d.lossLocation} | Full property address | 123 Main St, Houston, TX 77001 |
| {d.propertyStreet} | Street address | 123 Main St |
| {d.propertyCity} | City | Houston |
| {d.propertyState} | State | TX |
| {d.propertyZip} | ZIP code | 77001 |
Carrier & Adjuster
| Token | Description |
|---|---|
| {d.carrierName} | Insurance carrier name |
| {d.carrierAddress} | Carrier address |
| {d.adjusterName} | Assigned adjuster name |
Parties
| Token | Description |
|---|---|
| {d.insuredAppraiserName} | Insured appraiser name |
| {d.insuredAppraiserEmail} | Insured appraiser email |
| {d.insuredAppraiserPhone} | Insured appraiser phone |
| {d.carrierAppraiserName} | Carrier appraiser name |
| {d.carrierAppraiserEmail} | Carrier appraiser email |
| {d.carrierAppraiserPhone} | Carrier appraiser phone |
| {d.umpireName} | Umpire name |
| {d.umpireEmail} | Umpire email |
| {d.umpirePhone} | Umpire phone |
Dates
| Token | Description |
|---|---|
| {d.assignmentDateLong} | Assignment date (long format) |
| {d.inspectionDateLong} | Inspection date (long format) |
| {d.invoiceDate} | Invoice date |
Your Information
| Token | Description |
|---|---|
| {d.userName} | Your full name |
| {d.userTitle} | Your title |
| {d.userCompany} | Your company name |
| {d.userPhone} | Your phone number |
| {d.userEmail} | Your email address |
Business Branding
| Token | Description |
|---|---|
| {d.businessName} | Business/firm name |
| {d.businessAddress} | Business street address |
| {d.businessCity} | Business city |
| {d.businessState} | Business state |
| {d.businessZip} | Business ZIP code |
| {d.businessPhone} | Business phone |
| {d.businessEmail} | Business email |
| {d.businessWebsite} | Business website |
| {d.logoUrl} | Company logo (image) |
| {d.remitInstructions} | Remittance instructions (e.g. "Make checks payable to…") |
Award Values
| Token | Description |
|---|---|
| {d.totalRcv} | Total replacement cost value |
| {d.totalAcv} | Total actual cash value |
| {d.nonRecoverableDepreciation} | Non-recoverable depreciation |
| {d.recoverableDepreciation} | Recoverable depreciation |
| {d.acvClaimPayable} | ACV claim payable amount |
Conditional Flags
| Token | Description |
|---|---|
| {d.has_umpire} | True if umpire is assigned (for conditional sections) |
| {d.has_award_items} | True if award items exist |
Signature Fields
If you plan to send your custom document for e-signature, include these token pairs where you want signatures to appear. When you upload the template, toggle on "This document will be sent for signature" and AwardLettr will verify the tokens are present. The signature text will be invisible in the final PDF — your e-signature provider replaces them with actual signature boxes.
| Signature Token | Date Token | Signer |
|---|---|---|
| {d.insuredSignature} | {d.insuredDate} | Insured (homeowner) |
| {d.carrierAppraiserSignature} | {d.carrierAppraiserDate} | Carrier Appraiser |
| {d.insuredAppraiserSignature} | {d.insuredAppraiserDate} | Insured Appraiser |
| {d.umpireSignature} | {d.umpireDate} | Umpire |
Always include both tokens
Tips
- Use Word's Find & Replace (Ctrl+H) to quickly add tokens throughout your document.
- Test your template on a sample appraisal first to verify all tokens render correctly.
- Tokens are case-sensitive — {d.insuredName} works, but {d.InsuredName} does not.
- If a token has no data for a particular appraisal, it will render as an empty string.
- AwardLettr automatically fixes tokens that Word splits across formatting runs.
Troubleshooting
Tokens Not Being Replaced?
Related Articles
Data Tables: Repeating Sections in Your Templates
Define per-appraisal tables (comparison rows, weather events, roof slopes) that loop in your Word templates with auto-totaled currency columns.
Narrative Snippets: Reusable Boilerplate Prose
Define reusable paragraph templates with embedded tokens. Write the boilerplate once, fill it per appraisal, ship it in any number of Word templates.
Computed Defaults: Auto-Fill Custom Fields
Make a custom field auto-compute its value from a Data Table cell or by aggregating other custom fields. The user can still type a value to override.