Planning an office move for 100+ staff doesn’t need 12 months. It needs 90 days of disciplined governance.
Here’s the timeline that works for enterprise-scale relocations:
Days 90-60: needs assessment, stakeholder governance, budget lock, vendor selection.
Days 60-30: space planning, IT and network migration prep, communications rollout.
Days 30-7: detailed logistics, labelling, sector compliance checks.
Moving week: phased or out-of-hours execution with minimal disruption.
Post-move: a structured 30-60-90 day settling period, plus zero-landfill decommissioning of the old space.
One accountable lead. One plan. No hand-offs between departments guessing what’s already been done.
Why 90 Days Beats the 6-12 Month Generic Timeline
Most office move guides target a 20-person startup picking a WeWork desk cluster. They stretch planning across 6 to 12 months because nobody’s forcing a decision.
That approach doesn’t survive contact with a 300-person finance firm, a hospital trust, or a local authority moving three departments at once. Larger moves have more moving parts, not more time to waste on them. A compressed, structured 90-day office move timeline forces the governance, budget sign-off and vendor selection that vague multi-month plans let drift.
This is the difference between office move planning as a checklist exercise and office move planning as a project with a single accountable owner, a locked budget, and a date that doesn’t move. For businesses with multiple departments, regulated data, lab equipment or clinical operations, that structure isn’t optional. It’s the only way to hit a fixed date without a scramble in the final fortnight.
If you’re weighing up whether your organisation needs a formal relocation partner rather than an internal facilities team running this off a spreadsheet, our office relocation services page breaks down what full-scope project management actually covers for moves of this size.
Days 90-60: Needs Assessment, Governance and Vendor Selection
This phase sets the whole project up or sinks it. Get it wrong here and every later phase inherits the delay.
Build the governance structure first
Enterprise moves fail on ambiguity, not logistics. Before anything else, appoint:
A single project lead with authority to make binding calls on scope, budget and schedule.
A steering group with representation from facilities, IT, HR, finance and, where relevant, legal or compliance.
Department leads who own their team’s requirements and sign off on their own space allocation.
No shared ownership. No “we’ll decide later.” One name against every decision, one weekly governance meeting, and a documented escalation path for anything that stalls.
Lock the budget and scope
Confirm headcount, square footage, and what’s moving versus what’s being replaced. Budget creep almost always comes from scope decided too late, not from the move itself. Set a contingency line (most enterprise moves budget 10-15% above the core estimate) and don’t touch it until week six.
Assess needs across every department, not just facilities
A 90-day office move planning checklist for a multi-department organisation has to capture requirements that a single-floor SMB move never sees: server rooms, lab benches, secure archive storage, clinical equipment, trading floor connectivity. If your business runs specialist environments, this is the point to scope them properly. Our laboratory relocation services team, for instance, gets involved at this exact stage for any move involving calibrated equipment, cold storage or controlled substances, because retrofitting that planning at week 40 is how labs end up offline for a fortnight.
Select vendors on capability, not just price
By day 60 you need signed contracts with your removal partner, IT migration specialist, and any specialist movers (lab, archive, secure records). For a headquarters relocation specifically, involve your chosen partner in space planning conversations this early. Our headquarters relocation team routinely joins client steering groups at day 75, not day 20, because HQ moves carry brand, client-facing and board-level visibility that a standard office move doesn’t.
Days 60-30: Space Planning, IT Migration Prep and Communications
By the halfway point, the abstract plan needs to become a floor plan, a network diagram and a staff-facing message.
Finalise the space plan
Confirm desk allocations, meeting room ratios, breakout space and any hot-desking policy. Walk the new site with department leads. Flag anything that needs building work, cabling, or access control changes now, because these are the long-lead items that blow a 90-day timeline if they’re not flagged by day 55.
Start IT and network migration in parallel, not after
This is where most enterprise timelines actually break. Cabling, server relocation, network cutover and access control can’t be an afterthought squeezed into moving week. They need their own workstream running alongside the physical move from day 60.
Data centre and server migrations especially need a rehearsed cutover plan, redundancy testing, and a rollback option if something doesn’t come up clean on the other side. This is specialist work. Our IT relocation specialists plan network and server migrations as a parallel track precisely so a hardware move never becomes the reason a trading desk or a hospital system goes dark for a day it shouldn’t.
Build the communications plan
Staff need to know, in order: why the move is happening, when it’s happening, what changes for them personally, and who to ask if something’s unclear. Send this in phases, not one giant email. Weekly updates from day 60 keep anxiety down and questions manageable, rather than one confusing all-staff email in the last week.
Days 30-7: Detailed Logistics, Labelling and Sector Compliance
This is the operational tightening phase. Plans become task lists, task lists become labelled boxes and confirmed time slots.
Get granular on logistics
Confirm final floor plans and desk-by-desk labelling codes.
Issue packing kits and labelling instructions to every department, not just facilities.
Colour-code or number-code by floor, department and priority (what needs to be unpacked first versus what can wait a week).
Confirm building access, parking, lift bookings and loading bay slots with both buildings’ management.
A moving office checklist that’s specific to floor, desk and box number beats a generic “pack your desk” memo every time. Confusion on moving day almost always traces back to a labelling system nobody actually tested.
Run sector-specific compliance checks now, not on moving week
Regulated sectors carry compliance obligations that a generic office move planning checklist won’t cover. Build these into your 30-day checklist explicitly:
Healthcare and NHS: equipment decommissioning, clinical waste protocols, infection control during transit, and continuity of patient records. Anything touching clinical space should follow the frameworks our healthcare and NHS relocation specialists work to, because standard commercial movers aren’t set up for controlled drugs storage or clinical equipment handling.
Government and local authority: procurement rules, public records retention, and continuity of citizen-facing services during the transition. Our government and local authority relocation team builds these checks into the 30-day window specifically, because a council can’t simply close a service desk for a week.
Finance: secure handling of physical records, confirmation of business continuity for trading or client-facing systems, and data protection sign-off before anything with client data leaves the building.
Education: term-time constraints, safeguarding requirements for any move involving pupil or student records, and minimal disruption to teaching schedules.
None of these are a footnote. Skip them at day 30 and they become a moving-week emergency.
Moving Week: Execution With Minimal Disruption
By moving week, every decision should already be made. This week is execution, not planning.
Phase it, or move out of hours
For any organisation over 100 staff, moving everyone on one Saturday is a risk, not a plan. Better options:
Phased moves: department by department across several days or weekends, so critical functions never go fully offline at once.
Out-of-hours moves: evenings and weekends for the physical shift, with IT cutover happening overnight so staff arrive Monday to a working desk, not a half-finished setup.
No single point of failure. No department left without a fallback if one part of the move slips a day.
Keep one point of contact live throughout
Staff, movers and IT should have exactly one number to call if something’s wrong on the day. Split accountability during the physical move is how small issues (a missing box, a printer that’s not connecting) turn into a day of lost productivity.
Test before you declare it done
Before signing off moving week, confirm: network access from every floor, phone lines live, access control working, and a walk-through with each department lead confirming their team can actually work from the new space. Don’t call it complete until someone’s actually opened their laptop and logged in.
Post-Move: The 30-60-90 Day Settling Period
The move isn’t finished when the last box is unpacked. This is where most timelines stop and most problems actually surface.
Day 30: fix what’s broken
Collect issues from every department: connectivity gaps, missing furniture, access problems, anything that didn’t get flagged in the rush of moving week. Fix the practical stuff fast. Momentum matters here.
Day 60: check the plan against reality
Are desk ratios working? Is the meeting room mix right? Has anyone flagged a compliance gap in the new space? This is the point to adjust, not to assume everyone will just get used to it.
Day 90: formally close the project
Confirm every workstream is signed off: IT, facilities, HR, compliance. Run a short retrospective with the steering group. What worked, what didn’t, what would you change on the next move. Document it. The next relocation (and there usually is one) shouldn’t start from zero.
Decommission the old space properly, not as an afterthought
The old building isn’t done with you yet. Lease conditions usually require it back in a defined state, and there’s a genuine sustainability case for not sending a floor’s worth of furniture and equipment to landfill.
A zero-landfill approach means auditing what’s reusable, donating or reselling furniture that’s still fit for purpose, recycling what isn’t, and only sending genuinely unrecoverable material to disposal. This is specialist work in its own right, distinct from the move itself. Our sustainable office clearances service exists specifically for this stage, handling the old site’s clearance so nothing ends up in a skip that didn’t need to.
Sector Compliance: What to Flag Early, Not Late
A few sector-specific touchpoints deserve a second mention, because they’re the ones generic office move guides skip entirely.
Healthcare: continuity of clinical services and secure handling of patient data don’t pause for a move. Build redundancy into the plan from day 60, not day 7.
Government: public accountability means procurement and records retention rules apply throughout, not just at contract sign-off.
Finance: regulatory reporting and client confidentiality obligations follow the data wherever it physically sits, including in transit.
Education: safeguarding obligations extend to how student and staff records are handled during the move, not just where they end up.
None of these change the 90-day structure. They just mean specific checkpoints need a named owner and a sign-off, not a general assumption someone’s handling it.
Frequently Asked Questions
Is 90 days really enough time for a large office move?
Yes, for most 100+ staff relocations, provided governance and vendor selection happen in the first 30 days, not the last. The moves that overrun aren’t short on time. They’re short on a single accountable decision-maker and a locked scope.
What’s the biggest risk in an enterprise office move timeline?
IT and network migration treated as an afterthought. Cabling, server relocation and cutover testing need their own workstream from day 60, run in parallel with the physical move, not squeezed into moving week.
How do we minimise disruption to the business during the move itself?
Phase the move by department or run it out of hours, with IT cutover overnight. Keep one point of contact live throughout moving week so issues get resolved in minutes, not days.
What happens to the old office once everyone’s moved out?
It needs a proper decommissioning and clearance plan, ideally zero-landfill, covering furniture reuse, resale, recycling and lease-condition compliance. This should be scoped during days 60-30, not left until after the move.
Do regulated sectors need a different timeline?
The 90-day structure holds, but healthcare, government, finance and education moves need extra compliance checkpoints built into the 30-7 day phase, covering data protection, records retention, clinical continuity or safeguarding depending on the sector.