---
sourceDocument: Australia Field Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/field-service-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Field Service Management

ft:clusterId :

    - fsm

bundleId :

    - fsm

workflow :

    - Customer and Industry


---

# Create a scope

# Create a scope for Schedule Optimization {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Create a scope and associate a policy to the scope to define a configuration for the related batch, specifying the horizon offset start, horizon range and applicable qualifiers for each batch run.

## Vorbereitungen

Role required: wm_admin

## Warum und wann dieser Vorgang ausgeführt wird

Scopes link tasks to policies and can be based on assignment groups or geographical territories. A specific qualifier, such as a Territory or Assignment Group, must initiate optimization runs. Selecting the appropriate scope is crucial to ensure that your policies are applied to the right set of tasks, optimizing your resources where it counts.  
Hinweis:  
Utilize the 'Schedule Optimization' Application Scope for setting up and configuring these elements.  
Scopes associate a group of tasks with an existing optimization policy. Territorial planning can impact the task optimization process. Consider the following scenarios:

* Territory Planning plugin not installed: Task optimization relies solely on assignment groups.
* Territory Planning plugin installed but inactive: Scopes and batches can be created for both territories and assignment groups. Stick to assignment group-based scopes until Territory Planning is activated. You can create scopes and batches for both assignment groups and territories. However, you should activate batches associated with territories only when the Territory Planning plugin is activated.
* Territory Planning plugin installed and active: Tasks are optimized exclusively based on territories. Scopes for assignment groups are no longer possible.

{#create-an-optimization-job-soe__ul_v4w_5qj_p1c}  
Hinweis:  
Once you activate the territory model, you can't revert to assignment groups. Agents must be unique to each group or territory.

## Prozedur

1. Navigate to AllSchedule OptimizationScopes.
2. Select New.
3. Provide a name in the Name field.
4. Select a scheduling attribute configuration in the Scheduling attribute field.
5. **Wahlweise:** Set the Assignment horizon offset to specify the delay after the batch run before task assignments begin.  
   Hinweis:  
   The assignment horizon offset determines the window start value on the work order task record.
6. Set the Assignment horizon range to determine the span of time during which the tasks are assigned to the agents.
7. **Wahlweise:** Determine the priority of the scope when agents or tasks that are shared between scopes are being assigned by entering a priority in the Rank field.  
   Lower numbers indicate a higher priority.
8. Select Submit.
9. In the Qualifiers related list, add assignment groups or territories to the scope.  
   Hinweis:  
   To optimize by territory, the territory model must be activated. For more information, see [Enable the Field Service territory model](https://servicenow-prod.fluidtopics.net/vJ69bDjuIApLeyMJ8GrQWw "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."). After you switch to the territory model, you can't go back and create scopes for assignment groups. The transition to territories is permanent. Each assignment group and territory must have a unique set of agents. An agent can't be assigned to multiple assignment groups.
10. Select Submit.  
    A Schedule Optimization scope is created.