Distributed Office Opening and Relocation Runbook
Turn a branch opening or relocation into a controlled dependency plan with readiness gates, phased migration and day-one support.
Make each dispatch repeatable and recoverable
Define prerequisites, remote ownership, method of procedure, acceptance evidence and rollback before technicians arrive onsite.
Program readiness and site prerequisites
Confirm site and construction release, circuits, cabling tests, rack/UPS, furniture, room access and equipment delivery before dispatch. Build an owner matrix for carrier, network, voice, AV, security, printing, applications, facilities and movers. Map users and departments into migration waves with explicit old-site and rollback dependencies.
The remote team should supply the site identifier, approved design, equipment list, configuration status, contacts, access window and success criteria. The field technician verifies serials, labels, damage, accessories and prerequisites before changing production service.
- Construction/carrier/cabling gate
- Cross-team owner matrix
- User/department waves
- Old-site/rollback plan
Controlled onsite deployment
Stage and label equipment by site, room, rack and user/area. Install core services before endpoints and validate remote management before broad cutover. Coordinate phones, rooms, displays, printers, security and user devices without mixing assets between waves. Preserve old-site service and equipment until the authorized release point.
Use a written method of procedure with hold points for configuration-sensitive actions. Photograph and label the before state, preserve known-good cabling or configuration, and keep a practical rollback path. Record deviations as they occur instead of reconstructing them after the visit.
- Site/room/user staging
- Core before endpoints
- Remote management confirmation
- Controlled asset movement
| Deployment stage | Control point | Closeout evidence |
|---|---|---|
| Site readiness | Lease/construction release, power, carrier, cabling, furniture, rooms and access. | Readiness checklist |
| Technology stack | WAN, firewall, switching, Wi-Fi, voice, AV, printers, security and user devices. | Dependency/BOM reconciliation |
| Migration | Users, departments, numbers, data, equipment, old site, cutover and rollback. | Migration wave record |
| Day one | Support bridge, monitoring, walk-through, exceptions, spares and old-site disposition. | Opening report |
Workflow, resilience and acceptance testing
Test each carrier and uplink, addressing, identity, Wi-Fi, voice, conferencing, printing, security and representative business applications. Validate room and user-area workflows with local representatives. Exercise approved WAN or restart recovery and confirm monitoring and support can identify the new site. Track incomplete furniture or room work separately from network faults.
Validation must cover physical status, management visibility, addressing, uplinks, power, policies and representative user traffic. When redundancy is expected, test the approved failure and restoration scenarios. Escalations should include timestamps, identifiers and reproducible evidence.
- WAN/network/identity
- Voice/AV/printing/security
- Representative application tests
- Monitoring and recovery
Fleet records, exceptions and support handoff
Deliver site/rack/port/AP/room/device inventories, software, tests, user-wave status, photographs and exceptions. Maintain a day-one bridge and walk-through with severity and ownership. Complete old-site circuit cancellation and equipment disposition only after business and technical signoff, with chain of custody for retained media.
Closeout combines annotated photographs, serials, port and cable records, software versions, test output, exceptions and ownership. Credentials and private configurations belong in the client-controlled repository, while public pages should point only to official manufacturer support resources.
- Complete site/room asset record
- Day-one bridge/walk-through
- Old-site release/cancellation
- Media and equipment disposition
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Prepare
Confirm access, equipment, remote readiness and rollback.
Execute
Install through the approved method and document deviations.
Test
Validate management, service, resilience and user workflows.
Close
Deliver evidence, inventory, exceptions and support ownership.
Information to gather before design
Good decisions are easier when the project team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Site access and remote contacts
- Staging, inventory and prerequisites
- Method, maintenance window and rollback
- Acceptance tests and escalation
- Evidence and operational ownership
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
What commonly delays a branch opening?
Unready carriers, power, rooms, furniture, cabling, shipments or missing cross-team ownership.
When may the old site be disconnected?
After authorized business and technical acceptance and the rollback hold.
Should all users move in one wave?
Use waves when scale, risk or support capacity makes phased migration safer.
What belongs in day-one support?
A staffed bridge, monitoring, walk-through, issue severity, ownership and spares.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Build a repeatable field-deployment plan
Provide the site list, target schedule, equipment responsibility, change-window constraints and acceptance criteria. We will help turn them into a practical rollout and closeout workflow.