--- 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 --- # Batches and scopes # Batches and scopes {#ariaid-title1} Release version: Australia Updated September 29, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Batches and scopes Batches and scopes in Schedule Optimization work together to control the timing of optimization runs and the specific technicians and tasks considered during those runs. A batch governs when and how often Schedule Optimization executes, while a scope determines the subset of scheduling attributes and resources optimized in each run. Batches rely on scopes to perform optimizations, and a single batch can include multiple scopes. Show full answer Show less ## Batch Configuration * Batches define optimization start date, time window (start and end), and frequency of execution. * You can schedule up to 36 batches within a 24-hour period, with each batch lasting at least two hours. * A maximum of three batches can overlap at any time. * Scheduling options for batches include one-time runs, every day, or intervals of 7, 30, 60, 90, 120, or 180 days. * The "Schedule now" feature lets you run a batch immediately without affecting its regular schedule. * Schedule Optimization only applies technician or task record changes in the run following those changes; it does not detect them mid-run. ## Scope Configuration * Scopes define scheduling attributes such as assignment horizon offset and range, rank, and qualifiers. * The scope start time is relative to the batch start time, enabling optimization on specific days or time frames. * **Assignment horizon offset** sets the delay before task assignments begin relative to the batch run. * **Assignment horizon range** defines the time span during which tasks are assigned to technicians. * **Rank** determines priority when multiple scopes share tasks; lower rank means higher priority. * **Qualifiers** specify which assignment groups or territories the scope optimizes. ## Qualifiers * Assignment group qualifiers require unique technicians per group; a technician cannot belong to multiple groups. * Territory qualifiers allow technicians to belong to multiple territories; overlapping territories are optimized together. * With the Territory Planning plugin and active Territory Model, qualifiers default to territories, disabling assignment group scopes. ## Practical Considerations for ServiceNow Customers * Reuse scopes by copying their configurations into batches to avoid unintended changes to original scopes. * When using the same scope in multiple batches, schedule batch runs to avoid overlap for optimal performance. * Configure batches and scopes thoughtfully to match your organization's operational hours and task assignment needs. * Leverage the rank setting to prioritize scopes when tasks span multiple scopes. * Understand how qualifiers impact technician-task assignment based on organizational structure (assignment groups vs. territories). Learn how batches and scopes work together to control when Schedule Optimization runs and which technicians and tasks it considers. ## How batches and scopes work together {#batches-and-scopes__batches-and-scopes-how-work-together} A batch controls when and how often Schedule Optimization runs. A scope controls what each run optimizes. Batch optimization requires scopes to run. A batch can include multiple scopes. You can create a scope or reuse an existing one. Reusing a scope creates a copy of it, including all configuration records, and links the copy to the batch. Changes to the copy don't affect the original scope. When you reuse a scope in more than one batch, schedule the batches so their run times don't overlap. You can schedule batches that use the same scope on different days or back to back. ## Batch configuration {#batches-and-scopes__section_d44_j1z_skc} A batch configuration defines the optimization start date, the start and end time, and the run frequency. You can configure up to 36 batches in a 24-hour period. Each batch must last at least two hours, and no more than three batches can overlap. For example: * Batch 1: midnight to 02:00 * Batch 2: 01:00 to 03:00 * Batch 3: 02:00 to 04:00 {#batches-and-scopes__ul_nkh_51z_skc} Optimization runs on a continuous or fixed schedule. The default is every seven days. You can also run a batch one time, every day, or every 30, 60, 90, 120, or 180 days. Schedule now runs a batch independently of its regular schedule. It doesn't change or delay the next scheduled run. Schedule Optimization doesn't detect changes to technicians or tasks records during a run. Schedule Optimization applies those changes in the next run. ## Scope configuration {#batches-and-scopes__section_wfr_cbz_skc} A scope defines the scheduling attribute configuration, assignment horizon offset, assignment horizon range, rank, and qualifiers. The scope start time is relative to the batch start time. If the batch starts today and the scope start time is tomorrow, optimization focuses on the technicians and tasks for the next day. A scope also includes: * Assignment horizon offset: The delay between the batch run and the start of task assignments. This value determines the window start value on the work order task. * Assignment horizon range: The span of time during which tasks are assigned to technicians. * Rank: The scope priority when scopes share tasks. Lower numbers indicate a higher priority. * Qualifiers: The assignment groups or territories that the scope optimizes. {#batches-and-scopes__ul_xvf_ncz_skc} ## Qualifiers {#batches-and-scopes__section_syn_gdz_skc} Qualifiers define which assignment groups or territories a scope optimizes. * Assignment group qualifiers: Each assignment group must have a unique set of technicians. A technician can't belong to more than one assignment group. * Territory qualifiers: A technician can belong to more than one territory. When territories share technicians or tasks, optimization treats them as one group and optimizes them together. {#batches-and-scopes__ul_igm_pdz_skc}When the Territory Planning plugin is installed and the Territory Model is active, qualifiers are set to territories automatically, and you can't create scopes for assignment groups. For more information, see [Territory-Based Optimization](https://www.servicenow.com/docs/kykUcMEjI4g98yADfT9QDA "Enable the Field Service Territory model to focus optimization on territories rather than assignment groups."). **Related tasks** * [Create a scope for Schedule Optimization](https://www.servicenow.com/docs/qzPZmZHPUVYJzJ5XCR48qA "A scope defines the scheduling attribute configuration, horizon offset, horizon range, and qualifiers for an optimization run. Scopes are required for batch optimization to run.") * [Create a batch for Schedule Optimization](https://www.servicenow.com/docs/ubqPHkHjYeJK7_ZgYHekgw#create-an-optimization-batch "Create an optimization batch to determine the interval at which optimization should run. Set the start date, batch start time and end time, and run frequency for the related scope.") * [Add or remove scopes from an optimization batch](https://www.servicenow.com/docs/BkIyxMO6mUHNkhSmSdIV2w "Add scopes to optimization batches or remove a scope from a batch if the number of scopes in a batch becomes too large to manage.")