---
sourceDocument: Australia Field Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/field-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Field Service Management

ft:clusterId :

    - fsm

bundleId :

    - fsm

workflow :

    - Customer and Industry


---

# Territory-Based Optimization

# Territory-Based Optimization {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Enable the Field Service Territory model to focus optimization on territories rather than assignment groups.

You must [Configure Territory Planning](https://www.servicenow.com/docs/tWoxpiBO2hR~9D~Ma~TFBQ "Field Service Territory Planning identifies the best matched territory for a work order task based on conditions that you set. You can then assign tasks to the individual agent or group best positioned to execute a service call based on the associated territories."). When implementing Schedule Optimization based on territories, consider the following points:

Plugin dependencies
:   Territory-based optimization requires the Territory Planning plugin. The following conditions apply:

    * If the Territory Planning plugin is not installed or the Territory Model is inactive, optimization continues using assignment groups.
    * If both the Territory Planning and Schedule Optimization plugins are installed but the Territory Model is inactive, tasks are optimized based on assignment groups. Keep territory-related batches inactive until you activate the Territory Model.
    * If both plugins are installed and the Territory Model is active, tasks are optimized exclusively based on territories. You can create scopes specifically for territories.
    {#territory-based-optimization__ul_vc4_24d_xzb}

Activation prerequisite
:   Before [Enabling the territory model](https://www.servicenow.com/docs/20q5s~24qUlCvbB_WCkzlw "Activate the territory model to display the Territory field in the work order task form so the task can be assigned to an agent or crew associated with the selected territory. The territory model maintains a record of territories mapped to it."), confirm that batches optimized by assignment groups are inactive and batches optimized by territories are active.

Post-activation
:   After activating the Territory Model, tasks require a territory selection for Schedule Optimization to assign them to technicians.

Territory membership evaluation
:   Schedule Optimization evaluates territory membership at the day level. If a technician belongs to multiple territories during a single day, the system treats them as a member of all those territories for the entire day.
    Membership is based on technician membership records, not optimization horizon dates. The optimization job does not check for date overlaps regardless of when assignments take effect.

Overlapping Territories management
:   Territories can overlap geographically or share technicians.

Agent start location
:   When using the Territory Model, you can temporarily assign a technician a different start location with a specified start and end date. The system uses this temporary location when assigning tasks. When the end date passes or no
    temporary location is set, the technician's location reverts to their home location. During relocation, you can also adjust technician membership and availability attributes. For more information, see [Move agents between territories in the Territory Planning console](https://www.servicenow.com/docs/tXrfnEnu5WNeXYhdGHkATg "Relocate agents between territories to add flexibility to their work.").