Skip to content

Assisted Migration or Translocation Plan

Assisted-translocation method — instantiates Managed Retreat

Deliberately moves a place-bound, slow-migrating subject—a population, habitat function, or stateful system—into prepared, compatible receiving conditions when it cannot get there on its own in time.

An Assisted Migration or Translocation Plan is for the subject that cannot move itself fast enough: a rooted population, an ecological function, a stateful or costly-to-relocate system whose autonomous migration is too slow, too fragmented, or blocked outright. It does two things no other retreat mechanism does. It specifies what the subject minimally needs to stay viable — not just its location but its function, connectivity, and identity — and it specifies the receiving conditions that can actually sustain it, judged by compatibility rather than mere distance from the front. It carries the least-mobile part of the subject across, on the premise that a destination is only a destination if the subject can live there.

Example

A cold-water fish population is being squeezed as a warming river pushes its thermal limit upstream while a dam fixes the upper boundary — a closing band. The species cannot climb the dam and cannot migrate fast enough to track the receding cold water. An Assisted Migration or Translocation Plan first fixes the viability requirement: this population needs a specific temperature range, spawning gravel, connected refugia, and enough genetic diversity to persist — "some fish somewhere" is not viability. It then specifies a receiving zone on those terms: a headwater reach in an adjacent watershed cold enough under projected warming, with compatible substrate, free of a competitor that would displace them, reachable without introducing disease. Fish are moved in stages matched to the receiving habitat's capacity, with the least-replaceable genetic lines prioritized. The plan's discipline is that it can decline a site that is merely farther upstream but ecologically wrong — a place is not a refuge just because the front has not reached it.

How it works

  • Define viability before movement. What function, connectivity, and identity must survive is specified first, so relocation does not preserve the subject's location while destroying what made it the subject.
  • Judge the destination by compatibility. The receiving zone is qualified on ecological or technical fit, capacity, and freedom from transferring the same squeeze — not on distance from the front.
  • Move the least-mobile, least-replaceable part deliberately. Translocation is staged and matched to receiving capacity, prioritizing what cannot regenerate if lost.
  • Establish, don't just deposit. The plan carries responsibility through establishment in the new conditions, because a move that fails to take is not a retreat.

Tuning parameters

  • Viability threshold — how much function or diversity must survive to count as success. Strict thresholds protect the subject's identity but shrink the set of acceptable destinations.
  • Receiving-zone match — how close a compatibility fit is required. Tight matching lowers establishment risk but may leave no qualifying site; loose matching risks a destination that cannot sustain the subject.
  • Translocation dosing — how much of the subject moves per stage. Small doses protect the source and let the destination be tested; large doses move faster but bet more on an unproven receiving zone.
  • Intervention degree — from easing autonomous movement to full hands-on relocation. More intervention overcomes worse blockage but raises cost and the risk of harming source or destination.
  • Reversibility guard — how strongly the plan guards against transferring the problem (invasion, disease, competition). Conservative guards slow the move but prevent creating the next squeeze elsewhere.

When it helps, and when it misleads

Its strength is that it is the only retreat mechanism built for a subject that cannot participate in its own escape, and its insistence on specified viability and compatible receiving conditions prevents the hollow success of a relocation that keeps the thing alive on paper while destroying its function.

Assisted colonization can become the next front: a translocated population may fail to establish, or worse, thrive as an invader and impose the same squeeze on the receiving zone's incumbents.[1] The tidy label "we moved them to safety" hides both risks. It is misused when a destination is chosen for being convenient or merely farther from the hazard, skipping the compatibility and reversibility checks that are the whole point. The discipline is to qualify the receiving zone on evidence, dose the move so it can be halted, and treat "farther from the front" as necessary but never sufficient.

How it implements the components

  • exposed_subject_and_viability_requirement — it names the place-bound subject and specifies the minimum function, connectivity, and identity it must retain to count as preserved.
  • receiving_zone_specification — it qualifies the destination on ecological or technical compatibility, capacity, and freedom from transferring the squeeze — not distance alone.

It specifies what the receiving zone must be, but does not book or legally secure it (that's Receiving-Zone Reservation), build the route to it (that's Controlled Corridor), or fund the human side of the move (that's Transition Support Plan).

Notes

Assisted migration specifies the ecological or technical suitability of a destination; the legal, capacity, and access side of that same destination is Receiving-Zone Reservation. Splitting "is it habitable" from "is it secured" keeps a biologically sound site from being assumed available — and a legally reserved site from being assumed livable.

References

[1] Assisted colonization — moving a species beyond its historical range to escape a threat — is a genuinely debated conservation intervention precisely because a translocated population can fail to establish or turn invasive, which is why responsible practice treats receiving-site risk assessment as mandatory rather than optional. ↩