A workplace move may look simple on the surface, but it usually affects multiple systems at once. Access needs to work, equipment needs to be ready, workplace records need to be updated, and the employee’s new location needs to be reflected across the organization. That is why moves are treated as a defined operational process rather than a one-off request.
In workplace management, a move is the planned relocation of an employee, team, or department from one physical location to another within a corporate real estate portfolio. Moves are the most visible component of the MAC (Moves, Adds, Changes) framework and require coordination across HR, IT, facilities, and security to execute without disrupting productivity or degrading space data.
| Type | Example | Typical Timeline |
|---|---|---|
|
Individual
|
Single employee changes desk or floor
|
|
|
Team
|
Engineering squad moves to a new neighborhood
|
1–2 weeks
|
|
Floor consolidation
|
Vacating an underutilized floor
|
3–6 weeks, phased
|
|
Building migration
|
Relocating operations between buildings
|
2–6 months, multi-wave
|
Every move, regardless of scale, triggers a series of downstream actions. These often include access updates, IT setup, booking reassignment, mail routing, internal communication, and floor-plan changes. When those tasks are handled one by one instead of in parallel, even simple moves take longer than they should.
After a move is completed, the new location should be checked quickly to make sure access works, equipment is in place, and workplace records reflect the change accurately. This validation step matters because once a floor plan or booking system falls out of sync with reality, the quality of downstream reporting and planning starts to decline.
Explore Kadence Move Management