The ICS Org Chart and the EOC Org Chart Are Not the Same Chart

Quick Answers

ICS is: the on-scene command structure. An Incident Commander or Unified Command, a Command Staff, and a General Staff directing tactical resources against one incident.

An EOC is: an off-scene coordination structure. It supports Incident Command and manages jurisdiction-wide consequences. FEMA doctrine is blunt about the line — EOCs support Incident Command and do not normally perform command functions.

The trap: both are NIMS, and both charts have boxes labeled Operations, Planning, and Logistics. Practitioners assume the boxes mean the same thing. They do not.

One Component, Two Different Jobs

The NIMS Command and Coordination diagram stacks three tiers: MAC Group across the top for offsite policy guidance and resource prioritization, EOCs in the middle for support to Incident Command, and ICS at the bottom for on-scene incident management. The Joint Information System runs vertically down the entire left margin, spanning all three.

Read that stack as three verbs. ICS commands. The EOC coordinates. The MAC Group prioritizes. Every structural difference below follows from those three verbs.

The ICS Chart

The field chart is the one everyone knows, and the one NIMS standardizes hardest. An Incident Commander or Unified Command, a Command Staff of PIO, Safety Officer, and Liaison Officer, and a General Staff of four sections: Operations, Planning, Logistics, and Finance/Administration.

The modular expansion underneath is doctrinally fixed. Operations grows into Branches, Divisions, Groups, and Task Forces. Planning holds the Resources, Situation, Documentation, and Demobilization Units. Logistics splits into Service and Support Branches. Finance/Administration holds Time, Procurement, Compensation/Claims, and Cost Units.

Unity of command is absolute — every responder has exactly one supervisor, and the ICS 203 and ICS 204 record who that was for each Operational Period.

The Three EOC Charts

Here is where practitioners get surprised. NIMS does not prescribe one EOC organization. It describes three common structures, and states plainly that EOC leaders determine the structure that best meets their needs.

1. ICS or ICS-like

EOC Director, a PIO, and four sections. But look at what FEMA appends to each section title: Operations Coordination Section. Planning Coordination Section. Logistics Coordination Section. Finance/Administration Coordination Section.

That word is doing real work. The Operations Coordination Section is the primary EOC point of contact for on-scene response personnel — it coordinates unmet resource needs and ensures operational support reaches incident objectives. It is not running tactics, and it can organize by ESF or RSF instead of by ICS Branch, which no field Operations Section would ever do.

The advantage is familiarity and no training burden beyond ICS. The disadvantage is that the shared vocabulary hides the different job.

2. Incident Support Model

The ISM is the structure that actually looks different on paper, and it is the one worth studying even if you never adopt it. Four sections under the EOC Director: Situational Awareness, Planning Support, Resources Support, Center Support.

Two deliberate structural moves:

Situational awareness becomes its own section, reporting directly to the EOC Director. In field ICS, situation is a unit buried inside Planning. ISM says information is important enough in a coordination environment to sit at the top table — collecting and disseminating incident information, processing requests for information, and producing the reports and briefings the Director actually decides from.

Operations, Logistics, and Comptroller/Purchasing collapse into one Resources Support Section. One stop for sourcing, ordering, tracking, funding purchases and contracts, and reimbursement of expenses — an honest admission that in an EOC these are not separable activities.

FEMA's own caveat is worth quoting: ISM is not organized to manage response or recovery efforts. That is a feature. If your EOC's job is support, structure it for support.

3. Departmental

The EOC runs the jurisdiction's day-to-day departmental hierarchy — Public Works, Health and Human Services, Public Safety, Administration — coordinated by the emergency manager or a senior official. It can be ESF-aligned instead. Its virtue is that representatives function with almost no startup, because nobody has to learn a new chart under stress.

Where the Same Word Means Different Work

FEMA puts the resource difference in two columns, and it is the cleanest summary in the doctrine. The command post identifies needs, orders, checks in, assigns, tracks, and demobilizes. The EOC receives requests, prioritizes them, locates and orders, assigns according to priorities, tracks use, and pays for resources.

Prioritizes. Pays. Neither verb appears on the ICP side. That is the whole difference in two words.

The EOC ordering sequence also runs a fixed ladder the command post never sees: jurisdictional resources first, then local mutual aid agreements, then external sources — private sector, VOAD, state-acquired resources, EMAC requests to other states, and federal assistance. The ICP sees a resource arrive.

Two Clocks, One Incident

This is the difference that costs money, and almost nobody plans for it.

FEMA doctrine states directly that the EOC operational period may be different from the Incident Command operational period, and should be established in the EOC's own SOPs. The ICP runs the Planning P and produces an IAP for each Operational Period. The EOC runs its own battle rhythm — SitRep publication times, briefing schedules, situation picture updates — and produces an EOC action plan on its own cycle.

So the incident runs 12-hour periods and the EOC runs 24. Doctrinally fine. Operationally normal. Now follow one piece of equipment: ordered by the EOC's Logistics Coordination Section against a request the Operations Coordination Section prioritized, checked in at the incident on an ICS 211, assigned on an ICS 204, logged on an ICS 214, demobilized on an ICS 221 — while the EOC separately tracks its cost against the activation.

At closeout that resource has two partial records on two different clocks, and neither alone proves the full picture. The FEMA Public Assistance reviewer asks who authorized it, when it arrived, what it did, how long it worked, and what it cost. The ICP record has the work. The EOC record has the authorization and the money. The seam between them is where reimbursement quietly dies — not because the cost was ineligible, but because no single record spans both clocks.

Most agencies close that seam with reconciliation spreadsheets after the fact. That is reconstruction, and reconstruction is exactly what an auditor is trained to spot. The alternative is both structures writing into one operational-period-aware record as work happens, so the resource carries a continuous history across the boundary instead of having one rebuilt at day 30.

Honorable Mentions: MAC and JIS

Neither is a fourth org chart. They are the layer above and the ribbon across.

MAC Group sits above the EOCs — agency administrators, department heads, and elected officials making offsite policy decisions and prioritizing resources across competing incidents. No tactical authority, no operational staff. When two counties want the same debris contractor, that call belongs to the MAC Group, not the state EOC. We covered where that authority line falls in detail.

JIS is the only structure spanning all three tiers at once. PIOs at the ICP, in the EOC, and supporting the MAC Group operate as one system so the jurisdiction speaks with a single voice. Notably, in the ISM chart the Center Support Section carries the JIC as a supported facility — the EOC is expected to physically sustain the JIC, not just liaise with it.

The Bottom Line

Same doctrine, different charts, and one of them has three variants. ICS commands with a fixed modular structure. The EOC coordinates using whichever of the three NIMS structures fits the jurisdiction. The section titles overlap; the work does not.

Agencies that write both structures into the same EOP, staff them with people who know which chart they are standing in, and keep one record across both operational-period clocks run cleaner activations and defend cleaner audits. Agencies that assume the EOC is just ICS in a building with better coffee find out at closeout.

For the doctrine underneath all of this, start with NIMS and ICS Explained and the Multi-Agency Coordination Systems explainer. The full library lives in the NIMS and ICS Reference.