Forerunner’s record system is highly customizable. If the Record Builder is enabled for your account, manager-level users can create and modify record types directly—adding fields, configuring conditional logic, setting permissions, and more.
The Record Builder must be enabled for your account, and only manager-level users can access it. Contact your Customer Success Manager to turn on the Record Builder or to request customizations if you don’t have access.
Getting started with the Record Builder
The Record Builder lets you customize record types to match your workflows. You can:
- Create new record types - Build forms for new workflows from scratch
- Add and remove fields - Customize what information you collect
- Edit field properties - Update labels, help text, and options
- Reorder fields - Arrange fields in the order that makes sense for your team
- Configure conditional logic - Show, hide, or require fields based on responses
- Set permissions - Control who can create and view each record type
- Configure notifications - Set up email alerts when records are created
Don’t have the Record Builder enabled? Your Customer Success Manager can still help you with record customizations. Contact them to discuss your needs.
Record type versioning
When you update a record type’s form structure, Forerunner creates a new version automatically. This versioning system ensures data integrity while allowing your forms to evolve over time.
How versioning works
- Form structure updated - Fields are added, removed, or modified
- New version created - Forerunner creates a new version of the record type
- Choose what happens to existing records - You can keep existing records on their original version or update them to the new version
- New records use updated version - Any records created after the update use the new form
Benefits of versioning
| Benefit | Description |
|---|
| Historical integrity | Past records maintain their original structure and data |
| No data loss | Field removals don’t affect existing records |
| Audit compliance | Historical records remain valid for reporting and audits |
| Seamless exports | System handles different versions automatically in exports |
| Safe iteration | Make changes without worrying about breaking existing data |
When viewing older records that haven’t been updated, you’ll see the form as it existed when that record was created. This preserves the context of the original data entry.
Version considerations
When planning form updates, you can choose whether to update existing records to the new version:
- Adding fields - New fields appear on future records; if you update existing records, new fields will be empty
- Removing fields - Removed fields remain visible on existing records unless you update them to the new version
- Renaming fields - Creates a new field; existing data stays with the old field name
- Changing field types - May require creating a new field to maintain data integrity
When making changes, you’ll have the option to apply the new version to existing records or leave them on their original version.
Available field types
Records support 15+ field types to collect different kinds of information:
| Field Type | Use For | Key Options |
|---|
| Text | Short responses (names, IDs, addresses) | Character limits, format patterns |
| Text Area | Long descriptions, notes, observations | Character limits, row height |
| Number | Numeric values (costs, measurements, counts) | Min/max, decimal places, negatives |
| Number with Units | Measurements with units (feet, meters, dollars) | Available units, conversions |
| Date | Specific dates (inspection date, deadline) | Format, min/max ranges, default to today |
| Boolean | Yes/No choices (owner-occupied, in SFHA) | Default state, display style |
| Select | Single choice from list (permit type, status) | Available options, search capability |
| Multi-Select | Multiple choices (affected systems, violations) | Max selections, display style |
| Damage Degree | Standardized damage levels (for PDAs) | None, Affected, Minor, Major, Destroyed, Unknown |
| Tags | Categorization with visual styling | Predefined or free-form, colors |
| Property Attachment | Link to property in Forerunner | Required or optional, auto-populate |
| Property Market Value | Property value calculations | Source, depreciation method, percentages |
| User | Select staff member (inspector, reviewer) | Restrict by role, default to current user |
| Document Uploader | File attachments (photos, PDFs, docs) | Allowed types, file size, required/optional |
| Group | Visual section container | Collapsible, organizational only |
| Unique ID | Auto-generated reference numbers | Prefix, padding, increment rules |
File upload limits: PDFs up to 30 MB, images up to 30 MB each, videos up to 600 MB. Maximum 10 files per upload session.
Specialized field types
Some field types enable advanced functionality when used with specific modules:
Damage Degree - Updates property warnings automatically when used in PDA records. See Preliminary Damage Assessments.
Property Market Value - Enables SI/SD calculations with depreciation options. See SI/SD Tracking.
Document Uploader - Can trigger special processing for certain file types (e.g., EC PDFs are automatically extracted). See Permits and EC Submission.
Conditional logic
Record types support rules that show, hide, require, or unrequire fields based on other responses. This makes forms cleaner and reduces errors by only showing relevant fields.
Effect types
| Effect | Description | Use Case |
|---|
| SHOW | Reveal hidden field | Show flood zone fields when property is in SFHA |
| HIDE | Conceal field | Hide commercial fields for residential properties |
| REQUIRE | Make field mandatory | Require photos for major damage |
| UNREQUIRE | Make field optional | Make certain fields optional based on status |
Example rules
If "Property type" is "Commercial"
Then SHOW "Business name" and "Business license number"
If "Damage degree" is "Major" or "Destroyed"
Then REQUIRE "Photo documentation" and "Cost estimate"
If "In Special Flood Hazard Area" is "No"
Then HIDE "Base Flood Elevation" and "Flood zone"
Conditional logic makes forms cleaner by only showing relevant fields. This reduces errors and speeds up data entry.
Best practices for conditional logic
- Don’t over-complicate - Too many conditions confuse users
- Use strategically - Hide irrelevant fields, require documentation for critical decisions
- Test thoroughly - Verify logic works as expected before deploying
- Document rules - Keep a record of what conditions exist and why
Default values
Fields can auto-populate from various sources to save time and ensure consistency:
Property information - Address, parcel ID, coordinates, flood zone, property type, assessor data
User information - Name, email, phone, department, role of logged-in user
Computed values - Current date/time, calculations based on other fields, previous record data
Static defaults - Common selections, standard text, baseline values
Configure defaults in the Record Builder to match your workflow needs.
Permissions
Control who can create and view each record type:
User types
Team - Staff members in your organization who can create and update records
Guests - Members of the public who access your public website without an account
Public users - Members of the public who create accounts on your public website. Public users can be organized into user groups for more granular permissions.
Creation permissions
Configure which user types can create records of each type:
- Allow team members to create records
- Enable public submissions from guests or public users
- Restrict certain record types to specific public user groups
Visibility permissions
Team visibility - Control which team members can view records
Public visibility - Configure default visibility (public or hidden) with the option to override on individual records
Learn more about Public Sharing.
Add contextual information to guide users through the form:
Preamble - Instructions displayed at the top before fields. Use for prerequisites, important notices, or context about when to use this record type.
Postamble - Information at the bottom after fields. Use for next steps, additional resources, contact info, or disclaimers.
Success message - Custom confirmation shown after saving. Use for expected timeline, reference numbers, or what happens next.
Field help text - Guidance for specific fields. Use for explanations, examples, or format requirements.
Well-crafted guidance reduces confusion and support requests by setting clear expectations for users.
Notifications
Trigger email alerts when records are created:
Configuration options:
- Email addresses (individual or group)
- Subject line format
- Conditions for sending (based on field values)
- Whether to include record details
Example: Email permits@city.gov with subject “New Building Permit Application - [Address]” only when “In SFHA” is “Yes”
Configure notification rules in the Record Builder to match your workflow needs.
Specialized modules
Record types can include modules that add specific functionality:
| Module | Capability | Learn More |
|---|
| PDA | Automatic property warning updates based on damage degree | Preliminary Damage Assessments |
| SDE | Substantial Damage Estimate calculations with depreciation | SI/SD Tracking |
| SI/SD | Cumulative improvement/damage tracking with thresholds | SI/SD Tracking |
| EC Submission | Elevation Certificate upload, processing, and review | Permits and EC Submission |
| Mailings | Mailing and notification management | - |
Your Customer Success Manager can help configure specialized modules like Preliminary Damage Assessments, Substantial Damage Estimates, and Elevation Certificate processing to match your community’s requirements.
Object attachment options
Configure what records can attach to:
Properties only - Most common. Use for building inspections, permits, property assessments.
Custom objects only - For custom map features. Use for infrastructure inspections, asset maintenance.
Both - Records can attach to either type. Use for general inspections, complaints, work orders.
Best practices
Keep it simple - Only include fields you’ll use regularly
Consider the user - Put important fields first, use clear labels, add helpful defaults
Plan for public sharing - Some fields may need to be hidden from public view
Field naming
Use descriptive labels - “Building square footage” not “Size”
Be consistent - Use same terminology across record types
Avoid jargon - Especially for public-facing forms
Permissions
Grant appropriate access - Match permissions to roles and responsibilities
Protect sensitive data - Restrict access to confidential record types
Review regularly - Adjust as roles change
Getting help from your CSM
Your Customer Success Manager is available to help with record customization:
- Enable the Record Builder - Contact your CSM to turn on self-service customization for your account
- Specialized modules - Your CSM can help configure PDA, SDE, SI/SD, and EC processing modules to match your community’s requirements
- Complex customizations - For advanced configurations or bulk changes, your CSM can assist
- Migration support - If you need to update existing records or migrate data between field types
Don’t have the Record Builder enabled? Your CSM can still make customizations on your behalf. Contact them to discuss your needs.
