Last updated: November 19, 2026
By ZapAI Team
Dynamics 365 Field Service work orders are the record every visit, part, task and invoice hangs from. Our Dynamics 365 Field Service consultants design them for mid-market US service teams, and this guide covers the work order lifecycle, incident types, service tasks, inspections, assets, agreements, pricing, ERP integration and Copilot, checked against Microsoft Learn on November 19, 2026.
A Dynamics 365 Field Service work order moves through six system statuses, Unscheduled, Scheduled, In Progress, Completed, Posted and Canceled. Bookings drive most changes. Incident types prefill tasks, products, services, skills and duration.
Picture a hypothetical HVAC contractor with 40 technicians. Every work order says Repair. Durations are guesses. Half the invoices need manual fixes because nobody marked parts as used, and the dispatcher can’t tell a rooftop unit swap from a thermostat reset until someone phones the technician in the truck.
None of that is a software bug. It’s design debt. Our Dynamics 365 Field Service guide covers the product, plans and fit at a high level. This post sits one layer down, at the work order itself, where most of the long-term cost of a Field Service rollout is decided, long before anyone opens the schedule board or asks Copilot for a summary.
What Is a Work Order in Dynamics 365 Field Service?
It’s the job record. A work order says who the customer is, where the work happens, what’s wrong, which tasks to follow, which parts and labor to use, and what to bill.
Around it sit related records. Bookings put a technician on the calendar. Incidents describe the problem. Work order products, services and service tasks hold the detail, while customer assets and functional locations say exactly which piece of equipment needs attention and where on a large customer site it actually sits.
It’s a container with a status. Shape it well and everything downstream gets easier.
How Does the Work Order Lifecycle Work?
Six system statuses, set by Microsoft and not extendable. According to Microsoft’s work order lifecycle and system statuses page, updating one status can automatically update the others, and that chain reaction is the part teams underestimate.
| System status | What usually sets it | What it triggers |
|---|---|---|
| Unscheduled | Creation, or a canceled booking | Work waits on the schedule board |
| Scheduled | A booking is created | Booking status Scheduled, miles traveled calculated |
| In Progress | Booking moves to Traveling, In Progress or On Break | Arrival time, first arrived on, travel duration |
| Completed | All related bookings completed or canceled | Products flagged Convert to Customer Asset become assets |
| Posted | A back-office user, after review | Invoices for used lines, actuals, Closed By and Closed On |
| Canceled | A user cancels the job | Closed By and Closed On are set |
Booking statuses are a separate list. Out of the box you get Scheduled, Traveling, In Progress, On Break, Completed and Canceled, and technicians change them on the mobile app as they drive, arrive, pause and finish each visit. When a booking moves to Traveling, the work order jumps to In Progress. When the booking completes, Field Service writes booking journals, time entries, total cost and billable duration. Billing starts there.
Multiple bookings complicate things. One completed booking and one still scheduled leaves the work order In Progress. Only when every booking is completed or canceled does the work order turn Completed.
There’s a useful switch here. Each booking status has a Status completes work order toggle. Turn it off on a custom status like Partially Completed and finishing that booking drops the work order back to Unscheduled for a follow-up visit. Microsoft notes the change only affects future bookings.
The schedule board gets its own Field Service scheduling guide. Technician status updates live in our Field Service mobile guide.
Should You Customize System Statuses or Substatuses?
Substatuses. Always.
Microsoft says not to add, remove or edit the option set values for Work Order System Status. You may relabel them, and you may create Work Order Substatus records for the detail your process needs, each tied to one system status.
Good substatuses answer a dispatcher’s question. Waiting on Parts. Waiting on Customer Access. Quote Sent. Ready to Post. Each tells someone what to do next.
Bad ones duplicate the system status or describe the past. Scheduled Scheduled, anyone?
One more trap. Deactivating a work order doesn’t deactivate its products, services, time entries or actuals. Microsoft keeps them for history, so cleanup scripts need to touch each child record directly.
What Do Work Order Types Control?
Work order types categorize jobs, such as installation, preventive maintenance, inspection or repair, and they quietly control three settings that matter.
- Whether an incident type is required on the work order.
- Whether a service account is required, or whether context can come from a contact, functional location or project instead.
- A default price list for every work order of that type.
Service account is now optional per type. That’s newer behavior on Microsoft Learn, and it matters for internal facilities work and contact-centered service. Allow it only where you’ve already decided how the service address, billing context, tax setting, territory and price list get filled automatically when no account is there to supply them.
Keep types few. Five to eight covers most mid-market operations we see, because reports group by type and a list of thirty makes every dashboard unreadable.
How Should You Design Incident Types?
Treat them as templates. Microsoft’s incident types guide describes an incident type as the template that prefills a work order with products, services, service tasks, characteristics and an estimated duration, and the more detail you put in, the less your dispatchers type.
Duration math follows fixed rules. If service tasks carry durations, the incident type duration equals their sum, and you can only type a duration yourself when no task has one. A work order’s duration is the sum of its incidents, and the primary incident’s estimate feeds scheduling.
Take Microsoft’s own HVAC Annual Inspection example. Three tasks of 20, 30 and 30 minutes, plus a two-hour inspection service, put the work order estimate at three hours and twenty minutes.
Five rules from that same page catch teams out.
- Auto-population fails quietly if products are inactive, the price list doesn’t include them, or users lack Create privileges on work order product, service and service task tables.
- Multiple incidents on one work order make the schedule assistant look for one resource who can do all of them.
- Jobs that need two people belong in a requirement group template, and then the work order can carry only one incident.
- Characteristics go on the requirement group template in that case, not on the incident type.
- Changing an incident type means removing its products, services and tasks, then deleting the Work Order Incident record and adding a new one.
Agreements add a choice. Copy Incident Items to Agreement set to Yes freezes the scope for contractual work. Set to No, agreement work orders follow your latest procedure.
Here’s how we’d sketch the patterns. The examples are hypothetical, for an HVAC and building services company.
| Pattern | Hypothetical example | Best for | Watch out for |
|---|---|---|---|
| Job package | Annual PM, rooftop unit up to 10 tons | Agreements and repeatable visits | Split by size class or durations lie |
| Symptom first | No cooling, rooftop unit | Reactive calls from cases | One type per symptom explodes the list fast |
| Inspection led | Backflow preventer test | Compliance work with recorded answers | Republish when codes change |
| Install and commission | New split system install | Jobs that create customer assets | Products need Convert to Customer Asset set |
| Diagnose and quote | Diagnostic visit, unknown fault | Calls where nobody knows the cause yet | Short duration, no parts, then a follow-up work order |
Which pattern wins? Mix them. Most of the volume should sit in job packages and symptom types, with diagnose and quote as the safety valve.

When Should You Use Inspections Instead of Service Tasks?
Use service tasks for steps. Use inspections for answers you’ll report on.
Per Microsoft’s inspections overview, inspections are drag-and-drop forms technicians fill out on the work order, offline if needed, with versioning, asset history and answers stored in Dataverse. An admin publishes the inspection, which ties it to a service task type, and that task type rides along on incident types.
Analytics needs a switch. In Field Service Settings, on the Inspection tab, you turn analytics on and pick a frequency of daily, immediately on completion, or a custom interval between one and 365 days. Responses then get parsed into Dataverse tables you can report on.
Copilot can draft inspections too. The Copilot inspection builder converts up to three images or PDFs of up to three pages into a draft template. It’s labeled preview, isn’t available in environments hosted in the United Kingdom and Italy, and needs Field Service version 8.8.142.320 or later. Test it first.
How Do Customer Assets and Functional Locations Fit?
Assets are the what. Functional locations are the where.
Customer assets hold the equipment you service, with parent and child components, so a compressor sits under its rooftop unit. A work order’s Primary Asset lookup only shows assets tied to the service account by default, which keeps technicians from picking a neighbor’s chiller.
Functional locations build a site tree. Microsoft’s functional locations page uses a printer on the third floor of Building A on a campus as its example. You can set a different functional location on each work order incident, so one visit can cover two buildings.
Fallbacks matter. With no functional location, Field Service uses the service address on the work order, and failing that, the address of the contact who reported the issue.
Mobile has limits. Technicians need an internet connection to browse asset and location trees, and filtering functional locations by service account isn’t supported in the offline-enabled app. Plan for that if your techs work in basements.
Install jobs feed the asset list automatically. When a work order completes, any work order product whose product record says Convert to Customer Asset becomes a new customer asset, which is the cleanest way to keep the installed base current without a data entry clerk.
How Do Agreements Generate Preventive Maintenance Work Orders?
Agreements create recurring work orders and invoices from a schedule. Quarterly elevator checks. Weekly pest control. Annual HVAC tune-ups.
Each agreement has two halves. Booking setups define recurring work, with a recurrence pattern, an auto generate option, and agreement booking incidents that point at incident types, assets and functional locations. Invoice setups define recurring billing for fixed products and services. Agreements start in Estimate and generate nothing until they’re Active.
Microsoft’s customer agreements overview adds rules worth printing.
- One agreement covers one location, the service account. Different sites need different agreements.
- Several incidents in one booking setup make one work order. Several booking setups make several work orders.
- Agreement work orders still create invoices at Posted, even when the agreement bills on its own invoice setup.
That third rule bites. If the agreement invoice is the real bill, you need a process to deactivate the work order invoices, or price lists and entitlements that bring the work order subtotal to zero. Otherwise customers get billed twice.
Field Service Settings decide how far ahead the system generates booking dates and invoice dates. Long horizons look tidy. They also mean a change to the incident type won’t reach work orders that already exist.
Manufacturers weighing service against ERP-native options should also read Dynamics 365 for manufacturing.

Where Do Work Orders Come From?
Four main doors, plus manual entry.
| Source | How it works | Design note |
|---|---|---|
| Manual | A dispatcher or technician creates the work order | Require a work order type and, where it fits, an incident type |
| Case | Case to Work Order business process flow | Set the incident type on the case first |
| Agreement | Booking setup with auto generate on | Watch generation horizons and double billing |
| IoT alert | Connected Field Service alert, then case, then work order | Tune alert rules before anyone trusts them |
Per Microsoft’s create a work order from a case page, you need the Case to Work Order business process flow enabled and a Field Service Dispatcher or Administrator role. The case’s incident type becomes the primary incident type, its description becomes the work order instructions, and its functional location carries over. Our Dynamics 365 case management guide covers the case side.
IoT alerts still work. Microsoft’s IoT alerts page, updated July 2026, describes Azure IoT Hub and Stream Analytics rules creating alerts, then a business process flow that creates a case and, if remote fixes fail, a work order. Similar alerts for one device within five minutes get grouped under a parent by default. We found no 2026 deprecation notice, though the older IoT alert suggestions feature was removed after November 2024.
Email is the door that closed. Microsoft’s Field Service deprecations page lists the Outlook add-in, the Teams app, Viva Connections and Planner integrations as unsupported after October 30, 2025, which quietly took the Copilot feature that drafted a work order from an email with it. We found no direct replacement.
How Are Work Orders Priced and Posted?
Price lists set the base price. Field Service price list items add rules. Entitlements adjust last.
Microsoft’s price list guide says the work order price list comes from the billing account unless someone picks one, and it applies to every product and service line. Field Service price list items handle duration rounding, flat fees, minimum charge durations and minimum charge amounts. When rules overlap, those items beat the base price, and entitlements apply on top. Order matters.
Line status does the work. A new work order product or service starts as Estimated. The technician flips it to Used and enters quantity, or duration for services, plus the amount to bill. Only Used lines reach the invoice when the work order is Posted.
Posting creates actuals for time and cost, and sales actuals after the invoice is confirmed, while completed bookings add a travel charge line when the service account has a travel charge type. Inventory allocation for work order products is off by default, so decide early whether trucks are tracked as warehouses.
Small detail, big effect. A product missing from the price list falls back to the list price on the product record, which is how a filter with no list price ends up billed at zero.
How Do Work Orders Reach Business Central or Finance?
Business Central uses a Microsoft integration app. Finance is moving to a Project Operations route.
For Business Central, Microsoft’s Field Service integration guide describes two modes. Project mode syncs work order products and services to project journals. Project and Service mode also maps work orders to service orders, incidents to service item lines, and customer assets to service items, and it requires the Business Central Premium experience. The integration needs a Dataverse connection and Sales integration first, which our Business Central and Sales integration post explains.
Three Field Service settings change once Business Central owns billing. Turn off Calculate Price and Calculate Cost, and set Work Order Invoice Creation to Never. Canceled work orders don’t sync, so someone has to align them by hand. Item availability by location shows up through a virtual table, a pattern we compare in dual-write vs virtual tables.
Finance customers face a date. The deprecations page says the Field Service integration with finance and operations apps won’t be available after February 28, 2027, and it’s moving to the Field Service and Project Operations integration. In that model, each work order links to a project, Used lines become material usage logs, approved journal lines become project actuals, and Finance posts the invoice. Only the user who installs it needs a Project Operations license when you run Field Service with Finance and Supply Chain Management but skip Project Operations itself. Plan for it now.
Still choosing the ERP? Our Business Central vs Dynamics 365 Finance comparison and Project Operations guide cover the trade-offs, and the Dynamics 365 overview maps the wider product family.
What Can Copilot Do With Work Orders in November 2026?
Summaries, updates and inspection drafts, mostly. The status labels differ, so read the table before promising anything to technicians.
| Feature | What it does | Status we found on November 19, 2026 |
|---|---|---|
| Work order summary | On-demand summary on the work order or booking, tuned to the lifecycle stage | How-to page updated November 3, 2026, no preview label. Admin must enable |
| AI-powered work order update | Technician describes work by text or speech, Copilot proposes field changes | Preview, new mobile experience only, page updated November 17, 2026 |
| Inspection template creation | Turns images or PDFs into draft inspections | Preview, not in UK or Italy environments |
| Create work order from email | Lived in the Outlook add-in | Add-in unsupported after October 30, 2025 |
Summaries have quirks. Microsoft says a summary isn’t saved and is visible only to the user who generated it. Unscheduled work orders get scheduling detail, in-progress ones get asset history, and posted ones get costs, prices and invoice details. That makes summaries a briefing tool, not a record.
Updates are the one technicians will notice. Per the Copilot features page, the update feature can change booking status, booking times, task completion, product quantity and line status, and service duration and line status, after the tech confirms. It needs a paid environment and a connection. Offline, it’s gone.
Billing splits in two. Microsoft’s Field Service pricing page lists the Field Service plan at $105 per user per month with Copilot assistance for work order creation and updates, scheduling and summarization included, while the $50 Contractor plan excludes Copilot and planned maintenance. Agents are different. They need Copilot Credits and an Azure subscription, and the page shows the Scheduling Operations Agent as preview.
Ignite 2026 runs November 17 to 20. As of November 19 we found no indexed Field Service announcements we could verify, so we’ll refresh this section after the event. For other Copilot features worth switching on, see Copilot in Dynamics 365 use cases.

What Mistakes Break Work Order Design?
Eight, in our experience.
- Editing system status values instead of adding substatuses.
- Hundreds of incident types, half never used.
- Typed durations nobody revisits after go-live.
- Products missing from the price list, so lines bill at zero or list price.
- Agreement invoices plus work order invoices for the same visit.
- Assets loaded without functional locations at multi-building sites.
- Business Central or Finance turned on without switching off Field Service invoice creation.
- Custom plug-ins that set statuses directly and fight the booking logic.
The last one deserves a second look. Our CRM customization best practices explain why we route status logic through configuration before code.
What Belongs on a Work Order Setup Checklist?
Twelve steps, roughly in order.
- Confirm licenses, Field Service versus Contractor, plus Copilot Credits if agents are in scope.
- Pick the ERP path, Business Central, Finance through Project Operations, or Field Service invoicing.
- Define five to eight work order types with incident and service account rules.
- Write substatuses for each system status, with plain descriptions.
- Create custom booking statuses and set Status completes work order on each.
- Load products, services and price lists, then Field Service price list items.
- Build service task types and inspections, then attach them.
- Build incident types with tasks, products, services, characteristics and durations.
- Load functional locations, then customer assets, per service account.
- Set up agreements in Estimate, check generated dates, then activate.
- Enable Copilot summaries and test previews in a sandbox first.
- Run a full job end to end as a dispatcher, technician and billing user.
ZapAI Decision Rules for Work Orders
These are our practice opinions, not Microsoft guidance. Treat them as defaults. Adjust to your data.
| Situation | Our rule |
|---|---|
| Incident type count | Start with the 20 to 40 jobs that make up most of last year’s volume. Add more only when a dispatcher asks twice |
| Durations | Compare estimated against actual booking durations every quarter and update the worst ten |
| Substatuses | No more than four per system status |
| Follow-up visits | A custom booking status with Status completes work order off, not a new work order |
| Two-person jobs | Requirement group template with one incident |
| Agreement billing | Agreement invoice setup plus a zero-price list on agreement work orders |
| Compliance answers | Inspections with analytics on, never free-text notes |
One rule tops the rest. If a technician can’t tell from the work order what to do, what to use and where to go, the design isn’t finished.
Wrapping Up
Work orders reward boring discipline. Leave system statuses alone, write meaningful substatuses, build incident types as real templates, attach inspections where answers matter, and settle billing ownership before agreements start generating jobs. Copilot then has clean data to summarize, and technicians get a work order they can trust when they open the app in a parking lot at seven in the morning.
ZapAI is a Microsoft Dynamics 365, Power Platform, Fabric and AI consulting firm in Irving, Texas, working with businesses across Dallas-Fort Worth and nationwide. Want a second opinion on yours? Ask for a work order design review, and we’ll walk through your statuses, incident types and billing flow with you.
Questions Field Service Leaders Ask About Work Orders
Can I add a custom work order system status?
No. Microsoft says not to add, remove or edit the system status values, though you can relabel them. Create Work Order Substatus records for the extra detail your team needs.
Why did my work order jump back to Unscheduled?
Usually a canceled booking. A single booking set to Canceled returns the work order to Unscheduled, and so does completing a booking whose status has Status completes work order turned off.
Does completing a booking always complete the work order?
Only when every related booking is completed or canceled, and only for booking statuses with the toggle on. Otherwise the work order stays In Progress or returns to an earlier status.
How do I change the incident type on an existing work order?
Remove the products, services and service tasks it added, delete the Work Order Incident record, then add a new incident with the correct type.
Can Copilot still create work orders from Outlook emails?
Not through the Field Service Outlook add-in. Microsoft lists that add-in as unsupported after October 30, 2025, and we found no direct replacement as of November 19, 2026.
Do agreement work orders create their own invoices?
Yes, when they’re Posted, even if the agreement bills through an invoice setup. Deactivate those invoices or price agreement work orders at zero to avoid double billing.
Is Copilot included in the Field Service license?
Copilot assistance is listed in the $105 Field Service plan but not the Contractor plan. Agents, including the Scheduling Operations Agent in preview, need Copilot Credits and an Azure subscription.
