How document generation works
Document generation uses document templates — PDF files with smart fields that map to Forerunner data. When you generate a document, Forerunner fills in the mapped fields with data from the selected property or record and saves the result as a new file.| Concept | Description |
|---|---|
| Document template | A PDF with smart fields (form fields) that map to Forerunner data |
| Smart fields | Fillable fields in the PDF that Forerunner populates automatically |
| Field mapping | The connection between a PDF smart field and a Forerunner data field |
| Generated document | The final PDF with all fields filled in, saved as a file |
Generating a document
You can generate documents from the property information panel or directly from records.From a property
Open the property
Start document generation
Select a template
Create the document
From a record
Open the record
Start document generation
Available fields for mapping
Document templates can pull from a wide range of Forerunner data. Below are the field categories available for mapping into your PDF smart fields.General fields
These fields are available on every template regardless of object type.| Field | Description | Example value |
|---|---|---|
| Today’s date | Current date when the document is generated | March 27, 2026 |
| Account name | Your organization’s name in Forerunner | City of Springfield |
| Community number | Your NFIP community number | 120345 |
| Community name | Your community’s official name | Springfield, City of |
Property fields
Available when the template is configured for properties.| Field | Description | Example value |
|---|---|---|
| Property address line 1 | Street address | 123 Main Street |
| Property address line 2 | Additional address info (unit, suite) | Unit 4B |
| SI/SD percentage | Cumulative substantial improvement progress | 45% |
| SI/SD value | Total improvement value | $52,000 |
| Full assessed value | Total property assessed value | $185,000 |
Property attributes
Any custom property attributes configured for your account are also available for mapping. These appear grouped by their section and include attributes sourced from custom maps or raster data layers. Example: If your account tracks “First Floor Elevation” as a custom property attribute, you can map it directly into a flood zone determination letter alongside the base flood elevation from FIRM data.Parcel data fields
Parcel data imported into Forerunner is available for mapping. The specific fields depend on your account’s parcel import configuration.| Field | Description | Example value |
|---|---|---|
| Owner name | Property owner from parcel records | Jane Smith |
| Mailing address 1 | Owner’s mailing address | 456 Oak Avenue |
| Mailing address 2 | Additional mailing address line | PO Box 789 |
| Parcel ID | County parcel identifier | 12-34-567-890 |
| Land value | Assessed land value | $75,000 |
| Improvement value | Assessed improvement value | $110,000 |
| Parcel value | Total parcel value | $185,000 |
| Year built | Structure year built | 1985 |
| Legal description | Legal property description | LOT 4 BLK 2 SPRINGFIELD HEIGHTS |
| Lot | Lot number | 4 |
| Block | Block number | 2 |
| Building description | Property building description | Single Family Residential |
Flood Insurance Rate Map (FIRM) fields
Flood zone data from FIRM panels is available for mapping. Fields are available for your regulatory FIRM and any additional FIRMs enabled in your account (effective, preliminary, or custom).| Field | Description | Example value |
|---|---|---|
| Panel effective date | Date the FIRM panel became effective | January 15, 2024 |
| Panel number | FIRM panel number | 12001C0125F |
| Base flood elevation | Static BFE value | 12.5 |
| Design flood elevation | DFE value (regulatory FIRM only) | 14.5 |
| Flood zone | Flood zone designation | AE |
| Datum | Elevation datum | NAVD88 |
| SFHA determination | Whether property is in a Special Flood Hazard Area | In SFHA |
| In SFHA checkbox | Boolean for SFHA status (checked if in SFHA) | ✓ |
| Out SFHA checkbox | Boolean for non-SFHA status (checked if outside SFHA) | ✓ |
| Screenshot | Map screenshot of the FIRM panel area | (image) |
Record fields
When a template is linked to a specific record type, all fields from that record’s form are available for mapping. This includes text fields, boolean fields (checkboxes), and image fields (document uploads). The specific fields depend on the record type’s form configuration. For example, a permit record type might expose fields like permit number, issue date, expiration date, and permit status. Example: A “Permit Issuance Letter” template linked to your permits record type could map the permit number, issue date, and permit conditions directly from the record, combined with property address and owner name from the property and parcel data.Custom map object fields
When a template is configured for a custom map object type (instead of properties), you can map the object’s label and any additional fields defined on that custom map. Example: If you maintain a stormwater infrastructure map, you could generate inspection notice letters that pull the infrastructure asset’s label and custom attributes into the document.Sending mail
After generating a document, you can send it as physical mail directly from Forerunner.Select a submission type
Configure mailing options
| Option | Choices |
|---|---|
| Postage type | USPS Standard, USPS First Class, or USPS Certified |
| Paper size | U.S. Letter |
| Print in color | Yes or No |
| Double-sided | Yes or No |
Mailing status tracking
Each mailing record tracks the letter’s delivery status:- In production — Letter is being printed and prepared
- Mailed — Letter has been sent
- In transit — Letter is moving through the postal system
- Processed for delivery — Letter is at the local post office
- Delivered — Letter has been delivered
Setting up document templates
Document template creation and configuration is managed by the Forerunner team. To set up a new template or modify an existing one, reach out to your Forerunner point of contact. When requesting a new template, it helps to provide:- The PDF form you want to use as a template (with smart fields / fillable form fields already added)
- Which object type the template should apply to (properties or a specific custom map)
- Which record type generated documents should be associated with
- A description of which Forerunner fields should map to which PDF fields
Common use cases
Annual flood zone notification letters
Annual flood zone notification letters
Substantial improvement / substantial damage notices
Substantial improvement / substantial damage notices
Permit reminder notices
Permit reminder notices
Flood zone determination letters
Flood zone determination letters
Public hearing notices
Public hearing notices
Best practices
Review generated documents before sending
Review generated documents before sending
Use certified mail for compliance documentation
Use certified mail for compliance documentation
Generate from records when possible
Generate from records when possible
Check mailing options before sending
Check mailing options before sending
Frequently asked questions
What data can I use in document templates?
What data can I use in document templates?
Can I edit a generated document?
Can I edit a generated document?
What happens if property data changes after I generate a document?
What happens if property data changes after I generate a document?
How do I get a new template set up?
How do I get a new template set up?
Can I use document generation with custom map objects?
Can I use document generation with custom map objects?
How do I track whether a mailed letter was delivered?
How do I track whether a mailed letter was delivered?
Can I generate documents in bulk?
Can I generate documents in bulk?