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.
Dispatch for an office opening depends on facts other trades control: whether the circuit has been turned up at the demarc, whether keys and badges exist for the crew, whether pallets arrived intact. Naming a single onsite decision maker per wave, with a phone number that answers after hours, reduces stalled crews.
- 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.
Because two addresses run at once during a move, the plan needs a written order of waves and a stated moment when the old floor may be released. Photographs of each room before anything is unracked, plus asset tags read into the wave list, give the day-two team something to argue from.
- 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.
Acceptance at a new address gets signed by people who work there, so record which department representative watched which task succeed and when. Faults raised on opening morning should carry the site code, the room, the jack number and the clock time, since the support desk has no history for this location yet.
- 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.
The move is not finished when users sit down. Asset, monitoring and billing systems have to show the new address, the old circuits need a cancellation date somebody owns, and retired gear needs a signed custody record. Store floor plans, port maps and credentials where the client controls access rather than in a shared thread.
- 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.
Lock prerequisites
Confirm lease release, power, carrier delivery, cabling and furniture dates before any technician travel is booked.
Sequence the move
Order the dispatch by dependency so circuits, racks, wireless and user seating land in a recoverable sequence.
Migrate in waves
Move departments in planned groups, keeping the old site reachable until each group signs off on its workflow.
Staff day one
Place onsite and remote support for opening day, then transfer open exceptions to the standing service desk.
Information to gather before design
A branch opening depends on dates other trades control, so the schedule holds only when construction, carrier and furniture milestones are confirmed against each other early.
- Construction release and occupancy date
- Carrier circuit order numbers and due dates
- Floor plan with seat counts
- Old site disconnect and lease end date
- Department move groups and priority order
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.
Planning a branch opening or office move?
If the lease date, carrier due date and move weekend do not line up, we plan around the gap. Send the site list, target dates, seat counts and the applications each department cannot open without.