Beyond the Rip: Reconstructing Decision Trees for Multi-Victim Open Water Rescues in Blue-Green Zones

When a single swimmer in distress becomes three, then five, the margin for error collapses. In blue-green zones—the lakes, reservoirs, and coastal inlets where recreational water use spikes on warm weekends—rescue teams often face victim counts that outpace available assets. The classic rip-current response (one victim, one rescuer, one line) no longer applies. We need a decision tree that accounts for victim distribution, resource constraints, and the dynamic conditions of these often-overlooked environments.

This guide is written for experienced open-water rescuers, team leaders, and training officers who already know how to read a rip. We skip the beginner primer and go straight to the trade-offs that matter when you have more victims than rescuers, limited time, and a water body that can change in minutes.

Why Multi-Victim Decision Trees Matter Now

Blue-green zones are not the open ocean. They are smaller, often sheltered, but they concentrate risk. A single beach on a reservoir may see hundreds of swimmers on a holiday weekend, many without awareness of currents that form near dams or channels. When a group gets caught in a sweep or a sudden wind shift, the result is a multi-victim incident that can overwhelm local responders.

Traditional rescue doctrine often assumes a one-to-one ratio: one rescuer per victim. That assumption breaks down when the victim count exceeds the number of trained swimmers on scene. Decision trees offer a structured way to allocate attention, equipment, and evacuation priority under uncertainty. They force the incident commander to make explicit choices: who gets the first tube, who gets the second boat, and who may have to wait—knowing that waiting carries its own risks.

We have seen this play out in real incidents. In one composite scenario familiar to many teams, a sudden squall capsized several small craft near a lake outlet. Within minutes, eight people were in the water, scattered across a half-mile stretch. The first rescue boat on scene had a crew of three. Without a decision tree, the natural instinct is to go to the nearest victim first. But that may not be the best choice if that victim is a strong swimmer in a wetsuit while a child farther away is already struggling. The decision tree helps the team triage by survivability, not proximity.

The gap in existing training

Most open-water rescue courses cover single-victim scenarios thoroughly. Multi-victim drills are often limited to mass-casualty incidents on land or in controlled pool settings. The blue-green zone adds complications: cold water, limited visibility, currents that shift with dam releases or tidal gates, and victims who may be spread over a wide area. Decision trees tailored to these conditions are rare in standard curricula.

Why now

Recreational use of inland waters has grown steadily. More people are paddleboarding, kayaking, and swimming in reservoirs and lakes that were once off-limits or less crowded. At the same time, budget constraints mean many rescue teams operate with the same headcount they had a decade ago. The combination of increased exposure and static resources makes multi-victim decision tools not a luxury but a necessity.

Core Idea: Triage-Based Resource Allocation

The central idea is straightforward: in a multi-victim open water rescue, you cannot treat all victims equally. You must allocate resources—rescuers, boats, throw bags, medical attention—based on a rapid assessment of each victim's likelihood of survival if left unattended for a given time. This is triage, adapted from emergency medicine but modified for the aquatic environment.

We define three categories, using a simple color system familiar to most responders:

• Red (Immediate): Victim is not breathing, unconscious, or actively drowning. Without intervention within 2–3 minutes, death or severe neurological damage is likely.
• Yellow (Delayed): Victim is conscious but struggling, showing signs of fatigue or mild hypothermia. They can hold position for several minutes but will deteriorate without rescue within 10–15 minutes.
• Green (Minimal): Victim is conscious, breathing, and able to float or swim slowly toward safety. They can wait longer, though conditions may change.

The decision tree then asks a series of yes/no questions: Is the victim breathing? Are they responsive? Can they signal? What is the water temperature? How far are they from the nearest rescue asset? Each answer narrows the options and leads to a recommended action: immediate rescue, stabilize with a flotation device and move on, or defer until higher-priority victims are secured.

How this differs from land triage

Land triage assumes you can move from victim to victim quickly. In water, travel time between victims can be the dominant factor. A victim who is 200 meters away may take five minutes to reach by swimming, or one minute by boat—if a boat is available. The decision tree must incorporate transport time and the risk to rescuers. A red victim who is far away may become unrecoverable before you arrive, while a yellow victim closer may be saved with a quick throw bag.

The role of the incident commander

In a multi-victim scenario, the incident commander (IC) should not be in the water. The IC's job is to stay on shore or on a stable platform, maintain the decision tree, and communicate priorities to rescuers. This is a hard discipline: many experienced rescuers want to be in the action. But the IC who jumps in loses the overview, and the decision tree collapses into ad-hoc choices. We have seen teams where the most senior rescuer went after the nearest victim while two others farther away drowned. A decision tree, followed strictly, would have prevented that.

How the Decision Tree Works Under the Hood

The decision tree is not a static flowchart; it is a dynamic algorithm that updates as conditions change. We break it into four phases: initial assessment, resource matching, execution, and reassessment.

Phase 1: Initial assessment

Within the first 60 seconds of arrival, the IC must gather three pieces of information: victim count, victim distribution (approximate locations and distances), and visible status (who is conscious, who is waving, who is face-down). This is often done with binoculars, a drone, or reports from bystanders. The IC assigns a preliminary triage color to each victim based on visible signs.

Phase 2: Resource matching

With the victim list and available assets (number of rescuers, boats, throw bags, fins, wetsuits), the IC matches resources to victims. The rule is: assign the fastest asset to the highest-priority victim, unless that victim is unreachable within the critical window. For example, if a red victim is 300 meters out and the only boat is on the other side of the lake, it may be faster to send a strong swimmer with a rescue can. The tree includes a time-to-reach calculation: if estimated time to reach red victim > 3 minutes, consider whether a yellow victim closer can be saved quickly first, then reassess.

Phase 3: Execution

Rescuers execute the plan. The IC tracks each rescue attempt and notes when a victim is secured or when conditions change (e.g., a victim disappears, a boat breaks down). The tree allows for branching: if a rescuer reaches a victim and finds them worse than expected, they can upgrade the priority and call for backup.

Phase 4: Reassessment

After each victim is rescued or lost, the IC re-runs the decision tree with the remaining victims and resources. This loop continues until all victims are accounted for or until it is no longer safe to continue. The reassessment phase is where most failures occur: teams get tunnel vision and forget to re-prioritize.

Worked Example: Afternoon on Blue Lake

Let us walk through a composite scenario. Blue Lake is a 2-mile-long reservoir with a dam at the south end. Water temperature is 58°F. A group of six kayakers capsized when a microburst hit. Three are near the dam (red: one unconscious, two struggling), two are 400 meters north (yellow: conscious, clinging to a kayak), and one is 800 meters north (green: wearing a life jacket, waving). Available assets: one rescue boat with two crew, one shore-based rescuer with a throw bag, and one off-duty rescuer who can swim.

Step 1: Initial triage

The IC assigns: red to the unconscious victim near the dam, yellow to the two struggling nearby and the two clinging to the kayak, green to the distant solo. The boat is the fastest asset. The IC decides: boat goes to the unconscious victim (red) first, estimated time 2 minutes. The shore-based rescuer throws a bag to the nearest struggling victim (yellow), estimated 30 seconds. The off-duty rescuer swims to the second struggling victim (yellow), estimated 3 minutes.

Step 2: Execution and reassessment

The boat reaches the unconscious victim in 2 minutes, begins CPR and tows to shore. The shore-based rescuer secures the first struggling victim quickly. The off-duty rescuer reaches the second struggling victim but finds them now unconscious (upgraded to red). The IC reassigns: the boat, now free, heads to the upgraded victim, while the off-duty rescuer stabilizes the yellow victims near the kayak. The green victim is told to stay put and is retrieved last.

Outcome

All six victims are rescued. The unconscious victim at the dam survives due to rapid intervention. The upgraded victim requires hospitalization but recovers. The decision tree prevented the common mistake of sending the boat to the distant green victim first because they were waving the most.

Edge Cases and Exceptions

No decision tree covers every scenario. Here are the most common exceptions we have encountered in blue-green zones.

Submerged victims

If a victim is submerged and not visible, the triage color is black (deceased) unless there is a high probability of recovery within minutes. In cold water (<50°F), the drowning timeline extends, and some victims have been revived after 30 minutes. The decision tree should include a branch for cold-water immersion: if water temperature is below 50°F and submersion time is less than 30 minutes, treat as red and attempt rescue. Above 50°F, treat as black after 5 minutes.

Hypothermia in yellow victims

A yellow victim who is shivering and losing motor control may deteriorate faster than expected. The tree should include a sub-branch: if water temperature is below 60°F and the victim is showing signs of hypothermia (shivering, confusion, loss of grip), upgrade to red. We have seen cases where a seemingly stable victim stopped shivering—a sign of severe hypothermia—and became unresponsive within minutes.

Multiple red victims

If two or more victims are red and equidistant, the tree must prioritize by age and pre-existing conditions: children and elderly generally have less reserve. If no such information is available, prioritize the victim closest to the nearest asset to maximize the chance of at least one save.

Rescuer safety

The decision tree must include a branch for rescuer risk. If the water conditions are too dangerous (e.g., lightning, extreme currents, debris), the IC may decide to delay all rescues until conditions improve or use only boat-based rescues. No victim is worth a rescuer's life. The tree should have a hard stop: if risk to rescuers exceeds a predefined threshold, switch to defensive mode (e.g., throw bags only, no swimming).

Limits of the Approach

Decision trees are powerful, but they have real limitations that teams must acknowledge.

Information uncertainty

The initial assessment is often wrong. A victim who appears green may have internal injuries or be in shock. A victim who appears unconscious may be conscious and just resting. The tree relies on visual cues that can be misleading. Teams should train to update triage colors as soon as a rescuer makes contact, and the IC must be willing to override the tree based on new information.

Time pressure

In a fast-moving incident, the IC may not have time to run a full decision tree. The tree should be practiced to the point of automaticity, like a fire drill. If the team has not trained with the tree, it will fail under pressure. We recommend quarterly tabletop exercises with multi-victim scenarios.

Resource limits

The tree assumes you have at least some resources. If you have one rescuer and five victims, the tree will tell you to prioritize the red victim, but that may mean the other four die. The tree does not change the tragic math; it only makes the choice explicit. Teams must have realistic expectations and communicate those to the public.

Environmental variability

Blue-green zones can change rapidly. A dam release can double the current in minutes. A wind shift can push victims farther apart. The tree must be re-run whenever conditions change, not just when a victim is rescued. This adds cognitive load on the IC, which is why we recommend a second person to track environmental updates.

Reader FAQ

Q: Can this decision tree be used for surf rescues on ocean beaches?
A: Partially. The triage logic applies, but ocean conditions (larger waves, longer distances, rip currents) require modifications. This tree is optimized for blue-green zones—smaller, calmer water bodies where travel time is shorter but victim density can be higher.

Q: How do we train our team on this tree without expensive simulations?
A: Use tabletop exercises with printed victim cards and a map of your local water body. Assign roles (IC, rescuer, observer) and run through scenarios. Time each decision and debrief. You can also use free online flowchart tools to create a digital version.

Q: What if the IC is also the most experienced rescuer—should they stay on shore?
A: Yes. The IC role is too important to abandon. If your team is small, designate a second-in-command to lead the water response while the IC stays on shore. If that is not possible, the tree should be pre-briefed so that every rescuer knows the priorities without an IC.

Q: Does this tree apply to ice rescues?
A: Not directly. Ice rescues have different access challenges and hypothermia timelines. However, the triage concept (prioritize by survivability) still holds. Adapt the tree with ice-specific parameters.

Q: How do we handle victims who refuse rescue?
A: The tree should include a branch for refusal. If a conscious victim refuses help and is not in immediate danger, document and move on. If they are in danger, attempt to persuade, but do not put rescuers at risk for a non-consenting adult.

Practical Takeaways

Here are the specific actions we recommend for teams that want to implement decision trees for multi-victim rescues in blue-green zones.

1. Create a laminated decision-tree card for your IC kit. Include the triage categories, time thresholds (2 minutes for red, 10 minutes for yellow), and a simple flowchart for resource assignment. Test it in drills.
2. Run at least two multi-victim tabletop exercises per year using scenarios from your local water body. Include edge cases like submerged victims, hypothermia, and equipment failure.
3. Designate a primary and backup IC for every callout, even for single-victim incidents. This builds the habit of command separation.
4. Integrate the decision tree with your existing incident command system. The tree is a tool within ICS, not a replacement. Ensure your radio protocols include triage color codes.
5. Review real incidents (anonymized) from your region or others. Identify where a decision tree would have changed the outcome. Share lessons learned with neighboring teams.

This guide provides general information only and is not a substitute for professional training, local protocols, or medical advice. Always consult your agency's standard operating procedures and a qualified instructor before implementing new rescue techniques.