Setting up work orders and tasks

  • Release version: Zurich
  • Updated July 31, 2025
  • 4 minutes to read
  • Summarize
    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 Setting up work orders and tasks

    Work orders in Field Service Management (FSM) represent the work requests assigned to Field Service agents, containing key information such as customer details, locations, and configuration items. Work order tasks break down these requests into manageable activities, allowing detailed tracking and assignment. Setting up work orders and tasks enables structured, task-driven workflows that help agents efficiently complete their work.

    Show full answer Show less

    Configuring Work Orders and Tasks

    Configure FSM to use a task-driven process where each work order automatically generates associated task records. Work orders define the scope of work, while tasks specify the detailed actions, required skills, and parts. Task categorization ensures consistency by assigning similar tasks to designated groups and optionally requiring completion of questionnaires, such as safety checklists. Tasks also support automatic time tracking for labor management.

    Optional Configurations

    • Field Service Work Configurations: Customize task information to fit different workflows like maintenance or break-fix, capturing relevant cost and duration details.
    • Planned Work Management: Manage recurring activities such as maintenance schedules and inspections by installing the Planned Work Management application.
    • Auto-population of Access Hours: Define default access hours based on customer preferences to ensure tasks are scheduled when locations are accessible.
    • Linear Assets Support: Enable management of linear assets (e.g., roads, cables) via the Enterprise Asset Management plugin.
    • Playbooks: Guide agents through detailed workflows for specific task types, ensuring consistent task lifecycle management.
    • Customer Experience: Provide customers with real-time updates and agent tracking by activating the Customer Experience plugin.
    • Request Task Management: Split complex requests into multiple tasks to assign parts to different people or times.
    • Quality Management: Add reviewers to provide feedback on tasks by installing the Quality Management plugin.

    Access and Security Considerations

    FSM access is role-driven, with the wmagent role allowing agents to update and manage tasks flexibly. For stricter control, administrators can enforce access control rules, query filtering, and UI-level restrictions. To isolate sensitive data or separate departmental information, domain separation is recommended, providing strong data isolation and controlled sharing.

    When work is required, create a work order to provide information for the Field Service agents to fulfill the request. Create work order tasks to break down the tasks required to complete the work order.

    You can use Field Service Management and only set up work orders and work order tasks to start work. Or you can set up additional configurations to automate some of the process around creating and managing work orders and work order tasks.

    Configuration overview

    The steps for setting up work orders and tasks are:

    1. Configuring work orders

      Configure Field Service Management to use a task-driven process, wherein each work order encapsulates a list of essential tasks. Upon the creation of a work order, a corresponding task record is instantly generated. Task-driven processing can provide structure and clarity for intricate projects.

      Work orders in Field Service Management store information about requested work, including customer names and addresses, locations where work is to be performed, and any associated configuration items. Work orders can include one or more tasks that contain specific details about the work to be performed, such as required agent skills or part requirements. Work orders are the driving force behind Field Service Management. They define what Field Service agents must do to complete their jobs.

    2. Configuring work order tasks

      Categorize work orders are comprised of at least one, but usually multiple, work order tasks. You can categorize work order tasks by type so that work order tasks of the same type are consistent, like if a certain type of task always requires a specific assignment group. Additionally, you can require agents to complete questionnaires before, during, or after completing a task. For example, if you want agents to complete a safety checklist before starting a task, you can use questionnaires. Work order tasks also allow for automatic time recording that tracks and translates time worked on a task into a time card.

    3. (Optional) Configuring Field Service Work Configurations

      Customize the information captured on a work order task to better suite similar but different workflows. For example, maintenance and installations can have a fixed cost associated with them, but break-fix tasks may need to capture additional information related to the cost and duration of the task. With Field Service work configurations, you can set up these task types to capture specific information.

    4. (Optional) Configuring Planned Work Management

      Manage flexible work plans for any recurring activity that requires regular maintenance. For example, you can use planned Work management to schedule maintenance, inspections, or audits. You can install the Planned Work Management application (com.snc.fsm_planned_work_management) if you have the admin role.

    5. (Optional) Configuring the auto-population of access hours in a work order task

      Define default access hours for a work order task based on customer preferences such as account, location, or asset, enables the auto-population of the access hours for the task. For example, you can set the access hours for a business to guarantee that work order tasks are only assigned to the location when it’s open. You can activate the Field Service Management Access Hours Management plugin (com.snc.fsm_access_hours) for Field Service Management if you have the admin role.

    6. (Optional) Activate linear assets support in Field Service Management

      Enable effective management of assets like roads, telephone lines, or fiber cables. You can enable the Field Service Management application to support linear assets by activating the Enterprise Asset Management plugin (com.sn_eam) if you have the admin role.

    7. (Optional) Configuring Playbooks for Field Service Management

      Enable agents to manage the life cycle of work order tasks by guiding them through sequences of activities. Playbooks show detailed workflows associated with a specific type of work order task and the activities that must be completed to resolve that task.

    8. (Optional) Configuring Field Service Management Customer Experience

      Provide customers with timely updates about their reported issues, enabling them to track the location of agents and provide agent feedback. You can install the Field Service Management Customer Experience plugin (com.snc.fsm_customer_experience) if you have the wm_admin role.

    9. (Optional) Request task management

      Split requests into separate tasks. This can be helpful if you want to assign different parts of a task to different people, assign parts of a task to people in different locations, or schedule parts of a task to be completed at different times.

    10. (Optional) Configuring Field Service Quality Management

      Add the "Reviewer" role to Field Service Management. The reviewer can review tasks and provide feedback. You can install the Field Service Management plugin (com.sn_fsm_quality) if you have the wm_admin role.

    Note:
    As Field Service Management is built on ServiceNow Mobile Platform, its access is primarily role-driven. The roles are configured to be more flexible and less restrictive.
    Users with the wm_agent role can work with operational records and perform actions such as update certain task fields, record the task time, and cancel tasks even if they are not assigned to them, unless restricted by Access Control Lists (ACL) or query rules. To enforce stricter controls on the wm_agent role, you can:
    • Enforce access control at record and field levels. For more information, see Configure an ACL rule.
    • Apply pre-query filtering. For more information, see .
    • Apply dynamic filtering. For more information, see Before Query business rules.
    • Apply restrictions at the UI level. For more information, see .

    To enforce strict separation between different departments or to separate sensitive data, domain separation is recommended. It ensures data isolation, domain-specific access controls, and controlled data sharing.