Simultaneous State Repository and NERIS Incident Data Submission (New Feature)

• What - Incident data can now be submitted to both NERIS and an enabled State Repository at the same time. For state-required fields that are not part of NERIS, organizations can map those fields to existing Custom Questions, allowing the response entered for the Custom Question to be included in the appropriate State Repository field.
• Why - State reporting requirements may include information that is not collected as part of the standard NERIS dataset. This feature allows those additional requirements to be supported through Custom Questions while keeping NERIS and State Repository reporting within a single incident submission process.
• How
  • Contact your Client Success Manager or Implementation Manager to have the appropriate State Repository enabled and configured for your organization.
  • Once enabled, navigate to Setup > Field Export Management.
  • Use Field Export Management to map applicable non-NERIS State Repository fields to Custom Questions that have already been created.
  • When a user answers a mapped Custom Question, that response is used for the corresponding State Repository field.
  • Once configuration is complete, submitting the incident sends the applicable data to NERIS and the State Repository as part of the same submission process.
• Use Case - An organization has a state-required incident field that is not included in NERIS. The organization creates a Custom Question to collect the required information and maps that question to the appropriate state field in Field Export Management. When the incident is completed and submitted, the Custom Question response is included in the State Repository submission while the incident is also submitted to NERIS.

Custom Questions Now Inherited from Parent to Child Configurations (New Feature)

What - Agencies can now inherit Custom Questions from a parent configuration down to child configurations, similar to how workflow inheritance already functions. The inherited Custom Questions appear as a read-only list within the child's NFIRS Settings under the Parent Setting section.

Why - Managing consistent data collection across multiple configurations can be time-consuming when settings must be manually duplicated. Allowing Custom Question inheritance ensures child configurations automatically reflect the standards set at the parent level, reducing administrative overhead.

How
- This feature extends the existing parent-to-child inheritance model to include Custom Questions
- Navigate to NFIRS Settings in the child configuration
- Locate the Parent Setting section
- View the inherited Custom Questions from the parent — this list is read-only and reflects the ancestor's configuration
- Custom Question workflows from ancestor configurations are now included in inheritance, which were previously excluded
- Note: Inherited Custom Questions cannot be modified at the child level; changes must be made at the parent configuration

Use Case
- A agency managing multiple child configurations can define Custom Questions once at the parent level and have them automatically apply across all child configurations without manual re-entry.
- An administrator reviewing a child configuration can quickly verify which Custom Questions are inherited from the parent by viewing the read-only list in NFIRS Settings.
- A new child configuration automatically receives the parent's established Custom Questions, ensuring data collection consistency from the moment it is set up.

Incident Location Tool Validation and Boundary Configuration (New Feature)

What – System Administrators can now configure validation rules and geographical boundary constraints within the Incident Location Tool to control how location data is submitted. This ensures only valid, in-bounds addresses are accepted during incident reporting.

Why – Agencies need confidence that location data meets quality standards, and without enforced validation, invalid or out-of-bounds submissions can compromise data integrity and response accuracy.

How
- This feature introduces two configurable components within the Incident Location Tool settings available to System Administrators
- Navigate to the Incident Location Tool configuration in your system administration settings
- Enable Require Validation of Address via Location Tool to enforce that submitted addresses are verified before acceptance
- Configure Geographical Boundary Enforcement to define the spatial limits within which location submissions are considered valid
- Save your configuration to apply the validation rules agency-wide
- Once enabled, users submitting incident locations outside defined boundaries or with unverified addresses will be prevented from proceeding until a valid location is provided

Use Case
- A dispatcher attempting to log an incident with an unrecognized address is prompted to correct the entry before the record can be saved.
- A field user submitting a location that falls outside the agency's configured geographical boundary receives an alert and must select a valid location.
- An administrator reviewing data quality notices a reduction in invalid location entries after enabling boundary enforcement across the agency.

Configurable Additional CAD Data Section in Fire Reports (New Feature)

 
What – A new Additional CAD Data section can now be configured within Fire Reports, allowing agencies to expose CAD-populated fields that fall outside of standard CAD mapping. This provides a flexible way to capture and display supplemental CAD information directly within a report.
 
Why – Not all CAD systems map data to standardized fields, leaving some information inaccessible within Fire Reports. This enhancement gives agencies the ability to opt into displaying non-standard CAD fields, ensuring critical incident data is visible and usable without requiring custom development.
 
How 

• This section is configurable at the agency level and must be enabled before it will appear in Fire Reports
  • Navigate to the Fire Reports configuration settings
  • Locate the Additional CAD Data section option
  • Enable the section and select the CAD-populated fields to be displayed
  • Save the configuration — the section will now appear in applicable Fire Reports
• Only fields available through your agency's CAD integration will be eligible for display in this section

 
Use Case 

• An agency that receives caller name data from CAD can now surface that information directly within a Fire Report without manual entry.
• An agency that tracks a unique event identifier from their CAD system can configure that field to appear in reports for easier cross-referencing.
• A supervisor reviewing an incident report can access supplemental CAD data in one place without needing to reference a separate system.