Phased Relocation Plan¶
Transition plan — instantiates Defensible Boundary Retreat
Sequences the withdrawal as a staged, partly reversible ladder of moves rather than a single leap, so functions keep running while the old position is relinquished piece by piece.
Once it is decided that to retreat and validated where to, someone still has to choreograph the move — and doing it all at once usually converts an orderly retreat into a self-inflicted crisis. Phased Relocation Plan is the choreography. Its defining move is to break the withdrawal into an ordered ladder of stages, each of which can be paused, accelerated, or (while it is still genuinely feasible) reversed, and each with a small enough footprint that the whole enterprise keeps functioning across the transition. It answers how the move unfolds in time — the migration order, the dependencies, the go/no-go gate between rungs — as distinct from whether to move, where to move, or what happens to the people and assets left behind.
Example¶
A manufacturer is closing an aging plant and shifting production to a new facility across the region. A single-weekend "lift and shift" is tempting but ruinous: if any line fails to come up in the new building on Monday, the company has no production at all and a contract penalty for every day dark. The relocation plan instead lays out a ladder. Rung one moves the least-critical, most-modular line — the one whose output can be buffered from inventory — and runs it to full yield in the new plant before anything else moves. Only when that rung's gate passes (new line qualified, first articles approved, operators certified) does rung two begin: the next line, with the lessons from the first folded in.
Between rungs, both plants run in parallel for the critical products, so a stumble on the new floor falls back to the old one that is still, deliberately, kept alive. The reversibility on the early rungs is real — through rung two the company could still halt and hold the old plant — but the plan marks the rung past which reversal is no longer possible, because the old line's tooling has been decommissioned. By the final rung the old plant is idle by design, not by surprise, and the customer never saw a missed shipment.
How it works¶
- Order by dependency and blast radius, not convenience. The migration sequence moves the pieces that are most isolable and lowest-risk first, so early rungs build confidence and expose surprises cheaply before the hard, entangled parts move.
- Every rung is a gated increment. Between stages sits an explicit go/no-go gate — did this rung reach its target before the next begins — so the move advances on demonstrated success rather than a calendar.
- Overlap the boundaries to preserve continuity. For critical functions, old and new run in parallel across the handover, so a failure on the new side falls back rather than going dark.
- Mark where reversibility ends. The ladder names the rung past which reversal stops being real (once the old tooling is retired, the bridge is burned), keeping "we can always go back" from becoming a fiction used to justify drift.
Tuning parameters¶
- Rung granularity — many small stages versus a few large ones. Fine stages contain risk and surface problems early but stretch the timeline and the parallel-run cost; coarse stages are faster but riskier.
- Parallel-run overlap — how long old and new coexist per rung. Long overlaps buy safety and fallback but double running costs and prolong exposure at the old position.
- Reversibility depth — how many rungs preserve a genuine option to halt and return. More reversibility is insurance against a bad destination but delays the savings and the decommissioning it defers.
- Sequencing rule — lowest-risk-first (build confidence) versus highest-value-first (secure the crown jewels early). The choice trades learning against protecting what matters most.
- Gate strictness — how much a rung must prove before the next opens. Strict gates catch failures but can stall the whole move on one lagging component.
When it helps, and when it misleads¶
Its strength is that it keeps the enterprise running while it moves, turning a terrifying all-or-nothing leap into a sequence of survivable steps with fallbacks — and it buys evidence, since each rung teaches the next. The alternative it is defined against is the big-bang cutover, where everything switches at a single moment and any failure is total and simultaneous.[n1]
It misleads in two opposite ways. Over-staged, it becomes a transition bottleneck: parallel-running two positions for too long doubles cost and exposure, and a plan with infinite reversible rungs can become a way to never actually complete the retreat — the old position lingers half-alive, consuming the very resources the move was meant to free. Under-staged, the "phased" plan is a big-bang in disguise, with dependencies so entangled that the first rung drags everything with it. The classic misuse is preserving the fiction of reversibility long after the bridge is burned, so the team believes it can fall back when it no longer can. The guarding discipline is to gate rungs on demonstrated success, cap the parallel-run window, and mark the point of no return honestly so nobody plans a fallback that has already evaporated.
How it implements the components¶
Phased Relocation Plan realizes the movement machinery of the archetype — how the withdrawal actually unfolds:
transition_pathway— it is the sequenced path itself: the migration order, dependency handling, and gated increments that carry the enterprise from old boundary to new.partial_retreat_ladder— it builds the staged gates for partial retreat, pause, acceleration, and reversal, and marks the rung past which reversal is no longer genuinely feasible.
It does not decide when to trigger the move (retreat_trigger_set — see Managed Retreat Trigger Review), certify the destination (Receiving Boundary Readiness Assessment), retire what is left behind (Asset Decommissioning and Salvage Runbook), or protect displaced people (Retreat Compensation and Continuity Package).
Related¶
- Instantiates: Defensible Boundary Retreat — this plan is the how-to-move core that carries the retreat from old boundary to new.
- Consumes: Receiving Boundary Readiness Assessment certifies the destination the plan sequences movement toward; Managed Retreat Trigger Review supplies the fired trigger that starts the first rung.
- Sibling mechanisms: Managed Retreat Trigger Review · Receiving Boundary Readiness Assessment · Asset Decommissioning and Salvage Runbook · Retreat Compensation and Continuity Package · Hold-vs-Retreat Scenario Stress Test · Old-Position Sunset Clause · New Boundary Stabilization Review
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: The mechanism documents a prospective dependency-ordered relocation ladder, gates, overlaps, reversibility, and continuity protections.
Nearest alternative: Protocol, Workflow & Routine — Others may later enact the sequence, but the mechanism is the transition plan rather than execution itself.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Disaster Management & Risk Reduction
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Phased Relocation Plan is rooted in disaster management and risk reduction: Managed-retreat and continuity planning sequence relocation while essential functions remain operable.
Related originating lineages:
- Architecture & Urban Planning — Architecture and urban planning materially shaped Phased Relocation Plan through spatial composition, wayfinding, land, and built-form planning.
- Engineering & Design — Engineering and design materially shaped Phased Relocation Plan through reliability, physical systems, safety, and mistake-proof design.
- Environmental Science & Climate Studies — Climate adaptation developed anticipatory relocation under persistent hazard.
- Public Administration & Policy — Land, compensation, and service-continuity policy materially govern the transition.
Review resolution: Both blind reviewers agree that emergency and disaster-risk management is the primary origin. Reconciliation resolves alternate_origin_disagreement, domain_reach_disagreement, encyclopedia_synthesis_disagreement. Formative alternate lineages are retained as architecture_urban_planning, engineering_design, environmental_climate, public_administration_policy; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] A big-bang cutover switches an entire system from old to new at a single moment, with no parallel running; its opposite is a phased or parallel migration. Big-bang is faster and cheaper when it works, but any failure is total and immediate — which is precisely why a staged ladder trades speed for survivability. ↩