Corporate relocation support: synchronizing operations and real estate
The 4 critical interfaces of an office relocation
On an office relocation, most delays do not come from the construction site but from a lack of synchronization between real estate and operations. This observation reverses the usual reading that blames the works: it is the management of interfaces, not the duration of work packages, that determines the switchover date. Since 2006, Kytom has managed more than 150 office relocations. Initial 2-hour diagnostic, phasing in 5 steps, median duration of 6 to 8 weeks for 100 to 500 workstations. This page sets out the method for coordinating the four critical interfaces, the three recurring tensions in sequential management, and the indicators measured at the end of the project.
A corporate relocation simultaneously activates four interfaces that the project owner tends to handle in silos.
- Technical interface: synchronization between handover of technical work packages (HVAC, high-voltage systems, low-voltage systems), IT testing and furniture delivery. A typical window spans 10 to 15 working days depending on the size and complexity of the site.
- Organizational interface: calibration of phasing according to business peaks, accounting closing periods, HR constraints and remote-work agreements.
- Contractual interface: allocation of responsibilities between the moving company, the fit-out contractor, the outgoing landlord, the incoming landlord, and IT and security providers. A single owner of the schedule avoids grey areas.
- Temporal interface: overlap between real estate notice period (often 6 months), construction duration (generally on the order of 10 to 14 weeks) and operational switchover.
Projects that formalize these four interfaces from the DD phase significantly shorten the transition period.
For the CFO and the Asset Manager: the stakes are measured in avoided rent. On a 1,500 sqm floor in the Paris CBD (headline rent around 850 EUR/sqm/year excl. tax and charges, i.e. about 106,000 EUR/month), each week of double rent avoided represents a direct gain of around 25,000 EUR, excluding productivity costs. It is this order of magnitude, not the cost of the management itself, that justifies an integrated unit rather than a sequential chain.
Kytom’s position, running counter to sequential project-owner practice. Industry orthodoxy recommends breaking down into separate work packages (programming, project management, moving company, IT) to put each link out to competitive tender. In our recent experience, this breakdown produces pricing optimization of 4 to 7 % package by package, but a coordination and modification-works overrun of 8 to 12 %. The net gain is negative for private project owners with 100 to 500 workstations: the real lever for savings is schedule convergence, not atomized competitive tendering.
When this interface logic does not apply. Below 50 workstations or for an intra-building relocation without structural works, the integrated unit becomes oversized: an occasional consultant assistant two days a week is enough. Likewise, when the landlord delivers already fitted-out floors (turnkey for the tenant) and the IT system is pure SaaS, the technical interface comes down to 3 to 5 working days.
Three recurring tensions in sequential management
Our recent experience reveals three causes of drift that are regularly underestimated.
- Sizing before analyzing work modes: surfaces and zoning fixed before the flow audit. Consequence: post-relocation adjustments to the program, handled as modification works, often costly and avoidable.
- Underestimation of IT and security validations: in regulated environments (banking, healthcare, industry), approval testing spans several incompressible weeks. Realistic planning places them in parallel with finishing works, not downstream.
- Change management handled at the end of the project: internal communication starts on average 3 weeks before the switchover, which creates resistance and lengthens the adoption curve by 4 to 6 weeks.
For the Office Manager and the HR-QWL department: adoption is decided before the boxes are packed, not after. The Actineo barometer has long identified upstream employee involvement as a variable correlated with post-move-in satisfaction. Our experience points the same way: projects that start change management more than 8 weeks before the switchover achieve satisfaction rates significantly higher than late starts.
The corrective approach combines three levers: an audit of practices upstream of the design, integration of IT constraints into the technical plans from the SD phase, and a change management plan managed in parallel with the works schedule. The typology of spaces (open collaboration, engineering in concentration mode with a target noise level below 35 dB(A) per NF S 31-080) is then defined on the basis of observed uses, not assumed ones.
Limitation of these corrective measures. On time-constrained projects (non-negotiable landlord notice period, window under 10 weeks between signing and switchover), the full 3-week organizational audit becomes incompatible with the schedule. In this case, Kytom substitutes a 5-day flash audit, accepting a residual modification-works rate of 6 to 9 %: maximum optimization is not achievable, and it is more honest to say so at kickoff than to discover it at handover.
Kytom method in 5 synchronized steps
Typical phasing covers 4 to 6 months depending on the size of the scope and the condition of the future site.
| Step | Purpose | Duration |
|---|---|---|
| 1. Organizational audit | Flows, irritants, business constraints, occupancy measurements | 3 weeks |
| 2. Integrated design | Fit-out and switchover logistics co-developed | 4 weeks |
| 3. Convergence schedule | Construction milestones, technical tests, switchover waves | 1 week |
| 4. Coordinated management | Weekly multi-provider committees | Construction duration |
| 5. Post-occupancy | Adjustments, adoption measurement, snagging clearance | 2 months |
For the Architect and the real estate director: the value of design and build is measured in avoided trade-offs. The design team knows the construction constraints and adapts the phasing in real time, without contractual back-and-forth between the project manager and the general contractor. On multi-site operations, the network of 11 agencies in France and Spain applies the same methodological grid, which secures documentary consistency between locations.
Our reading differs from the dominant design and build = always faster narrative. On operations in regulated sectors (banking, healthcare), design and build provides only 1 to 2 weeks of net gain, because the IT and security approval milestones bound the schedule independently of the contractual mode. Selling design and build as a universal accelerator on these scopes is misleading: the real value here is documentary traceability and single-point responsibility in the event of a dispute, not speed.
When design and build is not the right contractual mode. For a public project owner subject to the public procurement code, or for a project where the program is still shifting by more than 30 % at launch, the separated mode (project management / contractors) remains more suitable: the flexibility to modify outweighs the coordination gain.
Frequently asked questions
How much time should be allowed for a 200-workstation relocation?
For a 200-workstation relocation, allow 4 to 6 months from the organisational audit through to post-occupancy. The upstream phase combines diagnosis, integrated design and resolution of critical interfaces, with the works themselves averaging 12 weeks. Post-occupancy then covers snagging and measuring adoption over the first weeks of use.
