Purpose Statement
The Notes feature in the Command Module allows incident commanders and personnel to document important information, communications, and observations during active incidents. This feature enables users to create three distinct types of notes—general notes for overall incident documentation, unit notes for specific apparatus or personnel, and assignment notes for tactical operations—ensuring comprehensive incident documentation and improved situational awareness throughout command operations.
Effective incident documentation is critical for maintaining accountability, supporting decision-making, and creating accurate after-action reports. The Notes feature provides a structured system for capturing real-time information during dynamic incident operations. Notes can be created, edited, and deleted throughout the incident lifecycle, with all actions automatically logged in the incident log for complete traceability.
The three note types serve different documentation purposes:
- General Notes: Document overall incident information, command decisions, or observations not specific to any unit or assignment
- Unit Notes: Capture information specific to individual apparatus, crews, or personnel
- Assignment Notes: Record details about specific tactical assignments or operational objectives
All notes are visible in a centralized Notes section on the Command Board, with a counter displaying the total number of notes created (not unread notifications). This system supports both immediate operational needs and post-incident review processes.
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.
4. To create a specific Unit Note:
- 4A Select Add Notes from the Unit Menu.
- 4B Enter the desired information into the text field of the Note.
- 4C Select Create.
5. The new Unit Note now appears in the Notes Section.
6. To create a specific Unit Note:
- 6A Select Add Notes from the Unit Menu.
- 6B Enter the desired information into the text field of the Note.
- 6C Select Create.
7. The new Assignment Note now appears in the Notes Section.
Best Practices
Do's
- Create notes promptly while information is fresh and accurate
- Use descriptive, clear language that will be meaningful during post-incident review
- Attach notes to the appropriate type (general, unit, or assignment) for better organization
- Document significant decisions, observations, or communications that may be relevant for after-action reports
- Review existing notes periodically during extended incidents to maintain situational awareness
- Use unit notes to track apparatus-specific information like equipment deployment or crew assignments
- Use assignment notes to document tactical progress, challenges, or completion status
Don'ts
- Don't assume the note counter indicates unread messages—it shows the total number of notes
- Don't use notes as a substitute for proper radio communications during time-critical situations
- Don't create general notes when information is specific to a unit or assignment—use the appropriate note type
- Don't delete notes without considering their value for post-incident documentation and review
- Don't use abbreviations or codes that may not be understood by other personnel reviewing the notes
Tips & Recommendations
- Establish consistent note-taking protocols within your department for standardized incident documentation
- Consider using notes to document resource requests, scene conditions, or tactical changes
- Train personnel on the distinction between the three note types to ensure consistent usage
- Review notes during incident transitions or operational period changes to brief incoming command personnel
- Use the automatic logging feature as evidence of documentation timeline during incident reconstruction
Troubleshooting & FAQs
Q: Why doesn't the number on the Notes section decrease when I read notes?
A: The number displayed on the Notes section represents the total count of notes created for the incident, not a count of unread notifications. The number will only decrease when notes are deleted.
Q: Can I see who created each note and when?
A: Yes. All note creation, editing, and deletion actions are automatically logged in the Log section with timestamps and user information.
Q: What happens to notes attached to units or assignments if those units or assignments are removed from the incident?
A: Unit and assignment notes remain in the Notes section even if the associated unit or assignment is removed. The note retains its original identifier for reference.
Q: Can I create notes from the mobile application?
A: Refer to mobile application documentation for specific capabilities. The core note creation functionality described here applies to the web-based Command Board interface.
Q: Is there a limit to how many notes I can create?
A: There is no specified limit on the number of notes that can be created during an incident. However, focus on documenting significant information rather than excessive note creation.
Q: Can I attach files or images to notes?
A: The current Notes feature is text-based. For media attachments, refer to other documentation features within First Due or follow your department's procedures for incident media management.
Related Articles
- Command Board: General Overview
- Command: Messaging
- Command: Board Section
- Command: PAR Checks
- Command: MAYDAY
- Command: Units
- Command: Assignments
- Command: Overview Section
- Command: Map Section
- Command: Log Section Overview
- Command: Manage Divisions