---
schema_version: "1"
id: a0a4ef04a0858611134698b7973bdd3db078107a37830962f686e49400ff9e3a
title: Configure Optimization for Field Work in Workforce Scheduling
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/wfs_config_scheduling_field_opt.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.wfs_config_scheduling_field_opt.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a9c4e89007da9ed5e257e9a918fe0e16f83c15875d1b97345e4ee913ead435f4
description: Configure org-level defaults for field-work optimization, including pin criteria and commit mode for global, in-day, and resource schedule optimization runs. Optimization is relevant to field appointments only.
products:
  - Public Sector
  - Service Cloud
release: "264"
---
# Configure Optimization for Field Work in Workforce Scheduling

Configure org-level defaults for field-work optimization, including pin criteria and commit mode for global, in-day, and resource schedule optimization runs. Optimization is relevant to field appointments only.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong> and <strong>Unlimited</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d10689e67">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d10689e67 ">To configure optimization:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d10689e67 ">Workforce Scheduling Admin</td>

          </tr>
        </tbody>
      </table>

Configure the org-level defaults from **Scheduling and Optimization** in Setup, on the **Field Scheduling** tab.

## Set Pin Criteria for Optimization

Pin criteria lock the start time of appointments in specific statuses so the optimization engine leaves them in place. Use pin criteria to protect appointments that are already dispatched, in progress, or committed to a customer.

1. From Setup, in the Quick Find box, enter Workforce Scheduling, and then select **Scheduling and Optimization**.
2. Select the **Field Scheduling** tab.
3. Under Optimization, select the **Pin Criteria** for each optimization type. Pin criteria determine which appointment statuses stay locked during an optimization run, for example, **Dispatched**, **In Progress**, or **Completed**.
4. Save your changes.

Considerations:

- Appointments in unselected statuses are candidates for the optimization engine to move, within the limits of your scheduling policies, work rules, and service objectives.
- Pin criteria set here apply to optimization runs only. To pin appointments during scheduling actions, see [Pin Appointments by Status](https://help.salesforce.com/s/articleView?id=service.wfs_config_scheduling_field_behavior.htm&release=264.0.0&type=5 "Pinned Service Appointments can’t be rescheduled by the Schedule action, the scheduling flow, or the Schedule and Appointment Booking APIs. Use pin criteria to protect appointments that are in flight or already committed to a customer.").

## Choose a Commit Mode

Commit mode controls what happens when a user changes the schedule while an optimization run is in progress. Workforce Scheduling watches for conflicts across the optimized date range and one buffer day on each side. A conflicting change is any of these: creating or deleting a Service Appointment, creating or deleting a Resource Absence, or updating a Service Appointment’s Assigned Resource, Scheduled Start, or Scheduled End.

Each optimization type has its own org-wide default Commit Mode:

- Global Optimization defaults to Always Commit, because global runs are typically overnight when concurrent changes are rare and partial improvements are usually preferable to no change.
- In-Day Optimization defaults to Rollback, because in-day runs happen during the working day when concurrent changes are likely, and rolling back protects the schedule from conflicts.
- Resource Schedule Optimization (RSO) defaults to Rollback, because RSO covers a single resource’s day and rolling back on any concurrent change keeps the resource’s schedule consistent.

1. From Setup, in the Quick Find box, enter Workforce Scheduling, and then select **Scheduling and Optimization**.
2. Select the **Field Scheduling** tab.
3. Under Optimization, select the **Commit Mode** for each optimization type according to the [guidelines](https://help.salesforce.com/s/articleView?id=service.wfs_config_scheduling_field_commit_guide.htm&release=264.0.0&type=5 "Learn what happens when a dispatcher or scheduling operation makes a change to the schedule that conflicts with an ongoing optimization process, and how the system behaves depending on the selected Commit Mode."):
    - **Rollback**: If a potentially conflicting change occurs during the run, the optimization rolls back and the schedule stays unchanged. Rollback is the conservative choice: it protects the schedule from conflicts at the cost of losing the run’s improvements.
    - **Always Commit**: Optimization results commit even when concurrent changes occur. The schedule updates per the optimization results, though the change can create overlaps or scheduling discrepancies that need manual reconciliation.
4. Save your changes.

Considerations:

- Commit Mode applies to Global, In-Day, and Resource Schedule Optimization runs only. It doesn’t affect scheduling-flow or manual scheduling actions.
- Rollback protects the schedule at the cost of losing an optimization run’s improvements when a conflict occurs. Expect more frequent rollbacks in orgs where the schedule changes often during optimization windows.
- Always Commit favors improvement over consistency and can leave the schedule with overlaps that need manual reconciliation.

#### See Also

- [What’s Workforce Scheduling Optimization?](https://help.salesforce.com/s/articleView?id=service.wfs_optimize_what_is_opt.htm&release=264.0.0&type=5 "Workforce Scheduling optimization automatically generates the ideal schedule by applying your scheduling policy and appointment priorities. Optimization is relevant to field work only.")
- [Optimize Your Schedule in Workforce Scheduling](https://help.salesforce.com/s/articleView?id=service.wfs_optimize.htm&release=264.0.0&type=5 "Schedule optimization creates the best possible plan for your service resources by balancing service-level agreements according to your organization’s business needs, for example, travel time, overtime, and cost. Workforce Scheduling runs optimization across your entire schedule, on the current day of service, or for a single resource. Optimization is relevant to field work only.")
- [How Does Workforce Scheduling Optimization Work?](https://help.salesforce.com/s/articleView?id=service.wfs_optimize_how_it_works.htm&release=264.0.0&type=5 "Workforce Scheduling optimization scores candidate schedules against your scheduling policy and appointment priorities, then applies the highest-scoring result. Optimization is relevant to field work only.")
- [In-Day and Global Optimization for Workforce Scheduling](https://help.salesforce.com/s/articleView?id=service.wfs_optimize_inday_global.htm&release=264.0.0&type=5 "Use In-Day Optimization to recover from same-day disruptions — such as last-minute schedule changes — by optimizing the team’s schedule across one or more service territories. Use Global Optimization to reoptimize the schedule across one or more service territories over a longer date range. In-Day and Global Optimization are relevant to field work only.")
- [Resource Schedule Optimization for Workforce Scheduling](https://help.salesforce.com/s/articleView?id=service.wfs_optimize_rso.htm&release=264.0.0&type=5 "In Workforce Scheduling, use Resource Schedule Optimization (RSO) to reoptimize a single service resource’s schedule when a last-minute disruption occurs. RSO reshapes a single resource’s day due to a shift change, a cancellation, or an unexpected block of unavailability — without affecting the rest of the team. RSO is relevant to field work only.")
- [Guidelines for Using Workforce Scheduling Commit Mode](https://help.salesforce.com/s/articleView?id=service.wfs_config_scheduling_field_commit_guide.htm&release=264.0.0&type=5 "Learn what happens when a dispatcher or scheduling operation makes a change to the schedule that conflicts with an ongoing optimization process, and how the system behaves depending on the selected Commit Mode.")
- [Configure Scheduling Behavior for Field Work in Workforce Scheduling](https://help.salesforce.com/s/articleView?id=service.wfs_config_scheduling_field_behavior.htm&release=264.0.0&type=5 "Configure org-level defaults for how Workforce Scheduling schedules field appointments, such as due dates, status transitions, sliding, pinning, and travel time.")