Multi-agency SAR coordination training should require organizations to establish shared objectives, exchange reliable information, request and assign resources, maintain a common operating picture and manage handoffs. The scenario must give each agency a meaningful role and legitimate information; otherwise “coordination” becomes one organization performing while others observe.
The exercise should reflect local authorities and agreements. Common terminology helps, but it does not replace clarity about who decides, who supports and how conflicts are resolved.
Design with partners, not for them
Invite participating organizations into the design process early. Confirm their capabilities, limitations, notification procedures, liaison arrangements and data-handling requirements. Ask what they need to practice, not only what the lead agency wants from them.
Document assumptions about availability and response. If an asset is represented in simulation, indicate whether its timing and capability are realistic or compressed for exercise purposes.
practice command relationships
Create a situation in which authorities or responsibilities overlap enough to require coordination. Participants may need unified objectives, agency representation, liaison or a clear interface between incident command and supporting coordination centers.
Evaluate whether roles and decision pathways are understood. The test is not whether participants reproduce an organization chart; it is whether the structure helps them make and communicate decisions.
Build a common operating picture
Agree what the team needs to know: search areas, clues, team locations, assignments, hazards, weather, resource status, public information and outstanding requests. Decide which source owns each type of information and how updates are validated.
During the exercise, introduce inconsistent or late reports. Observe whether the team marks uncertainty, resolves conflict and communicates corrections. A shared screen is not automatically a shared understanding.
Exercise communications as a workflow
Do not limit communications evaluation to whether devices connect. Test message content, routing, confirmation, terminology, fallback and the transition between channels or organizations.
Include one purposeful degradation, such as loss of a primary path or an overloaded channel. Participants should recognize the problem, activate an agreed alternative and tell partners how communication will continue. Avoid stacking failures until the scenario becomes implausible.
Make resource requests specific
Requests should describe the capability, task, location, reporting instructions, timing and support need. The receiving organization should be able to accept, clarify, modify or decline based on real constraints.
Track the request from identification through approval, assignment, arrival, status and release. This exposes handoff gaps that a simple list of resources will not show.
Include operational-period and shift handoffs
Longer missions depend on continuity. Require an outgoing team to brief the incoming team on objectives, assignments, clues, hazards, resource status and unresolved decisions. Observe whether the receiving team can continue without reconstructing the entire incident.
If time is limited, simulate the passage of an operational period. The handoff can still be a primary objective even in a short exercise.
Use a hybrid exercise architecture
Web simulation can distribute role-specific information and maintain a shared map. Immersive views can help with terrain or facility context. A command post or EOC can operate with real staff and procedures while field teams or external agencies are represented by a simulation cell.
Be transparent about the boundary between live and simulated activity. Evaluators should know which delays, capabilities and messages are controlled by the exercise.
Evaluate the interfaces
Many findings occur between organizations rather than inside one. Assign evaluators to interfaces such as field-to-command, command-to-EOC, agency-to-agency and outgoing-to-incoming shift.
Ask whether information retained its meaning, whether authority was understood, whether requests were actionable and whether partners received feedback. Convert the findings into jointly owned actions where appropriate.
Multi-agency readiness grows through repeated, reciprocal practice. A successful exercise leaves partners with clearer expectations, tested pathways and a common basis for the next improvement—not merely a record that everyone attended.
Sources
FEMA National Incident Management System: https://www.fema.gov/emergency-managers/nims
FEMA National Search and Rescue Response System: https://www.fema.gov/emergency-managers/national-preparedness/frameworks/search-rescue
FEMA EOC Quick Reference Guide: https://www.fema.gov/sites/default/files/documents/fema_eoc-quick-reference-guide.pdf
CISA Emergency Communications: https://www.cisa.gov/topics/emergency-communications
FEMA Homeland Security Exercise and Evaluation Program: https://training.fema.gov/programs/nsec/hseep/
Continue the conversation
Every training environment has different constraints. If you are working through how to make scenarios more repeatable, measurable, or accessible, share your training challenge with us.
Multi-agency SAR coordination training should require organizations to establish shared objectives, exchange reliable information, request and assign resources, maintain a common operating picture and manage handoffs. The scenario must give each agency a meaningful role and legitimate information; otherwise “coordination” becomes one organization performing while others observe.
The exercise should reflect local authorities and agreements. Common terminology helps, but it does not replace clarity about who decides, who supports and how conflicts are resolved.
Design with partners, not for them
Invite participating organizations into the design process early. Confirm their capabilities, limitations, notification procedures, liaison arrangements and data-handling requirements. Ask what they need to practice, not only what the lead agency wants from them.
Document assumptions about availability and response. If an asset is represented in simulation, indicate whether its timing and capability are realistic or compressed for exercise purposes.
practice command relationships
Create a situation in which authorities or responsibilities overlap enough to require coordination. Participants may need unified objectives, agency representation, liaison or a clear interface between incident command and supporting coordination centers.
Evaluate whether roles and decision pathways are understood. The test is not whether participants reproduce an organization chart; it is whether the structure helps them make and communicate decisions.
Build a common operating picture
Agree what the team needs to know: search areas, clues, team locations, assignments, hazards, weather, resource status, public information and outstanding requests. Decide which source owns each type of information and how updates are validated.
During the exercise, introduce inconsistent or late reports. Observe whether the team marks uncertainty, resolves conflict and communicates corrections. A shared screen is not automatically a shared understanding.
Exercise communications as a workflow
Do not limit communications evaluation to whether devices connect. Test message content, routing, confirmation, terminology, fallback and the transition between channels or organizations.
Include one purposeful degradation, such as loss of a primary path or an overloaded channel. Participants should recognize the problem, activate an agreed alternative and tell partners how communication will continue. Avoid stacking failures until the scenario becomes implausible.
Make resource requests specific
Requests should describe the capability, task, location, reporting instructions, timing and support need. The receiving organization should be able to accept, clarify, modify or decline based on real constraints.
Track the request from identification through approval, assignment, arrival, status and release. This exposes handoff gaps that a simple list of resources will not show.
Include operational-period and shift handoffs
Longer missions depend on continuity. Require an outgoing team to brief the incoming team on objectives, assignments, clues, hazards, resource status and unresolved decisions. Observe whether the receiving team can continue without reconstructing the entire incident.
If time is limited, simulate the passage of an operational period. The handoff can still be a primary objective even in a short exercise.
Use a hybrid exercise architecture
Web simulation can distribute role-specific information and maintain a shared map. Immersive views can help with terrain or facility context. A command post or EOC can operate with real staff and procedures while field teams or external agencies are represented by a simulation cell.
Be transparent about the boundary between live and simulated activity. Evaluators should know which delays, capabilities and messages are controlled by the exercise.
Evaluate the interfaces
Many findings occur between organizations rather than inside one. Assign evaluators to interfaces such as field-to-command, command-to-EOC, agency-to-agency and outgoing-to-incoming shift.
Ask whether information retained its meaning, whether authority was understood, whether requests were actionable and whether partners received feedback. Convert the findings into jointly owned actions where appropriate.
Multi-agency readiness grows through repeated, reciprocal practice. A successful exercise leaves partners with clearer expectations, tested pathways and a common basis for the next improvement—not merely a record that everyone attended.
Sources
FEMA National Incident Management System: https://www.fema.gov/emergency-managers/nims
FEMA National Search and Rescue Response System: https://www.fema.gov/emergency-managers/national-preparedness/frameworks/search-rescue
FEMA EOC Quick Reference Guide: https://www.fema.gov/sites/default/files/documents/fema_eoc-quick-reference-guide.pdf
CISA Emergency Communications: https://www.cisa.gov/topics/emergency-communications
FEMA Homeland Security Exercise and Evaluation Program: https://training.fema.gov/programs/nsec/hseep/
Continue the conversation
Every training environment has different constraints. If you are working through how to make scenarios more repeatable, measurable, or accessible, share your training challenge with us.