Purpose Statement

The Incident Command initiation and access feature enables authorized First Due users to create new command boards for active incidents, join existing command boards with appropriate permissions, and access command operations from multiple entry points across both web and mobile platforms. This feature provides flexible command board creation with customizable incident names and templates, role-based permission control for command access levels, and seamless integration between responder workflows and command operations to support efficient transition from incident notification to active command management.

---

Background Information

Incident command boards must be initiated before command operations can begin. First Due provides multiple access points and methods for creating and accessing command boards, with permission-based controls ensuring appropriate users have the necessary authority for command operations.

Permission Configuration

Incident command access is controlled through role-based permissions configured in the Admin Module under Roles and Permissions. The "Incident Commands" permission has four levels:

• Read: User can view command boards in read-only state that have already been initiated
• Update: User can update and edit existing command boards
• Create: User can create or initiate new command boards
• Delete: User can delete command boards

These permissions can be tailored to each role within First Due to control which users have command authority and at what level.

Platform Availability

The Command Module is designed for use on both web responder and mobile responder platforms with nearly identical functionality and user experience across both interfaces. Command boards can be initiated from either platform and accessed seamlessly between web and mobile.

Command Initiation Access Points

Mobile Responder:

• From Incidents list: Select incident → Select "Take Command" button
• From Map: Select incident marker → Select "Take Command" button

Web Responder:

• From Responder View: Navigate to Response Module → Responder View → Select incident from incident list → Select "Take Command"
• From Map: Select incident marker → Select "Take Command"
• From Incident Command List: Navigate to Response Module → Incident Command List → Select "Create Command"

Command Board Creation Process

When "Take Command" is selected from any location:

• Pop-up displays with generated incident name (based on incident details)
• Default template displays (configured in Command Setup based on incident type)
• Incident name can be modified before creation
• Template can be changed from default before creation
• Selecting "Create" initiates the command board and redirects user to the command board interface

Post-Initiation Behavior

After a command board is initiated for an incident:

• "Take Command" button is replaced with "Incident Command" button
• "Incident Command" button provides direct access to the existing command board
• Command list displays play icon for commands assigned to current user
• Command list displays "i" icon for commands available in read-only status to other users

Alternative Creation Method - Incident Command List

Users can create command boards directly from the Incident Command List:

• Navigate to Response Module → Incident Command List
• Select "Create Command"
• Select dispatch call to associate with new command
• Modify incident name as desired
• Change template from default if needed
• Command appears in command list with appropriate access indicator
  

---

Required Permissions

Users must have the Incident Commands permission configured in their role to access this functionality. Navigate to Admin Module > Roles and Permissions to configure these settings:

• Read: View existing command boards in read-only mode
• Update: Modify and update existing command boards
• Create: Initiate new incident command boards
• Delete: Remove command boards

Note: Most operational users will need Create, Update and Read permissions to effectively manage incident commands.

---

Video

---

Step-by-Step Guide

~Mobile~

1.  Select Incidents.

2.  Then select an incident from the incident list.

3. Scroll down in the incident information window to access the Take Command Button.

4. Another  way to Initiate a Command in Mobile is to click on an incident icon on the map.
5. Then select Take Command from the Incident Information window that pops up on the right side of the screen.

~Web Responder~

1. Select the Responder Module and then Responder View.

2. Select an incident from the Incident List and then Select Take Command.

3. In Web, Command can also be initiated by clicking on a Incident Icon and then Selecting Take Command from the pop-up window.

Both Mobile and Web

1. Regardless of selecting Take Command in Mobile or Web Responder, a pop-up window will appear where with the generated Incident Name and Default template for that incident. The Incident name can be edited and the template can be changed prior to starting the Command. Select Create.

2. The Incident Command is now initiated and the user will automatically be redirected to the active incident Command.

3. In both Web and Mobile, an Incident Command can also be created by navigating to the Response module, then to Incident Command List.

4. Select Create Command

5. Select the dispatch to assign this Incident Command to from the drop down list.

6. Edit the Incident Name and the template as desired. Then select create.

Joining an Incident Command

1. After a Command Board has been initiated for an incident, the Take Command button will be replaced with an Incident Command button which will take the User to the active command board. In the Incident Command List the Eye icon can be selected to join the specific incident command.

Best Practices

Do's

• Configure role-based permissions appropriately to ensure only authorized personnel can initiate or edit command boards
• Use descriptive incident names that clearly identify the incident location and type for easy reference
• Select the appropriate template for the incident type to ensure relevant assignments, checklists, and timers are configured
• Verify incident details before selecting "Create" to avoid creating command boards with incorrect information
• Train personnel on multiple access points for command initiation so they can quickly start command operations from their current workflow
• Use the Incident Command List view to monitor all active command boards and their status across the organization

Don'ts

• Don't grant Create or Update permissions to roles that shouldn't have command authority
• Don't create multiple command boards for the same incident—verify an existing board hasn't been initiated before creating a new one
• Don't forget to modify the incident name if the generated name doesn't accurately reflect the incident
• Don't select the wrong template during creation—changing templates mid-incident can cause confusion
• Don't assume all users can create command boards—verify permission levels for different roles
• Don't neglect to communicate when command boards are initiated so other personnel know active command has been established

Tips & Recommendations

• Configure default templates in Command Setup to match common incident types in your response area for automatic appropriate template selection
• Establish department protocols defining who has authority to initiate command boards for different incident types
• Train personnel to recognize the difference between "Take Command" (initiate new board) and "Incident Command" (join existing board)
• Use consistent incident naming conventions across your organization to support searchability and reporting
• Leverage the flexibility of multiple access points to initiate command from wherever you're working in First Due
• Review the Incident Command List regularly to monitor command board activity and identify which personnel are actively managing incidents

Troubleshooting & FAQs

Q: Why don't I see the "Take Command" button on incidents?
A: The "Take Command" button is only visible to users with "Create" permission level for "Incident Commands" in their role configuration. If you don't see this button, you likely have Read or Update permissions only. Contact your system administrator to adjust role permissions if command initiation authority is needed.

Q: What's the difference between "Take Command" and "Incident Command" buttons?
A: "Take Command" appears before a command board has been initiated and allows you to create a new command board for the incident. "Incident Command" appears after a command board has been initiated and provides access to the existing command board. The button changes after the first user creates the command board.

Q: Can I change the template after creating the command board?
A: Yes. Templates can be changed during incident operations through the command board interface. However, template switching triggers item matching and data preservation processes. It's best to select the correct template during initial creation when possible.

Q: Why do I see an "i" icon instead of a play icon on some commands in the command list?
A: The play icon indicates a command is currently assigned to you with active control. The "i" icon indicates the command is available for you to view in read-only status because another user has command control. Your access level depends on your role permissions and current command assignment.

Q: Can multiple users initiate command boards for the same incident?
A: Only one command board should exist per incident. Once a command board is initiated, the "Take Command" button is replaced with "Incident Command" to prevent duplicate board creation. If multiple boards are accidentally created, coordinate with system administrators to resolve the duplication.

Q: What happens if I create a command board from the Incident Command List instead of from the incident itself?
A: Creating from the Incident Command List requires you to manually select which dispatch call to associate with the command. This method works identically to other creation methods but requires an extra step to link the command to the specific incident. The resulting command board functions the same regardless of creation method.

Related Articles

1. Command: Incident Command List
   
2. Command: Transferring and Assuming Command