Which One of the Following Activities Is NOT an Example of Incident Coordination?

The answer

The activity that is NOT an example of incident coordination is "directing, ordering, or controlling". In NIMS and the Incident Command System (ICS), directing and controlling resources on scene is a function of command, not coordination. Coordination is a supporting, big-picture function that helps multiple incidents and agencies work together; it does not give tactical orders.

The genuine examples of incident coordination are:

• Establishing priorities among competing incidents (deciding which incident gets scarce resources first).
• Synchronizing public information so agencies deliver one consistent message.
• Resolving critical resource issues and shortages across jurisdictions.

Why directing/controlling is command, not coordination

NIMS deliberately separates command from coordination because they happen in different places and answer different questions.

• Command is exercised at the scene by the Incident Commander (or Unified Command). It directs, orders, and controls the actual response—assigning crews, setting tactics, and managing on-scene operations. Command is hands-on and directive.
• Coordination happens off-scene and above the incident, typically through the Multiagency Coordination System (MACS), EOCs, and MAC (policy) groups. Its job is to support command by setting priorities among many incidents, marshaling resources, and aligning information—not by telling responders what to do on the ground.

So the reason "directing, ordering, or controlling" is the odd one out is structural: coordination bodies have no tactical command authority. If they started directing field units, they would be violating the ICS principle of a single, clear chain of command per incident.

Ruling out the other choices

Every other typical answer choice is coordination:

• Establishing priorities between incidents — a classic MAC-group/EOC function when several incidents compete for the same helicopters, crews, or hospital beds.
• Ensuring resource management/resolving resource issues — coordination centers exist precisely to move scarce resources where they matter most.
• Coordinating public information — a Joint Information System keeps messaging consistent across agencies. That is coordination, not command.

Because those three all describe supporting, cross-incident work, none of them can be the correct "not coordination" answer. Only directing/ordering/controlling describes on-scene authority, which is command.

The bigger picture

A reliable exam cue: if the activity gives orders to responders, it is command; if it sets priorities, shares resources, or aligns information across incidents/agencies, it is coordination. Command flows down a single chain to the scene; coordination flows sideways among agencies and upward to policy makers. Keeping those two lanes separate is a core reason ICS scales cleanly from a single fender-bender to a multi-state disaster—the people directing the fight are never the same people arbitrating who gets the last fire engine.