How Incident Command Establishes Objectives That Actually Work in Crisis Situations
Ever wonder how a wildfire spanning 50,000 acres doesn't turn into complete chaos? Or how a multi-agency response to a major disaster somehow stays coordinated despite involving dozens of organizations that have never worked together before?
Here's the thing — it comes down to one fundamental concept: establishing clear incident objectives. Sounds simple, right? Worth adding: it is simple in theory. But getting it right under pressure, with lives on the line and agencies arguing over resources? That's where most responses either succeed or fall apart.
The incident commander (or unified command, when multiple agencies share leadership) is responsible for setting those objectives. And how they do it determines everything that follows.
What Is the Incident Command System and Why Does It Matter?
The Incident Command System, or ICS, is a standardized way to manage emergencies of any size. It was developed in California in the 1970s after a series of catastrophic wildfires revealed that poorly coordinated responses were costing lives. Since then, it's become the backbone of emergency management in the United States and around the world.
ICS isn't just for firefighters. It applies to law enforcement operations, public health emergencies, hazardous material spills, search and rescue missions, and even large-scale planned events. Any situation where multiple organizations need to work together under time pressure benefits from ICS structure Practical, not theoretical..
At its core, ICS provides a clear chain of command, a common organizational structure, and — here's the key part — a shared set of objectives that everyone works toward.
The incident commander is the person (or in unified command, the group of people) who makes the big calls. They're responsible for overall management of the incident. And the very first thing they need to do, before anyone cuts a fire line or evacuates a neighborhood, is establish what success looks like.
What Are Incident Objectives, Exactly?
Incident objectives are concise statements of what the response team intends to accomplish. They're not detailed operational plans — they're the guiding statements that inform every decision that follows Simple as that..
Good objectives answer a simple question: "What does a successful outcome look like?"
For a wildfire, that might be "protect critical infrastructure and evacuate residents while containing the fire perimeter within 72 hours."
For a hazardous materials spill, it could be "protect public health by establishing a safety perimeter, identifying the substance, and initiating containment within six hours."
For a multi-agency law enforcement operation: "safely secure the scene, preserve evidence, and ensure public safety during the investigation."
See the pattern? Each objective is specific enough to guide action but flexible enough to allow on-the-ground adaptation.
The Difference Between Incident Commander and Unified Command
Here's where it gets interesting. Not every incident has a single incident commander.
In simple incidents — a single-vehicle accident, a small structure fire, a localized hazmat release — one person typically takes command. They assess the situation, establish objectives, and direct the response.
But in complex incidents, you often get unified command.
Unified command happens when two or more agencies have jurisdictional authority or functional responsibility. On the flip side, a major wildfire might involve federal wildland fire agencies, state forestry, local fire departments, and law enforcement. A terrorist attack involves FBI, local police, EMS, and emergency management. A pandemic involves public health, hospitals, emergency management, and government leadership Less friction, more output..
In unified command, these agencies don't surrender their authority to a single commander. Also, instead, they work together to establish shared objectives. Each agency representative brings their own priorities and constraints to the table, and through collaboration, they develop objectives that everyone can commit to.
We're talking about harder than single-command decision-making. But it's also more effective, because when agencies feel heard in the objective-setting phase, they're far more likely to cooperate during execution.
Why Establishing Objectives Matters More Than Most People Realize
You might think the tactical stuff — the actual firefighting, the evacuations, the resource deployment — is what makes or breaks an incident response.
It's not. Or at least, it's not primarily.
The quality of your objectives determines the quality of everything that follows. Here's why:
Objectives drive resource allocation. Without clear objectives, incident commanders either hoard resources (just in case) or scramble chaotically. With clear objectives, every resource request can be evaluated against "does this help us accomplish our objectives?" If yes, approve it. If no, redirect. This prevents the common disaster scenario where trucks sit idle while crews elsewhere lack equipment.
Objectives create coordination. When every agency operates under the same objectives, coordination happens naturally. The law enforcement officer knows why they're establishing a perimeter. The paramedic knows why they're staging in a particular location. The public information officer knows what message to communicate. Without shared objectives, you have dozens of well-intentioned people working at cross-purposes.
Objectives enable adaptation. Counterintuitively, clear objectives actually make it easier to change tactics. When conditions shift — a wind change, new intelligence, unexpected casualties — the incident commander doesn't have to rebuild from scratch. They just ask: "How do these new conditions affect our ability to achieve our objectives? Do we need to adjust them, or just our tactics?"
Objectives provide accountability. At the end of an incident, someone will ask: "Did we do the right thing?" Objectives give you a yardstick. You can look at what you accomplished versus what you set out to do, learn from the gap, and improve next time And that's really what it comes down to..
What Happens When Objectives Are Poorly Defined
Real talk — I've seen incidents where the objective-setting phase was rushed or skipped entirely. The results are almost always the same Small thing, real impact..
People default to their own priorities. That's why the public health official focuses on exposure prevention. The police chief focuses on scene security. The fire chief focuses on suppression. Even so, resources get duplicated in some areas and neglected in others. Each is doing what they think is right, but there's no shared direction. Communication becomes fragmented because everyone is working from different mental models of what success looks like.
And here's the worst part: when things go wrong, there's no clear framework for figuring out what to do differently. Without clear objectives, you can't evaluate whether your tactics are working.
How Incident Objectives Are Established: The Process
Now let's get into the practical part. How does an incident commander actually go about establishing objectives?
Step 1: Assess the Situation
Before anything else, the incident commander needs to understand what they're dealing with. This means gathering information about:
- The nature and scope of the incident
- Current and projected conditions
- Threats to life, property, and the environment
- Resources already on scene or available
- Environmental factors (weather, terrain, time of day)
- Jurisdictional boundaries and authorities
This assessment isn't a one-time event. Think about it: it continues throughout the incident as conditions evolve. But you need enough information to make initial decisions Most people skip this — try not to..
Step 2: Identify Constraints and Considerations
Good objectives account for reality. The incident commander needs to understand:
- Legal authorities and restrictions (what can and can't be done)
- Political considerations (what decisions will have public or elected official implications)
- Resource limitations (what do we have, and for how long?)
- Time factors (when must certain actions be taken?)
- Interagency dependencies (who else is involved, and what do they need from us?)
A common mistake is setting objectives without acknowledging constraints, then being surprised when those constraints create problems later Less friction, more output..
Step 3: Develop Preliminary Objectives
Based on the assessment, the incident commander drafts preliminary objectives. These should be:
- Specific enough to guide action — "protect life safety" is too vague. "Evacuate all residents within the designated zone within two hours" gives people something to work with.
- Achievable given resources and conditions — setting unrealistic objectives sets everyone up for failure and erodes trust.
- Measurable — you should be able to look at an objective and determine whether you've achieved it.
- Time-bound — when should this objective be accomplished? Some objectives are ongoing (maintain evacuation traffic control), while others have endpoints (complete primary search of the structure by 1800 hours).
Step 4: Coordinate with Other Agencies (For Unified Command)
If this is a unified command situation, the incident commander (or the initial incident commander) brings other agency representatives into the objective-setting process.
This isn't just a courtesy. That said, the fire department knows the building codes. Which means the health department knows the disease transmission patterns. It's operational necessity. Now, each agency brings knowledge the others might lack. The law enforcement agency knows the threat environment No workaround needed..
Through collaborative discussion, the unified command team refines and finalizes the objectives. The goal isn't to find the lowest common denominator — it's to develop objectives that integrate each agency's mission and authorities into a coherent whole.
Step 5: Communicate Objectives Broadly
Objectives are useless if only the incident commander knows them. The objectives must be communicated to:
- All section chiefs and field personnel
- Supporting agencies
- The public (through the public information function)
- Higher headquarters or elected officials (as appropriate)
This communication should be clear, consistent, and repeated. In the chaos of an incident, people need to hear important information multiple times But it adds up..
Step 6: Review and Adjust
No plan survives contact with reality unchanged. The incident commander should regularly review objectives against current conditions and adjust as needed And that's really what it comes down to. Nothing fancy..
This doesn't mean changing objectives every few hours — that creates confusion and undermines confidence. But it does mean being willing to revise when conditions fundamentally change, when initial objectives were based on faulty information, or when the situation evolves in unexpected ways Less friction, more output..
Common Mistakes People Make With Incident Objectives
After years of studying and teaching incident command, I've seen the same mistakes repeat themselves:
Setting objectives that are really tactics. "Deploy three engine companies to the north side" is a tactic, not an objective. Objectives describe outcomes, not actions. If you find yourself writing sentences that start with "Deploy" or "Send" or "Establish," you're writing tactics, not objectives.
Making objectives too broad. "Ensure public safety" sounds good but provides zero guidance. Every decision-maker interprets "public safety" differently. Narrow it down: "Prevent civilian injuries within the incident perimeter."
Ignoring timeframes. Objectives without deadlines are aspirations, not objectives. When should this be accomplished? If you don't know, say so — but recognize that an objective without a timeframe is harder to evaluate and allocate resources against The details matter here..
Failing to prioritize. In complex incidents, you often have more objectives than you can accomplish with available resources. The incident commander needs to be explicit about which objectives are primary and which are secondary. This prevents the common problem of everyone trying to do everything simultaneously and accomplishing nothing well Which is the point..
Not involving key stakeholders. In unified command, failing to bring all relevant agencies into the objective-setting process creates buy-in problems later. In single command, failing to consult with key personnel (the operations chief, the safety officer, the agency representative) can result in objectives that are disconnected from operational reality Most people skip this — try not to..
Practical Tips for Establishing Better Incident Objectives
If you're involved in incident command — whether as the commander yourself or as someone who supports the command function — here are some things that actually help:
Use the incident objectives format. ICS provides a standard format: "What (the desired outcome), by when (the timeframe), while considering (any constraints or conditions)." Practicing this format before an incident means you'll use it correctly when it matters That's the part that actually makes a difference. Nothing fancy..
Write them down. Objectives that exist only in the incident commander's head aren't objectives — they're intentions. Written objectives can be communicated, referenced, and held accountable And that's really what it comes down to..
Limit the number. Three to five objectives is usually the right range. More than that and you lose focus. If you have more than seven objectives, you're probably not prioritizing properly Took long enough..
Make them visible. Post objectives where everyone can see them — on the incident action plan, on the command board, in the briefing. Every decision-maker should be able to look up the objectives at any time Easy to understand, harder to ignore..
Brief objectives at every shift change. When new personnel arrive or when operational periods change, the first thing they need is the objectives. Don't assume they've heard them already.
Test your objectives against the "so what?" question. If someone asked "Why does this objective matter?" you should be able to answer clearly. If you can't, the objective might not be well-founded But it adds up..
Frequently Asked Questions
Who establishes incident objectives in ICS?
The incident commander (or unified command) is responsible for establishing incident objectives. In practice, this is often done in collaboration with key staff, especially the planning section chief and other section chiefs, before being formalized in the incident action plan.
What's the difference between incident objectives and incident strategies?
Objectives are the specific, measurable outcomes you want to achieve. Strategies are the general approaches you'll use to achieve them. To give you an idea, an objective might be "contain the fire within the existing perimeter within 24 hours.That's why " The strategy might be "direct attack on the fire edge with defensive protection of unburned areas. " Strategies flow from objectives, but they're not the same thing.
Can incident objectives change during an incident?
Absolutely. Practically speaking, conditions change, new information emerges, and initial objectives may no longer be appropriate. The incident commander has the authority to modify objectives as needed, typically documented in each operational period's incident action plan.
How do unified command agencies agree on objectives?
Through collaborative planning. On the flip side, through negotiation and problem-solving, they develop objectives that integrate these different perspectives. Because of that, each agency representative brings their agency's priorities and constraints to the discussion. The key is focusing on shared outcomes rather than individual agency preferences Small thing, real impact..
What's an incident action plan and how does it relate to objectives?
The incident action plan (IAP) is the written document that communicates the objectives, strategies, tactics, and resource assignments for an operational period. Objectives are the foundation of the IAP — everything else in the plan flows from them That's the whole idea..
The Bottom Line
Here's what it comes down to: the quality of your incident response is directly tied to the clarity of your incident objectives.
When the incident commander (or unified command) takes the time to establish clear, specific, achievable, measurable objectives — and communicates them effectively — everything else falls into place more easily. Resources get allocated intelligently. Agencies coordinate naturally. People know what success looks like and can adapt their tactics accordingly.
When objectives are vague, absent, or poorly communicated, even the most skilled responders struggle to be effective.
So if you're involved in emergency response — whether as a commander, a responder, or someone who supports the function — pay attention to the objective-setting phase. It's not the glamorous part of incident command. It's not the firefighting or the rescues or the dramatic decisions.
But it is the foundation everything else builds on. Worth adding: get it right, and your response has a chance. Get it wrong, and you're building on sand Small thing, real impact..
