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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Field Service Management

ft:clusterId :

    - fsm

bundleId :

    - fsm

workflow :

    - Customer and Industry


---

# Create a batch

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

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Create an optimization batch to determine the interval at which Schedule Optimization should run. Set the start date, batch start time and end time, and run frequency for the related scope.

## Before you begin

[Configure the policy](https://www.servicenow.com/docs/iBbM5M8dZrF9Mgh5Tr6ozQ "Create policies to promote factors like the travel time and an agent's availability. Policies determine how to optimize an agent’s schedule based on defined objectives or constraints.") and [Scheduling attribute configuration](https://www.servicenow.com/docs/HXbBty8Ld4XVRftu9CjK_A "Create scheduling attributes to specify which tasks to optimize and define the rules to perform the optimization. You can create different scheduling attributes configurations for each policy.").  
Verify that your agent work schedules are set up correctly:

* Work schedule structure: Set up a repeating schedule for each technician, such as a weekly or monthly pattern. Individual day exceptions can override this base schedule. Schedules with single, individual day entries won't work for optimization.
* Agent availability: Verify technicians are marked as Free in their schedules for the time periods covered by the batch. Technicians marked as Busy will not receive task assignments.
{#create-an-optimization-batch__ul_o22_dfz_skc}

Role required: wm_admin

## About this task

For information about batch limits, run frequency, and how batches and scopes work together, see [Schedule Optimization batches and scopes](https://www.servicenow.com/docs/FHN0eFwqRY9apTQqaRSuZw "Learn how batches and scopes work together to control when Schedule Optimization runs and which technicians and tasks it considers.").

## Procedure

1. Navigate to AllSchedule OptimizationBatch OptimizationBatches.
2. Select New.
3. Enter a name in the Name field.
4. Set the start date, batch start time, and end time in the relevant fields.  
   Note:  
   When you activate a batch with a start date in the past, it creates two scheduled jobs: One to run immediately and another to run in the future. When you activate a batch with a future start date, the batch runs at the specified time. To avoid immediate processing, set the batch start date to a future date when you plan to activate the batch.
5. Determine how often a batch runs, and select a value for Run Frequency.
6. Select Save.
7. Add scopes to the batch.  
   * To create a scope: Complete steps from 8 through 11.
   * To reuse an existing scope: In the Optimization Scopes tab, select Edit to select an existing scope. When you reuse a scope, the system duplicates the selected scope, including all configuration records, and links the duplicate to the batch.
   {#create-an-optimization-batch__ul_j3b_pmx_g3c}
8. To optimize tasks by assignment groups or territories, select New in the Optimization Scopes field.
9. Enter a name in the Name field.
10. Select a scheduling attribute configuration in the Scheduling attribute field.
11. Set the Assignment horizon range to determine the span of time during which the tasks are assigned to the agents.
12. Select Activate.
13. **Optional:** Select Schedule now to run the batch immediately without affecting the regular scheduled trigger time.  
    The Schedule now action runs the batch independently of its regular schedule. Using Schedule now doesn't change or delay the next scheduled optimization run.

## Result

At each defined interval, the batch triggers the Schedule Optimization process. Work order tasks are automatically assigned to the most suitable technician, and the Assigned To field is updated accordingly. To verify the next scheduled trigger time, see [KB2142495](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2142495).  
Note:  
Schedule Optimization doesn't detect changes you make to agents or tasks during an optimization run. It considers changes to technicians and tasks during the next optimization run.

You can [View Schedule Optimization logs](https://www.servicenow.com/docs/vywZS~kCrtINSUcvB1M~Ug#view-schedule-optimization-logs "View the Schedule Optimization logs to gather insights from each optimization attempt.") to gather insights from each optimization attempt. To understand how tasks were processed and assigned during Schedule Optimization runs, see [Run summaries overview](https://www.servicenow.com/docs/qON2osEY1dHoSRCfGqUsTw "View the results of Schedule Optimization runs to understand how tasks were processed and assigned.").
**Related concepts**   

* [Batches and scopes](https://www.servicenow.com/docs/FHN0eFwqRY9apTQqaRSuZw "Learn how batches and scopes work together to control when Schedule Optimization runs and which technicians and tasks it considers.")  
**Related tasks**   

* [Create a scope for Schedule Optimization](https://www.servicenow.com/docs/k0tshckFlR4sv4v12fQlJw "Create a scope to define which technicians and tasks a Schedule Optimization batch includes.")
* [Add or remove scopes from an optimization batch](https://www.servicenow.com/docs/WfCmyelqOIEq~WPNWCe9ZQ "Add a scope to a batch to include it in optimization runs, or remove a scope to reduce the number of scopes the batch contains.")

*[\>]: and then