---
sourceDocument: Australia Field Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/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


---

# Create a territory

# Create a Field Service territory {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Create territories for optimizing agent and group scheduling. By mapping these territories to the territory model, you can maintain a record of your territory setup, ensuring efficient management.

## Before you begin

You must set up a territory geography before you start creating a territory. For more information, see [Create a GeoJSON geography in Territory Planning console](https://www.servicenow.com/docs/I1zeIl34f6dRQXdbQrx5HQ#Draw-geography-on-console "Draw boundaries on the map to define your geographic areas and create GeoJSON geographies. These geographies not only give you a clear visual on the map but also used task scheduling.").

Role required: sn_fsm_tp.fsm_territory_planner, sn_fsm_tp.fsm_territory_manager

## About this task

Set up a territory geography before creating territories. A territory is defined by its geographic area, and you can organize multiple territories in a hierarchy. The highest-level territory serves as the parent territory,
covering geographic areas within it as child territories. For example, you can create a parent territory, California, and its child territories: San Francisco, Los Angeles, San Jose, and Santa Clara.

When creating a new territory, you have the option to copy an existing territory record with any modified values by selecting the Insert and Stay option.

## Procedure

1. Open either Territory Planning platform or Territory Planning console.
   * Navigate to AllField ServiceTerritory PlanningTerritoriesNew.
   * Navigate to AllField ServiceTerritory PlanningTerritory Planning ConsoleCreate Territory.
   {#create-territories-territory-planning-console__choices_m14_z5y_szb}
2. On the form, fill in the fields.  
   {#create-territories-territory-planning-console__table_nhd_jpr_stb__entry__2}

   | Fields | Description |
   |-|-|
   | Name | Name of the territory. |
   | Description | Description of the territory. |
   | Parent | Name of the parent location for the territory to create a territory hierarchy. If no parent territory is specified, this territory will serve as the highest-level (parent) territory. Note: Territory manager can only create child territories for their territories. |
   | Rank | Set a ranking rule to prioritize territories for task assignment (descending order). |
   | Color | Enter the hexadecimal code or color picker to select the color. This helps to highlight the territory on the map in the Territory Planning console. Note: This field becomes optional when the selected territory has been created using matching attributes geography and the selected territory is a non-assignment territory. |
   | Model | Name of the territory model to which to map this territory. This field is automatically set to the default Field_Service_Territories territory model. |
   | Assignment Territory | Select the check box to convert the territory into an assignment territory, allowing you to add assignment groups and field service agents to it. Note: An inactive assignment territory is not eligible for scheduling and does not appear in the Dispatcher Workspace. |
   | Aggregated agent schedule cut off | The number of days until which the agent schedule details are available, and the aggregated agent schedule is used for task assignments when capacity is defined by aggregated agent schedule. Beyond the cut-off days, the base defined capacity is utilized for capacity management and task assignments. Note: * This field is available only for assignment territory. * The Aggregated Agent Schedule doesn't apply on the day when capacity is defined (Day 0). It always applies from the following day (Day 1) after the capacity is defined until the cut-off day or date. {#create-territories-territory-planning-console__ul_h2g_2cf_zfc} |
   | Aggregated agent schedule cutoff date | The date until which the agent schedule details are available, and the aggregated agent schedule is used for task assignments when capacity is defined by aggregated agent schedule. Beyond the cut-off date, the base defined capacity is utilized for capacity management and task assignments. Note: * This field is available only for assignment territory. * If both aggregated agent schedule cut off days and date is specified, only the aggregated agent schedule cutoff date is considered for capacity allocation and task assignments. {#create-territories-territory-planning-console__ul_fqc_vgc_wfc} |
   | Geography | Add the name of the geographic area defined for this territory. Note: This field is optional for a non-assignment territory. |
   | Active | Indicate whether the territory is available for scheduling. Note: An inactive territory is not eligible for scheduling and does not appear in the Dispatcher Workspace. |
   [Table 1. Territory form]

   {#create-territories-territory-planning-console__table_nhd_jpr_stb}
3. Select Save.  
   The territory is created.

## Result

When accessing a territory record, the displayed related lists depend on whether it is categorized as assignment or non-assignment type. Non-assignment territories allow the addition of managers and child territories
exclusively. However, assignment territories permits to add managers, qualification groups, dispatch groups, assignment groups, agents, child territories, capacity assignment, and crews. These assignment territories are
specifically considered in the context of work order management.

## What to do next

[Configuring resources for territories](https://www.servicenow.com/docs/0wSzvIUTbnAYabUHswYqwQ "Configure resources for territories effortlessly by linking them to groups.")

*[\>]: and then