Which ICS Functional Area Establishes Tactics?
Ever sat in a tabletop drill and heard someone shout, “We need a tactical plan, now!Consider this: ” and wondered which piece of the Incident Command System (ICS) is actually supposed to pull that together? You’re not alone. Consider this: the answer isn’t “the whole thing” and it isn’t “the incident commander” either. Day to day, it’s a specific functional area that lives for exactly that purpose. Let’s unpack it, step by step, so you can walk into the next exercise knowing who to tap for the tactical playbook It's one of those things that adds up. No workaround needed..
What Is the Incident Command System?
ICS is the standardized, on‑scene management framework that lets responders from fire, police, EMS, public health, and even private contractors speak the same language. Think of it as a modular orchestra: the incident commander is the conductor, but each section—operations, planning, logistics, finance/administration—has its own sheet music.
In practice, the system is built around five major functional areas:
- Command – sets overall objectives and priorities.
- Operations – does the work on the ground.
- Planning – gathers intel, develops the incident action plan (IAP).
- Logistics – supplies the resources needed to get the job done.
- Finance/Administration – tracks costs, paperwork, and contracts.
Each area has a chief (or section chief) and a cascade of units beneath them. The beauty of the system is that you can add or drop sections as the incident grows or shrinks, without reinventing the wheel Easy to understand, harder to ignore. Simple as that..
Why It Matters: Tactics vs. Strategy
If you’ve ever watched a military movie, you’ll notice the difference between “strategy” (the big‑picture goal) and “tactics” (the moves that get you there). So naturally, in the world of emergency response, the incident commander defines the strategy—the overall mission, the safety priorities, the end state. The tactics, however, are the concrete steps: where to set up a staging area, how to evacuate a building, which suppression method to use.
Getting tactics wrong can mean wasted resources, delayed rescues, or even injuries. Which means in a wildfire, for example, the commander might decide the strategy is “contain the fire within the fire line by sunset. ” The tactics are the specific fireline construction methods, crew assignments, and equipment placements that actually achieve that containment.
So, who writes those tactics? That’s where the Planning Section steps in.
How It Works: The Planning Section’s Tactical Role
### The Planning Section Chief
Let's talk about the Planning Section Chief is the person who translates the commander’s strategic intent into a usable, day‑to‑day plan. They don’t make the final call on what the incident’s goal is, but they decide how the team will get there.
The chief’s primary product is the Incident Action Plan (IAP), a document that outlines objectives, operational periods, resources, and—crucially—tactics. The IAP is updated every operational period (usually 12‑ or 24‑hour blocks) and distributed to every functional area.
### Developing Tactics
- Gather Intelligence – The Planning Section pulls data from the Situation Unit (weather, maps, hazard assessments), the Resources Unit (what’s available, what’s on the way), and the Documentation Unit (what’s been done so far).
- Identify Objectives – Using the commander’s strategic goals, the Planning Section breaks them into measurable, time‑bound objectives.
- Choose Tactical Options – Here’s the meat: the planners weigh different methods (e.g., direct attack vs. indirect attack in fire suppression) against available resources, safety considerations, and constraints.
- Draft the Tactics Section of the IAP – This includes:
- Operational Period – When the tactic starts and ends.
- Assignments – Which resources (crew, equipment, agencies) are tasked.
- Procedures – Step‑by‑step actions, safety zones, communications.
- Review with Operations – The Operations Section Chief validates that the tactics are feasible on the ground. If a tactic calls for a ladder truck that’s stuck in traffic, the plan gets re‑written.
- Finalize and Disseminate – Once approved by the Incident Commander, the IAP is posted on the Incident Command Post (ICP) board, emailed to all section chiefs, and briefed to each operational unit.
### The Planning Sub‑Units
- Resources Unit – Keeps tabs on what’s in play, what’s needed, and any gaps.
- Situation Unit – Provides the situational picture: maps, weather, incident growth.
- Documentation Unit – Records decisions, ensuring later reviews have a clear audit trail.
All three feed the tactics pipeline. Without accurate resource data, the tactics you write could be pure fantasy; without a solid picture of the incident’s evolution, you’ll be planning for yesterday’s problem.
Common Mistakes: What Most People Get Wrong
1. Assuming the Incident Commander Writes Tactics
New responders often think the commander issues every order. In reality, the commander sets the what and why; the Planning Section crafts the how. When the commander jumps straight into tactical directives, it can bypass the planning process, leading to duplicated effort or missed safety checks.
This is where a lot of people lose the thread It's one of those things that adds up..
2. Skipping the Operational Period Review
The IAP isn’t a “set it and forget it” document. Some teams treat the first draft as final, forgetting to revisit tactics each operational period. That’s a recipe for outdated tactics—think using a blocked road as an evacuation route when the blockage has cleared.
3. Over‑loading the IAP with Detail
A common pitfall is trying to write every micro‑step into the IAP. And the Planning Section should outline the key tactical steps, not a line‑by‑line script. Too much detail clogs the brief and makes it harder for crews to digest under pressure.
4. Neglecting Safety Integration
Tactics without explicit safety zones, PPE requirements, or abort criteria are dangerous. Also, the Planning Section must embed safety considerations directly into each tactical element. Skipping this step is the fastest way to turn a well‑intentioned plan into a liability Not complicated — just consistent..
5. Ignoring Inter‑Agency Coordination
When multiple agencies are involved, each may have its own standard operating procedures. Failing to harmonize tactics across jurisdictions creates confusion. The Planning Section should coordinate with liaison officers to ensure everyone speaks the same tactical language The details matter here..
Practical Tips: What Actually Works
- Use the “Five‑Ws” Checklist for each tactic: Who does it? What is done? Where? When? Why (the safety rationale).
- Create a Tactical Decision Matrix before the incident. List common scenarios (e.g., structure fire, hazardous material spill) and pre‑approved tactical options. During the incident, you’re just picking the right row, not reinventing the wheel.
- Run a Quick “Tactic Walk‑Through” with Operations before the operational period starts. A five‑minute walk‑through on the map can surface gaps you missed in the written plan.
- make use of Technology: Modern incident management software lets you edit the IAP in real time, push updates to tablets, and automatically timestamp changes.
- Document the “Why”: When you choose a particular tactic, note the rationale (resource availability, safety, weather). That makes after‑action reviews far more insightful.
- Practice the Planning Loop: In drills, rotate the Planning Section role among team members. The more people understand the process, the smoother the real‑world handoff.
FAQ
Q: Does the Operations Section ever create tactics?
A: Operations can suggest tactical options, especially when on‑scene realities shift, but the formal tactics go into the IAP and are authored by Planning. The two sections work hand‑in‑hand It's one of those things that adds up..
Q: What if the Incident Commander wants a tactic that Planning says is unsafe?
A: The commander has ultimate authority, but the Planning Section must document the safety concern and propose alternatives. This creates a clear record and often leads to a safer compromise No workaround needed..
Q: How long should an operational period be?
A: Most jurisdictions use 12‑hour periods for fast‑moving incidents and 24‑hour periods for slower, more stable events. The key is to match the period length to the incident’s pace.
Q: Can a single person handle the entire Planning Section?
A: In very small incidents (e.g., a single‑vehicle accident), the Incident Commander may double as Planning. Still, as complexity grows, you’ll need at least a Planning Chief and a Resources Unit And it works..
Q: Where do tactics for multi‑agency incidents get stored?
A: The IAP is the official repository. Also, many agencies maintain a shared digital workspace—like a cloud‑based incident management platform—so every partner can view the latest tactics instantly.
When the dust settles and you’re reviewing the after‑action report, you’ll see a clear line: Strategy → Incident Commander → Objectives → Planning Section → Tactics → Operations. Knowing that the Planning Section is the home of tactics helps you focus your training, your briefing notes, and your post‑incident analysis.
So next time someone yells “We need a tactical plan, now!” you’ll know exactly who to look for, what questions to ask, and how to keep the whole incident moving toward a safe, successful resolution No workaround needed..
