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


---

# Optimization for prioritized events

# Optimizing technician schedules in response to urgent events {#ariaid-title1}

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

Prioritized event optimization is a mode of intraday optimization that aims to run a faster, more focused intraday process. This mode specifically targets the most critical events.

## About intraday optimization for prioritized events {#triggering-optimization-on-task-or-agent-availability-change__section_xdz_pnn_tfc}

Prioritized event optimization enables same-day, event-driven schedule adjustments that run shortly after a prioritized event occurs. This mode targets a specific group of Field Service technicians and tasks without adjusting the entire qualifier.

The buffer window property determines how many minutes the system waits to collect additional priority events before running optimization. For example, with a one-minute buffer, the system waits one minute after detecting a
priority event to capture any other events before starting optimization.

## Technician selection {#triggering-optimization-on-task-or-agent-availability-change__section_ymc_v4j_xhc}

The optimization engine considers technicians directly affected by events, such as those running late or early. The system also considers technicians already assigned to affected tasks. Unlike default intraday optimization, the engine ignores overlapping territories and only includes territories directly impacted by the events.  
Hinweis:  
Task filters configured in the scheduling attribute configuration don't apply to prioritized intraday optimization.

## Task Selection {#triggering-optimization-on-task-or-agent-availability-change__section_hkm_y4j_xhc}

The optimization engine considers technicians directly affected by events, such as those running late or early. When a task-related event occurs, the system also considers technicians already assigned to affected tasks.

When only task-related events occur without technician events, the engine includes only existing task assignees. If no assignees exist, no technicians are considered.

Prioritized event optimization focuses on territories directly impacted by the events and doesn't include overlapping territories.

To set up intraday optimization for prioritized events, see [Configure optimization for prioritized events](https://servicenow-prod.fluidtopics.net/43tWaBXk_giVgVqfc91mCQ "Configure prioritized event optimization to enable schedule adjustments in response to critical, same-day events.").

## Optimization with matching rules {#triggering-optimization-on-task-or-agent-availability-change__section_h22_2pj_xhc}

You can apply matching rules to prioritized event optimization for improved control over job assignments. Matching rules are only available when [Territory-Based Optimization](https://servicenow-prod.fluidtopics.net/hbEVZ5vdMrz8S2uFaia6XA "Enable the Field Service Territory model to focus the optimization process on territories rather than assignment groups.") is enabled. [Territory-Based Optimization](https://servicenow-prod.fluidtopics.net/hbEVZ5vdMrz8S2uFaia6XA "Enable the Field Service Territory model to focus the optimization process on territories rather than assignment groups.") can't be used with configurations that use assignment groups.

If you installed the Field Service Management Demo Data plugin, two example matching rules are available: Filter technicians for prioritized events and Filter tasks for prioritized events. These rules include criteria for affected technicians
and affected tasks. You can use these example rules or create your own matching rules to identify subsets of tasks and technicians based on your defined criteria.

Matching rules identify a subset of relevant tasks and technicians to optimize based on criteria such as search radius, required skills, and time thresholds. For example, matching rules can limit
optimization to tasks and technicians within a 10-mile radius of a new high-priority task.

When matching rules are configured, they determine which tasks and technicians are directly impacted by a prioritized event. For example, when a technician calls in sick, matching rules identify all technicians with the same
certifications as directly impacted, enabling the system to reassign that technician's tasks efficiently. Matching rules also limit optimization to tasks and technicians within a specific radius of a new high-priority task.

When a prioritized event occurs and creates a task event, the system generates a prioritized job. If matching rules are configured for intraday events, the optimization engine applies those rules to filter the assignment options
before making recommendations.

To configure matching rules for intraday events, access the Intraday Event Type table from the Matching Rules table field. For more information about matching rules, see [Set up prioritized intraday optimization with matching rules](https://servicenow-prod.fluidtopics.net/uUz0DuHyPZWqPfgOsfBaww "Configure prioritized intraday optimization to use matching rules that narrow job assignment decisions. Matching rules deliver focused, efficient job recommendations.").  
Hinweis:  
Note: If you have custom event types and flows for intraday optimization, migrate them to the Intraday Event Type table. Update your flows to populate the event type field with table references instead of drop-down values.
**Zugehörige Verweise**   

* [Schedule Optimization properties](https://servicenow-prod.fluidtopics.net/nOe0OO1Ywabsvcm4I0Euwg "You can set parameters that control how optimization runs.")