Skip to main content
Most objects in Forerunner come from data imports managed by your Customer Success Manager. However, you can manually create individual properties when needed, and work with your CSM to import custom objects from GIS data.

​
Creating properties

Properties can be added to Forerunner through manual creation or bulk import.

​
Creating a property manually

Create properties manually when you need to add a location that isn’t in your imported parcel data—for example, a new structure not yet in assessor records, or a location you need to track for a specific workflow.
1

Navigate to Properties

Go to the Properties table from the main navigation.
2

Click Add or Create

Select the option to add a new property.
3

Enter the address

Provide the street address. Forerunner geocodes the address to determine the location on the map.
4

Verify the location

Confirm the map pin is in the correct location. Adjust if needed.
5

Add property details

Enter any additional information available—parcel ID, owner information, or other attributes your account supports.
6

Save the property

Create the property. It now appears on the map and in the Properties table.
Manually created properties may have limited attribute data compared to imported properties. Flood zone and parcel boundary data typically require CSM assistance to populate.

​
Importing properties

Bulk property imports are handled by your CSM, typically during initial onboarding or when updating parcel data. Property data sources:
  • Parcel/assessor data - Boundaries, ownership, land use, values
  • Address databases - Geocoded locations for properties without parcel geometry
  • FEMA data - Flood zones, BFE, and FIRM panel information
When to request a property data update:
  • New assessor data is available from your jurisdiction
  • FEMA has issued new or revised flood maps
  • You need to add properties for a newly annexed area
  • Property boundaries or addresses need correction
When contacting your CSM, provide the data source or file, what’s changed since the last import, and any specific properties that need attention.

​
After creating a property

Once a property exists—whether created manually or imported—you can:
  • Attach records to track workflows
  • Upload files like photos or documents
  • Create tasks for follow-up work
  • View the property on the map

​
Creating custom objects

Custom objects are created through GeoJSON imports managed by your Customer Success Manager. This process brings geographic data from your GIS systems into Forerunner.

​
The import process

  1. Prepare your data - Export your data as GeoJSON (or Shapefile/Geodatabase for conversion)
  2. Contact your CSM - Share the file and describe what you want to track
  3. Define attributes - Work with your CSM to determine which fields to display
  4. Configure display - Specify map styling, labels, and grouping
  5. Review the import - Verify objects appear correctly on the map and in tables
  6. Attach to workflows - Start creating records against the new objects

​
What to prepare for your CSM

Source data
  • GeoJSON file with geometries and attributes
  • If using other formats, your CSM can convert from Shapefile, Geodatabase, KML, etc.
Field information
  • Which attributes should be displayed
  • User-friendly labels for technical field names
  • A unique identifier field (for matching on future updates)
Display preferences
  • Map symbology—colors, icons, or line styles
  • Which attributes to show in map popups
  • How to group with other object types (if applicable)
Workflow needs
  • What record types should be attachable
  • Who needs access to these objects
  • Whether objects should appear on the public website

​
Updating custom objects

When your source data changes, your CSM can reimport to update object attributes:
  • Existing records, files, and tasks remain attached
  • Forerunner matches objects by geometry to preserve relationships
  • New objects are added; removed objects can be handled based on your preference
Include a stable unique identifier in your source data. This helps Forerunner match objects accurately during reimports, even if geometries shift slightly.

​
Frequently asked questions

Bulk property creation requires a data import managed by your CSM. You can create individual properties manually, but large-scale additions should go through the import process.
If you create a property at an address that already exists, you may end up with duplicates. Search for the property first before creating a new one. Contact your CSM if you need to merge or remove duplicates.
Custom objects require import by your CSM. The import process sets up the object type, attributes, and map styling. Mobile data collection for custom objects may be available depending on your configuration.
Simple imports can often be completed within a few days. More complex imports with custom styling, multiple object types, or data conversion may take longer. Your CSM can provide a timeline based on your specific needs.
Deletion permissions depend on your user role and whether the object has attached records or files. Contact your CSM if you need to remove objects.