Unified Command: When There Is No Single Boss

The Problem of Jurisdiction

In a wildfire that crosses from a National Forest (federal jurisdiction) into a city (local jurisdiction), two legitimate authorities exist simultaneously. If the Federal Incident Commander and the City Fire Chief both issue orders to the same crews, those crews receive conflicting instructions and the response collapses. The instinct is to fight over who is "really" in charge. That fight costs time the incident does not have.

The Solution: Unified Command

Unified Command (UC) is an ICS structure designed for multi-agency or multi-organization incidents where no single entity has sole authority. Instead of one IC, a small group of senior representatives from each organization forms a Unified Command Group. This group:

1. Meets privately to establish a single, shared set of objectives.
2. Produces one Incident Action Plan that all organizations execute.
3. Speaks with one voice to the Operations Section.

The critical constraint: there is still only one Operations Section. Unified Command does not mean two parallel response tracks. It means multiple authorities agreeing on one plan, then handing it to one unified team to execute.

Tech Scenario: The Multi-Vendor Outage

Your e-commerce platform is down. Investigation reveals two simultaneous contributing factors: your payment processor (Stripe) has a degraded API, and your cloud provider (AWS) has a regional network issue affecting your availability zone.

Three parties now have legitimate stakes in the response:

• Your team wants to activate the maintenance page and stop taking orders to prevent data inconsistency.
• Stripe's team wants you to keep sending traffic so they can validate their fix under real load.
• AWS's team wants you to shift traffic away from the affected AZ to reduce load on their degraded routers.

These three objectives directly conflict. Without Unified Command, each vendor's support engineer joins your Slack channel and starts giving your Operations team contradictory instructions. Your engineers freeze, unsure which authority to follow.

With Unified Command:

1. Your IC, Stripe's incident lead, and AWS's technical account manager join a private bridge call — the Unified Command channel.
2. They negotiate and agree: "We will shift 50% of traffic to the secondary AZ while Stripe validates their fix. We will not activate the maintenance page for 20 minutes."
3. That single decision is communicated to your Operations Section Chief, who executes it.
4. Stripe and AWS do not talk directly to your engineers. All external communication flows through the Liaison Officer.

The result: your engineers receive one coherent set of instructions and can work without second-guessing authority.

Senior insight: Unified Command is harder to maintain than it sounds. Each organization's representative arrives with their own priorities, and those priorities are often genuinely in conflict. The discipline required is to agree on shared objectives (restore customer service, prevent data loss) before debating tactics (maintenance page vs. traffic shift). Organizations that skip the objectives step and jump straight to tactics spend the entire incident arguing. Establish the objectives first, in writing, in the first five minutes of the Unified Command call.