The activity that is not an example of incident coordination is:

Directing, ordering, or controlling.

What incident coordination usually includes

In most emergency management and ICS/NIMS contexts, incident coordination refers to activities that help align and support multiple incidents or multiple agencies, without actually commanding the tactical response. Typical coordination activities include:

  • Resolving critical resource issues, such as allocating scarce personnel, equipment, or supplies where they are most needed.
  • Establishing priorities among incidents when several events are happening at once.
  • Synchronizing public information messages so all agencies communicate consistent, accurate information to the public and media.

These actions focus on supporting and harmonizing operations across organizations rather than telling individual responders exactly what to do.

Why “directing, ordering, or controlling” is different

Directing, ordering, or controlling are command functions, not coordination functions. They belong to the role of the Incident Commander or other command-level positions that manage tactics at the scene.

Incident coordination, by contrast, operates at a higher or parallel level (for example, in an Emergency Operations Center), where the focus is on policy, priorities, resource support, and information sharing rather than on issuing tactical orders.

So, among the typical choices:

  • Resolving critical resource issues – is incident coordination.
  • Establishing priorities among incidents – is incident coordination.
  • Synchronizing public information messages – is incident coordination.
  • Directing, ordering, or controlling – is not incident coordination (it is command).

Final answer: Directing, ordering, or controlling is not an example of incident coordination.

Information gathered from public forums or data available on the internet and portrayed here.