---
sourceDocument: Australia Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/service-management-for-the-enterprise

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Service Management

ft:clusterId :

    - sm4e

bundleId :

    - sm4e

workflow :

    - Technology


---

# Enterprise move scenarios

# Enterprise move scenarios {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Move scenarios are used by the Facilities team to see the implications of a move in
relation to other moves. Multiple scenarios can be created.
Predictive availability considers planned seating changes for the selected scenario (on or off current level).
* **[Plan a move scenario](https://servicenow-prod.fluidtopics.net/q7Bjb4ds6V~jH60KdoQb1w)**   
  Facilities administrators create move scenarios when planning and executing large-scale moves. When people are added to the scenario, move_detail records are created. These records contain all the information about the potential move for a specific person, such as the reference to the sys_user, destination floor, and destination building.
* **[Activate a delegator](https://servicenow-prod.fluidtopics.net/vZx4VEoPfEg02q9PbMnofA)**   
  Delegators assign users to seats in a scenario. Activating the delegator sends an email notification request that they assign seats using Move Details.
* **[Assign users to seats](https://servicenow-prod.fluidtopics.net/BomZ5g13elSgVBgKE8Y8UA)**   
  Delegators receive an email notification requesting that they assign seats using Move Details.