---
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


---

# Embedded breaks and lunches

# Embedded breaks and lunches {#ariaid-title1}

Release version: Australia  
Updated September 30, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Embedded breaks and lunches

Embedded breaks and lunches enable technicians to take scheduled breaks directly within a work order task without leaving the task.
This integration pauses the task during the break and adjusts the task's estimated end time accordingly.
The feature helps maintain accurate scheduling and break tracking for both technicians and managers.
Show full answer Show less  

## How Embedded Breaks and Lunches Work

* Break status updates depend on the **Auto-status breaks** setting:
  * If enabled, breaks automatically transition to taken at the scheduled start and completed at the scheduled end without technician action.
  * If disabled, technicians must manually mark breaks as taken.
* Work order tasks pause during breaks and resume afterward, with adjusted end times.
* Each break is logged in the work order task's Work Notes for visibility and record-keeping.
* Breaks cannot overlap; each must have a distinct time window.
* Tasks scheduled over planned breaks automatically embed those breaks if the break starts during the task and after the task start time.
* Lunch breaks are visually indicated by a fork and knife icon on the calendar.
* If multiple breaks occur during a task, a fractional indicator shows how many breaks were taken versus scheduled; missed breaks are marked with an "X."
* The work order task form includes a read-only "Break Embedded" checkbox that updates dynamically.

## Configuration Options for Administrators

* Enable or disable embedded breaks globally using `snfsmshiftschdl.enableembedbreakinwot`.
* Control automatic break status updates with `snfsmshiftschdl.wfo.break.autostatus`.
* Set reminder notification timing before breaks via `snfsmshiftschdl.wfo.break.reminderminutes` (default is 15 minutes).
* Allow technicians to end breaks early from the mobile app when auto-status is off using `snfsmshiftschdl.wfo.break.endearlyenabled`.
* Configure flexible break start times with buffers around break windows via `snfsmshiftschdl.breakbufferenabled` and `snfsmshiftschdl.breakbufferminutes`, with per-technician overrides available in Resource Schedule Attributes.

## Schedule-Locked Tasks Considerations

Tasks marked as schedule-locked have fixed start and end times and do not allow embedded breaks to be added or removed. This ensures task timing remains consistent without adjustments for breaks.

## Practical Benefits for ServiceNow Customers

* Streamlines technician workflows by embedding breaks directly within tasks, reducing task interruptions.
* Provides accurate tracking of break times for compliance and performance management.
* Automatically adjusts task timing to reflect real-time availability changes due to breaks.
* Offers administrative flexibility to tailor break handling and notifications to organizational policies.
* Improves dispatch and scheduling accuracy by reflecting technicians' real-time break statuses and availability.  
A break or lunch can be embedded directly within a work order task, so a technician doesn't have to leave the task to take scheduled time away.

## How embedded breaks and lunches work {#embedded-breaks-and-lunches__section_how_embedded_breaks_and_lunches_work}

Whether a break's status updates automatically depends on the Auto-status breaks setting. When it's on, a break automatically transitions to taken at its scheduled start time and to completed at its scheduled end time, without technician action. When it's off, the technician manually takes the break. Either way, the work order task pauses while the break is in progress and resumes once the break is complete. The task's estimated end time adjusts to account for the time away. Each break is recorded
in the Work Notes of the work order task, so managers and technicians have a record of when breaks were taken. Breaks on a work order task can't overlap; each break must have a distinct time window.

Scheduling a work order task over an agent's planned break automatically adjusts the task to accommodate the break, embedding it into the task as long as the break starts at or after the task start time and falls within the task duration. A break that has already started is not embedded. Lunch breaks are indicated on the calendar with a fork and knife icon. If more than one break is scheduled during a task, a fraction on the break indicator shows the number of breaks taken versus scheduled (for example, 1/2). Technicians must mark their breaks as taken; if a technician misses a scheduled break, an X shows on the break indicator.

The work order task form shows a Break Embedded checkbox that indicates whether the task currently has an embedded break. This field is read-only and updates automatically as breaks are added or removed.

## Embedded break configurations {#embedded-breaks-and-lunches__section_embedded_break_configurations}

Administrators have the option to further configure embedded breaks. They can turn off automatic breaks so technicians take breaks manually instead. They can also change how many minutes before a break's start time the reminder notification is sent, instead of the default 15 minutes. They can also let technicians end a break early from the mobile agent app instead of waiting for it to end automatically. They can also configure a buffer around each break's window, giving a technician flexibility to start a break early or late without falling outside the allowed range.

* `sn_fsm_shift_schdl.enable_embed_break_in_wot` --- Enables or disables break embedding within work order tasks globally.
* `sn_fsm_shift_schdl.wfo.break.auto_status` --- When enabled, a break's status updates automatically once its scheduled end time passes, so technicians don't have to manually mark the break as taken.
* `sn_fsm_shift_schdl.wfo.break.reminder_minutes` --- Sets how many minutes before a break's scheduled start time the system sends a reminder.
* `sn_fsm_shift_schdl.wfo.break.end_early_enabled` --- When enabled (and Auto-status breaks is off), technicians can end a break early from the mobile agent app instead of waiting for it to end automatically. If Auto-status breaks is on, this property is ignored.
* `sn_fsm_shift_schdl.break_buffer_enabled` --- Enables or disables a pre/post buffer around break windows, letting a break start outside the scheduled window within the buffered range.
* `sn_fsm_shift_schdl.break_buffer_minutes` --- Sets the global fallback buffer, in minutes, applied on each side of a break window when a technician has no buffer value set on their own Resource Schedule Attribute record.
{#embedded-breaks-and-lunches__ul_rpv_1jk_jkc}

You can also set the buffer for an individual technician using the Pre-break buffer and Post-break buffer fields on their Resource Schedule Attributes record. These values override the global buffer set in
sn_fsm_shift_schdl.break_buffer_minutes.

For details, see [Properties installed with Field Service Management](https://www.servicenow.com/docs/1mMQLHdGZixdKQ6Y4MxeQw "System properties provided with the Field Service Management application.").

## Schedule-locked tasks {#embedded-breaks-and-lunches__section_schedule_locked_tasks}

A schedule-locked work order task has a fixed start and end time that can't shift to accommodate a break. As a result, you can't add a break to a task that's schedule locked. You also can't delete a break that's already embedded in a task once it's locked.

## Related tasks {#embedded-breaks-and-lunches__section_related_tasks_embedded_breaks_and_lunches}

* [Add a break to a shift](https://www.servicenow.com/docs/OEEoE4CsWN8tnns7YhTRCQ "Add a break to a shift to give technicians scheduled rest time within their shift, without leaving the schedule view.")

  Schedule a break for a technician so their availability reflects real-time off during a shift.
* [Edit or delete a break](https://www.servicenow.com/docs/cBdgzNaXmf15GleBr8tXsw "Edit or delete a break to keep a shift's schedule accurate as break needs change, without recreating the shift.")

  Adjust a break's timing or remove it entirely when a technician's schedule changes.
* [Check a break in Dispatcher Workspace](https://www.servicenow.com/docs/UToB8KQxcxfqGrQqby6L4Q "Check whether a break on a work order task has been taken or is still planned, without leaving Dispatcher Workspace.")

  See whether a technician's break is planned or already taken before you assign or reschedule work.
* [Check on a break](https://www.servicenow.com/docs/nAD3mN7wF6QalDHO5fMYpA "Check on a scheduled or upcoming break in the ServiceNow Agent application to see whether it's still planned or has already been taken.")

  Confirm your own break status from the field so you know when you're expected back on task.
* [Take a break manually in the mobile agent app](https://www.servicenow.com/docs/deweQmnz0hXy3PdOvzizhQ "Manually record a break in the ServiceNow Agent application when your organization's Auto-status breaks setting is off.")

  Manually record a break when Auto-status breaks is turned off.
{#embedded-breaks-and-lunches__ul_related_tasks_embedded_breaks_and_lunches}