← All Case Studies National Facilities Program

National Office Relocation

300+ employees relocated. 25+ offices. No two moves alike.

A running, multi-year program of office relocations, new office build-outs, and site closures, with several projects overlapping in timing at any given point, each one requiring its own vendor lineup, lease timing, and IT cutover plan.

Scope25+ Offices
300+ Employees

ApproachConcurrent, Site-by-Site

OutcomeEvery Site Fully Operational

01Situation

Roughly 25 offices needed to move, get newly built out, or close, each one different, with no two moves following the same playbook.

Some sites were straightforward relocations. Others were ground-up office builds, standing up a new space from the IT closet out to every desk. Others were closures, winding a site down cleanly and accounting for every piece of equipment that came out of it. No single checklist covered all three.

This also wasn't one project running at a time. Several relocations, builds, and closures ran on overlapping timelines, all pulling from the same pool of vendors, budget, and internal resources at once.

More than 300 employees were relocated over the life of the program, across offices nationwide.

Why it mattered

This wasn't one relocation, it was a portfolio of them, moves, builds, and closures running at the same time, each with its own landlord, vendor list, and IT footprint. A miss on any one site meant a team without a working office on day one.

02Challenge

Three kinds of projects, often at the same time, across sites that didn't share a landlord, a vendor list, or a clock.

Coordinating walkthroughs with vendors and third parties at every site, and getting floor plans, the IT closet build, and networking sign-off settled before a single box moved
Negotiating lease timing with landlords to land a favorable move-in window instead of just the one that happened to be open
Overlapping timelines: multiple relocations, builds, and closures running at once, competing for the same vendors, budget, and internal resources
Operational risk on every site, downtime, vendor delays, and facility readiness, any one of which could leave a team without a working office on day one

03Action

Ran every site the same disciplined way, walkthrough to closeout, while carrying several of them at once.

Ran office walkthroughs between HQ, the local office, and vendors at every site, reviewed floor plans for networking, and managed the build-out of each new IT closet, coordinating with cabling vendors on CAT 6 installation and the placement of access points and security cameras.

Negotiated lease timing with landlords for favorable move-in windows, requested the office's primary and secondary internet circuits the same week the lease was signed, coordinated with furniture and insurance companies, and kept travel and equipment spend hitting budget on schedule for every deployed team.

Planned and ran the disconnect, transport, and reconnect of every IT system: disconnecting phone, internet, and fax service at the old space and standing it all back up in the new one, network cutover, telecom changes, server moves, and endpoint configuration (network printers, scanners, and more), most of it delivered after hours to keep the business running.

Documented every connection from switch port to wall jack, with clear labeling across every site, for easier troubleshooting, faster upgrades, and one organized view of the overall IT infrastructure.

Identified operational risks early, downtime, vendor delays, facility readiness, and built mitigation plans before they became problems. For closing sites, decommissioned equipment, returned it to headquarters, and updated the asset management inventory.

Closed every site the same way: punch-list items resolved with building management, every team confirmed fully operational, lessons learned documented, and a full project closeout report delivered.

04Results

25+offices moved, built out, or closed

300+employees relocated

Twenty-five-plus sites, moves, builds, and closures alike, running on overlapping timelines, and every one of them landed the same way: teams at their desks, systems live, and a closeout report on file to prove it.