Incident Command for Company Officers

You're the IC Until You're Not

If you're the first-arriving company officer, you're the Incident Commander. That's not a suggestion — it's NIMS. You own the incident until command is formally transferred to a higher-ranking officer. What you do in those first 3–5 minutes sets the tone for the entire operation. Get it right and the fireground runs smooth. Get it wrong and you're chasing problems for the rest of the call.

Initial IC Responsibilities

The moment you arrive, you have five immediate obligations:

1. Give a clear initial radio report — what you see, what you're doing, and what you're calling it. ("Engine 7 on scene, two-story wood frame, smoke showing from the second floor Side Alpha. Engine 7 is assuming Main Street Command, attacking with a 1¾.")
2. Establish command — state your command name. Use the street name or building name. Keep it simple.
3. Size up the scene — building construction, fire conditions, exposures, access, hazards.
4. Assign arriving units — don't let companies freelance. Every unit gets a task or a staging assignment.
5. Request additional resources if needed — it's better to call for help early and cancel than to be behind the eight ball.

Command Transfer

When a chief officer arrives, command transfers — but only through a face-to-face briefing. The arriving officer must:

• Get a full briefing from the current IC (conditions, actions taken, resources committed, needs).
• Announce the transfer on the radio: "Battalion 1 is assuming Main Street Command."
• The outgoing IC can be reassigned to a division, operations, or back to their company.

Never just grab the radio and start giving orders without a briefing. You'll duplicate assignments, miss critical info, and undermine the operation.

Span of Control

NIMS says 3–7 resources per supervisor, with 5 being optimal. On a working fire, if you have more than five companies operating and you're trying to manage them all directly, you've already lost the span. That's when you need divisions and groups.

Divisions and Groups

Divisions are geographic — they manage a physical area. Groups are functional — they manage a task.

• Division 1 = first floor. Division 2 = second floor. Division A/B/C/D = sides of the building (exterior).
• Vent Group = all ventilation operations. RIT Group = rapid intervention team. Medical Group = patient care operations.
• Each division/group supervisor manages their assigned resources and reports to the IC (or Operations, if established).

Assign division/group supervisors early. If you wait until the fireground is chaotic, it's too late. A good rule of thumb: if you're going to a second alarm, you should already have divisions established.

CAN Reports

CAN stands for Conditions-Actions-Needs. This is how division/group supervisors communicate with the IC. It's the standardized format that replaces rambling, unstructured radio traffic.

• Conditions: What's happening in your area right now? Fire showing, smoke conditions, visibility, structural concerns.
• Actions: What are you doing about it? Advancing a line, performing search, holding position.
• Needs: What do you need from Command? More personnel, another line, relief crews, nothing.

The IC should request CAN reports on a regular cycle — every 10–15 minutes at a minimum, or whenever conditions change. If you're not getting CAN reports, you've lost situational awareness.

Decision-Making Under Pressure

As IC, you'll make dozens of decisions in a short window. Use the risk management framework from NFPA 1500:

• Risk a lot to save a lot — known life hazard, aggressive interior attack.
• Risk a little to save a little — savable property, no confirmed life hazard.
• Risk nothing to save nothing — fully involved structure, no life hazard, go defensive.

Your job is not to fight fire. Your job is to manage the incident so your people go home. Every order you give should pass through that filter first.

Common IC Failures

• Tunnel vision: Focusing on one sector and losing track of the rest of the fireground.
• Freelancing tolerance: Letting companies operate without assignments erodes accountability.
• No PAR: Failing to conduct personnel accountability reports at benchmarks (fire knockdown, mode change, mayday).
• Late resource calls: Requesting additional alarms after you already need them, not before.

Incident command is a skill. Like everything else in this job, the only way to get good at it is reps. Run tabletop exercises, practice on every working incident, and debrief honestly. The fireground will expose every gap in your command ability.