Purpose Statement

The Operations section in ePCR incident documentation enables users to comprehensively document command structure, safety protocols, and departmental actions taken during emergency incidents. This section ensures proper documentation of incident command activities, resource deployment, and operational decisions, supporting accurate reporting, after-action reviews, and compliance with NFIRS (National Fire Incident Reporting System) requirements.

Background Information

The Operations section is completed after the Scene Size-up section and represents a critical component of incident documentation. This section is divided into two primary fields: Command and Safety, and Actions. The Command and Safety field captures the incident command hierarchy, including command establishment, transfers, size-up activities, and operational structure. The Actions field documents the overall department response activities based on the incident type selected in the Response section.

This documentation is essential for maintaining chain-of-command records, tracking operational decisions, and ensuring NFIRS compliance. The system automatically populates certain action options based on the incident type, streamlining documentation while maintaining accuracy. Only the first three actions selected are transmitted to NFIRS, ensuring compliance with reporting standards.

Best Practices

Do's

• Document command establishment immediately when incident command is initiated to ensure accurate timestamps.
• Record all command transfers with detailed notes explaining the reason for transfer and any relevant situational changes.
• Complete the 360° size up documentation if performed, as this provides valuable situational awareness information.
• Select actions taken in priority order, as only the first three will be sent to NFIRS for reporting.
• Document special resources deployed to maintain comprehensive resource tracking.
• Verify that the incident type in the Response section is correct before documenting actions, as this determines available action options.
• Include detailed notes in each subsection to provide context for after-action reviews and training purposes.
• Ensure PAR completion is documented when performed to maintain accountability records.

Don'ts

• Don't skip the Operations section even for routine calls, as it provides essential command and action documentation.
• Don't select more than necessary actions if only a few were actually performed—prioritize the most significant actions in the first three selections.
• Don't forget to document staging division discontinuation times, as this provides complete operational timeline information.
• Don't change the incident type after completing the Operations section without reviewing that the documented actions still align with the new incident type.
• Don't omit notes fields when additional context would benefit future review or training analysis.

Tips & Recommendations

• Establish a standard practice within your department for who documents command-level information versus unit-level actions to avoid duplication or gaps.
• Use the field navigation buttons at the top of the Operations section to move quickly between Command and Safety and Actions subsections, especially during complex incidents.
• When documenting actions for multi-unit responses, coordinate with other documenting personnel to ensure the first three actions selected accurately represent the overall department response.
• Consider creating department-specific documentation guidelines that define when Operation Section branches should be engaged and documented.
• Review completed Operations section documentation during after-action reviews to identify areas for improved real-time documentation practices.