Consider a regional operation with several depots and offices. At 05:40, flooding blocks the main approach to one depot. The night shift remains on site, the incoming shift is beginning its journey, and inbound vehicles need new instructions. At 06:05, a power fault disables access control and part of the fire-safety system at a second site before its day shift begins.
Each local plan is workable on its own. Both, however, call for the same regional facilities engineer, the same security lead, the same communications team, and an executive authorised to suspend operations. The flood response also proposes using the second site as an alternative base just as that site's own readiness becomes uncertain.
The problem is no longer confined to either incident. The organisation must compare consequences, deadlines, audiences, and alternatives without stripping either local team of the authority and context it needs to respond.
Why do single-incident plans conceal portfolio risk?
A well-designed local plan can still depend on shared resources that are visible only at group level.
The plan may name an on-call security lead, engineer, legal counsel, vehicle, alternative workplace, or contracted response team. It may also depend on a senior executive authorising expenditure or a change to operations. Those assumptions become fragile when several plans activate together.
Official incident-management doctrine recognises this directly. The US National Incident Management System describes Area Command as a structure that can oversee multiple concurrent incidents and prioritise scarce resources between them. It also places resource prioritisation and allocation with multi-agency coordination groups when competition becomes significant.1 A commercial organisation does not need to copy that structure to recognise the principle. An incident team should not be the sole arbiter of a resource it considers essential to its own response.
The hidden risk is often not absolute shortage, but an untested collision. In the two-site example, the flood plan names the regional facilities engineer as the source of technical advice and the second site as an alternative location. The power-fault plan assumes that the same engineer will attend in person and that the site remains available to receive displaced work. Each plan looks adequately resourced in isolation, yet their assumptions cannot all remain true at the same time. Unless the plans are tested together, the collision stays hidden until demand peaks.
What counts as a scarce response resource?
Physical assets such as vehicles, generators, fuel, accommodation, specialist equipment, and medical support are obvious constraints. People, authority, and information can be equally important. A specialist assigned to two sites is one contested resource, not two available owners. A duty manager scheduled for simultaneous calls creates a command conflict that the plans must resolve. A senior leader may be the only person authorised to accept a particular risk. Several teams may also depend on one provider, analyst, or system for the information that shapes their decisions.
FEMA's resource-management guidance advises organisations to decide responsibility for resource planning before a complex incident, identify gaps, exercise the process, and track the type, timing, staffing, location, and status of resources from deployment through demobilisation.2 This supports a wider definition of capacity. A resource is not merely something the organisation owns. It is a capability that can be requested, authorised, mobilised, supported, and released within the required time. The regional engineer, communications team, and approving executive therefore belong in the resource picture alongside equipment and vehicles.
A response plan that lists a capability without its capacity, readiness, location, authority, and competing commitments may give false reassurance.
How can every incident appear controlled while the organisation is overcommitted?
Each incident team sees its own objectives, actions, deadlines, and local resources. It may accurately report that work is progressing. The enterprise risk appears only when those views are combined.
In the two-site example, the depot assigns the regional security lead to verify an alternative access route, while the second site expects the same person to oversee access restrictions during the power fault. Both local records show an owner, but neither reveals the conflict. The regional facilities engineer appears in the same way, and two urgent communications await the same approval at nearly the same time.
The group-level picture must therefore show demand as well as status: active incidents, time-critical objectives, requested and committed capabilities, duplicated roles, and deadlines that still lack accepted support.
This does not require every local detail to be centralised. UK emergency-response guidance places decisions at the lowest appropriate level, supported by clear direction, information, integration, cooperation, and continuity.3 Wider coordination becomes necessary when interdependence exceeds the authority or view of one local team.
Who should arbitrate between incidents?
The decision should sit with a role that has the authority, information, and organisational perspective to compare the consequences.
That role may be a group incident director, executive crisis team, global security lead, regional operations director, or another pre-agreed coordination function. The title matters less than the mandate. The decision-maker must be able to reallocate a shared resource, accept the consequence, authorise an alternative, and escalate when neither response can be supported adequately.
Local incident leads define what they need and explain the impact of delay. The coordinating authority compares requests that state the objective, required capability, latest useful arrival time, consequence if unavailable, alternatives, and duration. It resolves demands that local teams cannot settle without taking over their wider response.
International guidance supports that separation. ISO 22320 addresses incident-management processes, roles, tasks, resource management, joint direction, and cooperation. It applies both to a single organisation and to organisations working together through separate or combined structures.4 Within a company, local command can continue while an agreed coordination layer handles shared constraints and common objectives.
What should determine which request takes priority?
Priority cannot be reduced safely to who asked first, who is most senior, or which incident sounds most dramatic.
Life safety is the starting point in recognised resource-allocation doctrine.5 Beyond that, the organisation needs criteria appropriate to its responsibilities and operating model. These may include the immediacy and severity of potential harm, the number and vulnerability of people exposed, time before an option closes, the availability of substitutes, critical service impacts, environmental consequences, legal or regulatory duties, and the possibility that one intervention will prevent escalation.
The coordinating authority should compare the effect of assigning the capability now, later, or not at all. In the example, the facilities engineer may attend the power-fault site first if an on-site assessment is the only timely route to a safe operating decision, while a competent depot team can gather flood evidence under remote direction. If water is rising towards critical equipment and the second site can remain closed safely, the order may reverse. The choice should reflect current consequences, time constraints, and viable alternatives rather than the size or visibility of either incident.
Uncertainty must remain visible. One team may have high-confidence information about a moderate impact, while another reports a potentially severe situation with weak evidence. The coordinating authority may allocate reconnaissance or communication capacity first, because improving the evidence is the decision that unlocks the next decision.
The rationale matters. If a resource is redirected, the incident that loses it needs a revised plan, not silence. The decision record should show the evidence, assumptions, authority, expected consequences, mitigation, and review time. That turns an unwelcome outcome into a controlled organisational choice.
How should communication work when audiences and incidents overlap?
Concurrent incidents can create a second form of contention: the same people may receive instructions from different teams.
An employee may work at a site affected by severe weather while supporting an outage elsewhere. A manager may belong to two response groups. In the example, depot drivers need the flood-related route instruction, but some are also scheduled to collect equipment from the site affected by the power fault. If each incident communicates independently, those drivers could receive two instructions without a clear order of priority.
Coordination should identify audience overlap before messages are sent. That does not mean combining unrelated incidents into one vague broadcast. It means agreeing which team owns each instruction, how the incident and location are labelled, which instruction is current, whether one response can satisfy both teams, and what happens if the required actions conflict.
Before sending, authorised teams can review ReachScore™ across each affected group. ReachScore™ is a continuously updated communication-readiness indicator built from five current signals: SMS availability, notification permissions, location access, recent device engagement, and battery life. Its scope here is deliberately narrow. It shows correctable readiness gaps in the planned contact routes, rather than staff capacity, operational availability, or incident priority.
A reduced ReachScore™ can prompt the team to correct a number, restore an agreed permission, ask a user to reopen the app, charge or replace a device, or confirm another configured contact route. The responsible team can then issue a site-specific Mass Notification through the channels chosen for that audience and incident. The depot notification carries the current route or shift instruction, while the second site's notification carries the access or closure instruction. Where a person belongs to both groups, the messages are clearly labelled, and their ownership and priority are resolved before sending.
Where a response is needed, a Check-In asks the event-specific question and shows responses and non-responses. Non-responses enter the relevant team's follow-up procedure. This creates a controlled sequence from ReachScore™ review, through readiness correction and Mass Notification, to Check-In and owned follow-up without treating any one signal as proof of a person's circumstances.
The Joint Decision Model used by UK emergency services is helpful here because it treats shared information, risk assessment, relevant policy, options, action, and review as a continuing cycle.6 A Mass Notification or Check-In is an action within that cycle. Its responses may change the resource picture, reveal a new need, or show that an assumption was wrong.
The communication function should be included in the resource plan. Drafting, approval, translation, channel selection, monitoring, and follow-up each require an owner and a usable deadline. FEMA's guidance on pre-incident resource planning, gap identification, status tracking, and demobilisation provides an appropriate discipline for managing that finite capability.2
When should the organisation seek mutual aid or an alternative capability?
The point to seek help is before every internal option is exhausted.
If demand, mobilisation time, and consequence thresholds are visible, the organisation can identify when internal capacity will not arrive in time. It can then use a contracted alternative, reciprocal arrangement, additional supplier, remote specialist, or deliberate reduction in non-critical activity. In the two-site example, a pre-approved local electrical contractor may provide the second site's technical assessment while the regional engineer supports the flood response. The alternative is useful only if its competence, access, authority, and mobilisation time fit the decision that must be made.
UK recovery guidance defines mutual aid as assistance across organisational boundaries when an emergency may overwhelm one organisation's resources. It describes formal protocols for allocating responsibilities and says that testing mutual-aid arrangements is beneficial.7 Private-sector arrangements need similar clarity about authority, capability, mobilisation time, access, command, cost, security, and accountability.
Alternatives should be described by capability, not by contract alone. A supplier relationship is not useful if the responding people lack the competence, permissions, equipment, or local access required. The incident team needs to know what the alternative can do within the relevant time.
The release of resources also matters. A team held “just in case” by one incident may be urgently needed elsewhere. Demobilisation criteria, handover requirements, rest periods, replenishment, and travel time should all influence when the capability becomes genuinely available again.
How can AtlasNXT support decisions across simultaneous incidents?
AtlasNXT can preserve the integrity of each response while helping authorised leaders compare shared constraints. Remits define geographic responsibility and authorised views. Within each response, an Incident Room keeps significant updates, tasks, communications, decisions, and status changes with the event. Teams can record the capability requested, urgency, latest useful time, owner, consequence of delay, allocation decision, and resulting action as appropriate updates, tasks, or decisions.
ReachScore™ can expose known communication-readiness gaps before either incident team sends an instruction. Mass Notifications can then target the relevant groups, while Check-Ins show responses and non-responses for operators to handle under the agreed SOP. Where the same person is involved in two incidents, the operating model can establish which instruction takes priority and which team owns the follow-up. Authorised location context can contribute where appropriate, using live, event-led, or consent-based information according to the purpose and applicable requirements.
Priority and allocation remain organisational decisions. AtlasNXT provides the context in which authorised teams can apply agreed priorities, authorities, escalation thresholds, and alternatives, then communicate and record the result.
What should a multi-incident exercise reveal?
The most useful exercise activates two ordinary plans together. The flood and power-fault scenario can begin with both local teams requesting the regional facilities engineer, security lead, communications team, and approving executive. A key approver can become unavailable, ReachScore™ can expose a correctable readiness gap in one affected group, two teams can prepare Mass Notifications for overlapping audiences, and an initially lower-priority incident can deteriorate.
The evaluation should examine when the resource conflict became visible, whether requests were comparable, who had authority to arbitrate, how quickly the losing incident received an alternative plan, whether communications conflicted, and whether resources were released and reassigned in a controlled way.
The exercise tests whether the organisation understands the capacity implied by its own plans. Local command needs room to act, shared resources need an owner, and senior coordination needs a timely view of demand, consequence, and alternatives. When those elements connect, scarcity becomes a decision to manage rather than a collision discovered too late.
Book an AtlasNXT demonstration to explore how ReachScore™, Mass Notifications, Check-Ins, separate Remits, and Incident Rooms can support local responses while giving authorised leaders the shared context needed to manage simultaneous incidents and competing resources.
References
3. UK Cabinet Office, “Emergency response and recovery”, updated 29 October 2013
6. Joint Emergency Services Interoperability Principles, “The Joint Decision Model”
7. UK Cabinet Office, “National Recovery Guidance: common issues”, updated 26 March 2013
