Dispatch Incident Types: Creating and Customizing

Dispatch Incident Types: Creating and Customizing

Purpose Statement

The Dispatch Incident Types feature allows administrators to create, configure, and manage standardized incident classifications that are used throughout the Web Responder module. This functionality ensures consistent incident categorization, proper routing of alerts to appropriate personnel, and accurate reporting by linking dispatch codes to NFIRS codes and incident groups. By maintaining a structured library of dispatch incident types, departments can streamline their response workflows and maintain compliance with national reporting standards.

Background Information

Dispatch Incident Types serve as the foundation for incident classification and routing within First Due. Each incident type connects a dispatch code (used by your CAD system or dispatch center) to standardized reporting codes such as NFIRS (National Fire Incident Reporting System) and NFRS codes. For departments that have transitioned to the NERIS (National Emergency Response Information System), NERIS codes can also be assigned. This feature allows departments to control which personnel receive alerts for specific incident types through user access restrictions, ensuring that the right responders are notified for each type of emergency. Common use cases include differentiating between fire, EMS, rescue, hazmat, and service call incidents, as well as creating specialized incident types for unique departmental needs. Prerequisites include appropriate administrative permissions and familiarity with your department's dispatch codes and NFIRS/NERIS reporting requirements.

Required Permissions

To create, edit, and manage dispatch incident types, users must have the following permission:

Others Tab:  Dispatch Incident Types:

  1. Read: View Only Access
  2. Update: Edit ability to already established Dispatch Incident Types
  3. Create: Create New Dispatch Incident Types
  4. Delete: Delete any Dispatch Incident Types

Video


Directions

1. Navigate to Response Module then Click on Dispatch Incident Types.


Navigate to Response Module then Click on Dispatch Incident Types.



2. Click on New Dispatch Incident Type.


Click on New Dispatch Incident Type.



3. Fill in the following fields.
  1. Department (required)
  2. Dispatch Code (required)
  3. Name (required)
  4. Description is not required but can be used for any additional information.
  5. Complaint Reported By Dispatch Code - This dropdown will auto populate the complaint to the First Due ePCR whenever this incident type is used.






4. From the Dispatch Incident Group dropdown select what Group to associate the new incident type with.  This defines the incident icon that displays on the map


From the Dispatch Incident Group dropdown select what Group to associate the new incident type with.

Notes
INFO: The following icons represent the different Dispatch Incident Groups:

  - -- (NULL)
 - Aircraft
 - Fire
 - Hazmat
 - Law
 - MVA
 - Marine
 - Medical
 - Other
 - Rescue




5. The incident type can be associated with an NFIRS or NERIS code.


The incident type and be associated with an NFIRS code.



6. Indicate of you want this incident type to be active or inactive.






7. Selecting Limit Users allows you to limit the alerting of this Incident Type to specific users, shifts, units, stations or ranks.  The default is All System Users.






8.   After selecting a Search Group, select the users or groups of users, then select the "+" icon. The names or groups of the users allowed to receive the alert will populate under Selected Users.  Be sure to select Save.






9.  Click Create to complete the New Incident Type.





10. To edit a Dispatch Incident Type, select the Pencil Icon.





11. To delete a Dispatch Incident Type, select the Trash Can Icon.


Best Practices

Do's:

  • Align dispatch codes with your CAD system or dispatch center's coding structure
  • Use clear, descriptive names that are easily understood by all personnel
  • Select the appropriate NFIRS code to ensure accurate national reporting
  • Review and update incident types when your dispatch protocols change
  • Use incident groups to organize related incident types for easier management
  • Document the purpose and usage of each incident type in the description field
  • Regularly audit your dispatch incident types to ensure they remain current and relevant

Don'ts:

  • Don't create duplicate incident types with different codes for the same type of response
  • Don't leave dispatch incident types inactive if they are no longer used—delete them instead to avoid confusion
  • Don't restrict user access unnecessarily, as this may prevent appropriate personnel from receiving alerts
  • Don't use vague or ambiguous names that could lead to misclassification
  • Don't forget to update NERIS codes if your department has transitioned from NFIRS
  • Don't create incident types without consulting with dispatch and field operations personnel

Tips & Recommendations:

  • Coordinate with your dispatch center when creating or modifying dispatch incident types to ensure consistency
  • Use the user access restriction feature strategically for specialized teams (e.g., hazmat, water rescue, technical rescue)
  • Consider creating separate incident types for different response levels or alarm assignments
  • Test new dispatch incident types with a small group before making them available department-wide
  • Maintain a master reference document that maps dispatch codes to NFIRS/NERIS codes for training purposes
  • Export your dispatch incident types periodically as a backup and reference document
  • When transitioning to NERIS, update all existing incident types rather than creating duplicates

Troubleshooting & FAQs

Q: What is the difference between limiting access by user and making an incident type inactive?
A: Making an incident type inactive removes it from use for all users department-wide, while limiting access by user allows the incident type to remain active but restricts alerts and visibility to only selected personnel. Use access restrictions for specialized response teams; use inactive status for deprecated incident types.

Q: How do I know which NFIRS code to assign to a dispatch incident type?
A: Consult the NFIRS coding manual or your department's records management personnel to identify the appropriate NFIRS code for each incident type. NFIRS codes follow a standardized national classification system.

Q: What happens if I delete a dispatch incident type that has been used for past incidents?
A: Historical incident data that used the deleted incident type will retain that classification in records, but the incident type will no longer be available for new incidents. Consider making the incident type inactive instead of deleting it to preserve the reference in your system.

Q: Can I assign multiple NFIRS codes to a single dispatch incident type?
A: No, each dispatch incident type can only be assigned one NFIRS code. If a dispatch code could apply to multiple NFIRS classifications, create separate dispatch incident types for each NFIRS code variation.

Q: My department recently transitioned to NERIS. Do I need to create new dispatch incident types?
A: No, you can edit your existing dispatch incident types to add the appropriate NERIS codes. The NERIS code field will be available for selection once your department's transition is complete in the system.

Q: How does user access restriction affect incident alerts?
A: When user access is restricted on a dispatch incident type, only the selected users will receive alerts for incidents of that type and will be able to view those incidents in the system. This is useful for specialized teams but should be used carefully to avoid missing critical alerts.


    • Related Articles

    • Dispatch Incident List: Overview

      Purpose Statement The Dispatch Incident List within the Response module provides a comprehensive interface for viewing, filtering, creating, and managing emergency dispatch incidents. This feature allows dispatchers and administrators to track ...

    • Managing / Creating Exposure Types

      Purpose Statement This article explains how to manage and create custom Exposure Types within the Health & Wellness module. Exposure Types help categorize different types of occupational exposures for documentation and reporting purposes. Background ...

    • Dispatch Units: Create, Edit & Delete

      Purpose Statement Dispatch units within the Responder module represent the operational units that can be alerted and dispatched to emergency incidents. This feature allows administrators to create, configure, and manage dispatch units with specific ...

    • Mobile App (iOS): Creating New Incidents and Messages

      Purpose Statement The manual incident creation and messaging feature enables authorized users to create dispatch incidents and send messages to other users directly from the First Due mobile app. This functionality provides operational flexibility ...

    • Personnel Setup - Activity Types

      Purpose Statement Activity types serve as organizational categories for tracking personnel activities across incident documentation and training events. They enable departments to accurately categorize work for payroll processing, compliance ...