A relocation plan should let the project team decide whether to proceed, pause or recover when conditions change. Use this guide to connect inventory, dependencies, interruption limits and recovery evidence before the physical move is scheduled.
Create one inventory with separate owners
Record equipment, connections and application dependencies. Name the facility, transport, infrastructure and application contacts. Each must understand their handoff; physical equipment labels do not explain how a business service is restored.
Agree stop and rollback decisions
Confirm backup validation and destination readiness before shutdown. Define the change window, decision points and fallback options. A delay should lead to an agreed decision rather than pressure to continue into an unapproved outage.
Record what recovery proves
Test the included connections and application dependencies, then collect acceptance and exceptions. NIST contingency-planning guidance is a useful planning reference for recovery priorities and exercises, not a current transport procedure or zero-downtime guarantee.
Technical reference
NIST SP 800-34 Revision 1, Contingency Planning Guide: csrc.nist.gov This 2010 framework needs adaptation to the current environment and project.
Can the move plan rely on transport timing alone?
No. Include site readiness, application dependencies and recovery decisions.
Who decides when to stop?
Name an authorized decision owner and escalation path before the move.