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


---

# Manage work orders

# Manage work orders {#ariaid-title1}

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

Work orders are requests for off-site work. Users with the appropriate roles create the work orders and provide the necessary information needed for the work order tasks. Then other users qualify those work
orders and create the tasks necessary to complete the work order.

## Creating work orders {#c_ManageWorkOrders__CreatingWorkOrders}

If you have the wm_initiator or wm_initiator_qualifier role, you can create work orders. You can create entirely new work orders, or you can create a work order from another record.

Work orders can be created from these other record types: case, incident, change, problem, or project task. They can also be created from another existing work order. For each record, you can create only one work order.

Work orders created from another existing work order

:   If the scope of an existing work order changes during the execution phase, you can create another work order from it. Analyze whether the scope change can be managed by adding additional tasks instead of creating
    another work order.

    When you create a work order from an existing work order, the following information is copied from the original work order:

    * Work order record reference (in the Initiated from field)
    * Affected CI
    * Caller
    * Location
    * Priority
    * Short description
    * Description

    {#c_ManageWorkOrders__ul_kps_15k_2r}

    Because some information is copied from the original record, an existing work order can be used as a template to create new work orders.

Work orders created from an incident, problem, change, or project task record

:   If an incident, problem, change record, or project task must be assigned to an off-site agent and tracked, you can create a work order from it. Some information from the original record is copied automatically into the
    new work order.

    {#c_ManageWorkOrders__table_b5b_2nk_2r__entry__2}

    | Record type | Fields copied to the work order |
    |-|-|
    | Incident | * Incident record reference (in the Initiated from field) * Caller * Location * Priority * Short description * Description {#c_ManageWorkOrders__ul_f1y_fnk_2r} For more information, see [Integration with Incident Management](https://servicenow-prod.fluidtopics.net/9fEmGNZwOZ6IIoTHTD2Jpw "With ServiceNow Incident Management for Field Service, create work orders from an incident record and also track the progress of the work order directly in the incident record when a state change occurs or a work note is added to the work order."). |
    | Case | * Account * Contact * Affected CI * Location * Asset {#c_ManageWorkOrders__ul_z4k_lwp_kwb}For more information about creating a work order from the case, see [Work orders in CSM Agent Workspace](https://servicenow.com/docs/bundle/vancouver-field-service-management/page/product/field-service-management/concept/field-service-workspace.html). |
    | Problem | * Problem record reference (in the Initiated from field) * Affected CI * Priority * Short description * Description {#c_ManageWorkOrders__ul_ltl_gnk_2r} |
    | Change | * Change record reference (in the Initiated from field) * Affected CI * Priority * Short description * Description {#c_ManageWorkOrders__ul_vjq_tgz_lr} For more information, see [Integration with Change Management](https://servicenow-prod.fluidtopics.net/Vt2rQGIqtBvdOf4e5ogVQQ "With ServiceNow Change Management for Field Service, create work orders from a change request and also track the progress of the work order directly in the change record when a state change occurs or a work note is added to the work order."). |
    | Project task Hinweis: Before work orders can be created from project tasks, Field Service Management must be integrated with Project Portfolio Management | * Short Description * Location {#c_ManageWorkOrders__ul_wlc_bxs_w1b} These work order fields are synchronized with the project task * State * Scheduled start * Estimated end {#c_ManageWorkOrders__ul_mdv_yxs_w1b} For more information about the synchronized fields, see [Integration with Project Portfolio Management](https://servicenow-prod.fluidtopics.net/McJ1xrLdqn29UeLPoumtsw "Link project tasks to work orders to assist with managing installation or deployment projects in the field."). |
    [ ]

    {#c_ManageWorkOrders__table_b5b_2nk_2r}

    Work orders can be filtered based on different attributes, such as qualification group, location, initiated from, priority, state, and so on. This help to create a group of similar work orders.

