01
Define the operational outcome before design coordination
The move date is not the project requirement. The requirement is a workplace that can support people, transactions and critical operations at the agreed opening time. Record the business functions that must be available, the acceptable outage window and who can accept each system.
Build one scope register across landlord, fit-out, electrical, telecom carrier, network, AV, security, workplace technology and move vendors. Every interface needs one accountable owner even where several suppliers contribute.
Business-critical services
Name the teams, applications, rooms, links and security functions that cannot miss day one.
Authority and approvals
Confirm landlord, building management, change-control, access and work-permit requirements early.
Acceptance owners
Assign a named business or technical owner to accept every system and exception.
02
Make hidden dependencies visible
A corporate workplace behaves as one connected system. Wi-Fi depends on switch ports, cabling, power and configuration; meeting rooms depend on networks, identity services and acoustic completion; access control depends on doors, power, network paths and approved user data.
Power and rooms
Validate distribution capacity, outlets, UPS needs, earthing, rack layout, cooling and maintainable access.
Carrier and network
Track building entry, wayleave or access, circuit delivery, firewall readiness, Wi-Fi coverage and cutover configuration.
AV, security and IoT
Map devices to power, data, cloud or on-premise services, licences, accounts and support owners.
Migration and move
Sequence data, equipment, people, records and vendor access against a single minute-by-minute runbook.
03
Use readiness gates, not percentage-complete reporting
A project can look 95% complete while one carrier circuit or untested security interface still prevents occupation. Readiness gates convert progress into evidence-based decisions.
T-minus 30 days
Freeze the integrated programme, scope interfaces, test scripts, issue owners and escalation path.
T-minus 14 days
Complete device-level checks, confirm circuit and account availability, rehearse the cutover and agree rollback criteria.
T-minus 2 days
Close critical defects, capture backups, confirm attendance and obtain go/no-go approval.
Day one and stabilisation
Operate a command channel, log incidents, triage by business impact and retain vendors until agreed exit criteria are met.
04
What a useful relocation handover contains
Handover is a controlled transfer of operational knowledge. The final pack should allow the facilities and IT teams to operate, support and change the workplace without reconstructing the project history.
Verified records
As-built drawings, rack and port schedules, asset records, circuit details and approved configuration baselines.
Proof of function
Signed test results, integrated scenarios, defect status and accepted exceptions.
Operational control
Support contacts, warranty dates, licences, renewal ownership, backup and recovery procedures, and training records.
Sources
Primary references
These primary sources were used to check public requirements, the purpose of standards or recognised practice. Project-specific applicability must be confirmed.
FAQ
Frequently asked questions
When should engineering coordination start for an office relocation?
Start during site due diligence or early design, before layouts and procurement freeze key power, carrier, communications-room and system decisions. The exact lead time depends on landlord approvals, carrier delivery and business criticality.
Who should own the move-weekend go/no-go decision?
A named client decision-maker should own the decision, informed by technical leads against agreed readiness, rollback and business-impact criteria. The delivery team should provide evidence, not make an undefined business-risk decision.
Can UPNX coordinate vendors already appointed by the client?
Yes. The responsibility matrix and integrated programme can include client-appointed designers, contractors, carriers, IT teams and specialist vendors, subject to a clearly agreed scope and authority model.