Three New Command Views, One Connected Incident

Why Traditional Accountability Boards Fall Short on Complex Incidents

Personnel accountability has always meant who is doing what, where, during an incident. But complex incidents (e.g., high-rises, strip malls, and multi-exposure fires) demand even more rigorous adherence to this practice. Commanders need to quickly and accurately visualize these changes as they occur across the fireground, without relying on constant radio updates to maintain situational awareness.  

Traditional accountability boards track who is assigned to an incident, but they weren’t designed to organize resources geographically or adapt to the incident's evolving shape. As conditions change, commanders are forced to rely on frequent radio traffic, whiteboards, notes, and separate worksheets to keep an accurate picture of the incident. This consumes valuable airtime and increases workload at the exact moment when clarity, speed, and coordination matter most.  

Three Views, Same Board

First Due now has three new ways to organize the ICS Command Board, each reachable with a quick action from the standard board departments already use:

• Floors View: Built for high-rise operations, and any incident with fire above or fire below. The active fire floor is flagged with a clear visual indicator, and floors immediately above and below are automatically marked as IDLH caution areas. Command can assign companies by floor, capture a CAN report for each level, and rename floors to match building or SOP-specific terminology.  

• Custom View: A left-to-right column layout that flexes to the incident. Columns can represent geography (Bravo 1, Bravo 2 for a strip mall) or status (rehab, recycling). It’s the most flexible of the three views, and the one most commanders haven’t used yet—worth a look any time an incident doesn’t fit floors or sides neatly.  

• Alpha/Bravo/Charlie/Delta: Side-based accountability for incidents defined by exposures rather than levels. Strip malls, commercial buildings, and other structures with a clear A/B/C/D footprint can have assignments organized around the building’s physical sides instead of its floors.  

None of these views replace the Default board. They provide different ways to organize and view the same accountability data, allowing assignments to be created and managed from whichever layout best matches the incident.

Connected Accountability: Personnel, CAD, and Pre-Plan Data in One View

Whichever view Command is working in, the underlying incident data doesn’t change. Incident personnel assignments, CAD notes, occupancy details, and pre-plan information remain linked across every view, ensuring every responder is working from the same information.

A CAN report logged from the Floors view, a status update made in Custom view, and an assignment made by side in A/B/C/D are all part of the same operational picture. Switching views doesn’t mean switching context, and it isn’t a separate tool the IC has to reconcile later.  

Incident Documentation & NERIS Reporting, Without Duplicate Entry

The same connection carries past the incident itself. The floor-by-floor CAN reports, side assignments, and status changes captured in the moment aren’t just for situational awareness during the incident—they become part of the incident documentation once operations wrap up.  

Instead of reconstructing a timeline from notes or memory after the fact, the geographic and operational detail captured in real-time carries forward into the incident report, reducing duplicate entry and supporting the level of detail departments need for accurate, NERIS-compliant reporting.  

Geographic Accountability for Complex Incidents

High-rise fires, strip malls, and multi-exposure incidents all demand more than personnel accountability. They demand accountability that matches the shape of the incident, without asking ICs to leave the board they already know or duplicate work afterward.  

That’s the idea behind all three views: geographic accountability that extends the standard board, stays connected to the rest of your First Due data, and carries through to your documentation.