Project Management for Office Moves: A Practical Plan

What makes an office move different from other projects?

project management for office moves is a key topic in modern project management and teamwork. It combines a fixed contractual deadline with a physical build, a technology cutover, and a change-management problem affecting every employee at once. Most projects can absorb a two-week slip. An office move usually cannot, because the old lease ends and the new space is either ready or it is not.

Three characteristics shape the plan:

• The date is set by contracts, not by the team. Lease expiry, handover, and rent commencement dates are negotiated months earlier and cost real money to change.
• Long-lead items dominate. Carrier circuits, electrical switchgear, custom joinery, and lifts are ordered months ahead and cannot be accelerated with effort.
• The audience is internal and unanimous. Every employee has an opinion about location, desk, meeting rooms, and noise. Communication is a workstream, not a memo.

What are the six workstreams?

Split the project into six workstreams, each with one named owner and a weekly status line. Shared ownership is the same as no ownership when a vendor needs a decision.

Each workstream needs a single decision-maker. If two people can approve a change, the vendor will wait for the third, and the schedule will absorb the delay silently.

What is the critical path?

The critical path is the longest chain of dependent tasks that determines the move date. In most office moves it runs: lease signed → design freeze → permits approved → construction complete → cabling and circuits live → furniture installed → IT cutover → occupancy.

Everything else can be compressed with money or overtime. The critical path can only be compressed by changing sequence or scope, which is why it deserves a weekly review rather than a monthly one.

Two long-lead items catch teams repeatedly:

Carrier circuits. Fibre and dedicated internet circuits commonly take 60–120 days from order to live, and longer if the building needs new conduit or the carrier needs landlord approval. Order before the design is final if you must; a circuit in the wrong comms room is easier to fix than a circuit that arrives in August.

Permits and inspections. A change of use, sprinkler modification, or electrical upgrade can add weeks. Ask the landlord and the local authority early, in writing, what the building has already approved.

> Important note: The building’s base build being “ready” does not mean your floor is ready. Handover, landlord works, and your fit-out are three different dates, and they are often conflated in the lease negotiations.

What timeline should you plan?

For a mid-size office of 100–250 people, start nine months out. Compressed timelines are possible, but they cost a premium and remove the buffer that absorbs surprises.

The gates matter more than the dates. Design freeze at T-6 months is the single most valuable discipline in the plan, because every change after procurement has a multiplied cost.

How do you budget an office move?

Build the budget bottom-up by category, then add contingency based on how much is unknown. A relocation with a new build and a first-time fit-out deserves more contingency than a like-for-like move within the same building.

Industry cost guides commonly put office relocation at roughly $1,500 to $7,500 per employee, but the range is too wide to plan with. Build the estimate from your own square footage, specification, and vendor quotes.

Worked example: a 150-person relocation

A company leases 18,000 square feet for 150 staff. The budget build looks like this:

That is $16,202 per employee and $135 per square foot. If the board approves only $2.2 million, the gap is not a negotiation tactic; it is a scope decision about specification, furniture reuse, or square footage.

Worked example: what downtime actually costs

IT cutover is usually planned as a technical task and budgeted as nothing. Put a number on it.

A 150-person company with a loaded cost of $65 per hour plans a four-hour cutover on a Monday morning. The cost is 150 × 4 × $65 = $39,000 in lost productive time, plus the frustration of a broken first day.

Moving the cutover to Friday 18:00, with a six-person IT crew working eight hours at $95 per hour and a 1.5× premium:

• IT labour: 6 × 8 × $95 × 1.5 = $6,840
• Residual downtime: 1.5 hours on Monday for 150 people = 150 × 1.5 × $65 = $14,625
• Total: $21,465, a saving of about $17,535 compared with the Monday cutover.

The Friday option also gives the team a weekend to fix what breaks. That is usually worth more than the calculated saving, because the alternative is 150 people watching an error message.

Worked example: compress the schedule or extend the lease?

A permit approval slips three weeks. The construction phase is twelve weeks with $380,000 of labour, so three weeks is $95,000 of labour. Weekend and evening work carries a 25% premium: $23,750 extra.

The alternative is a one-month lease extension on the old space at $42 per square foot per year: 18,000 × $42 ÷ 12 = $63,000, plus the cost of moving twice if the new space is not ready.

Compression is cheaper by roughly $39,000, but it concentrates risk: faster work means more defects, and defects in a fit-out show up as snagging lists that delay occupancy anyway. The right answer depends on how much float remains after the delay. If the schedule had two weeks of buffer, compress one week and keep one. If it had none, negotiate the extension early rather than paying a premium for a date you will still miss.

What are the main risks, and how do you manage them?

The trigger column is what makes a risk register useful. A risk without a trigger is a worry; a risk with a trigger becomes a decision with a date.

What does the move-day runbook contain?

The runbook is a timed sequence of events with names and phone numbers. Keep it to two pages and give it to every vendor, not just the internal team.

A workable structure:

• T-5 days: go/no-go meeting. Confirm access, lifts, power, network, and the fire alarm procedure.
• T-1 day: pack completion check, labeling scheme verified, old-site access confirmed, vendor arrival times.
• Move day 06:00–08:00: building access, loading dock control, floor protection.
• 08:00–12:00: IT decommission and transport priority equipment first.
• 12:00–17:00: furniture placement, workstation setup, network smoke tests.
• 17:00–20:00: IT cutover, print and access control tests, cleaning.
• Day after 08:00: support desk at the entrance, floor walkers, escalation channel.

Two details decide whether the day feels calm: a single radio channel or chat channel for the move coordinator, and a rule that no one moves a labeled box to a second location. Every unlabeled box becomes a 20-minute search on Monday.

How do you communicate with staff?

Communicate on a fixed cadence and repeat the same facts. Uncertainty is what generates rumors, not bad news.

• T-8 weeks: why we are moving, the date, the address, and what is decided so far.
• T-4 weeks: floor plans, seat allocation process, packing instructions, what to bring and what to leave.
• T-1 week: day-of logistics, arrival time, access cards, IT setup, who to ask for help.
• Day before: a one-page summary with the support number and the first-day schedule.
• Day one: a short welcome note, lunch plan, and a feedback channel.

Seat allocation deserves its own decision process. A pure free-for-all creates conflict; a rigid assignment ignores how teams actually work. Publish the rule, apply it consistently, and give teams a week to raise exceptions before the plan is locked.

What are the most common mistakes?

• Starting too late. Six months is workable for a simple like-for-like move; nine months is realistic for a fit-out.
• No single owner. A steering committee is not a project manager.
• Freezing design after procurement. Change orders are where fit-out budgets die.
• Treating IT as a subcontractor. The network is the critical path for day-one productivity.
• Forgetting the old landlord. Make-good obligations, dilapidations, and handback inspections cost money and time after the move.
• No downtime cost. Without it, the Friday cutover looks expensive and the Monday outage looks free.
• Communicating once. One town hall is not a communication plan.

Who should run an office move?

A dedicated project manager with facilities experience, supported by a workplace consultant for design and a move coordinator for logistics. For moves under about 50 people, a capable office manager with a checklist can run it, provided someone senior owns the lease and budget decisions.

The failure pattern is assigning the move to someone who already has a full-time job. Office moves generate decisions daily in the final eight weeks, and a part-time owner becomes the bottleneck without anyone noticing until the schedule is already late.

Where does a tool help?

An office move is a coordination problem disguised as a construction problem. The construction has a contractor and a schedule; the coordination has six workstreams, 200 tasks, 15 vendors, and a date that cannot move.

That is the problem Doitify is built for: separate projects or boards per workstream, multi-level tasks with owners and due dates, dependencies for the gating decisions, checklists for move day, and reports that show what is late before the weekly meeting. Doitify is our product, so treat that as a disclosure. It will not replace a fit-out contractor or a lease lawyer. It does replace the spreadsheet that three people are editing and nobody trusts.

Conclusion

An office move succeeds or fails on the decisions made in the first eight weeks: who owns each workstream, when design freezes, when long-lead items are ordered, and how much contingency is held.

Treat the date as fixed, the critical path as sacred, and communication as a deliverable. Then the move becomes what it should be: a busy, well-run project that most employees experience as a smooth first Monday.

If this post on project management for office moves was helpful, you might also enjoy Project Kickoff Checklist: The Complete PM Guide and Software Development Project Template: Sections, Example, and How to Use It.