Critical Incident Flag in Reports

• What - A new Critical Incident dropdown has been added as the final field in the Response - Dispatch section, after Alarms. The field includes blank, Yes, and No options and is also available in Workflows, Field Customization, and the Fire Doc API.
• Why - This enhancement provides a consistent, reliable way to identify critical incidents across the platform without relying on custom questions or narrative keyword searches. It also gives external health and wellness integrations a standardized data point for retrieving critical incident information.
• How
  • In the Response - Dispatch section, select a value from the new Critical Incident dropdown.
  • Use Field Customization to configure the field’s visibility and behavior based on your organization’s setup.
  • Use Workflows to create automated logic that sets or evaluates the Critical Incident value.
  • Retrieve the field through the Fire Doc API using the supported critical incident field key.
  • When no selection has been made, the API returns a null value rather than omitting the field.
  • This field is not automatically populated through narrative keyword detection and does not retroactively update historical incidents.
• Use Case - A system administrator can configure a workflow to flag qualifying responses as Critical Incident: Yes, allowing authorized external health and wellness systems to retrieve the value through the API and consistently identify personnel who may require follow-up support.

Import Command Logs into the AI Transcription Tool

• What - Users with access to the Command Module can now import authorized, time-ordered Incident Log entries directly into the AI Transcription Tool. Imported timestamps, unit actions, tactical benchmarks, assignments, and notes are processed as a transcription source to generate suggested incident report field values.
• Why - This enhancement reduces manual data entry and helps improve report accuracy by allowing information already captured during an incident to be reused without copying, pasting, or retyping it.
• How
  • Open the AI Transcription Tool and select Import Command Logs.
  • Search for an incident using available criteria such as Incident Number, Date Range, Address/Location, Unit/Apparatus, or Commanding Officer.
  • Select an incident from the results and choose Import.
  • Review the imported content in the source panel and evaluate the suggested field mappings.
  • Accept the appropriate suggestions before saving them to the incident report.
  • The Import Command Logs option is available only when the Command Module is enabled.
  • Search results are limited to incidents within the user’s agency and existing permissions.
  • Imported suggestions are not automatically saved to the report.
• Use Case - After an incident, a user can import Command Module logs containing alarm and arrival times, responding units, tactical benchmarks, command assignments, actions taken, and key event notes. The AI Transcription Tool analyzes the imported entries and suggests values for relevant report fields, allowing the user to review and accept the information with less manual entry.

Ingest Historical NERIS Records

• What - Administrators can now import historical NERIS records into First Due through an admin setting. Each successfully imported record is created as a distinct fire incident report and appears in the incident list alongside existing records.
• Why - This enhancement helps organizations centralize historical and current incident data in First Due, providing a more complete record of past activity and allowing imported incidents to be accessed through existing reporting and operational workflows.
• How
  • Open the applicable Admin Settings area for historical NERIS record imports.
  • Start the import to retrieve available historical NERIS records through the API.
  • Review the import output to identify records that were imported successfully and records that could not be imported.
  • Imported records appear in the standard incident report list as individual fire incident reports.
  • Custom questions are not supported as part of the historical record import.
• Use Case - When an organization transitions to First Due after previously submitting incident data directly to NERIS or through another system, an administrator can import its historical NERIS records so users can view and work with past incidents in the same location as newly created reports.

Enabling Historical Data Access adds a Historical Fire Incident Import subsection under Incident Documentation, where administrators can import historical fire incident records.

Expanded Parent/Child Workflow Hierarchies

• What - Parent and child workflow inheritance has been expanded beyond Canada-specific configurations to support U.S. and other non-Canadian environments using jurisdiction and reporting-standard compatibility rules. The hierarchy now also supports a third level, allowing eligible deployment-level clients to inherit workflows from another deployment-level parent when the higher-level parent is configured as State Level.
• Why - This enhancement provides a more flexible and consistent way to manage shared workflows across multi-level organizations while preventing incompatible clients from being linked. It also preserves existing Canadian relationships while extending the same hierarchy capabilities to additional jurisdictions and reporting standards.
• How
  • Parent eligibility is also evaluated using applicable jurisdiction and reporting-standard compatibility rules.
  • Existing Canadian parent and child relationships remain supported.
  • The State Level setting is used to control which deployment-level clients can serve as the top level of a three-level hierarchy.
• Use Case - A local client can inherit workflows from a regional deployment client, while that regional deployment client inherits workflows from a state-level deployment account. This allows workflows to be managed across local, regional, and state levels while ensuring that each relationship is compatible with the client’s jurisdiction and reporting standard.