MAC Group vs. EOC vs. Unified Command: Who Actually Has Authority When Incidents Escalate

Quick Answers
A MAC Group is: a policy-level body of agency administrators and senior executives that prioritizes resources and coordinates strategic decisions across multiple agencies or multiple incidents — without taking command of any single incident.
An EOC is: an off-scene operational coordination structure that supports a single jurisdiction's response — coordinating resources, information, and inter-agency support. The EOC is not in command of the incident.
Unified Command is: a mode of ICS used when multiple agencies share jurisdictional authority over the same incident. It is on-scene, tactical, and co-equal — not a separate structure outside ICS.
Three different authorities. Three different jobs. The most common — and most expensive — doctrinal error in local government is collapsing them into one.
The Authority Map
| Structure | Level | Where It Sits | Who Is In It | What It Decides | What It Cannot Do |
|---|---|---|---|---|---|
| Unified Command | Tactical | On-scene, at the ICP | Co-equal Incident Commanders from each agency with jurisdictional authority | Tactical objectives, strategies, resource assignments, operational period priorities for this incident | Set strategic priorities across multiple incidents; make policy for jurisdiction |
| EOC | Operational support | Off-scene, jurisdiction-wide | EM director, agency liaisons, support staff | Resource coordination across the jurisdiction, information management, support to ICS | Command the incident; override the IC; set state-level policy |
| MAC Group | Strategic / policy | Off-scene, often state-level | Agency administrators, department heads, elected officials | Resource prioritization across competing incidents, policy decisions, strategic direction | Take tactical command; override IC decisions on tactics |
| Joint Information System | Public messaging | Wherever JIC personnel sit | PIOs from each participating agency | Coordinated external messaging | Make operational or policy decisions |
This is the same four-row structure introduced in our Multi-Agency Coordination Systems explainer, expanded with two additional columns — what each structure decides and what each cannot do. Those last two columns are what separate doctrine from the lived reality of an activation.
Scenario 1: A Type 1 Incident Overruns a Single IC
A wildfire crosses from federal land onto state land, then into the wildland-urban interface of an unincorporated county. Three jurisdictional authorities are now in play.
Wrong answer: Stand up a MAC Group to "take command" of the fire.
Right answer: Establish Unified Command. The federal land manager, the state forestry IC, and the county fire IC sit as co-equal Incident Commanders with a single, integrated set of incident objectives. Unity of command is preserved — every Operations Section position reports up through one structure, not three. The MAC Group does not activate yet, because there is one incident, not multiple. Authority over the response stays at the ICP under Unified Command.
If a second fire ignites two counties over the next day and starts competing for the same Type 1 hand crews, then the MAC Group activates — at the state level — to prioritize crew allocation between the two incidents. Unified Command keeps running each fire. The MAC Group decides which fire gets the next crew off the order list.
Scenario 2: Two Declared Incidents Competing for State ESF Resources
A coastal county is recovering from a hurricane. Three days into the response, a tornado outbreak hits a different region of the state. Both incidents have Stafford Act declarations pending. Both need ESF-3 debris management contractors, ESF-6 sheltering capacity, and ESF-8 medical surge.
Wrong answer: Have the state EOC arbitrate between the two county requests.
Right answer: The state EOC does what state EOCs do — it coordinates the requests, maintains situational awareness across both events, and supports each county's response. But the decision about who gets the limited debris contractors first is a strategic, policy-level decision affecting two jurisdictions with comparable claims. That is the MAC Group's job. The state's MAC Group convenes — typically the governor's senior staff, agency directors, and the state EM director — and makes the priority call. The EOC executes against that priority.
The distinction matters operationally: the EOC is staffed by coordinators who do not have the authority to favor one county over another. Forcing that decision down to the EOC creates either paralysis or improper authority — both of which surface in the after-action review.
Scenario 3: A Multi-Jurisdiction Wildfire Crossing Three Counties
The fire crosses three county lines. Each county has its own EOC. The state has activated. Two federal agencies are in play. There is one fire and three impacted jurisdictions.
What activates at each level:
- At the fire: Unified Command — federal, state, and the lead county IC.
- In each affected county: the county EOC, coordinating evacuations, shelters, and county resources in support of Unified Command.
- At the state: the state EOC, coordinating mutual aid, ESF activations, and inter-county requests.
- Above the state EOC: the state MAC Group, if the fire begins to compete with another active incident, or if policy decisions (mandatory evacuation orders across multiple jurisdictions, suspension of normal regulatory frameworks) need to be made.
If the fire is the only major incident in the state and no strategic policy questions are open, the MAC Group may never convene. Activating it for symbolic reasons is a doctrinal error — it dilutes the structure for the next incident when it is actually needed.
The Decision-Rights Matrix
Most disputes during an activation come down to a single question: who can authorize this? The default routing should be:
- Tactical decisions (deploy this strike team to this division) → Operations Section under Unified Command
- Operational coordination (move the shelter from Site A to Site B) → EOC
- Resource prioritization across jurisdictions (county A gets the contractor before county B) → MAC Group
- Policy decisions (declare a curfew, suspend a regulation, request federal assets) → MAC Group, with the jurisdiction's elected officials in the room
- Public messaging → JIS
When a request hits the wrong structure, two things happen — both bad. The structure that received it either rejects it (delay) or makes the call anyway (improper authority). Both show up in FEMA audits.
The Doctrine Error That Kills Audits
FEMA Public Assistance documentation requires clear accountability for every reimbursable expense: who authorized it, when, under what authority, why was it reasonable. When a jurisdiction collapses MAC Group, EOC, and Unified Command into one undifferentiated "the response" in its post-incident record, the audit trail gets murky. Murky audit trails lose reimbursement.
A common version: an EOC coordinator authorizes a contractor procurement that should have routed through the MAC Group, because the MAC Group hadn't convened yet. The contract is signed, the work happens, and at closeout the FEMA reviewer asks who in the chain of authority approved the expenditure. The answer — "the EOC" — does not align with the jurisdiction's own emergency operations plan, which reserves that authority for the MAC Group. The cost gets flagged.
These are not paperwork problems. They are doctrine problems made visible by documentation. The platforms that survive an after-action review — and a FEMA reviewer — are the ones that preserve the organizational hierarchy of ICS, EOC, and MAC Group in the data model itself, routing decisions to the right authority by default and recording who actually made the call.
The Bottom Line
MAC Group, EOC, and Unified Command are not interchangeable names for "people in charge during an emergency." They are three different structures with three different authorities, designed to operate at the same time without overlapping. The agencies that understand the boundaries run cleaner activations, defend cleaner audits, and produce cleaner after-action reviews.
For a deeper walk through how all four NIMS Command and Coordination structures fit together — including the Joint Information System — start with our Multi-Agency Coordination Systems explainer. For the broader NIMS framework, NIMS and ICS Explained covers the doctrinal foundation.
Software that respects the structure
Operational period architecture, decision-rights routing, and a data model that preserves the MAC Group / EOC / ICS hierarchy — so the authority chain shows up in the documentation, not just the org chart.
See how NIMS Logic models it →Ready to modernize your incident management?
See how NIMS Logic transforms emergency management from an administrative burden into operational advantage with real-time visibility and automated workflows.
Schedule a DemoPresident & Co-Founder
Martin brings over 40 years of emergency management experience to NIMS Logic, including service as a Type 1 Incident Commander. His field expertise in ICS operations, multi-agency coordination, and FEMA cost recovery drives the platform's operational design.
Continue Reading

Multi-Agency Coordination Systems, Explained: What MACS Actually Means Under NIMS Today
April 2, 2026
Multi-agency coordination is not one system — under NIMS, it is the umbrella for ICS, EOCs, MAC Groups, and JIS. Here is what the doctrine actually says.

What EOC Directors Get Wrong About Real-Time Visibility
March 13, 2026
Dashboards are not situational awareness. Learn why most EOCs mistake data display for actionable intelligence during multi-agency incident response.

NIMS and ICS Explained: The Relationship That Most Practitioners Get Wrong
March 6, 2026
NIMS is the national framework. ICS is the on-scene command system inside it. Most practitioners conflate the two — here is what actually distinguishes them and why it matters.