Command: Transferring and Assuming Command

Command: Transferring and Assuming Command

Purpose Statement

  1. The command transfer feature enables seamless transitions of incident command authority between authorized users during emergency operations. This functionality supports proper Incident Command System (ICS) protocols by providing controlled, documented handovers of command responsibility while maintaining operational continuity and accountability throughout the incident lifecycle.

Background Information

  1. Command transfer is a critical component of incident management, allowing for planned leadership transitions during extended operations, shift changes, or when higher-ranking personnel arrive on scene. The system supports both voluntary transfers (where the current commander initiates the transfer) and assumed command scenarios (where authorized personnel can take command when necessary). All command transfers are automatically documented in the system log, ensuring proper accountability and chain of command tracking.

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

Additional permissions may be required for specific functions like messaging and roster access based on integrated modules.


Video 


Step by Step Guide

1. To demonstrate the Transfer Command feature, two users are shown in a side by side format to best show the following details:
A.   The Current Command Board User is denoted by the Blue COMMAND button
B.   All other Users will be denoted with the blue VIEW ONLY Button.
C.   The Transfer Command button must be selected by the current Command Board User.
D.   The Assume Command button in available to users with permissions.







2. When Transfer Command is Selected a pop up appears for the current Command Board User to select a User they want to to transfer command to and then selects Transfer Command.






3. The current Command Board User (A) will see the pop-up window stating waiting for (user) to accept Command. The current user only has the choice to cancel the transfer. The User that command is being transferred (B) to will see a pop-up with the choice to Assume Command or Decline Command. If either user Cancels or Declines Command, both user will see a new 






4. If either user Cancels or Declines Command, both user will see a pop-up denoting the cancelation of the Transfer.
A: Current Command Board User
B: User that command was being transferred to.





5. If the User that command is being transferred to Accepts Command, both will see a confirmation that the command has been assumed and transferred.
A. Previous Command Board User
B. New Command Board User





6. The Command Board will also reflect the change with the new Command Board User having the blue COMMAND and the old command board user displaying the blue VIEW ONLY.

7. Command can also be ASSUMED (if permissions are enabled). To Assume Command, the user who IS NOT the current Command Board User:
A. Selects Assumed Command button.
B. Selects YES to confirm assuming command.







8. A pop-up will appear for both users:
A. Notification that a Forced Assumed Command has occurred. (For the User that Command was taken from)
B. Confirmation that the forced transfer has completed. (For the User that Initiated the Forced Assumed Command)




9. As with all actions, edits and changes that occur within the Command Board, a detailed account is recorded within the Log Section.


Best Practices

Do:

  • Follow your organization's chain of command protocols
  • Communicate the reason for command transfer to all personnel
  • Brief the incoming commander on current operations and status
  • Verify the transfer is properly logged for documentation
  • Use voluntary transfers when possible for smooth transitions

Don't:

  • Transfer command without proper operational briefing
  • Use Assume Command unnecessarily 
  • Transfer command during critical operational phases without cause or proper notification
  • Ignore command transfer notifications from other users

Tips:

  • Plan command transfers during natural operational breaks, if possible
  • Ensure the incoming commander is fully briefed before accepting
  • Use the notes section or Log entry to document transfer reasons and conditions
  • Coordinate with dispatch and field units about command changes

Troubleshooting & FAQs

Q: I don't see the Transfer Command option. What should I check?
A: Verify that you currently have command control (blue status button reads "Command" not "View Only") and that you have Transfer Command permissions in your user role.

Q: What happens if I decline a command transfer?
A: The transfer is cancelled and both users receive a "declined command" notification. Command remains with the original commander.

Q: Can I cancel a transfer after I've initiated it?
A: Yes, the initiating commander can select "Cancel" in the confirmation window before the target user responds.

Q: What's the difference between Transfer Command and Assume Command?
A: Transfer Command requires acceptance by the target user, while Assume Command immediately takes command without the current commander's consent (requires special permissions).

Q: How can I see who currently has command?
A: The current commander is displayed in the "Command Board User" section at the top of the interface, and their interface will show "Command" while others show "View Only."

Q: Are command transfers logged automatically?
A: Yes, all command transfers (both voluntary and assumed) are automatically recorded in the log section with timestamps and user details.


    • Related Articles

    • NERIS Documentation - Command and Safety

      Purpose The purpose of this article is to assist with the documentation of the Command and Safety section when completing a fire report. Video Directions 1. Navigate to the Operations section and select the Command And Safety tab. 2. Within the ...

    • Command: Initiating or Joining an Incident Command

      Purpose Statement The incident command feature allows users to create, access, and manage command boards for active incidents. This functionality enables incident commanders to coordinate resources, track assignments, and maintain situational ...

    • Command Board: General Overview

      Purpose Statement The command board module provides a comprehensive incident management interface that remains consistently available while navigating all sections of the command system. This central hub allows incident commanders to manage critical ...

    • Command Setup: Command Staff

      Purpose To explain how to create, edit and manage Command Staff in the Command Module through Command Setup. Video Directions 1. In Web Responder, select the Responder Module and then Command Setup. 2. In Command Setup, select Command Staff. 3. To ...

    • Command 101

      First Due Academy: Command 101 This training session focuses on First Due's Command Module functionality and processes. Sessions of this level have been developed for personnel involved in the operation of the Command Module. In 101 level sessions we ...