Which ICS Functional Area Sets the Incident Objectives
If you've ever sat through ICS training — or worse, tried to run an emergency response without it — you know that one of the first questions that comes up is exactly this: who sets the incident objectives? It's one of those foundational ICS questions that sounds simple but trips people up all the time.
Here's the straightforward answer: the Incident Commander sets the incident objectives. But — and this is the part most people miss — the Planning Section is the functional area that drives the entire planning process to develop those objectives into a usable Incident Action Plan.
Let me unpack what that actually means, because the relationship between the Incident Commander and the Planning Section is where the real understanding lives.
What Is ICS and Why Does It Matter
ICS, or the Incident Command System, is the standardized framework used across the United States for managing incidents of all sizes — from a two-alarm fire to a massive hurricane response. It was developed in the 1970s following a series of catastrophic wildfires in California, where poor coordination between agencies led to deaths and devastating property loss The details matter here..
The system exists because emergencies don't respect jurisdictional boundaries. That's why when a wildland fire crosses from federal to state to private land, when a hazmat spill threatens multiple counties, when a disaster overwhelms local resources and draws in federal assistance — everyone needs to be on the same page. ICS provides that common language and structure.
At its core, ICS organizes response into five major functional areas: Command, Operations, Planning, Logistics, and Finance/Administration. Each has a specific role, and they all report up through the chain of command Still holds up..
Understanding which piece does what isn't just academic. Get it wrong, and you end up with duplicated efforts, gaps in coverage, or — worse — objectives that nobody actually agreed on Surprisingly effective..
The Role of the Incident Commander
The Incident Commander sits at the top of the ICS structure. This is the person with overall authority and responsibility for the incident. Full stop The details matter here..
The IC makes the big calls: what are we trying to accomplish, what's our priority, what's the overall strategy? These become the incident objectives — the foundation upon which everything else is built Small thing, real impact. Practical, not theoretical..
Here's how it works in practice: When an incident occurs, the first arriving responder or appointed IC establishes initial objectives almost immediately. " Those are objectives. Plus, "Protect life safety, protect the hospital, establish a perimeter. They're broad, strategic statements about what success looks like.
As the incident grows and more resources arrive, those objectives get refined through the planning process. But the IC always retains authority over them. The objectives belong to Command But it adds up..
How the Planning Section Fits In
This is where it gets interesting. The Planning Section — led by the Planning Section Chief — is the functional area that facilitates the development of the Incident Action Plan, which contains those objectives in written form Turns out it matters..
Think of it this way: the Incident Commander provides the destination, and the Planning Section builds the roadmap.
The Planning Section does the heavy lifting of gathering information, assessing the situation, forecasting what might happen next, and organizing that into a coherent plan. Within the Planning Section, the Situation Unit tracks what's happening now and creates the maps and status displays that everyone uses. The Resources Unit tracks what's assigned and what's available. The Documentation Unit keeps everything on record.
When it's time to develop the next operational period's plan — typically every 12 or 24 hours, depending on the incident — the Planning Section Chief pulls together a planning meeting. Representatives from each functional area come together, review the current situation, discuss resource needs, and build out the tactics that will achieve the objectives set by the IC That's the whole idea..
So while the IC says "here's what we need to accomplish," the Planning Section says "here's how we'll do it, here's what we need, and here's what we expect to happen."
The Incident Action Plan: Where Objectives Live
The Incident Action Plan, or IAP, is the written document that captures everything. Every operational period gets an IAP — it includes the incident objectives for that period, the specific strategies and tactics to achieve them, resource assignments, communications plans, and safety measures Small thing, real impact. Nothing fancy..
The Planning Section produces this document. But the objectives within it come from the Incident Commander.
This distinction matters because in ICS, authority and responsibility flow clearly. The IC can't delegate away the responsibility for objectives — they're ultimately a Command function. But the IC absolutely depends on the Planning Section to turn those objectives into an actionable plan that everyone can follow.
What Most People Get Wrong
The most common mistake I see is confusion about who actually "owns" the objectives. Some people think the Planning Section sets them because they write them down. Others think the Operations Section sets them because they're the ones doing the tactical work.
Neither is correct.
Another misunderstanding: treating incident objectives as fixed and unchanging. In reality, objectives evolve as the incident changes. Also, the initial objectives at the start of a wildland fire — "protect structures in the path" — might shift to "contain the fire perimeter" once structures are secured. The Planning Section's job is to help the IC reassess and update those objectives each planning cycle.
People also sometimes skip the formal planning process entirely on smaller incidents, thinking ICS is only for big operations. Even a simple structure fire follows ICS principles — there's a commander, someone handling operations, someone planning what's next. That's a mistake. The terminology might be less formal, but the structure exists.
Practical Tips for Getting This Right
If you're in a position where you're either the IC or working within the Planning Section, here's what actually matters:
For Incident Commanders: Be clear and specific when you set objectives. "Save lives" is a given — it's your starting point. But your operational objectives need to be measurable. "Establish a 500-foot defensive perimeter within two hours" gives your team something concrete to work toward. Trust your Planning Section to build the tactics around those objectives Worth keeping that in mind. Still holds up..
For Planning Section personnel: Don't wait for the IC to come to you with fully formed ideas. Proactively gather information, present options, and help the IC see the full picture. Your job is to make their decision-making easier, not just document what they've already decided.
For everyone else: Understand that objectives aren't suggestions. They're the compass for the entire response. If you're working an incident and your actions aren't moving toward the stated objectives, something's wrong.
FAQ
Can the Planning Section Chief set incident objectives?
No. The Planning Section Chief facilitates the planning process and helps develop the plan, but the authority to set objectives rests with the Incident Commander. This is a Command function Not complicated — just consistent. Nothing fancy..
What happens if there's no Planning Section established?
On smaller incidents, the IC often handles planning functions directly or delegates them informally. But as incidents grow, establishing the Planning Section becomes critical — trying to manage complex planning without the section is a common failure point Turns out it matters..
How often do incident objectives change?
It depends on the incident. Some objectives stay consistent for the entire event. Others shift with each operational period as conditions change. The planning cycle — typically 12 or 24 hours — is when objectives are formally reviewed and updated.
What's the difference between incident objectives and operational objectives?
Incident objectives are the broad, strategic goals set by the IC. That's why operational objectives are the more specific, measurable targets that Operations develops to achieve the incident objectives. Think of it as incident objectives being "what we want" and operational objectives being "how we'll know we're getting it It's one of those things that adds up..
Who approves the Incident Action Plan?
The Incident Commander approves the IAP before each operational period begins. The Planning Section produces it, but Command authorizes it.
The Bottom Line
Here's the thing — ICS works when everyone understands their role and trusts the system. The Incident Commander sets the direction. The Planning Section charts the course. Operations executes it. Logistics and Finance keep it resourced and accounted for Simple, but easy to overlook..
When it comes to incident objectives, the answer is clear: the Incident Commander sets them, and the Planning Section builds the plan around them. Here's the thing — get that relationship right, and your incident response has a solid foundation. Get it wrong, and you're just hoping things work out But it adds up..
They usually don't.
