Purpose Statement

The Transfer Command feature in the Command Module enables incident commanders to formally hand over operational control of the command board to another authorized user through a structured transfer process, supports both voluntary transfers requiring acceptance and forced assumption for critical situations, maintains clear command authority indicators showing who controls the command board, and automatically logs all command transfers with complete timestamps to ensure accountability and documentation of command transitions throughout incident operations.

Background Information

Command transfer is a critical incident management function that must be executed clearly and documented thoroughly to maintain operational continuity and accountability. The Transfer Command feature provides a formal, traceable process for changing command authority within the First Due Command Module.

Command Status Indicators

• Users in control of the command board see "Command" indicator displayed
• Users not in control see "View Only" indicator displayed
• Command status determines editing capabilities versus read-only access to the command board
• Only one user can have command control at any given time

Transfer Command Process (Voluntary Transfer)

• Initiated by the current command board user selecting "Transfer Command"
• Current commander selects the recipient user from the system user list
• Both users receive notification windows with transfer options
• Current Commander Options: Cancel the transfer request
• Recipient Options: Assume command or Decline command
• If either user declines or cancels, both users receive "Declined Command" notification
• If recipient assumes command, both users receive confirmation notifications
• Command board control shifts to the new commander
• Previous commander's interface changes to "View Only" status

Assume Command Process (Forced Assumption)

• Available to users with appropriate permissions
• Allows authorized users to take control without current commander's approval
• Initiated by selecting "Assume Command" and confirming with "Yes"
• Current command board user receives notification of forced assumption
• Command board control immediately transfers to the assuming user
• Used in critical situations requiring immediate command changes

Command Transfer Documentation

• All command transfers are automatically logged in the Log Section
• Detailed records include transfer timestamp, transferring user, receiving user, and transfer method (voluntary vs. forced)
• Log entries support post-incident review and accountability documentation
• Creates complete chain of custody record for command authority

Post-Transfer Status

• Previous commander retains access to command board in "View Only" mode
• New commander gains full editing and operational control
• Command indicator updates immediately for both users
• All subsequent command board actions are attributed to the new commander
  

Best Practices

Do's

• Use voluntary transfer process whenever possible to ensure clear communication and acceptance of command authority
• Provide comprehensive verbal briefing to incoming commander during voluntary transfers, supplementing the digital transfer
• Verify the recipient user is correct before initiating transfer to avoid confusion or multiple transfer attempts
• Document the reason for command transfer in notes or log entries to provide context for post-incident review
• Ensure incoming commanders understand current incident status before accepting command authority
• Use forced assumption only when operationally necessary and authorized (critical situations, unresponsive commanders, emergency circumstances)
  

Don'ts

• Don't use forced assumption unnecessarily—voluntary transfers support better communication and operational continuity
• Don't transfer command without verbal coordination when possible, even though the system allows digital-only transfers
• Don't forget that command transfer is automatically logged—all transfers are documented and traceable
• Don't assume the recipient is ready to assume command without communication or verification
• Don't cancel transfers after initiating them unless there's clear operational justification
• Don't decline command transfers without understanding the operational need for transfer
  

Tips & Recommendations

• Coordinate command transfers with operational period transitions for natural handoff points during extended incidents
• Establish department protocols defining when forced assumption is appropriate versus voluntary transfer
• Train all personnel with command authority on both voluntary and forced transfer processes during non-emergency periods
• Use the automatic logging feature to create clear documentation of command transitions for accountability
• Consider implementing standard briefing checklists for command transfers to ensure consistency
• Review command transfer logs during post-incident analysis to evaluate command continuity and decision-making timeline
  

Troubleshooting & FAQs

Q: What happens if I decline a command transfer?
A: If you decline a command transfer, both you and the current commander receive a "Declined Command" notification. Command authority remains with the original commander, and the command board status remains unchanged. The declined transfer is logged in the Log Section.

Q: Can I transfer command back to the previous commander immediately after accepting it?
A: Yes. After assuming command, you have full command authority and can initiate a new voluntary transfer back to the previous commander or to any other authorized user. The previous commander would need to accept the transfer following the same voluntary transfer process.

Q: What's the difference between "Transfer Command" and "Assume Command"?
A: "Transfer Command" is a voluntary process where the current commander offers command to another user who must accept it. "Assume Command" is a forced process where an authorized user takes control without requiring the current commander's approval. Voluntary transfers support better communication, while forced assumption is for critical situations.

Q: How do I know if I have permission to use forced command assumption?
A: The "Assume Command" option is only available to users with appropriate permissions configured in their system role. If you don't see this option, you don't have permission for forced assumption. Contact your system administrator regarding permission configuration if needed.

Q: What happens to command board edits I made after someone forces assumption of command?
A: All command board actions are logged with the user who performed them and the timestamp. Actions you took while in command remain in the log attributed to you. The new commander's actions are logged separately under their user identification. The log maintains a complete record of who made which changes and when.

Q: Can multiple users attempt to assume command simultaneously?
A: The system processes command changes sequentially. If multiple users attempt forced assumption simultaneously, the system will process them in the order received. Only one user can hold command at any time, so subsequent attempts would take command from whoever currently has it.