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

To access and manage the Incident Command List, users need appropriate response module permissions. Specific permissions required will vary based on the actions performed:

• Incident Command Board > Incident Commands: Allows user to view, update, create and delete incident commands.

Note: Users can enter 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

Accessing the Incident Command List

Navigate to the Response module in your First Due system and select "Incident Command List" from the module menu.

Searching and Filtering Incident Commands

1. Use the search and filter area at the top of the list to locate specific incident commands. Available filter options include:

• Name (keyword search)
• Address (keyword search)
• Dispatch Type (dropdown filter)
• Archive Status (dropdown filter - archived or not archived)
• Agency (dropdown filter)

1. Enter keywords in any text field without a dropdown, or select values from dropdown menus for filtered fields then select the "Apply" button to execute your search criteria. To clear all filters and return to the full list, select the "Reset" button.
   

Customizing Column Display

1. By default, eight columns are displayed in the incident command list.  To add additional columns, select the dropdown in the "Show Columns" area.

1.  Columns can be rearranged in any order and sorted in ascending, descending, or default order by selecting the column header.
   

Starting or Entering an Incident Command

1. To start a new command or enter a command where you are the command board user, select the play symbol icon next to the incident.
   

To view closed or completed commands, or to enter a command in read-only mode (when you are not the command board user), select the "Eye" icon.

Downloading for Offline Use

1. To download an incident command for offline access, select the cloud icon next to the incident. The sync status will change from a cloud icon to a mobile device with a checkmark, indicating successful download to local cache.
   

1. To remove the incident command from local cache, select the Mobile Device w/ A Trash Can icon that appears after download.
   

Managing Incident Commands

1. To archive an incident command, select the file box icon next to the incident.
   

1. To delete a single incident command, select the trash can icon next to the incident.
   

1. To bulk delete multiple incident commands, check the boxes next to each command you wish to delete, then select the bulk trash can icon at the top of the list.
   

Creating a New Incident Command

1. Select the "Create Command" button.
   

1.  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.

2.  Modify the incident name if desired.

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

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

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.

Related Articles

1. Command: Initiating or Joining an Incident Command
   
2. Command Board: General Overview