When Multiple Search & Rescue Agencies Respond: Who's Really in Charge?
A county-wide alert goes out for a lost hiker. Your team responds. So does the team from the next county over, because the trailhead sits close to the line. So does a third team that trains with the sheriff's office every spring. Forty-five minutes in, there are three organizations' vehicles at the trailhead, two people independently telling hasty teams where to search, and one radio channel with two different voices calling themselves "Command."
Nobody did anything wrong to get there. Everyone showed up because they were paged, and everyone assumed someone else had already sorted out who was running it. Multi-agency response like this isn't rare anymore — mutual aid, regional SAR councils, and shrinking rosters mean most non-trivial searches now involve more than one organization. This guide answers one question plainly: when several agencies arrive at the same incident, how does command actually get established?
Command is a legal question, not a competitive one
Before any team arrives, the incident already has a legal owner. In most states, statutory responsibility for search and rescue sits with a specific office — commonly the county sheriff — not with whichever team shows up with the most people or the most experience. Washington's SAR statute states plainly that "the sheriff of each county... has the responsibility for county search and rescue activities," and that state and local plans "must specify the use of the incident command system for multiagency/multijurisdiction search and rescue operations" (RCW 38.52.400). That authority — usually called the Authority Having Jurisdiction (AHJ) — can be delegated to a deputy, an emergency manager, or an Incident Commander the AHJ names. It does not shift because a different team arrived later, brought more people, or has a more experienced leader on the roster. (Not every state uses the sheriff model — see Why Search & Rescue Command Looks Different in Pennsylvania Than It Does Out West for a state that runs it through emergency management instead.)
That's the answer to the question everyone's actually asking on scene, whether they say it out loud or not: your team is a resource under the AHJ's command, not a competing command. However skilled, however senior, however many members you brought — you're there to be assigned, not to assume.
ICS in plain English
The Incident Command System (ICS) is the standardized structure that makes multi-agency response work at all, and it's simpler than it sounds. Two ideas carry almost all of the weight:
- Unity of command — every person answers to exactly one supervisor and takes assignments only from that supervisor (FEMA, IS-100.c, Introduction to the Incident Command System). No one reports to two chains at once.
- Manageable span of control — one supervisor oversees a workable number of people, generally three to seven, with five as the sweet spot (FEMA ICS Organization materials). This is why a big search doesn't funnel through one overwhelmed person — the org chart grows in a modular way as the incident grows.
Everything else — sections, divisions, task forces — exists to keep those two principles true no matter how large the operation gets. You don't need an ICS-100 certificate to use this guide; you need to know that one person is accountable for the whole incident, and every resource on scene reports somewhere specific inside that structure.
Unified Command, explained without the jargon
"Unified Command" gets used loosely in SAR circles — often as a stand-in for "we'll all just work it together," with each agency running its own piece side by side. That isn't what the term means, and it isn't how it works.
NIMS defines Unified Command as a structure used specifically when multiple agencies or jurisdictions share legal authority over the same incident — for example, two counties' sheriffs when a search crosses the line between them. Those authorities sit together at one command post and agree to one set of objectives and one plan. Doing this "does not affect individual agency authority, responsibility, or accountability" (FEMA, National Incident Management System, 3rd ed., 2017, Ch. 3) — nobody's statutory authority disappears; they're just coordinating instead of competing.
Two things worth being precise about:
- Unified Command is for agencies with actual jurisdictional authority over the incident. It is generally not the mechanism for combining several volunteer SAR teams that all answer to the same sheriff — those teams are resources under one Incident Commander, not co-equal commanders.
- A single Incident Commander remains the default and the right model for most SAR callouts, even ones with several responding teams. Unified Command exists for genuine overlapping jurisdiction — it isn't a courtesy title for showing up.
How resources actually get folded in
Once command exists — one IC, or a Unified Command among the actual authorities — every team checks in and gets assigned into that single structure.
Check-in happens at a designated location (staging, the command post, or a specific assignment) and is logged on the ICS-211 Incident Check-In List, recording who arrived, when, and their initial assignment (FEMA, ICS Form 211). If your people aren't on that list, they're not part of the operation yet, no matter how many of them are standing at the trailhead.
From there, resources are organized by capability, not by patch. A strike team is a group of the same kind and type of resource with one leader. A task force is a mix of different resources assembled for a specific need, also with one leader (FEMA, ICS Organizational Structure and Elements). In practice, this is often exactly how three teams' worth of searchers get organized — not "Team A here, Team B there," but hasty teams or task forces built from whichever qualified people are available, each reporting to one named leader inside the ICS structure.
Why nobody just "does their own thing"
If Team A's leader is directing Team A's people, and Team B's senior member is separately directing Team B's people, you've broken unity of command twice — and now two uncoordinated groups may be searching the same area while another goes uncovered, with no single person accountable for the whole picture. That's the exact failure the check-in process and modular org chart exist to prevent.
It's also why experience and headcount don't confer authority by themselves. ICS positions — including who leads a mixed task force — are assigned by the Incident Commander based on qualification and the incident's needs, through the National Qualification System's credentialing framework, not claimed by whoever has served the longest or brought the most people (FEMA, NIMS Guideline for the National Qualification System). A highly experienced member from a mutual-aid team can absolutely end up leading a task force that includes your people — but through an explicit ICS assignment from the IC, not by declaring it. And tasking still flows through each team's own supervisor, so one agency's people aren't directly commanded by another's outside that formal assignment — this preserves both unity of command and what NIMS calls agency integrity (FEMA, NIMS, 2017, Ch. 3).
Who owns the paperwork
Two documentation questions come up after any multi-agency incident, and they have different answers.
The official incident record belongs to the IC/AHJ. That's the ICS-201 Incident Briefing (a permanent record of the initial response), the ICS-211 check-in list, the ICS-214 Activity Logs from each unit, and the Incident Action Plan for each operational period (FEMA, ICS Form 201; ICS Form 214). That package is the incident's single source of truth and is typically retained by the sponsoring agency.
Your agency's internal records are a separate, necessary thing. The official incident record documents the incident — it generally doesn't give your organization a clean internal account of which of your members responded, their hours, mileage, or which of your team's qualifications were in play. That's the detail your own grant reporting, member recognition, and liability protection actually need, and it's on you to keep it regardless of who held command that day. See The 7 Records Every Search & Rescue Team Should Keep for the full list, and You Arrive at a Mutual Aid Search. Now What? for what to actually do in the first few minutes on scene.
Where to go from here
If your team can't currently answer "who is the AHJ for searches in our jurisdiction, and what happens when three teams get paged to the same call," settle it on paper before the next callout — not during one. Bring it to your next joint training with a neighboring team.
References
- FEMA, National Incident Management System, 3rd ed. (2017) — Incident Command, Unified Command, unity of command, span of control — fema.gov
- FEMA, IS-100.c, Introduction to the Incident Command System — training.fema.gov
- FEMA, ICS Organizational Structure and Elements — single resources, strike teams, task forces — training.fema.gov
- FEMA, ICS Form 211, Incident Check-In List — training.fema.gov
- FEMA, ICS Form 214, Activity Log — training.fema.gov
- FEMA, ICS Form 201, Incident Briefing — iectraining.org
- Revised Code of Washington § 38.52.400 — county sheriff SAR responsibility and required use of ICS — app.leg.wa.gov
This guide is educational information about how NIMS/ICS doctrine typically addresses multi-agency command — it is not legal advice. Confirm your obligations against your own state's statutes and your county's emergency operations plan.