Skip to main content

Search

Knowledge Center

Responder: Dispatch Incident List

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 incident history, create custom views, initiate new dispatches, and maintain accurate incident records with flexible filtering and organizational capabilities.
 

Background Information

The Dispatch Incident List serves as the central hub for incident management, displaying dispatches based on configurable timeframes and criteria. By default, the system shows dispatches from the last 90 days, but users can create custom views with specific filters, column arrangements, and sharing permissions. This functionality is essential for dispatch operations, incident tracking, reporting, and maintaining operational awareness. The interface supports both viewing historical incidents and creating new dispatch entries with proper location validation and unit assignment capabilities.
 

Required Permissions

These permissions are located in the Others- Others Section of Permissions:
 
  1. Dispatch Items Read--Allows user access to the Dispatch Incident List section in a read only status.
  2. Dispatch Items Update--Allows user to update Dispatches within the Dispatch Incident List.
  3. Dispatch Items Create--Allows user to create Dispatches within the Dispatch Incident List..
  4. Dispatch Items Delete--Allows user to delete Dispatches within the Dispatch Incident List..

Video

Step-by-Step Guide

1. Navigate to Response module then select Dispatch Incident List.
 

 
2.  The default Dispatch Incident List is displayed at the top left. Each list has a unique corresponding Filter.
  1. A.  The Filters for this corresponding list are available by selecting Filter at the top right.
     
  2. B. The Filter can be pinned in the open position using the Thumbtack icon or closed using the 'X' icon.
     


 
3. Columns can be rearranged, as well as sorted in ascending, descending and default order.
 

 
4. To select other views, select the dropdown and then choose from the list.
 

 
5. To create a custom view, select the kabob menu and then either +Add View or Clone.
 

 
6.  Enter the Desired name for the view, then choose the Columns to display in the new View and then select the right arrow to move them to the selected columns. To remove them from the Selected Columns select them and choose the left arrow.

 
7. The columns can be reordered by dragging and drop them in the desired order. Additionally, the default primary column sort order can be chosen as well as a secondary column sort order.
 

 
8.  The Filter menu can also be customized by choosing from the following options within the Allow Filtering By:
 
  1. Dispatch Units
  2. Result
  3. Initial Address
  4. Full Message
  5. Create Date
  6. Status
     

 
9.  Criteria can also be selected to further refine the custom View.
 

 
10.  The new custom view can also be marked as private (Only Me), shared with Everyone or Selected Users. IF Everyone or Selected Users is chosen the "allow other user to apply changes to this view" becomes available.
 

 
11.  If Selected Users is chosen, pop-up window will appear where the the selected user can be chosen from All Users, Ranks or Roles. 
 


 
12. Lastly the default pagination can also be chosen for the new View.
 

 
13.  The new list will now appear in the Custom Views list. Any view can be marked a Favorite by selecting the Star icon or pinned by selecting the Thumbtack Icon.

 


 
14.  Based on permissions, a User may have the ability to Edit and/or Delete a Custom View.
 

 
 
15.  To create a dispatch select the Add Dispatch Button.
 

 
16.  In the New Dispatch window the following sections will need to be completed:
 
  1. 16A.  Select the department (Generally there is only one choice).
     
  2. 16B.  Select the Dispatch Type Code and enter the Dispatch Type. (if Configured Correctly, the Dispatch Type will automatically populate based on the Dispatch Type Code.
     
  3. 16C.  Select the responding units from the dropdown menu.
     
  4. 16D.  Enter the Call Notes.
     

 
17.  To complete the New Dispatch, the following sections will need to be completed:
 
  1. 17A.  Enter the Incident Address. Using the Place area will ensure that the address is matched to an addressed contained within First Due. 
     
  2. 17B.  If no address can be matched, the address can be placed the Address Line 1.
     
  3. 17C.  Choose the status of the dispatch at the time of creation (Open/Closed).
     
  4. 17D.  Choose to create or not create an NFIRS Notification. (Only available if the department is utilizing the Incident Documentation Module).
     
  5. 17E.   Select Create. 

 

 
18.   To Edit an Incident select the Pencil Icon and to Delete and incident select the Trash Can Icon.
 
 

 

Best Practices

Do's

  • Use the FirstDue address search function first for accurate location data
  • Create custom views that align with operational workflows and reporting needs
  • Share useful custom views with appropriate team members
  • Use descriptive names for custom views to ensure clarity
  • Regularly review and update custom view criteria to maintain relevance
  • Enter comprehensive call notes for better incident documentation

Don'ts

  • Don't manually enter addresses without first searching FirstDue's address database
  • Don't create unnecessary custom views that duplicate existing functionality
  • Don't share sensitive views with unauthorized personnel
  • Don't delete incidents without ensuring they're no longer needed for reporting
  • Don't skip essential dispatch information like unit assignments or incident type
  • Don't overlook the incident status setting which affects workflow

Tips & Recommendations

  • Coordinate with dispatch personnel when creating department-wide custom views
  • Use filtering options to focus on specific time periods or incident types for analysis
  • Consider creating views for different operational roles (dispatcher, supervisor, administrator)
  • Test custom views thoroughly before sharing with large groups
  • Document custom view purposes and criteria for training and reference
  • Regularly audit dispatch incident accuracy for quality control

Troubleshooting & FAQs

Q: Why can't I see the edit or delete options for custom views? 
A: These options only appear if you have the proper permissions and if you own or have modification rights to the view.

Q: What happens if I delete a dispatch incident? 
A: The incident is permanently removed from the system and cannot be recovered. Ensure you have proper authorization and backup if needed.

Q: Why doesn't my dispatch type auto-populate when I select a code? 
A: Auto-population requires proper configuration between dispatch type codes and dispatch types. Contact your system administrator if this isn't working.

Q: Can I modify a custom view that someone else shared with me? 
A: Only if the view creator enabled "allow others to make changes" when sharing the view.

Q: Why don't I see the incident report creation option? 
A: This option only appears if your department utilizes the Incident Documentation module. Contact your administrator about module availability.

Q: How do I know if an address is in the First Due database? 
A: Use the address search function first - it will show matches from the First Due database. If no matches appear, the address isn't in the system.