Ever walked into an incident command post and heard someone say, “We need clear objectives, now,” but had no idea who actually writes them?
And if you’ve ever been on a fireground, a hazmat spill, or a cyber‑security breach and felt the confusion when the goals keep shifting, you’re not alone. The answer lies in the ICS functional area that sets the incident objectives—and it’s not the one most people assume.
What Is the Incident Objectives Question in the Context of ICS?
In the Incident Command System (ICS), objectives are the concrete, measurable things you need to accomplish to bring an incident under control. Think of them as the “north star” that guides every action, from resource deployment to public information.
The functional area that actually writes those objectives is the Planning Section. But not Operations, not Logistics, not Finance. Planning is the brain that takes the incident’s overall strategy—usually supplied by the Incident Commander (IC)—and translates it into specific, time‑bound objectives that every other section can follow.
The Role of the Planning Section
The Planning Section does more than just jot down notes. Its core responsibilities include:
- Developing the Incident Action Plan (IAP)
- Maintaining the status of resources and situational awareness
- Forecasting future needs and potential hazards
- Setting, revising, and communicating incident objectives
In short, Planning is the “objective‑setter” because it’s the only section tasked with turning the IC’s strategic intent into actionable steps Less friction, more output..
Why It Matters / Why People Care
When objectives are vague or missing, the whole response unravels. Imagine a wildfire where the only goal is “contain the fire.” Without specifics—like “establish a control line 500 feet north of the ridge by 1500 hrs”—crews waste time guessing, resources get misallocated, and safety suffers Surprisingly effective..
Real‑World Consequences
- Delayed containment – Without clear objectives, crews may chase the fire in circles, burning more acreage.
- Resource fatigue – Units stay on scene longer than needed because there’s no “stop” point.
- Public confusion – Media and community members hear nothing concrete, eroding trust.
On the flip side, when Planning crafts tight, measurable objectives, you see faster decision‑making, better safety outcomes, and smoother inter‑agency coordination. That’s why understanding who writes the objectives isn’t just academic—it’s a matter of life, limb, and liability.
How It Works: From Strategy to Objective
Below is the step‑by‑step flow that most ICS incidents follow. Keep in mind that the exact sequence can vary, but the core logic stays the same.
1. Incident Commander Sets the Strategy
The IC looks at the big picture: the type of incident, the available resources, the legal and political context, and the risk to life and property. The IC says, “Our strategy is to protect life, then property, then the environment.”
2. Planning Receives the Strategy
The Planning Section Chief meets with the IC, often during the initial briefing. They ask:
- What is the desired end state?
- What are the critical milestones?
- What constraints exist (budget, time, safety)?
3. Drafting the Incident Action Plan (IAP)
Planning pulls together intel from Operations, Logistics, Finance/Administration, and the Situation Unit. They draft the IAP, which includes:
- Incident Objectives – Clear, measurable, time‑bound statements.
- Tactics – How each objective will be achieved.
- Resources – What assets are assigned where.
- Safety Messages – Specific hazards tied to each objective.
4. Review and Approval
The IC reviews the draft IAP. That said, if an objective feels off—maybe it’s too ambitious or too vague—the IC sends it back. Planning revises until the IC signs off.
5. Dissemination
Once approved, Planning distributes the IAP to all sections, usually via a briefing and printed copies. Every unit receives the same set of objectives, ensuring everyone pulls in the same direction.
6. Monitoring and Adjusting
During the operational period, Planning tracks progress against each objective. If the fire jumps a ridge, the objective to “establish a control line 500 feet north” may need a new target. Planning updates the IAP and informs the IC, who may adjust the overall strategy Simple, but easy to overlook. Worth knowing..
Common Mistakes / What Most People Get Wrong
Mistake #1: Assuming Operations Sets the Objectives
A lot of new responders think the Operations Section Chief decides what needs to be done because they’re the ones actually doing the work. That’s a classic mix‑up. Operations executes the objectives; Planning writes them Still holds up..
Mistake #2: Using Jargon Instead of Measurable Language
Objectives like “improve safety” or “reduce impact” sound good but are impossible to measure. The right format is SMART: Specific, Measurable, Achievable, Relevant, Time‑bound.
Mistake #3: Forgetting to Align Objectives with the Incident Strategy
If the IC’s strategy is “protect life first, then property,” but the objective reads “secure the entire perimeter by 1800 hrs,” you’ve missed the hierarchy. Objectives must cascade from the strategy Still holds up..
Mistake #4: Overloading the IAP with Too Many Objectives
More isn’t better. Stick to 3‑5 high‑impact objectives per operational period. But ten tiny goals can drown a crew. The rest belongs in the “tactics” section That alone is useful..
Mistake #5: Not Updating Objectives When Conditions Change
Incidents are dynamic. Because of that, if a storm rolls in, the original objective to “contain the fire by sunset” may become unsafe. Planning must revise the IAP promptly; otherwise, crews chase an impossible target.
Practical Tips / What Actually Works
- Start with the “End State” – Write a one‑sentence description of what success looks like. Then break it down into objectives.
- Use the “Objective‑Tactic‑Resource” chain – For each objective, list the tactic that achieves it and the resource that will carry it out. This keeps the IAP tight.
- Make objectives visible – Post them on a whiteboard in the command post, include them in radio briefings, and put them on the tactical map. Repetition cements focus.
- Assign an Objective Owner – Even though Planning writes them, give a specific section or individual responsibility for each objective’s progress.
- Run a quick 5‑minute “objective check” each shift change – Verify that the incoming crew knows what they’re supposed to accomplish before the next watch starts.
- apply technology – Modern incident management software can auto‑populate objectives into dashboards, making real‑time tracking easier.
- Practice with tabletop exercises – The more often your team drills the objective‑setting process, the smoother it will be under pressure.
FAQ
Q: Can the Operations Section ever modify an objective?
A: Only with the IC’s approval. Operations can recommend changes based on field realities, but the official revision must come from Planning.
Q: What if there’s no Planning Section Chief on scene?
A: In smaller incidents, the IC may assume Planning duties or delegate them to a qualified staff officer. The key is that someone formally owns the objective‑writing process.
Q: How often should the IAP be updated?
A: Typically every 12‑24 hours, or sooner if the incident’s conditions shift dramatically (e.g., sudden weather change, new hazard detection).
Q: Do financial constraints affect objective setting?
A: Yes. The Finance/Administration Section provides cost data to Planning, which then tailors objectives to stay within budget while still meeting the strategic goals.
Q: Are objectives the same as goals?
A: Not exactly. Goals are broad, long‑term aspirations (e.g., “protect the community”). Objectives are the short‑term, concrete steps that move you toward those goals.
When the dust settles and the incident is finally under control, you’ll notice one thing: the teams that succeeded had one thing in common—a clear, well‑crafted set of objectives that everyone understood and could measure. That clarity didn’t happen by accident; it was the product of the Planning Section doing its job.
So next time you walk into a command post and hear, “We need objectives now,” you’ll know exactly who to look for, what questions to ask, and how that single piece of the puzzle can make the whole response click into place. And that, in practice, is the difference between a chaotic scramble and a coordinated, safe resolution.
