Skip to main content

Search

Knowledge Center

Command: Incident Command List

Purpose Statement

The Incident Command List provides a centralized view of all incident commands in your system, enabling users to search, filter, manage, and access incident command boards efficiently. This feature streamlines incident management by allowing users to start new commands, access existing commands, archive completed incidents, and download commands for offline use.

Background Information

The Incident Command List serves as the main hub for incident command operations within First Due's Response module. This feature is essential for managing multiple incidents simultaneously, tracking command status, and maintaining organized records of both active and historical incident commands. Users can view commands across their agency or filter to specific incidents based on multiple criteria. The list interface supports both online and offline operations, making it valuable for field personnel who may need to access incident information in areas with limited connectivity.

Required Permissions

Users must have the appropriate level of the Incident Commands permission configured in their role:

  • Read: View command boards in read-only mode
  • Update: Modify command board settings and information
  • Create: Initiate new command boards and add custom items
  • Delete: Remove command board elements and complete incidents
📝

Important Note:

Users can Access Incident Commands in read-only mode even if they are not assigned as the command board user for that specific incident.

Video

Step-by-Step Guide

 

Access the Incident Command List

  1. Navigate to the Main Menu.
  2. Select Responder Module.
  3. Select Incident Command List.

 

Search and Filter Incident Commands

  1. Use the search and filter area at the top of the list.
  2. Search using the following data points:
    • Name
    • Address
    • Dispatch Type
  3. Apply optional filters:
    • Archived
    • Agency
  4. Select Reset to clear all search criteria.

Note: Searches utilize fuzzy search functionality.

 

 

Customize the Incident Command List Display

  1. Select the Column Display option.
  2. Configure visible columns as needed.

     
  3. Rearrange columns by dragging them. Resize columns. Sort columns in:
  4. Ascending order
  5. Descending order
  6. Default order

 

Understand Incident Command Action Icons

Play Icon

The Play Icon indicates:

  • The incident command is active.
  • The logged-in user is the assigned command board user.

Selecting the icon opens the command board with full command access.

 

Eye Icon

The Eye Icon indicates one of the following:

  • The incident command board is active, but the logged-in user has read only access.
  • The incident command board is archived or inactive and read only for all users.

Selecting the icon opens the command board in read only mode.

 


 

Cloud Icon

The Cloud Icon allows the user to download the incident command board for offline use.

Once downloaded:

  • The icon changes to indicate successful synchronization.
  • The command board is stored in the device’s local cache.

Important offline behavior:

  • Other users cannot view updates made while offline.
  • Actions performed offline remain local until synchronized.
     

 

Re-Synchronize an Offline Command Board

  1. Select the synchronization icon.
  2. The command board updates the locally cached version.

 

Remove an Offline Command Board

  1. Select the remove cache icon.
  2. Confirm removal from the local cache.
 

Archive an Incident Command

  1. Select the File Box Icon.
  2. Confirm the archive action.

The command board becomes archived and read only.

 

Delete an Incident Command

  1. Select the Trash Can Icon.
  2. Confirm deletion.

Note: Deletion permanently removes the incident command board.

 

Bulk Delete Incident Commands

  1. Select multiple incident command boards.
  2. Select the Bulk Trash Can Icon.
  3. Confirm deletion.


 

Create a New Incident Command

  • Select Create New Command.

     

A.  From the dropdown list, select the dispatch you want to create the incident command from. All active dispatches available in your system will appear in this list.

B.  Modify the incident name if desired.

C.  Select the appropriate template for this incident command from the template dropdown.

D.  Select "Create" to finalize the new incident command and he new incident command will now appear in your Incident Command List.
 


 
 

9. Exporting Data

  1. At the bottom of the page, use the pagination controls to navigate through multiple pages of incident commands.
     

  1. To export the currently viewed list, select either the CSV or Excel file format download option at the bottom of the page.
     

Best Practices

Do's

  • Use the search and filter functions to quickly locate specific incident commands rather than scrolling through the entire list
  • Download incident commands to local cache when planning to work in areas with limited or no connectivity
  • Archive completed incident commands regularly to maintain an organized active incident list
  • Utilize column sorting and rearrangement to prioritize the information most relevant to your workflow
  • Review closed or completed commands using the information icon to access historical incident data without editing capabilities
  • Apply consistent naming conventions when creating new incident commands to improve searchability
  • Export incident command lists periodically for reporting and record-keeping purposes

Don'ts

  • Don't delete incident commands without verifying they have been properly archived or backed up
  • Don't attempt to start a command as the command board user if you are not assigned that role for the specific incident
  • Don't leave unnecessary incident commands downloaded to local cache, as this can consume device storage
  • Don't forget to apply filters after selecting your search criteria—the list won't update until you select "Apply"
  • Don't bulk delete incident commands without carefully reviewing the selected items
  • Don't create duplicate incident commands for the same dispatch—check the existing list first

Tips & Recommendations

  • Use the dispatch type filter to quickly separate different incident categories (fire, EMS, rescue, etc.)
  • Customize your column display to show the data points most relevant to your daily operations
  • When working in the field, download all relevant incident commands to local cache before leaving areas with reliable connectivity
  • Establish agency-wide standards for when incident commands should be archived versus deleted
  • Consider exporting incident command lists at regular intervals (weekly or monthly) for supervisory review and reporting purposes
  • Use keyword searches in the Name and Address fields for partial matches when you don't have complete information
  • Remove incident commands from local cache once they are no longer needed to optimize device performance

Troubleshooting & FAQs

Q: Why can't I start an incident command using the play button?
A: You can only start a command using the play button if you are assigned as the command board user for that specific incident. If you need to view a command where you are not the command board user, use the information icon to enter in read-only mode instead.

Q: What's the difference between archiving and deleting an incident command?
A: Archiving preserves the incident command in your system but removes it from the active list, allowing you to access historical data when needed. Deleting permanently removes the incident command from the system. Always archive incident commands before deleting unless you are certain the data is no longer needed.

Q: My filters aren't working—what should I check?
A: After entering filter criteria, you must select the "Apply" button for the filters to take effect. If you've applied filters and still don't see expected results, verify that your search terms match the data exactly or use broader keyword searches. Select "Reset" to clear all filters and start over if needed.

Q: How do I know if an incident command has been downloaded for offline use?
A: When an incident command is successfully downloaded to local cache, the cloud icon changes to a mobile device icon with a checkmark. Additionally, a new removal icon will appear next to the incident command, allowing you to delete it from local cache when no longer needed.

Q: Can I add more than two additional columns to the default view?
A: No, the system allows you to add only two additional columns beyond the eight default columns, for a maximum of ten visible columns. However, you can change which additional columns are displayed at any time through the "Show Columns" dropdown.

Q: What happens to incident commands that have been downloaded to local cache if I delete them from the main list?
A: Deleting an incident command from the main Incident Command List will also remove it from any devices where it has been cached. If you need to preserve offline access while removing it from the active list, archive the command instead of deleting it, then download the archived version for offline use.