Multi-Agency Coordination Systems, Explained: What MACS Actually Means Under NIMS Today

Ask five seasoned emergency managers what a "multi-agency coordination system" is and you will get five different answers. Some will describe their EOC. Some will describe a mutual aid agreement. Some will reference an old IS-701 course they took a decade ago. One will probably tell you nobody uses that term anymore.

They are all partly right, and all partly wrong. Multiagency Coordination under NIMS is one of the most misunderstood terms in emergency management — not because the doctrine is unclear, but because it was quietly redefined, and most practitioners never got the memo.

The Term That Changed Meaning

Here is a fact that surprises even veteran emergency managers: FEMA retired the standalone IS-701.A "NIMS Multiagency Coordination System (MACS)" course in September 2016 without a direct replacement. The concept was not eliminated. It was absorbed.

When FEMA released the refreshed NIMS Third Edition in October 2017, it did something important. It repurposed "Multiagency Coordination" as the umbrella term for the entire NIMS Command and Coordination component. MACS is no longer a separate system sitting alongside ICS. It is the framework that contains ICS — and three other structures alongside it.

This matters because when an agency searches for "multi-agency coordination system" or "multi-agency coordination software," what they actually need isn't a single tool. It is a clear-eyed understanding of the four NIMS Command and Coordination structures, and how the technology under each one has to work differently.

The Four Structures Under the Umbrella

Under current NIMS doctrine, Command and Coordination — the umbrella formerly labeled MACS in training — consists of four distinct structures:

Incident Command System (ICS). On-scene, tactical-level response. This is where the Command Staff and General Staff actually run the incident using ICS 201 through ICS 221 — under a single Incident Commander or, when multiple agencies share jurisdiction over the same incident, a unified command. ICS has authority over the tactics of the response. Everything else supports it.

Emergency Operations Centers (EOCs). Off-scene support to ICS. The EOC is not in command of the incident. It coordinates resources, manages information across jurisdictions, and supports policy decisions. The most common doctrinal mistake in local government is treating the EOC as an alternate command post. It is not.

Multiagency Coordination (MAC) Groups. Policy-level bodies made up of agency administrators and senior executives — not operations staff. MAC Groups do not run the incident. They prioritize resources across competing incidents, resolve policy conflicts, and enable strategic decision-making across jurisdictions. When a state activates its MAC Group during a major disaster, elected officials and department heads are the ones sitting in it.

Joint Information System (JIS). The coordinated public information apparatus that ensures consistent messaging across agencies. Formalized as the fourth Command and Coordination structure in the 2017 refresh.

Three different authorities, one supporting discipline, one umbrella.

These four structures operate alongside NIMS principles that make coordination actually work — modular organization that lets the ICS org chart scale up or down with incident complexity, and the interoperability standards that let mutual aid resources plug into an incident without a week of onboarding. When a single incident outgrows a single IC, NIMS also provides Area Command as an adjacent structure for coordinating multiple concurrent incidents or large-scale incidents that share a resource pool. All of it sits inside the NIMS Command and Coordination component — one of three major NIMS components, alongside Resource Management and Communications and Information Management.

Why the Confusion Costs You

The operational cost of blurring these distinctions is real, and it shows up in two places.

The first is decision speed. When a resource request stalls because nobody knows whether the EOC can approve it, the ICS Logistics Section Chief has authority over it, or the MAC Group has to prioritize it against a competing incident — that is not a process problem. It is a doctrine problem masquerading as a software problem. Most multi-agency coordination software on the market makes it worse, because it presents every user with the same interface, the same workflows, and the same authorities. If the tool does not know the difference between a MAC Group member and a Division Supervisor, neither will the people using it.

The second cost is reimbursement. FEMA Public Assistance documentation requires clear accountability: who authorized this expense, when, under what authority, and why was it reasonable. When a jurisdiction cannot cleanly distinguish policy decisions (MAC Group), coordination decisions (EOC), and operational decisions (ICS) in its post-incident record, the paper trail gets murky. Murky paper trails lose audits. With federal cost-share proposals pushing more of the burden to state and local agencies, murky is no longer affordable.

What Multi-Agency Coordination Software Should Actually Do

Software that claims to enable multi-agency coordination has to respect the structure NIMS lays out. Not in a marketing brochure — in the data model itself.

That means the platform needs to know who is a MAC Group member versus an EOC coordinator versus a Division Supervisor, and surface different information, different approval authorities, and different decision rights to each. The organizational hierarchy should reflect unity of command the way ICS 203 defines it — preserving the Command Staff and General Staff structure, not collapsing everyone into a flat user list. Resource requests should route through the right authority path by default, with policy decisions captured as policy decisions and operational decisions captured as operational decisions.

It also means operational period architecture has to be real. MAC Groups and EOCs operate on different cycles than ICS. Planning Section briefings drive the ICS tempo. EOC shift changes drive the coordination tempo. MAC Group convenings drive the policy tempo. Software that flattens all activity into one timeline loses the distinctions that make after-action reviews meaningful and FEMA documentation defensible.

This is the approach platforms like NIMS Logic take — modeling the NIMS Command and Coordination structure into the data itself, so the documentation produced during an activation reflects the actual organizational reality of the response rather than a simplified dashboard view of it.

The Bottom Line

"Multi-agency coordination system" is not a product category. It is the NIMS doctrinal frame that organizes everything else. Agencies that treat it as a shopping term will end up with dashboards. Agencies that treat it as a doctrine problem — and demand software that respects the four distinct structures beneath the umbrella — will end up with systems that actually survive an activation, an audit, and an after-action review.

See how NIMS Logic models the NIMS Command and Coordination structure in practice.