Emergency Management and Critical Incident Command
This domain tests command at a scene that is still developing. The exam rewards the captain who establishes command, organizes by function, requests resources early, and documents decisions - and penalizes the one who personally joins the tactical action.
Command structure
Use ICS principles as applied through the Citywide Incident Management System: a single Incident Commander, unified command where multiple agencies have jurisdiction, and a span of control of roughly three to seven subordinates per supervisor. Functions are established as needed - operations, perimeter, traffic, staging, medical, logistics, and a command post - and the commander stays at the post.
Mobilization
Department mobilization levels escalate from precinct-level to borough-level to citywide to full departmental response. Request the level you will need, not the level you currently have; a captain who waits for the situation to outgrow the response has already lost time.
Critical incidents
Active shooter: first arriving officers form a contact team and move to the threat; rescue task forces follow with fire/EMS in warm zones. For explosions, building collapses, and hazardous scenes, establish inner and outer perimeters, a staging area, and a media point, and transfer command formally - face to face, with a briefing - when a higher authority or specialized unit arrives.
Worked example
A partial building collapse with injuries. The captain establishes command, sets perimeters beyond the debris field, requests a mobilization level sufficient for traffic and crowd control, establishes staging, and assigns a recorder. When ESU and the Fire Department arrive, command transfers formally with a briefing on units deployed and victims located.
Traps
Commanding from inside the hot zone; no recorder, so the timeline cannot be reconstructed; no staging area, so units block access; assuming a radio broadcast equals a formal command transfer; failing to schedule an after-action review.