Dynamics 365 Field Service Work Order Management Guide [2026]

Work order management in Dynamics 365 Field Service is built around a single record: the work order. A work order describes the work that needs to be done — an installation, a repair or preventive maintenance — and carries the customer, location, asset, tasks, parts and pricing needed to schedule and complete it. It is the object that connects a customer request to a dispatched technician and, ultimately, to an invoice (Microsoft Learn).

This guide explains what a work order is, how it moves through its lifecycle, what it contains, how the scheduling engine assigns it, and how technicians complete it in the field. Every claim is cited to Microsoft Learn. It is part of the Dynamics 365 Field Service hub, alongside the pricing and mobile app guides.

What a Work Order Is in Field Service

Microsoft defines a work order as the record that has information on what work needs to be done, used to coordinate and schedule resources and activities. Work orders can cover different types of work, including installations, repairs and preventive maintenance (Microsoft Learn).

The work order determines its location by looking first at a manually entered service address, then the address from the functional location if one is set, and then the service address from the account. That location is what routes the technician from job to job. Work orders can be grouped by geographical territory and line of business, and once created a work order is scheduled either manually, with the schedule assistant, or with the Resource Scheduling Optimization add-in (Microsoft Learn).

The Work Order Lifecycle

Field Service tracks a work order with system statuses, work order substatuses and booking statuses. Updating one can automatically update the others (Microsoft Learn).

The work order system statuses are:

• Unscheduled — the default status when a work order is created.
• Scheduled — a booking has been created for the work order.
• In Progress — work has started (for example, when the booking status changes to Travelling or In Progress).
• Completed — all related bookings are completed or cancelled.
• Posted — the back office has reviewed the work and started billing.
• Canceled.

Booking statuses live on the booking record and are updated by technicians on the mobile app: Scheduled, Travelling, In Progress, On Break, Completed and Canceled. The schedule board visualises booking statuses with a colour and icon so a dispatcher can see progress at a glance (Microsoft Learn).

Microsoft's default work order lifecycle runs through six stages: create, schedule, dispatch, service, review/approval, and invoice and inventory adjustment. A status change can automatically fill in data and trigger the next step — for example, when a technician changes the booking status to In Progress, the actual arrival time populates on the booking, and when a booking is completed, the work order's completed-on field updates (Microsoft Learn).

Work Order Components

A work order carries the detail that a technician and a dispatcher need:

• Customer and location — the service account, billing account, service address and territory.
• Asset — the customer asset being serviced, with its service history.
• Parts and services — the products and services to use or bill, drawn from a price list.
• Work order type and priority — which control defaults such as the process, duration and scheduling window.
• Service agreements — recurring or agreement-backed work that generates work orders automatically.

Work orders can be created manually, from a case, from an agreement, from an opportunity, automatically with Power Automate, or programmatically through the Dataverse Web API. Microsoft's guidance maps each creation scenario to the appropriate method (Microsoft Learn).

Scheduling & Dispatch

Field Service schedules work with Universal Resource Scheduling (URS), the scheduling solution shared across Dynamics 365 service applications. URS assigns resources to jobs and tasks based on availability, skills, promised time, business units, geographies and more (Microsoft Learn). It is the same engine used by Dynamics 365 Customer Service and Project Operations, and administrators can enable scheduling for other entities, including custom entities (Microsoft Learn).

In practice, scheduling happens in three ways:

• Manually — a dispatcher drags an unscheduled requirement onto a resource and time slot on the schedule board.
• Schedule assistant — a dispatcher selects a requirement and runs Find availability, and the assistant lists available, matching resources.
• Resource Scheduling Optimization — the add-in automatically finds and books the optimal resources, and can re-optimise a single resource's schedule after cancellations or emergency work.

The schedule board shows each resource — employee, contractor or equipment — and their scheduled work orders, with Gantt, list and map views. The map view shows resources, requirements and routes for a day, and travel time and work-hour calendars are part of the scheduling model (Microsoft Learn).

Mobile Completion

Technicians carry out the work from the Field Service mobile app. For each work order they can view the location, step-by-step instructions, customer assets and service history, then record what they did: capture photos and video, add notes with speech to text, record a customer signature, and generate a service report. Offline-by-default operation means the technician can keep working without connectivity and sync when back online (Microsoft Learn).

As the technician progresses, booking statuses update — Travelling, In Progress, On Break, Completed — and those changes flow back to the dispatcher's schedule board and to the work order's status (Microsoft Learn). See the Field Service mobile app guide for the full device and offline detail.

Incident Types & Service Agreements

Two Field Service features turn repeatable work into structured work orders:

• Incident types define the tasks, products, services and characteristics for a common type of job, so creating a work order for that incident populates the detail automatically (Microsoft Learn).
• Service agreements hold predefined details — customer, price list, date range and booking recurrence — that generate work orders automatically on a schedule. This is how preventive, agreement-based maintenance runs: the system creates work orders on a rolling basis, ahead of the service date, for a dispatcher to schedule (Microsoft Learn).

Reporting & KPIs

Field Service includes analytics for reporting on key performance indicators for managing work orders, scheduling activities and customer interactions. Service managers can track performance metrics and oversee service delivery. Because the work-order lifecycle populates fields such as actual arrival time, travel duration, total duration in progress and completed-on, those measures are available for reporting without manual calculation. Power BI can be layered on Dataverse for custom dashboards (Microsoft Learn).

Licensing

Work order management is part of the Dynamics 365 Field Service license, which Microsoft lists at $105 per user per month, paid yearly (Microsoft pricing). The Field Service Contractor edition at $50 per user per month includes essential work-order management for external technicians, limited to own-resource and manual scheduling (Dynamics 365 Licensing Guide, September 2026). See the Field Service pricing guide for entitlements and add-ons.

Pricing as of 2026-09-12. All prices USD, per user per month, paid yearly. Refresh trigger: the next Dynamics 365 release wave (Release Wave 2, October 2026) or any change to the Microsoft Field Service pricing page or the Dynamics 365 Licensing Guide.

Sources

• Create a work order (Microsoft Learn) — definition, location resolution and creation methods.
• Work order lifecycle and system statuses (Microsoft Learn) — system statuses, booking statuses and the six lifecycle stages.
• Use the schedule board (Microsoft Learn) — schedule board, schedule assistant and Resource Scheduling Optimization.
• Universal Resource Scheduling overview (Microsoft Learn) — resource matching criteria.
• Universal Resource Scheduling for Field Service (Microsoft Learn) — URS in the Field Service context.
• Set up customer agreements to generate work orders (Microsoft Learn) — agreement-generated work orders.
• Dynamics 365 Field Service overview (Microsoft Learn) — capabilities, roles and service-delivery models.
• Dynamics 365 Field Service pricing (Microsoft) — edition prices.