Command: Log Section

Command: Log Section

Purpose Statement

The Log section in the Command Module provides comprehensive tracking and documentation of all activities, changes, and edits made within the Command Board during incident operations. This feature enables incident commanders and personnel to maintain detailed chronological records of incident actions, search and filter log entries by multiple criteria, create custom log entries, and export documentation for post-incident review and reporting purposes.

Background Information

Background Information

Accurate incident logging is essential for accountability, legal documentation, operational review, and continuous improvement processes. The Log section automatically captures all system-generated actions while also allowing users to create manual log entries for significant events, decisions, or observations that may not be automatically recorded.

Each log entry includes detailed metadata that supports comprehensive incident reconstruction:

  • Timestamp: Precise date and time of the logged action
  • Description: Detailed explanation of the action or event
  • Assignment Association: Links to specific tactical assignments when applicable
  • Unit Association: Connects to specific apparatus or personnel when relevant
  • Division Association: Associates with organizational divisions when appropriate
  • User Information: Identifies which user performed the action
  • Agency Information: Records the agency affiliation of the user

The Log section supports advanced search and filtering capabilities, customizable display options, bulk actions, and multiple export formats to meet various documentation and reporting requirements.

Required Permissions

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

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

Video


Step by Step Guide

1. Log Entries can be searched by keyword and filtered by Assignment, Unit and Log by. 






2. Every Log Entry is visible in the Log Section. Log Entries can be: 
  • Edited by selecting the Pencil Icon. 
  • Delete by selecting the Trashcan Icon.






3. Click the pencil to edit a log entry. 


Click the pencil to edit a log entry.



4. Make the appropriate changes and click Save when done. 






5. To bulk delete a log entry, select the checkbox(s), then click the trashcan. 






6. A pop-up will appear. Click confirm if you want to delete the entries. 






7. Click on Create Log Entry to add a new Log Entry. 






8. Enter the Log Entry information. If this Log Entry is attached to a specific Assignment, Unit or Divison choose those from the drop down menus.
Add an attachment (if warranted) and click Create. 



Best Practices

Do's

  • Create manual log entries for significant decisions, tactical changes, or notable observations not automatically captured
  • Use descriptive, specific language in log entry descriptions that will be meaningful during post-incident review
  • Associate log entries with relevant units, assignments, or divisions to improve searchability and organization
  • Attach supporting documentation (photos, diagrams, reports) to log entries when it enhances understanding
  • Establish department-specific protocols for when manual log entries should be created
  • Use search and filter functions during extended incidents to quickly review specific aspects of operations
  • Export log data regularly during long-duration incidents for backup and interim reporting purposes
  • Review log entries during operational period transitions to brief incoming personnel

Don'ts

  • Don't delete log entries without careful consideration of documentation and legal implications
  • Don't use vague or unclear language in log entry descriptions
  • Don't create redundant manual entries for actions that are already automatically logged
  • Don't edit log entries to misrepresent the timeline or nature of incident actions
  • Don't assume all critical information is automatically logged—create manual entries for important decisions and observations
  • Don't neglect to associate entries with units, assignments, or divisions when relevant relationships exist
  • Don't use log entries as a substitute for proper radio communications during time-critical operations

Tips & Recommendations

  • Utilize the fuzzy search feature by entering partial words to find entries when you're unsure of exact terminology
  • Combine multiple filters to narrow results when searching through extensive log data from long-duration incidents
  • Customize column display to focus on the most relevant information for your current task or review purpose
  • Export log data in both CSV and PDF formats to support different reporting and analysis needs
  • Train all command personnel on consistent log entry creation practices to maintain documentation standards
  • Consider creating manual log entries at key incident milestones (arrival, water on fire, under control, etc.)
  • Use the timestamp data in exported logs to create detailed incident timelines for after-action reports
  • Periodically backup log data during extended incidents to prevent potential data loss

Troubleshooting & FAQs

Q: What types of actions are automatically logged in the Log section?
A: The system automatically logs all changes and edits made within the Command Board, including unit assignments, assignment creation and modification, division changes, note creation and deletion, and other significant command board actions. Each automatic entry includes relevant metadata such as the user who performed the action and associated units or assignments.

Q: Can I recover a log entry after deleting it?
A: Deleted log entries cannot be recovered through the Command Module interface. Exercise caution when deleting entries, especially when using the bulk delete function. Consider your department's data retention policies before removing documentation.

Q: How does the fuzzy search work?
A: The fuzzy search function performs partial word matching. For example, searching "assign" will return entries containing "assign," "assignment," "assigned," "reassigned," or any other word containing that letter sequence. This makes it easier to find entries when you don't know the exact wording used.

Q: Can I edit automatically generated log entries?
A: While the edit function may allow modification of log entries, automatically generated entries should generally not be edited to preserve the integrity of the incident timeline. Manual log entries created by users can be edited if corrections are necessary, but maintain documentation standards regarding log modifications.

Q: What file types can be attached to log entries?
A: The system accepts common file formats for attachments. Refer to system specifications or contact support for specific file type limitations and size restrictions.

Q: Does exporting the log to CSV or PDF include all log entries or only filtered results?
A: The export function creates a file containing the currently displayed entries based on your active filters, search criteria, and visible columns. To export all log entries, reset any filters before exporting. To export specific subsets, apply appropriate filters before exporting.

Q: Can multiple users create and edit log entries simultaneously?
A: Yes, multiple users with appropriate permissions can access and create log entries simultaneously. The system timestamps each entry with the specific user information to maintain accountability.

Q: Are log entries retained after an incident is closed?
A: Log entries are typically retained as part of the permanent incident record. Consult your department's data retention policies and First Due system configuration for specific retention timeframes and archival procedures.


    • Related Articles

    • Command: Overview Section

      Purpose Statement The overview section provides a comprehensive dashboard view of critical incident information, consolidating map visualization, pre-plan data, assignment tracking, and resource request management into a single interface. This ...

    • Command: Board Section

      Purpose Statement The command board section serves as the primary operational interface for incident management, providing comprehensive control over command staff positioning, unit assignments, and tactical operations. This central workspace enables ...

    • Command: Map Section

      Purpose Statement The map section provides comprehensive visual incident management capabilities within the command module, enabling incident commanders to visualize tactical operations, place pre-planned units, create annotations, and manage ...

    • Command: Transferring and Assuming Command

      Purpose Statement 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 ...

    • Command: Notes

      Purpose Statement The notes feature in the command module allows incident commanders and operators to create, manage, and track important information throughout an incident enabling organized documentation and communication of critical incident ...