Which Command Staff Member Approves the Incident Action Plan
If you've ever sat through an ICS training class, you've probably seen the org chart — all those boxes and arrows showing who reports to whom. But when it comes time to actually run an incident, one question trips up a lot of people: who actually signs off on the incident action plan?
Here's the short answer: the Incident Commander approves the incident action plan. But like most things in emergency services, there's more nuance to it than that single sentence. Let me walk you through what actually happens, because understanding this distinction matters — especially when things get complicated.
What Is an Incident Action Plan?
An incident action plan (IAP) is the written document that guides operations for a specific time period, called an operational period. Think of it as the game's game plan for the next several hours of an incident.
The IAP typically includes:
- The incident objectives (what are we trying to accomplish?)
- The strategy for achieving those objectives
- Resource assignments (who's doing what)
- Communications plan
- Safety measures
- Any contingencies or contingencies
Every operational period gets its own IAP. So if you're running a 12-hour incident, you might have two or three different plans — each one covering a specific chunk of time Still holds up..
The planning section chief is typically responsible for pulling the IAP together. They coordinate with all the other sections — operations, logistics, finance — and synthesize all that information into a coherent document. But here's the key: developing the plan and approving the plan are two completely different things.
Why the IAP Matters
Without a solid incident action plan, you're just reacting. Now, people run in different directions. Resources get duplicated or, worse, nothing gets covered at all. The IAP brings structure to chaos Easy to understand, harder to ignore..
It also creates accountability. Think about it: when something goes wrong, you can look back at the plan and see what was supposed to happen. When things go right, the plan is the roadmap that got you there It's one of those things that adds up. Took long enough..
Who Approves the Incident Action Plan
The Incident Commander approves the incident action plan. That's the straightforward answer, and it's the one you'll find in any ICS manual Worth keeping that in mind..
The IC is the person in charge of the entire incident. They're responsible for everything — outcomes, safety, resource management, coordination with outside agencies. So it makes sense that the person with ultimate responsibility would be the one signing off on the plan that guides the operation.
But here's where it gets interesting.
The Unified Command Situation
When two or more agencies respond together — say, a wildfire with both forest service and local fire department — they often establish a Unified Command. In this structure, multiple incident commanders share authority.
So who approves the IAP then?
All of them. The Unified Command operates by consensus, and the incident action plan requires approval from all command entities. This can take longer, but it ensures everyone is on the same page and no agency is being asked to implement a plan they didn't agree to.
At Different Incident Levels
ICS scales up or down depending on the size of the incident. At a small, single-resource response, the incident commander might be the one person on scene with a portable radio. They might verbally approve the plan — there's no requirement for a written IAP below a certain threshold Worth keeping that in mind..
As incidents grow, the planning process becomes more formal. The written IAP becomes standard, and the approval process follows a clear chain. But the principle stays the same: the person in command — the IC — is the one who approves.
What About the Planning Section Chief?
This is where confusion creeps in. Because of that, the Planning Section Chief does the heavy lifting. They coordinate the planning process, gather input from all sections, compile the plan, and present it to the command staff. Their role is essential.
But they're not the approver. They're the facilitator.
I've seen people assume that because the planning chief "makes" the plan, they must "approve" it. Worth adding: that assumption can create problems, especially if the IC isn't closely involved in review. The buck stops with the Incident Commander.
How the Approval Process Works
Here's how it typically plays out:
-
The planning section chief convenes a planning meeting, usually a few hours before the next operational period begins Worth keeping that in mind..
-
Each section reports on their situation — what resources they have, what they're facing, what they need.
-
The Incident Commander reviews the proposed objectives and strategy Practical, not theoretical..
-
The planning section chief drafts the IAP based on that discussion.
-
The IC reviews the written plan and either approves it or requests changes.
-
Once approved, the plan is disseminated to all sections and becomes the guiding document for the next operational period.
This happens every operational period. It's a cycle — plan, approve, execute, evaluate, repeat.
Briefing the Plan
Approval isn't the final step. Once the IAP is approved, it needs to be communicated. In practice, the operations section chief typically briefs all subordinate personnel on the plan's contents. Everyone needs to know what the objectives are and what their role is in achieving them.
Common Mistakes People Make
Assuming the planning chief has approval authority. I've seen this cause real friction. The planning section chief works for the IC, not the other way around. If there's a disagreement about the plan, it's the IC who makes the final call The details matter here..
Skipping the approval step in fast-moving situations. When things are escalating, there's pressure to just "get after it" and skip the formal planning process. But skipping the IAP — or approving it without real review — leads to confusion on the ground The details matter here..
Not understanding unified command dynamics. If you're used to a single IC structure, transitioning to Unified Command can be jarring. The approval process changes, and everyone needs to be clear on that from the start Small thing, real impact..
Failing to communicate changes. The approved IAP is the plan — until it's not. If circumstances change dramatically mid-operational period, the IC may need to approve modifications. But those changes need to be communicated just like the original plan.
Practical Tips for Handling IAP Approval
If you're in a position where this matters for your work, here are a few things worth keeping in mind:
Know who the IC is. Seems obvious, but in complex incidents with multiple agencies, it can get murky. Make sure you know who has approval authority before you start the planning process It's one of those things that adds up..
Build time into the cycle. The planning process takes time. If your operational periods are too short, you'll constantly be playing catch-up. Most guidance suggests at least a few hours between the planning meeting and the start of the next operational period Which is the point..
Document everything. The approved IAP should be in writing, distributed to all relevant personnel, and retained for after-action review. Verbal approvals are fine in emergencies, but they create problems later.
When in doubt, ask. If you're not sure about the approval process in your specific situation — especially with multi-jurisdictional incidents — ask. It's better to clarify upfront than to assume Not complicated — just consistent..
FAQ
Does the Incident Commander always approve the IAP in writing?
Not always. This leads to for small incidents, verbal approval is acceptable. For larger or more complex incidents, written approval is standard and often required by policy or protocol.
Can the IC delegate approval authority?
In theory, the IC can delegate, but this is rare and risky. The IC retains overall responsibility for the incident, so delegating approval of the plan that guides the operation would be unusual. Some structures allow the Deputy IC to approve plans in the IC's absence, but this should be explicitly established.
What happens if the IAP isn't approved?
If the plan isn't approved, it can't be implemented. On top of that, operations either continue under the previous plan (if still valid) or wait until approval is obtained. Running operations without an approved plan is essentially operating without direction — and that's when things go sideways.
Who approves the IAP at a wildland fire with multiple agencies?
In a multi-agency wildland fire, Unified Command is common. Day to day, all agencies in the Unified Command must approve the IAP together. This ensures each agency is committed to the plan and understands their role in it The details matter here..
Is the IAP the same as the incident briefing?
No. Now, the IAP is the comprehensive written plan. An incident briefing is a quick update — often just a few minutes — given at the start of an operational period. The briefing typically covers the key points of the IAP, but they're different documents serving different purposes.
The Bottom Line
The Incident Commander approves the incident action plan. That's the answer, and it's not complicated — but the context around it matters.
Understanding who approves the IAP isn't just about checking a box in your training record. It's about understanding the chain of command, the flow of authority, and how decisions get made under pressure. When you know who has the pen, you know who has the power to shape how an incident is managed Not complicated — just consistent..
And that matters when you're the one in the hot seat.
