The management of any emergency, whether a localized hazardous material spill or a multi-state natural disaster, requires a clear sense of direction. In the framework of the Incident Command System (ICS), the incident objectives that drive incident operations are established by the Incident Commander (IC) or Unified Command (UC).

This fundamental principle ensures that all tactical activities are aligned with a centralized strategy. The Incident Commander holds the ultimate responsibility for the overall management of the incident, including the critical task of defining what must be accomplished. When multiple jurisdictions or agencies are involved, a Unified Command is formed, allowing these diverse entities to work together to establish a single set of incident objectives without individual agencies abdicating their authority or responsibilities.

The Pivotal Role of the Incident Commander in Objective Setting

The Incident Commander is the first position filled in any ICS activation. Regardless of the size of the incident, someone must be in charge. One of the very first actions this individual takes upon arriving at the scene and assuming command is to assess the situation and determine the incident objectives.

These objectives are not merely suggestions; they are the governing directives for every person deployed to the incident. The IC must look beyond the immediate chaos to identify the "end state" of the operation. By establishing these objectives early, the IC provides a roadmap for the Planning Section to develop strategies and for the Operations Section to execute tactics.

In smaller incidents, the Incident Commander might perform all functional responsibilities, including writing the objectives. As the incident grows in complexity and a General Staff is activated, the IC remains the one who approves the final objectives, even if the Planning Section Chief assists in documenting them within the Incident Action Plan (IAP).

Understanding Unified Command and Collaborative Objectives

In many modern emergencies, a single agency rarely has all the resources or legal authority to manage every aspect of the response. Consider a major flood that affects transportation, public health, and private property across three different counties. In such a scenario, a Unified Command (UC) is established.

The Unified Command consists of the Incident Commanders from the various jurisdictions and agencies involved. Instead of having multiple sets of conflicting goals, the UC members sit together to negotiate and agree upon a consolidated set of incident objectives. This collaborative process is essential for:

  1. Eliminating Duplication: Ensuring that two different agencies aren't trying to achieve the same task using different methods.
  2. Resource Optimization: Directing all available resources toward a shared priority.
  3. Consistency: Providing a single "voice" for the incident, which is crucial for public information and safety.

Even in a Unified Command, the principle remains: it is the command level that establishes the objectives that drive the entire operational machine.

Management by Objectives as a NIMS Characteristic

The National Incident Management System (NIMS) identifies "Management by Objectives" as one of its 14 core management characteristics. This approach is what separates professional incident management from a reactive, uncoordinated response.

Management by objectives within the ICS involves a specific four-step cycle:

  1. Establishing overarching objectives.
  2. Developing strategies based on those objectives.
  3. Developing and issuing assignments, plans, procedures, and protocols.
  4. Establishing specific, measurable tactics or tasks for various incident management functional elements and directing efforts to attain them.

Without the Incident Commander setting the objectives in step one, the rest of the response has no foundation. The objectives serve as the "why" behind every "how" performed by the responders on the ground.

The SMART Criteria for Incident Objectives

In my years of experience managing complex regional incidents, I have seen that the quality of an incident response is often a direct reflection of the clarity of the objectives set at the command post. Effective Incident Commanders do not set vague goals like "put out the fire" or "help the people." Instead, they utilize the SMART criteria to ensure the objectives are actionable.

Specific

Objectives must be clear and concise. Instead of "Improve safety," a specific objective would be "Establish a 500-foot perimeter around the hazardous zone by 18:00 hours."

Measurable

There must be a way to track progress. "Search all affected residential structures in Sector A" is measurable; you either have a list of searched homes or you don't.

Achievable

The objectives must be realistic given the resources currently available or expected during the operational period. Setting an objective to "Evacuate the entire city in 30 minutes" when you only have two transport buses is a failure of command.

Relevant

Every objective must directly relate to the overall strategic goals of life safety, incident stabilization, or property preservation.

Time-bound

Objectives must have a deadline, typically tied to the "Operational Period"—the window of time (usually 12 or 24 hours) for which the current Incident Action Plan is active.

Prioritizing Objectives: The Golden Rules of Response

When an Incident Commander sits down to establish objectives, they aren't working in a vacuum. ICS dictates a hierarchy of priorities that guides the objective-setting process.

1. Life Safety

The first and most important objective is always the protection of life. This includes the safety of the responders as well as the public. Objectives related to search and rescue, medical triage, and evacuation always take precedence.

2. Incident Stabilization

Once life safety is addressed, the IC focuses on keeping the incident from getting worse. This might involve containing a spill, extinguishing the seat of a fire, or securing a perimeter in a law enforcement scenario.

3. Property and Environmental Preservation

The final priority level involves protecting infrastructure, private property, and the natural environment. While important, these goals never override the safety of individuals or the need to stabilize the situation.

How Objectives Are Communicated: The Incident Action Plan (IAP)

Once the Incident Commander or Unified Command establishes the objectives, they must be communicated to the rest of the organization. This is done through the Incident Action Plan (IAP).

The IAP is a formal document (or a series of documents) that outlines the incident's status and the plan for the upcoming operational period. The core of the IAP is ICS Form 202 (Incident Objectives). This form lists the specific objectives set by the IC/UC and provides general situational awareness.

As an Incident Commander, I have found that the ICS 202 is the most important piece of paper at the scene. It ensures that the Operations Section Chief knows exactly what the tactical goals are, and it ensures that the Logistics Section knows what resources they need to procure to meet those goals.

The Relationship Between Objectives, Strategies, and Tactics

A common point of confusion for those new to ICS is the difference between these three levels of planning. It is vital to understand that while the Incident Commander sets the objectives, they often delegate the development of strategies and tactics.

  • Objectives: State what is to be accomplished. (Established by the IC/UC).
  • Strategies: State how the objectives will be achieved. (Often developed by the IC with input from the Planning and Operations Section Chiefs).
  • Tactics: Specify the specific actions and resource assignments to execute the strategy. (Developed by the Operations Section Chief).

For example:

  • Objective: "Prevent the floodwaters from reaching the Main Street substation for the next 24 hours."
  • Strategy: "Deploy physical barriers and high-capacity pumps along the north bank."
  • Tactic: "Strike Team 1 will stage 5,000 sandbags at the intersection of 5th and Main by 14:00."

By keeping these roles distinct, the Incident Commander avoids "micromanaging" the scene and instead focuses on the high-level strategic direction.

Real-World Perspective: The Challenge of Shifting Objectives

In my experience on the ground, incident objectives are rarely static. An emergency is a dynamic environment. I recall a specific incident involving a multi-car pileup during a winter storm. Initially, the Incident Commander’s objective was purely life safety: "Extricate and transport all trapped victims within 60 minutes."

However, mid-way through the operation, a fuel tanker involved in the crash began to leak. The IC had to immediately establish a new objective for incident stabilization: "Contain the fuel spill and establish a 300-foot fire suppression line within 20 minutes."

This illustrates that the IC/UC must constantly evaluate the "Ground Truth"—the reality of the situation versus the plan. If the objectives are no longer relevant or achievable, the Incident Commander must have the situational awareness to revise them and communicate those changes immediately.

What Happens if the Incident Commander Fails to Set Objectives?

When a response lacks clear objectives established from the top, the result is "freelancing." Freelancing occurs when individual responders or teams begin taking actions based on what they think needs to be done rather than what the incident management requires.

This is dangerous for several reasons:

  • Safety Risks: Responders may enter hazardous areas without backup or coordination.
  • Resource Waste: Multiple teams might perform the same task while other critical needs are ignored.
  • Loss of Control: The Incident Commander loses the ability to predict the outcome of the event.

In every case study of failed emergency responses, from the early wildfire disasters of the 1970s to modern-day urban crises, a lack of clear, centralized objectives is almost always a contributing factor. This reinforces why the rule is so strict: the Incident Commander, and only the Incident Commander (or UC), is the authority for establishing these objectives.

Summary of Responsibilities within the Planning Cycle

The establishment of objectives is part of a larger "Planning P" process used in NIMS. Here is how the responsibility breaks down:

  1. Incident Command: Establishes the objectives and approves the IAP.
  2. Operations Section: Provides input on the feasibility of objectives and executes the tactics.
  3. Planning Section: Facilitates the planning meetings and documents the objectives into the IAP.
  4. Logistics Section: Ensures the objectives can be supported by providing the necessary personnel and equipment.
  5. Finance/Administration: Tracks the costs associated with achieving the objectives.

Ultimately, every section of the ICS organization exists to support the objectives set by the Command level.

Frequently Asked Questions

Who is responsible for establishing incident objectives?

The Incident Commander (IC) or the Unified Command (UC) is responsible for establishing the objectives that drive the incident operations.

Can the Operations Section Chief set the incident objectives?

No. The Operations Section Chief develops the strategies and tactics to achieve the objectives, but the objectives themselves must be set or approved by the Incident Commander.

What is the difference between a goal and an objective in ICS?

In the context of NIMS/ICS, "objectives" are the specific, measurable results to be achieved. "Goals" is a less formal term and is often used interchangeably with "Strategic Priorities" (Life Safety, Incident Stabilization, Property Preservation).

When are incident objectives established?

Incident objectives are established during the initial assessment and are formally documented at the beginning of each planning cycle for the upcoming operational period.

How does Unified Command handle conflicting objectives?

In a Unified Command, the representatives from different agencies must reach a consensus. They work together to create a single set of objectives that addresses the needs and legal mandates of all participating organizations.

Conclusion

The principle that incident objectives are established by the Incident Commander or Unified Command is a cornerstone of effective emergency management. This centralized authority ensures that the response is organized, prioritized, and safe. By focusing on SMART objectives and adhering to the priorities of life safety, incident stabilization, and property preservation, the IC/UC provides the necessary leadership to navigate even the most complex crises. Whether you are a first responder or a corporate crisis manager, understanding this hierarchy is essential for operational success. In the absence of clear objectives, there is only chaos; with them, there is a path to resolution.