
Jump to a section in this guide
An office can be physically ready while its technology is still a week away from being usable. Desks, keys, and a moving truck do not establish internet service, transfer phone numbers, or prove that the meeting room works. Treat the move as a sequence of dependencies with named owners. This checklist helps the business, facilities team, carriers, and technology providers coordinate the work around the date staff actually need to operate.
In this guide
Use the sections below to prepare requirements, compare proposals, and agree on a useful handover. Each example is a planning illustration rather than a claim about a client project.
Plan from the opening date backward
List the systems that must work on the first day in the new space. Include internet connectivity, employee workstations, phones, wireless coverage, security equipment, and meeting rooms. Give each dependency an owner and an agreed date; the moving company’s schedule is only one part of the plan.
Divide the plan into decisions, installation work, tests, and the cutover itself. Start with the business activities that must continue: taking calls, accessing essential applications, processing transactions, or communicating with customers. Identify which activities can tolerate an interruption and which require a temporary arrangement.
Give each dependency a person responsible for confirmation, not just a company name. For example, “carrier service ready” should have an order reference, contact, and person who verifies the connection. Keep a shared list of decisions and dates. If the opening date moves, review dependent tasks together rather than assuming every supplier has independently received the update.
Confirm what the new space provides
Review the floor plan and inspect the infrastructure already installed. Determine whether the available outlets, cable routes, equipment spaces, and power arrangements fit the planned layout. Confirm building access and any restrictions before installation work is scheduled.
Inspect the actual rooms against the proposed seating plan. Existing outlets may be in the wrong place, insufficient for the equipment, poorly labeled, or unsuitable for reuse without assessment. Consider printers, wireless access points, reception, shared desks, security devices, and collaboration spaces as well as individual workstations.
Identify where network and communications equipment will be located, who can access that space, and what work other trades must complete first. Ask the building contact about installation access and any approval requirements. A route that appears simple on a drawing may need coordination on site. Resolve those questions before setting an installation date that depends on them.
Coordinate services and equipment
Keep track of carrier orders, account information, equipment that will move, equipment that will be replaced, and the parties responsible for each task. If phone numbers are transferring, confirm the requirements and sequence with the carriers involved. Avoid assuming that one vendor’s completion means the whole system is ready.
Create a move-or-replace list for equipment and a retain-or-transfer list for services. Include ownership, support contacts, contract responsibilities, and any account information needed for coordination. Do not cancel a service merely because a replacement order has been submitted; confirm the dependency and the agreed transition sequence.
Phone number transfers deserve their own tracking item. Confirm account details and requirements with the carriers, identify who coordinates the transfer, and plan test calls after the cutover. The same discipline helps with internet circuits and hosted applications. Ask each provider what evidence they will supply when their part is ready and what remains for another party to complete.

Test before the team arrives
Create a short acceptance checklist for representative desks, wireless devices, phone calls, and meeting-room scenarios. Test with the equipment and applications staff actually use. Leave time to resolve problems before a fully occupied office makes troubleshooting harder.
Write short tests that represent a normal workday. At a desk, connect the expected device and open the required application. On Wi-Fi, try a representative staff device in important working areas. For phones, test incoming and outgoing calls and the intended reception or voicemail path. In a meeting room, join a real test meeting and share content.
Record failures with an owner and a resolution date. Leave time between installation completion and staff arrival so fixes do not compete with moving-day activity. If a system cannot be fully tested until cutover, identify that limitation explicitly and assign someone to perform the test immediately when the dependency becomes available.
Plan the old-site handover
Identify which systems remain active until the move is complete and who confirms they can be retired. Coordinate account changes, equipment removal, and any required cabling work with the appropriate parties. Preserve useful diagrams, labels, and configuration records for the new site.
Define the old-site exit alongside the new-site plan. Some equipment or services may need to remain active until the transition is confirmed. Identify the person who approves shutdown, the records that need to be retained, and the responsibilities for equipment removal or other agreed handover work.
Keep an updated contact list for the first days in the new location. Staff should know where to report a fault, and the receiving support team should have the new layout, equipment records, and carrier contacts. A short post-move review can capture unfinished items before they become permanent workarounds. Mark those items separately from the tasks required for day-one operation.
Planning example: the new office opens on Monday
A hypothetical planning example
A small team is moving over a weekend. The cabling installation finishes on Thursday, but the carrier handoff is scheduled for Friday and the phone transfer is still awaiting confirmation. The useful action is to test what can be tested on Thursday, identify the carrier and phone dependencies explicitly, and agree on who confirms them before the move. If a required service is delayed, the business can choose a temporary working arrangement with accurate information. This hypothetical example illustrates dependency planning; it does not promise a particular carrier lead time.
Compare the important decisions
| Milestone | Evidence of readiness |
|---|---|
| New-space plan agreed | Seating, device locations, equipment space, and access reviewed |
| Infrastructure installed | Links identified and agreed tests recorded |
| Services ready | Carrier and system owners confirm the required connections |
| Cutover authorized | Business owner accepts the sequence and remaining limitations |
| Move complete | Day-one workflows tested and outstanding tasks assigned |
A checklist to take into the conversation
- Internet and carrier readiness
- Cabling and equipment-space requirements
- Phone numbers and call routing
- Wireless and security requirements
- Meeting-room tests
- Cutover owners and old-site handover
Turn the plan into a useful next step
A successful technology move is easier to manage when “ready” has a shared meaning. Use a short readiness review before authorizing the cutover, keep the contacts accessible during the move, and hand the completed records to the team responsible for supporting the new office.
R.W. Communications works with organizations in Central Pennsylvania and surrounding regions. Explore our structured cabling services, or tell us about the site and the work you are planning.
Plan a project with our regional team
R.W. Communications is based in Harrisburg and serves Central Pennsylvania and surrounding regions. Explore Harrisburg and Central PA project planning or find your service area.
Let’s plan your next technology project.
Tell us what you need, where you need it, and what success looks like.
